
From nobody Mon Feb  1 04:17:28 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 4E1D43A10B1 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 04:17:27 -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 QXzj0TlZq2dF for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 04:17:25 -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 8BDB13A10C0 for <dmarc@ietf.org>; Mon,  1 Feb 2021 04:17:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612181842; bh=iSBsFUriFBDcjTh1hxbycyi3vLDpxcDtouFwnBAQiz4=; l=4134; h=To:References:From:Date:In-Reply-To; b=BIItaW7wWO5gc5+sQcqW8YgyQiMegINRnkfoPuC0xyzUMc3f9HHvSdVLV+7K23qRg OEsm3gEi/5IXvc/Ub9yt2uCEpas0NlyYC+vs1GKeubGZJqjUWw1EQj4VAaphR5RlqP vFyf8+LCvzbxvkV1UWvlWLfri9ONQx85HqM6UvfevFMjo8rN9cDKuh/0t5ihG
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.000000006017F151.00001D7A; Mon, 01 Feb 2021 13:17:21 +0100
To: dmarc@ietf.org
References: <20210130212339.447316D04763@ary.qy> <36a1c70-875d-89c8-7e95-a32324654275@taugh.com> <CAH48ZfwBKyA-TwSrr2422zmMO8wr1CKf2MiQZ3KvQu2hOH=_CA@mail.gmail.com> <1654196.ygyh55z74P@zini-1880>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <babf1538-5172-f101-d5e4-c4fa33dea495@tana.it>
Date: Mon, 1 Feb 2021 13:17:20 +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: <1654196.ygyh55z74P@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/NBCIF05Wd47EU0-oz4dLW3TZUTk>
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 12:17:27 -0000

On Mon 01/Feb/2021 01:10:01 +0100 Scott Kitterman wrote:
> 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.


Perhaps Courier-MTA is not so properly implemented, but when mail from is empty 
it just omits the corresponding Received-SPF: header field.

OTOH, properly implemented SPF verifiers could skip producing a Mail From 
result if the helo identity was verified successfully.

In conclusion, the idiosyncratic requirement can hardly be implemented.


> 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.


It makes sense to add a section that modifies RFC 7208.  See below.

On Sun 31/Jan/2021 03:27:41 +0100 Douglas Foster wrote:
> My data, cited previously, indicates that HELO can be useful for both
> blacklisting and whitelisting.   It should not be ignored.


>> 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.


Does that mean that an implementation that uses the RFC5321.HELO identity 
without taking care of whether RFC5321.MailFrom is empty is *atypical*?

Please note that all the text occurring before that paragraph would suggest 
that any authenticated domain, if aligned, would do.  The quoted paragraph 
comes as a note, by surprise, without bringing any rationale.  That text needs 
to be revised whether or not we remove the idiosyncrasy.

And the only rationale learnt in this thread is that one could type whatever it 
wants in the helo/ehlo command, as if that weren't true for the whole SMTP session.


>>> 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.


"Postmaster" is necessary, because SPF mechanisms can refer to the local part.

The SPF part I'd modify, however, is Section 2.3, where it says:

                                If a conclusive determination about the
    message can be made based on a check of "HELO", then the use of DNS
    resources to process the typically more complex "MAIL FROM" can be
    avoided.

I'd append to that sentence:

           , unless downstream filters need it anyway.

Since we're at it, that paragraph continues with the following sentence:

             Additionally, since SPF records published for "HELO"
    identities refer to a single host, when available, they are a very
    reliable source of host authorization status.

Isn't that the exact opposite of what many of us are claiming?  And is it legit 
for a proposed standard to quietly counter an existing proposed standard 
without some kind of rationale?


>>> 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.


OTOH, relaxing the requirement that the SPF HELO identity be used only when 
MAIL FROM is empty brings no incompatibility.  It's just a cleanup.


Best
Ale
-- 





























From nobody Mon Feb  1 04:32: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 11E7B3A10E7 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 04:32:15 -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 tOJ9QkyWCYuq for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 04:32:13 -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 82EF43A10E6 for <dmarc@ietf.org>; Mon,  1 Feb 2021 04:32:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612182730; bh=mC4uDVnSHH6RXlxZG1LUJ8SEP3AYz8w2fAvopj1Pjp4=; l=1403; h=To:References:From:Date:In-Reply-To; b=A9Yi0mdGyyJiHx2KGvx4I3htWVDS6qcCEYdYVS/1XWW4VS4Te2IiXaVAJ39jyqPyh wJ/PRDXok4ExDXgLFobYQ3gBlgKMpG0+e5v5jwcs+lqA6N5LzKbZN5bZovmnnTgFKc cZzTgHvap1PmXpMLXB9NdbdvJvYuA5tuo7cW1N1M1NVf45sU/JSg6Njx9oXEV
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.000000006017F4CA.00001EF4; Mon, 01 Feb 2021 13:32:10 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210131200238.931356D11D79@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <e7e27e1f-b6e6-96b6-e12e-672084562b8a@tana.it>
Date: Mon, 1 Feb 2021 13:32: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: <20210131200238.931356D11D79@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/-x3JwSPLwbcyUAle-THvBluwwzU>
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: Mon, 01 Feb 2021 12:32:15 -0000

On Sun 31/Jan/2021 21:02:38 +0100 John Levine wrote:
> 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.


True, it's not worth suggesting a super duper rate limiting.

Committed text:


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.

    Reporters SHOULD rate limit the number of failure reports sent to any
    recipient to avoid overloading recipient systems.


Not MUST?

Best
Ale
-- 






















From nobody Mon Feb  1 06:26: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 817CC3A11C4 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 06:26: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 tzHZg0hekxc5 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 06:26:49 -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 652003A11C3 for <dmarc@ietf.org>; Mon,  1 Feb 2021 06:26:49 -0800 (PST)
Received: by mail-vs1-xe34.google.com with SMTP id 186so9146128vsz.13 for <dmarc@ietf.org>; Mon, 01 Feb 2021 06:26: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=gnU3ObnLvQoWRRKc2Xo+9KWU8Q3X+eH15csawGYoWiU=; b=d1UthBtf5pLui0YwXzH+Gj44L9t8C3TL3PObYaQkU1F+ZYgTkkyyi6zmsxCK+yvU8t hu/JmCLbxR9CLDDuZMSALeylLyB/IV9LWA/+8Y1DZHObOr889ppz2lfwk8WteF1tkpT8 IlLCsJN6+ul4WU+HCZPwcwxAridjnm157F/Ni28c46CzXjZ+dDtCHBdOaRt5Yd9OdpwP HWV4FOyC9QlctH2rqdsku7aL4zd3ZDDG32JUAfbEAgA95JfTXAIBJRvYSj3R3kU4XB93 fPcsyd20ZmpEobt43I+cG9LROCdsEmLFzJGJIRnEED/0nUVbI7Pb6EyW6lagDK62XsIo aXcA==
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=gnU3ObnLvQoWRRKc2Xo+9KWU8Q3X+eH15csawGYoWiU=; b=EWdDYnyahmwQCRB+GJ9nGoAbmQqf8J9sdkIWVdOUDylaT4PmuHcaaTjLI1imLLqrlu +wXjvkVRGLecf+tn/xfwZghGkpRIFaFx0WCT01hHgJsMRT6KXhR5Ya5e4h23ow/PLsmE yzWcHWdKyfJFQfiaCPBjdaLVJEQ2vfiev/FAQdP9Xl+6udohiiHXKBKCNmNZDDZv81K2 CxKdMG0VV5CJsbYp6egUo+oyxSqW591UxdDk5CliowMYi9FttWuoYb7ZQ8EEj47yLKED pIj5n4HYz7IvoczDKi9lPSAuAl9U5zZkhWkd9isWq0LVDJ1gOg4C0MpQIL2/1XlzpFL9 9cLw==
X-Gm-Message-State: AOAM533jE+d52RBJKGw/VCyQTwXPCUW9xm+Pz/SArSm1NpSt1NSsB/qt lXHiO9BvgZqH/3ZBY8e6WJU174ktFW2kh+UmYWDVwjlqBgg=
X-Google-Smtp-Source: ABdhPJyEWB9oHUh2eDqvvTxsgYUkr7RBDt8Y85J7CKkNoR0W2vtCDseZBtniFxnhIyVfo/5cG3qNBK7srhojOmL3eqg=
X-Received: by 2002:a67:24c5:: with SMTP id k188mr9207102vsk.16.1612189608161;  Mon, 01 Feb 2021 06:26:48 -0800 (PST)
MIME-Version: 1.0
References: <20210130212339.447316D04763@ary.qy> <36a1c70-875d-89c8-7e95-a32324654275@taugh.com> <CAH48ZfwBKyA-TwSrr2422zmMO8wr1CKf2MiQZ3KvQu2hOH=_CA@mail.gmail.com> <1654196.ygyh55z74P@zini-1880> <babf1538-5172-f101-d5e4-c4fa33dea495@tana.it>
In-Reply-To: <babf1538-5172-f101-d5e4-c4fa33dea495@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 1 Feb 2021 09:26:37 -0500
Message-ID: <CAH48ZfzAEhxSgS=VZtsp-xdWMzKq0Zow7DyCALq=qvMAv8_mEQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e7b5b505ba4724c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/eE2uTHmP-BIZ2zAmDOVDMZOf5S8>
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 14:26:52 -0000

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

An SPF check on MailFrom says that this host has permission to send on this
particular SMTP mail domain, and From alignment with that this SMTP mail
domain has permission to send on behalf of that same domain.

If Helo aligns with From, it says that the mail server has permission to
send on behalf of the From domain, but it does not justify using a
different domain in the SMTP address.   If the SMTP address is null, this
is not a problem.   If it is not null and is different from the HELO
domain, we have permitted domain abuse.



On Mon, Feb 1, 2021 at 7:17 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Mon 01/Feb/2021 01:10:01 +0100 Scott Kitterman wrote:
> > 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.
>
>
> Perhaps Courier-MTA is not so properly implemented, but when mail from is
> empty
> it just omits the corresponding Received-SPF: header field.
>
> OTOH, properly implemented SPF verifiers could skip producing a Mail From
> result if the helo identity was verified successfully.
>
> In conclusion, the idiosyncratic requirement can hardly be implemented.
>
>
> > 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.
>
>
> It makes sense to add a section that modifies RFC 7208.  See below.
>
> On Sun 31/Jan/2021 03:27:41 +0100 Douglas Foster wrote:
> > My data, cited previously, indicates that HELO can be useful for both
> > blacklisting and whitelisting.   It should not be ignored.
>
>
> >> 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.
>
>
> Does that mean that an implementation that uses the RFC5321.HELO identity
> without taking care of whether RFC5321.MailFrom is empty is *atypical*?
>
> Please note that all the text occurring before that paragraph would
> suggest
> that any authenticated domain, if aligned, would do.  The quoted paragraph
> comes as a note, by surprise, without bringing any rationale.  That text
> needs
> to be revised whether or not we remove the idiosyncrasy.
>
> And the only rationale learnt in this thread is that one could type
> whatever it
> wants in the helo/ehlo command, as if that weren't true for the whole SMTP
> session.
>
>
> >>> 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.
>
>
> "Postmaster" is necessary, because SPF mechanisms can refer to the local
> part.
>
> The SPF part I'd modify, however, is Section 2.3, where it says:
>
>                                 If a conclusive determination about the
>     message can be made based on a check of "HELO", then the use of DNS
>     resources to process the typically more complex "MAIL FROM" can be
>     avoided.
>
> I'd append to that sentence:
>
>            , unless downstream filters need it anyway.
>
> Since we're at it, that paragraph continues with the following sentence:
>
>              Additionally, since SPF records published for "HELO"
>     identities refer to a single host, when available, they are a very
>     reliable source of host authorization status.
>
> Isn't that the exact opposite of what many of us are claiming?  And is it
> legit
> for a proposed standard to quietly counter an existing proposed standard
> without some kind of rationale?
>
>
> >>> 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.
>
>
> OTOH, relaxing the requirement that the SPF HELO identity be used only
> when
> MAIL FROM is empty brings no incompatibility.  It's just a cleanup.
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr">An SPF check on MailFrom says that this host has permissio=
n to send on this particular SMTP mail domain, and From alignment with that=
 this SMTP mail domain has permission to send on behalf of that same domain=
.=C2=A0 =C2=A0=C2=A0<div><br></div><div>If Helo aligns with=C2=A0From, it s=
ays that the mail server has permission to send on behalf of the From domai=
n, but it does not justify using a different domain in the SMTP address.=C2=
=A0 =C2=A0If the SMTP address is null, this is not a problem.=C2=A0 =C2=A0I=
f it is not null and is different from the HELO domain, we have permitted d=
omain abuse.</div><div><br></div><div><br></div><div></div></div><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Feb 1, 2=
021 at 7:17 AM Alessandro Vesely &lt;<a href=3D"mailto:vesely@tana.it">vese=
ly@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 Mon 01/Feb/2021 01:10:01 +0100 Scott Kitterman wrote:<br>
&gt; I think that we&#39;re well past learning anything new in this thread.=
<br>
&gt; <br>
&gt; SPF is what it is (RFC 7208).=C2=A0 DMARC doesn&#39;t need to re-inven=
t the protocol<br>
&gt; (and shouldn&#39;t).=C2=A0 For any properly implemented SPF verifier, =
DMARC should be<br>
&gt; able to consume the Mail From result.<br>
<br>
<br>
Perhaps Courier-MTA is not so properly implemented, but when mail from is e=
mpty <br>
it just omits the corresponding Received-SPF: header field.<br>
<br>
OTOH, properly implemented SPF verifiers could skip producing a Mail From <=
br>
result if the helo identity was verified successfully.<br>
<br>
In conclusion, the idiosyncratic requirement can hardly be implemented.<br>
<br>
<br>
&gt; On Sunday, January 31, 2021 2:03:45 PM EST Douglas Foster wrote:<br>
&gt;&gt; I don&#39;t see any justification for using HELO unless the SMTP a=
ddress is<br>
&gt;&gt; null.=C2=A0 If the SPF RFC says otherwise, this should be correcte=
d.<br>
<br>
<br>
It makes sense to add a section that modifies RFC 7208.=C2=A0 See below.<br=
>
<br>
On Sun 31/Jan/2021 03:27:41 +0100 Douglas Foster wrote:<br>
&gt; My data, cited previously, indicates that HELO can be useful for both<=
br>
&gt; blacklisting and whitelisting.=C2=A0 =C2=A0It should not be ignored.<b=
r>
<br>
<br>
&gt;&gt; On Sun, Jan 31, 2021 at 11:52 AM John R Levine &lt;<a href=3D"mail=
to:johnl@taugh.com" target=3D"_blank">johnl@taugh.com</a>&gt; wrote:<br>
&gt;&gt;&gt; On Sun, 31 Jan 2021, Alessandro Vesely wrote:<br>
&gt;&gt;&gt;&gt; One way to interpret RFC 7489 is that you can put dmarc=3D=
pass based on <br>
&gt;&gt;&gt;&gt; the helo identity *only if* MAIL FROM is null. &gt;&gt;&gt=
;<br>
&gt;&gt;&gt; That would be consistent with 7489.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Sec 3.1.2 says<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0Note that the RFC5321.HELO identity is not =
typically used in the<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0context of DMARC (except when required to &=
quot;fake&quot; an otherwise null<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0reverse-path), even though a &quot;pure SPF=
&quot; implementation according to<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0[SPF] would check that identifier.<br>
<br>
<br>
Does that mean that an implementation that uses the RFC5321.HELO identity <=
br>
without taking care of whether RFC5321.MailFrom is empty is *atypical*?<br>
<br>
Please note that all the text occurring before that paragraph would suggest=
 <br>
that any authenticated domain, if aligned, would do.=C2=A0 The quoted parag=
raph <br>
comes as a note, by surprise, without bringing any rationale.=C2=A0 That te=
xt needs <br>
to be revised whether or not we remove the idiosyncrasy.<br>
<br>
And the only rationale learnt in this thread is that one could type whateve=
r it <br>
wants in the helo/ehlo command, as if that weren&#39;t true for the whole S=
MTP session.<br>
<br>
<br>
&gt;&gt;&gt; But then 4.1 says<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0o=C2=A0 [SPF], which can authenticate both =
the domain found in an [SMTP]<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 HELO/EHLO command (the HELO identit=
y) and the domain found in an<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 SMTP MAIL command (the MAIL FROM id=
entity).=C2=A0 DMARC uses the result<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 of SPF authentication of the MAIL F=
ROM identity.=C2=A0 Section 2.4 of<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 [SPF] describes MAIL FROM processin=
g for cases in which the MAIL<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 command has a null path.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; That section of 7208 says that if there&#39;s a null bounce ad=
dress, SPF<br>
&gt;&gt;&gt; pretends that the MAIL FROM was postmaster@HELO.<br>
<br>
<br>
&quot;Postmaster&quot; is necessary, because SPF mechanisms can refer to th=
e local part.<br>
<br>
The SPF part I&#39;d modify, however, is Section 2.3, where it says:<br>
<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 =C2=A0 =C2=A0 =C2=A0 =C2=A0 If a conclusive determination about =
the<br>
=C2=A0 =C2=A0 message can be made based on a check of &quot;HELO&quot;, the=
n the use of DNS<br>
=C2=A0 =C2=A0 resources to process the typically more complex &quot;MAIL FR=
OM&quot; can be<br>
=C2=A0 =C2=A0 avoided.<br>
<br>
I&#39;d append to that sentence:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0, unless downstream filters need i=
t anyway.<br>
<br>
Since we&#39;re at it, that paragraph continues with the following sentence=
:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Additionally, since SPF rec=
ords published for &quot;HELO&quot;<br>
=C2=A0 =C2=A0 identities refer to a single host, when available, they are a=
 very<br>
=C2=A0 =C2=A0 reliable source of host authorization status.<br>
<br>
Isn&#39;t that the exact opposite of what many of us are claiming?=C2=A0 An=
d is it legit <br>
for a proposed standard to quietly counter an existing proposed standard <b=
r>
without some kind of rationale?<br>
<br>
<br>
&gt;&gt;&gt; If we want, we can say not to use the SPF HELO identity, but t=
hat would be<br>
&gt;&gt;&gt; an incompatible change to 7489 and I suspect would not match w=
hat most<br>
&gt;&gt;&gt; DMARC checking code does.<br>
<br>
<br>
OTOH, relaxing the requirement that the SPF HELO identity be used only when=
 <br>
MAIL FROM is empty brings no incompatibility.=C2=A0 It&#39;s just a cleanup=
.<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>
<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>

--000000000000e7b5b505ba4724c0--


From nobody Mon Feb  1 07:12:12 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 4044B3A1203 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 07:12:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, SPOOF_COM2OTH=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 ctyAz1o2yoW6 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 07:12:09 -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 46A6E3A11FE for <dmarc@ietf.org>; Mon,  1 Feb 2021 07:12:09 -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 111EuJ1Z020270 for <dmarc@ietf.org>; Mon, 1 Feb 2021 10:12:08 -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=spSEp/3vYT0oGO8ifyQCdexYTFgYek8fVIEKAy044mM=; b=fye7/igOknCrGa5CzVKHpLGp4g2ImH/DSUuKgLUtKMAGUa6ZxFxitSC/n4vNOT1m6BGD S5DQtcY8AaTocGWpZxEIKhayFPcrJrZhPJ7gOG1V7Kfv83Gfkk8GIj/ywRDaluCq/Ri/ XXmKl51SLXcgs1VBHLU/EB7inrUMAxwuVsu89pKPP2iA0FHOhkh+uj3zVcEI6BrVV5D3 y1u44Ntn6+Yc/KVYP/BqqmbG8V1mFj9C/UeeHocSba8fCP+PjICq5ylEeJSSxFPsT7P0 ySuA7pDP8TKANyvJieCM4nFyRiC9QHp5tcgSZnuSyn4efK8bDHNr+DoI5wtVLbB/lUTH +Q== 
Received: from pacdcex56.cable.comcast.com (dlppfpt-wc-1p.slb.comcast.com [96.99.226.136]) by mx0a-00143702.pphosted.com with ESMTP id 36d3nqawy4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Mon, 01 Feb 2021 10:12:07 -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, 1 Feb 2021 10:12:05 -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, 1 Feb 2021 10:12:05 -0500
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (104.47.66.47) by webmail.comcast.com (76.96.78.71) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Feb 2021 10:11:55 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by MN2PR11MB4224.namprd11.prod.outlook.com (2603:10b6:208:18f::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3805.24; Mon, 1 Feb 2021 15:11:51 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::2495:cfaf:88ca:6b2d]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::2495:cfaf:88ca:6b2d%7]) with mapi id 15.20.3805.027; Mon, 1 Feb 2021 15:11:51 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: DMARC IETF <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Discussion: Removal of validation for external destinations (Ticket #76)
Thread-Index: AdbLDJ36lgBe/Aa+SKaTRhc/gVa6SQAu5JsAAEfomQAK8RXdIA==
Date: Mon, 1 Feb 2021 15:11:51 +0000
Message-ID: <MN2PR11MB4351895D112A3C903F9A5271F7B69@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <MN2PR11MB4351D62302C7357DE653F8B4F7F00@MN2PR11MB4351.namprd11.prod.outlook.com> <fc1d9d7c-4e14-78af-0416-b6cfb0873468@tana.it> <0359b009-5b18-46f8-85a5-959ad337dd49@beta.fastmail.com>
In-Reply-To: <0359b009-5b18-46f8-85a5-959ad337dd49@beta.fastmail.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:6089:8838:a37e:a0bc]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4fcab91e-9ae7-4467-8602-08d8c6c3b410
x-ms-traffictypediagnostic: MN2PR11MB4224:
x-microsoft-antispam-prvs: <MN2PR11MB422469E06E1AAA4239FFF74FF7B69@MN2PR11MB4224.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: dDlrDuGFRUdO/36MK66oYmpD6/wC9qfmSjVEGWj8OMrcJ8DcmC8NTXq04XTGuMQo+xvKQVWei+kTz6R/Yw4LlcsmAs6VdfH59q5dZe+Hm3HJcMxmqzIadlggSHKfpwGpl8aJ8AxPWhAqci5VzmVUIPCHQzCSOQ3XY5JXKd1UDSN6BzEBl5aLYAi/V6FhxaHbdVWe1KLxpxZIfoa2QCCO7SwyoWl2WWB2NDV3kMi7F3cTwFsyljwLejPsNfDdbGsEojAuz+XyjNol8gPNznzvv8Wx1P1G0H7ckr6Z5x+iQmJ6YcRU8JNVyk9lghAqZo7rwevqaIHn/g6KLgrBoHVhNhxDpG61yAPRPpNybcr6yaNcIQ6//0FY13zmPIRwr8/O9JBHQu+fESTAyAt6gJ1DyEnKeq9Iia6WAJZjIn+rccK0Hpodn+ZopDHm+FwMvFHoBaUMTeMhYcFPZqW7U+SsY1f3/TzsPiqFhFh1CZ3OnKWvl5SMlrgv9fPMWLV2uTObDAtjN2lSE7+8tuavYAEP/2ee78pMzqCCA8T69WJ1si15FLqGAOKSvHmRDtdVmcJI9CeRdiqYMNmqBIjQJ2Lvyd3AIhw6oq/crtJVA+2q51I=
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)(39860400002)(396003)(376002)(136003)(366004)(52536014)(66476007)(66446008)(66556008)(66946007)(64756008)(76116006)(55016002)(966005)(5660300002)(2906002)(316002)(478600001)(7696005)(8936002)(33656002)(53546011)(71200400001)(6506007)(9686003)(8676002)(166002)(6916009)(186003)(86362001)(83380400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?evyrsutflNFx3eJMQis1YD1q/i7EF2EsEwbl3ucIJTdFXMHEbl8/xTlnSiPK?= =?us-ascii?Q?4IEYjscqrWNHsuHOOOMtPrI0fKUnSnz+obM6yciL8fn1eu+aB465quI97lvZ?= =?us-ascii?Q?Ueyehq+AiTqExoEA9PTuM693msTgacRh54wZAEMSepZpJPCeF4OBoA1ZvH62?= =?us-ascii?Q?rjvV+TjI2e9x05sllVq4R0QcyxE/j7u7JUqX94RTcNzsGWQLWk2/wimW53gs?= =?us-ascii?Q?PtyKvdIckC/V1yxVOrajvf259KXmJ42+q/Lbgy78JfdTXT/bv0EiCfXLlEAt?= =?us-ascii?Q?NECcxANnrRMmR/4n0yhU54lUbn0+kBTLeMjX3wyaCg/Wy65cX0ScljXVPJcK?= =?us-ascii?Q?5nwG6GH3CzOD8r3slB7ldWPzpYqEBMzb0YJkrnP/miIbllaajePx3J8a/wCP?= =?us-ascii?Q?dnuki3XLbcZr5gHvnkBq902cavElh4iglZL1LJMASbcQ2dokz0Wttljx0h/v?= =?us-ascii?Q?RKtGENZxBWloR+vnnL9tc2YLB7gAnA9K5NpaLfNiN6zRaL+U4ic7MBd4U59N?= =?us-ascii?Q?ZUBlLSpyNe6O3+l7h0rVrpjPgTtnO7oKX6EGMNIyjFY6o0eIKHKAAI6k+Vu8?= =?us-ascii?Q?aapTI+xLCXErsss/kKkuO0t6buAQ1BczTEDcK7ua+0ldHrPFOc392Mgvg/p3?= =?us-ascii?Q?6Ohu4lHAaTg+dzz72k2t8NjccNZuk60Dt7bl0Vi79TX3LKMvcyPM2EaBZ1oE?= =?us-ascii?Q?XE2+/fh7zFm0WZ7dt6nE9q96nxObSsQiwnoCYeqcQJnAEMGfLmVyYYmVaodH?= =?us-ascii?Q?6WDqiU9OFWCN8KTXMPX+ry2CLx4LISHyAcESwt9P4cVrzz64fZUed8Lnv0Wr?= =?us-ascii?Q?h9AsT5lXBu86MY93acVlUSKfNFr5lfcsSFsHGccBKcLhd6ALgv7LlauDGR/J?= =?us-ascii?Q?rF3UPP/UPUnYGrZoznz1I97QEJqhX0mv3hGYXOwXcbsyhekSaVMqoglKc+Jz?= =?us-ascii?Q?LKsZDRNU3z6I0+qsb9bHbxhb6fvpqNaRZNV6mBDJrOONum1LWLdfyHT1Vm9C?= =?us-ascii?Q?LhrSrXY17N63+ubNTdQHpe9JSTyogTPhrM2ftLGNtt00O72oskw5RNUAwgrk?= =?us-ascii?Q?v8OP5ccZsKfNx3rdj9YbFq5xQysyMKATTj9bbk0IHtJE2AJ5G0A=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TRzd8ggZNWrpJr3qxBGWmOHTuCNB9AiyS9zUuVG/btwlKvtJjIWDRQp+uXsGFe3nTKKQRHsPT1AISbhIf0TIl2zBJZJRS7iSyqPf2hd8fU3Mzcw5KBD0IV8L/btNyC8s7mGV3jT1WoBaFRz3r6JJu/YbLTxkbdPT8wXuJu4VJLCevGNNdh4QV0J+1C7dQktI+MAL/Zw/RfL8jelvm1/lDHnj6mBsOsMjpyIPvilmBD8idyKei9440nSXTYVzHyIJakIN1yQx+AZnQvnO8mD6YysW1mygYe1jBWzRLTpYkDTPYOCi9+6vFd79San2dCh1+ceTctXGEK6g/Ibtc1AboA==
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=VRbS1xVE423MctPPEDpq5z4aEUUWqt7SYjg9z7YQC0g=; b=gM6L3j/asD8nZI7yWqX7LqjoRct7+ii2YZsZHyr7V2pKsjF4CEu8cPm93RpfRET8eYZX+Zlxe/H8cGFlmhSbZmpbNJmK0O15njcZ2E2NoRDsRFzX3iiPheHO0JbOBSZ6pB7Udv2nOoyCF5ZJZKYrB3uT2kD0eM8BG9Zpiwp2cAPX+2J/sTkR56LOQvoTDFlL5vWlaRoBFk2hgdaDHwtwO74iaXVBK27KH/QY8UN2DX5xeeQpo1yewM9BrD26kwWI70yTP+29SHbABs4zVfJZ9uJ1WKQlgTzhKP1KNBBLIH3ZHV2BUI1O3Vk3Jn3ZA+Q2BPVOvdsJ58S54keIpN6ukg==
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: 4fcab91e-9ae7-4467-8602-08d8c6c3b410
x-ms-exchange-crosstenant-originalarrivaltime: 01 Feb 2021 15:11:51.2580 (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: wy+oLfzV867rVb+OicEYHW9Wn2zkERpXOuuJuZvx0seJ4kpbpf8E3XvyBIXHxFsY9IeyoaeJaZE/4EveJ/UL/nkPKlCF3F5vr1xdxsGojdQ=
x-ms-exchange-transport-crosstenantheadersstamped: MN2PR11MB4224
x-originatororg: comcast.com
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB4351895D112A3C903F9A5271F7B69MN2PR11MB4351namp_"
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWZ
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.737 definitions=2021-02-01_06:2021-01-29, 2021-02-01 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/zIuiCuIvUcKgudJZH2NS2IqEp2w>
Subject: Re: [dmarc-ietf] Discussion: Removal of validation for external destinations (Ticket #76)
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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 15:12:11 -0000

--_000_MN2PR11MB4351895D112A3C903F9A5271F7B69MN2PR11MB4351namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

This came up in another thread elsewhere, and wanted to see if there was an=
y more input before closing this as "wontfix".  The only feedback I got dur=
ing this thread was that this external check should remain as it may preven=
t abuse and it appears that many have already implemented this.

The original thread is here: https://mailarchive.ietf.org/arch/msg/dmarc/pL=
7dsXjXn9BmADxly0yO2cDC_ro/

Thanks

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

From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Marc Bradshaw
Sent: Monday, December 7, 2020 5:25 PM
To: DMARC IETF <dmarc@ietf.org>
Subject: Re: [dmarc-ietf] Discussion: Removal of validation for external de=
stinations (Ticket #76)

Removing this opens up the potential for abuse, I don't see the value in re=
moving it.

On Sun, 6 Dec 2020, at 11:06 PM, Alessandro Vesely wrote:
On Sat 05/Dec/2020 14:51:52 +0100 Brotman, Alex wrote:
>
> There's currently a ticket that suggests that the requirement for externa=
l validation be removed.  Today, if example.com has an RUA that points at e=
xample.net, the latter must create a record as such:
>
> example.com._report._dmarc.example.net TXT "v=3DDMARC1"


Actually, the record can also be:

example.com._report._dmarc.example.net TXT "v=3DDMARC1; rua=3Dupdated-addre=
ss@example.net<mailto:updated-address@example.net>"

or even, considering a parallel thread:

example.com._report._dmarc.example.net TXT "v=3DDMARC1; rua=3Dreport@exampl=
e.net<mailto:report@example.net>, /https://www.example.net/report/<https://=
urldefense.com/v3/__https:/www.example.net/report/__;!!CQl3mcHX2A!TJoHWx6S1=
NRchnwhQ0ijzD46MbakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHivpAiHzHx$>"


That way, external services have the ability to control or suspend  their s=
ervice.  I think this is an essential requirement.  Let's keep it.


> The original thought was that a bad actor could overwhelm a target with u=
nrequested reports.  It seems in reality, most report generators only send =
once per day.


Once-per-day has to be amended.  See ticket #71.


> Additionally, there appear to be some generators who ignore the absence o=
f these records.


Aggregate reports are often tagged as spam anyway, but when sent in violati=
on of the spec such tagging is certainly deserved.


> https://tools.ietf.org/html/rfc7489#section-7.1<https://urldefense.com/v3=
/__https:/tools.ietf.org/html/rfc7489*section-7.1__;Iw!!CQl3mcHX2A!TJoHWx6S=
1NRchnwhQ0ijzD46MbakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHivpuaI_16$>


Why don't you refer to either of the drafts we're editing:
https://tools.ietf.org/html/draft-ietf-dmarc-aggregate-reporting-00#section=
-2.1<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-dmar=
c-aggregate-reporting-00*section-2.1__;Iw!!CQl3mcHX2A!TJoHWx6S1NRchnwhQ0ijz=
D46MbakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHivpqSIEHa$>
https://tools.ietf.org/html/draft-ietf-dmarc-failure-reporting-00#section-3=
.2<https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-dmarc-=
failure-reporting-00*section-3.2__;Iw!!CQl3mcHX2A!TJoHWx6S1NRchnwhQ0ijzD46M=
bakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHivqDi6FH6$>

BTW, this duplication is worth yet another ticket.


Best
Ale
--


















_______________________________________________
dmarc mailing list
dmarc@ietf.org<mailto:dmarc@ietf.org>
https://www.ietf.org/mailman/listinfo/dmarc<https://urldefense.com/v3/__htt=
ps:/www.ietf.org/mailman/listinfo/dmarc__;!!CQl3mcHX2A!TJoHWx6S1NRchnwhQ0ij=
zD46MbakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHivrqoGdKN$>


--
[https://secure.gravatar.com/avatar/b214a020f4eb135ce2a6901d7540bdb1?s=3D44=
&d=3D404]

  Marc Bradshaw
  marcbradshaw.net<https://urldefense.com/v3/__http:/marcbradshaw.net/__;!!=
CQl3mcHX2A!TJoHWx6S1NRchnwhQ0ijzD46MbakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHivmAR=
oKHF$> | @marcbradshaw<https://urldefense.com/v3/__https:/twitter.com/marcb=
radshaw__;!!CQl3mcHX2A!TJoHWx6S1NRchnwhQ0ijzD46MbakofNi7Vpmyu0BaBaZslL1pTcb=
vwKcBEHivu6ug4qh$>




--_000_MN2PR11MB4351895D112A3C903F9A5271F7B69MN2PR11MB4351namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
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-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea=
k-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">This came up in another thread elsewhere, and wanted=
 to see if there was any more input before closing this as &#8220;wontfix&#=
8221;.&nbsp; The only feedback I got during this thread was that this exter=
nal check should remain as it may prevent abuse and
 it appears that many have already implemented this.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The original thread is here: <a href=3D"https://mail=
archive.ietf.org/arch/msg/dmarc/pL7dsXjXn9BmADxly0yO2cDC_ro/">
https://mailarchive.ietf.org/arch/msg/dmarc/pL7dsXjXn9BmADxly0yO2cDC_ro/</a=
><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">--<o:p></o:p></p>
<p class=3D"MsoNormal">Alex Brotman<o:p></o:p></p>
<p class=3D"MsoNormal">Sr. Engineer, Anti-Abuse &amp; Messaging Policy<o:p>=
</o:p></p>
<p class=3D"MsoNormal">Comcast<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> dmarc &lt;dmarc-bounces@ietf.org&gt; <b=
>On Behalf Of </b>
Marc Bradshaw<br>
<b>Sent:</b> Monday, December 7, 2020 5:25 PM<br>
<b>To:</b> DMARC IETF &lt;dmarc@ietf.org&gt;<br>
<b>Subject:</b> Re: [dmarc-ietf] Discussion: Removal of validation for exte=
rnal destinations (Ticket #76)<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Removing this opens up the potential for abuse, I do=
n't see the value in removing it.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">On Sun, 6 Dec 2020, at 11:06 PM, Alessandro Vesely w=
rote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt" id=3D"qt">
<div>
<p class=3D"MsoNormal">On Sat 05/Dec/2020 14:51:52 &#43;0100 Brotman, Alex =
wrote:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&gt;&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&gt; There's currently a ticket that suggests that t=
he requirement for external validation be removed.&nbsp; Today, if example.=
com has an RUA that points at example.net, the latter must create a record =
as such:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&gt;&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&gt; example.com._report._dmarc.example.net TXT &quo=
t;v=3DDMARC1&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Actually, the record can also be:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">example.com._report._dmarc.example.net TXT &quot;v=
=3DDMARC1; rua=3D<a href=3D"mailto:updated-address@example.net">updated-add=
ress@example.net</a>&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">or even, considering a parallel thread:<o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">example.com._report._dmarc.example.net TXT &quot;v=
=3DDMARC1; rua=3D<a href=3D"mailto:report@example.net">report@example.net</=
a>, /<a href=3D"https://urldefense.com/v3/__https:/www.example.net/report/_=
_;!!CQl3mcHX2A!TJoHWx6S1NRchnwhQ0ijzD46MbakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHi=
vpAiHzHx$">https://www.example.net/report/</a>&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">That way, external services have the ability to cont=
rol or suspend&nbsp; their service.&nbsp; I think this is an essential requ=
irement.&nbsp; Let's keep it.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&gt; The original thought was that a bad actor could=
 overwhelm a target with unrequested reports.&nbsp; It seems in reality, mo=
st report generators only send once per day.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Once-per-day has to be amended.&nbsp; See ticket #71=
.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&gt; Additionally, there appear to be some generator=
s who ignore the absence of these records.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Aggregate reports are often tagged as spam anyway, b=
ut when sent in violation of the spec such tagging is certainly deserved.<o=
:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&gt;&nbsp;<a href=3D"https://urldefense.com/v3/__htt=
ps:/tools.ietf.org/html/rfc7489*section-7.1__;Iw!!CQl3mcHX2A!TJoHWx6S1NRchn=
whQ0ijzD46MbakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHivpuaI_16$">https://tools.ietf=
.org/html/rfc7489#section-7.1</a><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Why don't you refer to either of the drafts we're ed=
iting:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"https://urldefense.com/v3/__https:/tools.=
ietf.org/html/draft-ietf-dmarc-aggregate-reporting-00*section-2.1__;Iw!!CQl=
3mcHX2A!TJoHWx6S1NRchnwhQ0ijzD46MbakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHivpqSIEH=
a$">https://tools.ietf.org/html/draft-ietf-dmarc-aggregate-reporting-00#sec=
tion-2.1</a><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"https://urldefense.com/v3/__https:/tools.=
ietf.org/html/draft-ietf-dmarc-failure-reporting-00*section-3.2__;Iw!!CQl3m=
cHX2A!TJoHWx6S1NRchnwhQ0ijzD46MbakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHivqDi6FH6$=
">https://tools.ietf.org/html/draft-ietf-dmarc-failure-reporting-00#section=
-3.2</a><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">BTW, this duplication is worth yet another ticket.<o=
:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Best<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Ale<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">_______________________________________________<o:p>=
</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">dmarc mailing list<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"mailto:dmarc@ietf.org">dmarc@ietf.org</a>=
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"https://urldefense.com/v3/__https:/www.ie=
tf.org/mailman/listinfo/dmarc__;!!CQl3mcHX2A!TJoHWx6S1NRchnwhQ0ijzD46Mbakof=
Ni7Vpmyu0BaBaZslL1pTcbvwKcBEHivrqoGdKN$">https://www.ietf.org/mailman/listi=
nfo/dmarc</a><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"sig63695113">
<div id=3D"sig21503313">
<div>
<p class=3D"MsoNormal">--<o:p></o:p></p>
</div>
<div>
<table class=3D"MsoNormalTable" border=3D"0" cellspacing=3D"3" cellpadding=
=3D"0">
<tbody>
<tr>
<td style=3D"padding:.75pt .75pt .75pt .75pt">
<p class=3D"MsoNormal"><img border=3D"0" width=3D"44" height=3D"44" style=
=3D"width:.4583in;height:.4583in" id=3D"_x0000_i1025" src=3D"https://secure=
.gravatar.com/avatar/b214a020f4eb135ce2a6901d7540bdb1?s=3D44&amp;d=3D404"><=
o:p></o:p></p>
</td>
<td style=3D"padding:.75pt .75pt .75pt .75pt">
<div>
<p class=3D"MsoNormal">&nbsp; Marc Bradshaw<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;&nbsp;<a href=3D"https://urldefense.com/v3/__h=
ttp:/marcbradshaw.net/__;!!CQl3mcHX2A!TJoHWx6S1NRchnwhQ0ijzD46MbakofNi7Vpmy=
u0BaBaZslL1pTcbvwKcBEHivmARoKHF$">marcbradshaw.net</a> |&nbsp;<a href=3D"ht=
tps://urldefense.com/v3/__https:/twitter.com/marcbradshaw__;!!CQl3mcHX2A!TJ=
oHWx6S1NRchnwhQ0ijzD46MbakofNi7Vpmyu0BaBaZslL1pTcbvwKcBEHivu6ug4qh$">@marcb=
radshaw</a><o:p></o:p></p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_MN2PR11MB4351895D112A3C903F9A5271F7B69MN2PR11MB4351namp_--


From nobody Mon Feb  1 08:29: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 1F43D3A12BC for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 08:29:28 -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=O3wbwxNn; dkim=pass (2048-bit key) header.d=taugh.com header.b=CIGSN9ot
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fn08JCZ1Jx5g for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 08:29: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 36BF73A12BB for <dmarc@ietf.org>; Mon,  1 Feb 2021 08:29:25 -0800 (PST)
Received: (qmail 70410 invoked from network); 1 Feb 2021 16:29: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=11308.60182c63.k2102; bh=QZPcsx1K+A0w9mVyZ43S9nPnxoKyyYfrsGt2Mm6F67Q=; b=O3wbwxNn7J1P3MNYC+U7L4Il++Ww3foYN1wBxqjpFKTm0hN3coem/YAD8QUmyBRe5BInjUulzIKk4t1kzUyehPYCC0iYfJqs07y7W84otC28k1kcHwbNkL7X+HuDNGxyv9VUskB84Od2G8mx/we6ObCKtjCxL/UCTnfT4EMvH57IBpFjdbD1DHC1k01EvPE+DEP/irneB4WzdUdmONE1yh5jeh55M1ojPnlhBGWi5srAzNLDVCSD13ixd6TG3SQxPyWnSBDu/BIojcVvgMuEJxQSJXVwca8e4wP8h2Kw1w8J5Oi1JvrcovdXNHRVcbVwJwCAvd/2eTZmcwkItZRPOg==
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=11308.60182c63.k2102; bh=QZPcsx1K+A0w9mVyZ43S9nPnxoKyyYfrsGt2Mm6F67Q=; b=CIGSN9oteGGG18YdcC4w8Zg29M4HkouAR9Fu6pYqYgz5dTaeSo8AHO5bRD9Ednxi6gGEQZLIVe/DrdJiAOka6YLNzZ5QUDBeaoSPkWwOmYswO9JHEx0MTdmYIWtTayr6joNLweU4P054XGIlL9zdbug+XRp11mkphe6z1uS7v6FBpd5CI7QqbKW8M8s29QDCI3fQpAY3JUBnswVVfr5OuHflXfZHZWEnvCUfkKbVHUkbyN++kqOTuBFTP3DgEMTjHCYcxSS2KOn8McPDrl+0VQm9OwzFoClg3rpuUlgt0wBMV7a6Cb+dn4srqf+wFBbvwhWI0RtXqOQud1X1w84pKw==
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; 01 Feb 2021 16:29:23 -0000
Received: by ary.qy (Postfix, from userid 501) id 388F66D1C56E; Mon,  1 Feb 2021 11:29:23 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 380246D1C56D; Mon,  1 Feb 2021 11:29:23 -0500 (EST)
Date: 1 Feb 2021 11:29:23 -0500
Message-ID: <41bc91e9-8c9a-e2bd-a351-602436f3f5bb@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
In-Reply-To: <e7e27e1f-b6e6-96b6-e12e-672084562b8a@tana.it>
References: <20210131200238.931356D11D79@ary.qy> <e7e27e1f-b6e6-96b6-e12e-672084562b8a@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/j9lIyVCAhSArDXwk6CJB5ZbbPeA>
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: Mon, 01 Feb 2021 16:29:28 -0000

> 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.
>
>   Reporters SHOULD rate limit the number of failure reports sent to any
>   recipient to avoid overloading recipient systems.
>
> Not MUST?

You might have other ways to prevent mailbombing, e.g., only sending 
failure reports to people who you know have bigger mail systems than you 
do.

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 Feb  1 08:38:14 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 CB1543A12BE for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 08:38: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, 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 lZ7d-lwy4IKe for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 08:38:11 -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 65F2B3A10AC for <dmarc@ietf.org>; Mon,  1 Feb 2021 08:38:11 -0800 (PST)
Received: by mail-oi1-x231.google.com with SMTP id k25so19414449oik.13 for <dmarc@ietf.org>; Mon, 01 Feb 2021 08:38:11 -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=MA15fescts+Y7MUj1QbLvx6tCbKdE+BIs1TvJqwDiGE=; b=olxQ/bUfrzFr7KaJ3TFzNQ5meEiPSFusKq1X1I0i4pGIWwFlqtFQwlIYP9usJDKTVu 9fzavj0kd17bpznXV+WE5LdOub5gepLDv98/766cL6Pm6ii4OnjHsIMshkV8sPZga/kO 51dR9DSelkTUymZDOMAVPDz87k3lxChRJO07oMSQ7prOIRLhama0ilakC5eN3n8wxhc7 1wYHeRRF0Wi19hky50r0Sle0j9elHAI9K4lWmlZdCRB1JcNlXY0lUJ78bpwTJDCZtUx/ Fr+vZzWfFP4q3RcaXwNXdsDuQgFSAOWzGylVfOaVc3TLH/w7wE01iK48RXFc0Eaz9Byh VbqQ==
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=MA15fescts+Y7MUj1QbLvx6tCbKdE+BIs1TvJqwDiGE=; b=bBFS1aS6QKnH9q1NsRZltnOlXoq8lq+PDQdNlaaoc+SzY8vuoCWJXXYKXYeFdmXiyQ ed6CascFhsJC11NuQdNb6XAZ+0m4xMBFSUS7EDinBzGw9dBC+GZl1NZUVsPp49K6GoVZ yqctm9IBakACq2Jvrr+fd8rB/3swLOc14TsDU7EUZSkSSzE9MXgIi98NL4yZ6gDO3sDU rvz2t8PN0yeAaA11keWF42NfK6/a6HdxIFt20dVd8i3fO+6lmawYI16ni16H+pB+tP+c nGjVsw14KkDRq8bYwst23BFTmzIXlAwHmm7Ee8KL2h0EhHTbcxhNwg4Bz2A/5jV1cWFo PIhw==
X-Gm-Message-State: AOAM530PC/n00RgRjuj66oN8cq5Zi1CYkIq+VuooPlWstLEHdKB921WO 1n1yovSyB4fAEprUsfwsMaa+h8l1hjXVJg==
X-Google-Smtp-Source: ABdhPJyN/y/MoRIG0BSVF7jrUjLdMR4ygzB397ZZauGyYlN6dznrBEShYpuJhBnDEsy2uHunT7MfAQ==
X-Received: by 2002:aca:c60d:: with SMTP id w13mr11194633oif.26.1612197490558;  Mon, 01 Feb 2021 08:38:10 -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 w10sm4531567oih.8.2021.02.01.08.38.09 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 08:38:09 -0800 (PST)
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: Dave Crocker <dcrocker@gmail.com>
Message-ID: <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com>
Date: Mon, 1 Feb 2021 08:38:07 -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: <b7ea6cb8-ce79-7df7-c521-544358c1866e@crash.com>
Content-Type: multipart/alternative; boundary="------------1DAEF1CFA5BA85BB45675C4C"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/aa4z6r--ztiMSYZxxS_MSJ4fywU>
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: Mon, 01 Feb 2021 16:38:13 -0000

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

On 1/27/2021 7:17 PM, Steven M Jones wrote:
> 3.3. Transport
>
>    Email streams carrying DMARC failure reports MUST conform to the
>    DMARC mechanism, thereby resulting in an aligned "pass". 


    1. I haven't been tracking discussion closely.  So if this is
    something already sufficiently well-discussed and understood and
    still landed on the above normative text, I'll apologize for re-raising.

    2. But not really, because it strikes me as a serious operational
    mistake, though a well-motivated one.

Mostly this will discourage reporting.  Legitimate reporting.

Consider the challenges to ensuring a DMARC pass.  That's a pretty high 
barrier to entry against generating reports.  It should take a very, 
very substantial record of reporting problems to justify such a barrier.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


--------------1DAEF1CFA5BA85BB45675C4C
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/2021 7:17 PM, Steven M Jones
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:b7ea6cb8-ce79-7df7-c521-544358c1866e@crash.com">3.3. 
      Transport <br>
      <br>
         Email streams carrying DMARC failure reports MUST conform to
      the <br>
         DMARC mechanism, thereby resulting in an aligned "pass". </blockquote>
    <blockquote>
      <p><br>
      </p>
      <p>1. I haven't been tracking discussion closely.  So if this is
        something already sufficiently well-discussed and understood and
        still landed on the above normative text, I'll apologize for
        re-raising.</p>
      <p>2. But not really, because it strikes me as a serious
        operational mistake, though a well-motivated one.</p>
    </blockquote>
    <p>Mostly this will discourage reporting.  Legitimate reporting.</p>
    <p>Consider the challenges to ensuring a DMARC pass.  That's a
      pretty high barrier to entry against generating reports.  It
      should take a very, very substantial record of reporting problems
      to justify such a barrier.</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>

--------------1DAEF1CFA5BA85BB45675C4C--


From nobody Mon Feb  1 08:59:41 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 D852F3A12E3 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 08:59:39 -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 p_laHOd3evGk for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 08:59:38 -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 6E5CE3A12D8 for <dmarc@ietf.org>; Mon,  1 Feb 2021 08:59:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612198776; bh=urgQDQAhrhxX0xSRldP7DngElmqVd7Udx5zdT84ZyxQ=; l=757; h=To:References:From:Date:In-Reply-To; b=DCBkPTPp0Kgt53jfv9RHVfAdh5sIW5SnAmNwgAdZPi4PPiSVL1X+rpCFIrdriE5oZ 34lpQPrTbElaRCK8VOR/X91QMpV0wnrCIW+kKQzVNGC5deApCPKNyX7QzPp/zjjC/w TNH+i8N+5dqAEpPZgJGUEsLHe9EWaZi/wgTQHLdhJj5kFjfUAJkZdZt84wl6v
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.0000000060183378.00003C7E; Mon, 01 Feb 2021 17:59:36 +0100
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <20210130212339.447316D04763@ary.qy> <36a1c70-875d-89c8-7e95-a32324654275@taugh.com> <CAH48ZfwBKyA-TwSrr2422zmMO8wr1CKf2MiQZ3KvQu2hOH=_CA@mail.gmail.com> <1654196.ygyh55z74P@zini-1880> <babf1538-5172-f101-d5e4-c4fa33dea495@tana.it> <CAH48ZfzAEhxSgS=VZtsp-xdWMzKq0Zow7DyCALq=qvMAv8_mEQ@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <90e67edb-1433-41b4-1027-c0bb853b5a9f@tana.it>
Date: Mon, 1 Feb 2021 17:59:34 +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: <CAH48ZfzAEhxSgS=VZtsp-xdWMzKq0Zow7DyCALq=qvMAv8_mEQ@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/LSypRcOIZXf5A9NO0Zbp9xbPZzE>
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 16:59:40 -0000

On Mon 01/Feb/2021 15:26:37 +0100 Douglas Foster wrote:
> 
> If Helo aligns with From, it says that the mail server has permission to send 
> on behalf of the From domain, but it does not justify using a different domain 
> in the SMTP address.   If the SMTP address is null, this is not a problem.   If 
> it is not null and is different from the HELO domain, we have permitted domain 
> abuse.


Who said a different MAIL FROM is abusive?  What if I have an account at gmail 
and, for convenience, prefer to collect bounces at that mailbox?  Would I need 
a special permission to do so?

What if helo is verified, bounce address is null, but there is a DKIM-Signature 
which is not aligned.  Is that domain abuse too?

Hm...


Best
Ale
-- 










From nobody Mon Feb  1 09:12: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 83F953A13AC for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 09:12:52 -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, 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 0znMvESyhrXl for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 09:12:51 -0800 (PST)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 CAA513A1393 for <dmarc@ietf.org>; Mon,  1 Feb 2021 09:12:47 -0800 (PST)
Received: by mail-pl1-x62d.google.com with SMTP id b8so10351072plh.12 for <dmarc@ietf.org>; Mon, 01 Feb 2021 09:12: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-language; bh=UqcwetRIyx3a/jnqWCgAFc9YOMt+M3osbsAVwr0Fm4o=; b=MIXHBAbqCHJccHnL6l20gNFcueOOCRmXDLPRHJxoflnlWhga0WQEadFZUzsrC1sGus LdLK3b2ZvgrsbYnoDCtdOp4g/JyRjIXhQJ7PDH45ksfRWGkyk44rvI+RZGoJqwQbZ0fT R2jSPK5RdPuS+5S04EgUR2jxTcAaxnCrf+C2XlL+nq34DILc+ZWSuFUOjXPU98uABCLX EzrszSLm+J7+KN8lMUUHFJoEd/9ytb6MYWgsriwh6TaqWsB0ODSTEtBACSAQCDCigKAB O1xA/XS1B/mYr7VdOzJroavou8GZ36Et1AGSUwbDX0t8JCoyWEdawTQM0WnLz72R0CTB eSww==
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=UqcwetRIyx3a/jnqWCgAFc9YOMt+M3osbsAVwr0Fm4o=; b=RFMg4FinRJGxXAeAPe87R6Nx5n0xSjeLEsQ1WgV714pt1liz5H5d9qAewGxQunKGiK gKG1KUUyy0/7R+EOGl7GzJFElUfIKNXRZ6kcnkaGO1QE/DVnyOSUrT0bE9M6pbIuSP1u d5ODP/5rHQMs3tPlCLMPkRW+Iyc7pOqMuh03/NtfHyyLFCBp4oJVQuaLYZWsDp3mmRn+ lyr3TexmZEBLtR6e6JkajDOTLjo64lo+HeVsqbo43RGgfq3uVen3qb4Ht2+KTKo/pn1J STTBlwApvauLl1HlPfyLBYcOTGwocbhflc/WO/m6c5ebX4F5R+VcUeAtdFAvhAi6k/ma FRzQ==
X-Gm-Message-State: AOAM530L33iyuV+sKROopxIz9lQ3utYtgicjHFfXnbo2mNRhk66XEcII +Ks19hcjexKMPZd2GVw9f7zP2dbXGP3g/A==
X-Google-Smtp-Source: ABdhPJycsh+kE3g64/Qmnfg/W41oHErllHm92eelnXeodK8QWfFb7e4qcbrB5/4AeAk6QuXvpUhCOQ==
X-Received: by 2002:a17:903:22c2:b029:de:45c0:69f2 with SMTP id y2-20020a17090322c2b02900de45c069f2mr18546866plg.26.1612199566830;  Mon, 01 Feb 2021 09:12:46 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id m1sm16855963pjz.16.2021.02.01.09.12.45 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 09:12:45 -0800 (PST)
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> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <316980c7-631c-4e94-c22d-7d23e99baa36@mtcc.com>
Date: Mon, 1 Feb 2021 09:12: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: <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com>
Content-Type: multipart/alternative; boundary="------------32D4428E028222CDFD804A72"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/XGtf5sPMCICA6vIO2vAW9qaiLk8>
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: Mon, 01 Feb 2021 17:12:59 -0000

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


On 2/1/21 8:38 AM, Dave Crocker wrote:
> On 1/27/2021 7:17 PM, Steven M Jones wrote:
>> 3.3. Transport
>>
>>    Email streams carrying DMARC failure reports MUST conform to the
>>    DMARC mechanism, thereby resulting in an aligned "pass". 
>
>
> Mostly this will discourage reporting.  Legitimate reporting.
>
Versus illegitimate ones you'd assumedly want to ignore.

Mike


--------------32D4428E028222CDFD804A72
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 2/1/21 8:38 AM, Dave Crocker wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div class="moz-cite-prefix">On 1/27/2021 7:17 PM, Steven M Jones
        wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:b7ea6cb8-ce79-7df7-c521-544358c1866e@crash.com">3.3. 
        Transport <br>
        <br>
           Email streams carrying DMARC failure reports MUST conform to
        the <br>
           DMARC mechanism, thereby resulting in an aligned "pass". </blockquote>
      <blockquote><br>
      </blockquote>
      <p>Mostly this will discourage reporting.  Legitimate reporting.</p>
    </blockquote>
    <p>Versus illegitimate ones you'd assumedly want to ignore.</p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------32D4428E028222CDFD804A72--


From nobody Mon Feb  1 09:25:54 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 C3B383A132C for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 09:25:51 -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, FREEMAIL_FROM=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 WSBF4WTJoQ3g for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 09:25:50 -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 4EC9B3A132B for <dmarc@ietf.org>; Mon,  1 Feb 2021 09:25:50 -0800 (PST)
Received: by mail-ot1-x333.google.com with SMTP id d7so17075794otf.3 for <dmarc@ietf.org>; Mon, 01 Feb 2021 09:25:50 -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=p5tGpswP2E7EFNhqwZ0i46H/aEcO05mhYEHDUXJqmrg=; b=Yizs5mG2AqSoxk7ZVUYEde9w+edpMTVnoCRfKOGDuffruiVGD2Xkh437gYDEOrIU61 XhvRhZJUFXnjeo7Tq/aQ78HlPbJvr/WsEXKhP0fpksVBZBlwadBpwOO+rLYc++1Wh+++ PXO8mQRTNMEaNC18ZhBjjvKllImbU8vWAqGcuv9Cz51Xhu/v6fTMsHYvvRmlZzbwJiyX 7FCL3UAI+6mRHuWSqGvRwFfYqAy/Lbf9YP6C9jyEVxbiNK1gaDCXYDGhIByssNDv5Rtg QvhBp6F52XS6D/sdDMeztILkMoSLOVMR7NQrGwoNMbw+iHeSL/T1GUNZUHiIB9Mvg1On HAyg==
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=p5tGpswP2E7EFNhqwZ0i46H/aEcO05mhYEHDUXJqmrg=; b=BsGmvalevnCv8wApWg4TvbY+kBcingin51MUxjwQZ4sj05t0gZCr5MAO/Q2TrkvSoU Lt6nMWTQH2bMAZashmueumumgJxBznDBn9vhx2WbTqzHtNlclNInu97vlpCry7CrE7Im JZcN2AsfVBgZtv3b+IGcXIBvOVq2hQPJz07sO+Nv5Cn7qHJzp0UR8gamcVGebk95nWrS 7cx5Adnw2BDhCObKpQkpA0dsEdhJUpHXYYrZTW6+NLf8aC+zGGUZnRvW5uLqCOhvc44F DdV3ZnBjOKqapIzhH8iyBpPDc701FE8xLy+cA/VXUUXlHOolZfMi67zZvceEFNogFqYB QJ7w==
X-Gm-Message-State: AOAM533ReOBiL4/Oa6QsRLr070/e4Euv4kqCwjXS229ZMGKWAnda0YDZ 0slrGRBqEsYlJks4r4mRrTbktAExiJ5hIg==
X-Google-Smtp-Source: ABdhPJzs/oHChG1s/MmPtKSlmgzSoIMTsjx2jr+kbx5xjAm4YMeZSYTXeF54SSHL2x9Osj3E4vqJ1w==
X-Received: by 2002:a9d:1e7:: with SMTP id e94mr12722415ote.219.1612200347886;  Mon, 01 Feb 2021 09:25:47 -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 s189sm255525oif.19.2021.02.01.09.25.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 09:25:47 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, 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> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com> <316980c7-631c-4e94-c22d-7d23e99baa36@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <6af16adc-eae4-9800-92cf-6a7daf6e5064@gmail.com>
Date: Mon, 1 Feb 2021 09:25:46 -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: <316980c7-631c-4e94-c22d-7d23e99baa36@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/2ULPy9gbJofSVMhKdlZVxlfrnQI>
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: Mon, 01 Feb 2021 17:25:52 -0000

On 2/1/2021 9:12 AM, Michael Thomas wrote:
> On 2/1/21 8:38 AM, Dave Crocker wrote:
>> Mostly this will discourage reporting.  Legitimate reporting. 
>
> Versus illegitimate ones you'd assumedly want to ignore.
>

So, it's probably a good thing I emphasized:

"It should take a very, very substantial record of reporting problems to 
justify such a barrier."


d/


-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Mon Feb  1 09:50:41 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 1F55D3A135C for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 09:50:40 -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 oHF0cXJUZlhS for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 09:50:38 -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 571B53A1358 for <dmarc@ietf.org>; Mon,  1 Feb 2021 09:50:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612201835; bh=KLUrBm+QZPcgdAPGZMlnkGSxOa9OHGhykBhLRxT/pUc=; l=846; h=To:References:From:Date:In-Reply-To; b=B8rsqUTgpNm3M1MqWVHXTYX8xa5zEDaIkJYt6zzYTuwUT2o/QBKRtDIRWOJbn3Lh0 ArqgR/AxoE9gowBfWarsDpeoYhnswspvEUC0RqBDacw9j10rhsb15aM+b0BsrXILIf BepXwcGWnTbhPFKtc1QNLs6Ks0bBcV7w7uZQ7ANwOxFdaces3UnItbDSpGlOn
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 00000000005DC0C6.0000000060183F6A.00004213; Mon, 01 Feb 2021 18:50:34 +0100
To: dmarc@ietf.org
References: <MN2PR11MB4351D62302C7357DE653F8B4F7F00@MN2PR11MB4351.namprd11.prod.outlook.com> <fc1d9d7c-4e14-78af-0416-b6cfb0873468@tana.it> <0359b009-5b18-46f8-85a5-959ad337dd49@beta.fastmail.com> <MN2PR11MB4351895D112A3C903F9A5271F7B69@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <6530aef3-715b-a2c2-aed6-dc28f67f6107@tana.it>
Date: Mon, 1 Feb 2021 18:50:33 +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: <MN2PR11MB4351895D112A3C903F9A5271F7B69@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/mdtbS1YHvN0HmT9e-qD3lpJuFJ8>
Subject: Re: [dmarc-ietf] Discussion: Removal of validation for external destinations (Ticket #76)
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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 17:50:40 -0000

On Mon 01/Feb/2021 16:11:51 +0100 Brotman, Alex wrote:
> This came up in another thread elsewhere, and wanted to see if there was any 
> more input before closing this as “wontfix”.  The only feedback I got during 
> this thread was that this external check should remain as it may prevent abuse 
> and it appears that many have already implemented this.


Yes, please close it.

For the record, two implementations are here:
https://github.com/trusteddomainproject/OpenDMARC/blob/master/libopendmarc/opendmarc_policy.c#L574
http://www.tana.it/svn/zdkimfilter/trunk/src/zaggregate.c#line=725
(if your browser doesn't implement RFC 5147, search "check_addr")


> The original thread is here: 
> https://mailarchive.ietf.org/arch/msg/dmarc/pL7dsXjXn9BmADxly0yO2cDC_ro/ 


That's the same thread we're in now.


Best
Ale
-- 











From nobody Mon Feb  1 10:08:29 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 49B573A1380 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:08:28 -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 LvcIzz1jBdvA for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:08: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 0B65C3A137E for <dmarc@ietf.org>; Mon,  1 Feb 2021 10:08:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612202905; bh=LRtWExRJOV7JQjGGDUCbO40A9g4Te0LDbd4iY5ZTcS4=; l=344; h=To:References:From:Date:In-Reply-To; b=DD+ebXgf6BSHoKMKn05pjkNupareIekJIMDMAr97mYSILxiN/66eRHIPY0KxniCgT CDJcYvFEuWdhQqY9/gCDCm7Fnxgu2i//8jcCkCihr4glwJzI5gUroLcXzEFR2gFdK6 m0Qf4QqbIJopPZNfGpo9sWtNtFP/yjQKZyB8KBQNSwJQHiuRkPWnnilS0BQf5
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.0000000060184399.000043CE; Mon, 01 Feb 2021 19:08:25 +0100
To: Dave Crocker <dcrocker@gmail.com>, 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> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <379e4493-1287-9dd5-5c8f-ae5adf949cbd@tana.it>
Date: Mon, 1 Feb 2021 19:08: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: <dc398e7b-2fc6-f418-4e66-456a6c1189d6@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/alorLoU_zlOb42tIdSNG9MYe7Yw>
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: Mon, 01 Feb 2021 18:08:28 -0000

On Mon 01/Feb/2021 17:38:07 +0100 Dave Crocker wrote:
> 
> Consider the challenges to ensuring a DMARC pass.  That's a pretty high barrier 
> to entry against generating reports.


Well, if a mail site is unable to get a DMARC pass, they have more urgent 
problems to solve than setting up aggregate report generation.


Best
Ale
-- 























From nobody Mon Feb  1 10:13: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 E89713A113F for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:13:06 -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 NoDERgWA3tm2 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:13:05 -0800 (PST)
Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) (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 8377B3A0D74 for <dmarc@ietf.org>; Mon,  1 Feb 2021 10:13:05 -0800 (PST)
Received: by mail-oi1-x233.google.com with SMTP id d18so19811537oic.3 for <dmarc@ietf.org>; Mon, 01 Feb 2021 10:13: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-language; bh=30AF6NjwmnsU4Cu+wxRnumT68XXnyhDC5ZTNxWu/wHs=; b=j4xWqvJfC/+xMPZwgInV2Qbh3CiSWYHYoQm9cdC6T3xInr6phN+JPiTKPEOqvV7abT lASp84V5cHtVU9ZPcKkN9ope08ZKtCYIPujBRbgBnZZKbIKbocZArbZ0VD1cZn90TPcO 2o5UWx0OMn8WNz1CdLG1vz5HzShh6d3tTS4CTSMIOELVO8uc+TDaJR7H+05QnoLy/g+4 k51S1eT0+8vOcSAYcjB9+tF+adM/o1F+SM3K6BeJUWXHJ296724hFVWZP0H8533KGY5I N0f79yUkphMys5Aj6S/sG99SnUCNDrvooZao0vOAsi8WC/d40DnXechJ6O1dJ/i7LlGu RZvQ==
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=30AF6NjwmnsU4Cu+wxRnumT68XXnyhDC5ZTNxWu/wHs=; b=JkfEABADlITY0O+5DnpYx8wfCQG4hE9D6FZcO8Dm4ZsEdUHyXTim4zMz/5IrfkiaOY LGsgmrNPsyfHZb6mJBEeT3CQQM0dvCslg4EIj8wrCz+NPDDEuVE1aYwvnfzKbVwz6MJE mzjFG5Gx6jXPz1B7wlBN0mKZQaF4v/2QDY84Zt1x083/5w9qy9hVYjMQ95yMCN4j6A3C tLMVPchaEqitEBv5C1CGF7i4hj+3XgeWhlGmZwyDmJePKfsTeknJqYy4sHrj6Xr7sx4w nzVs3wYBq32LCUWuyVoI4wlv74iJy4zjR6J2P9C9EtAvcvW/i31Pijx7hhNdEDWUgs21 gOEA==
X-Gm-Message-State: AOAM530Cd5/wNXOCunYvCWtkSMvIv7bbeLMYkh0dYJsFkB2uaRFNttmn A7Mi1DZV0hZqA75qRnDZjJo1RHzWE62Vdw==
X-Google-Smtp-Source: ABdhPJwe8RW/NatwBIpXMkUSR3dVHZEMt/48002i26rHodVRt75OQYVku7nCHS9w5D++lieu9opqFQ==
X-Received: by 2002:aca:dc56:: with SMTP id t83mr80230oig.75.1612203184504; Mon, 01 Feb 2021 10:13:04 -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 a76sm4655086oib.45.2021.02.01.10.13.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 10:13:03 -0800 (PST)
To: Alessandro Vesely <vesely@tana.it>, 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> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com> <379e4493-1287-9dd5-5c8f-ae5adf949cbd@tana.it>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <9aea1615-64a5-a310-b8c7-83ec0c316dae@gmail.com>
Date: Mon, 1 Feb 2021 10:13:02 -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: <379e4493-1287-9dd5-5c8f-ae5adf949cbd@tana.it>
Content-Type: multipart/alternative; boundary="------------152ADBFD33EA181060980680"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ZZ-VrjsatatI8DUIGoDyAJjWvrs>
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: Mon, 01 Feb 2021 18:13:07 -0000

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

On 2/1/2021 10:08 AM, Alessandro Vesely wrote:
> On Mon 01/Feb/2021 17:38:07 +0100 Dave Crocker wrote:
>> Consider the challenges to ensuring a DMARC pass.  That's a pretty 
>> high barrier to entry against generating reports.
>
> Well, if a mail site is unable to get a DMARC pass, they have more 
> urgent problems to solve than setting up aggregate report generation. 


No, they probably don't have more urgent problems. Sites choose not to 
adopt DMARC for a variety of reasons. It's probably a good idea to 
respect that variety.

The model that a receiving site is not allowed to report DMARC traffic 
unless that site is also generating DMARC authentication is 
Procrustean.  And as I noted, is likely counter-productive.

I understand the zeal that drives a lot of the effort to promote DMARC, 
but the danger with aggressive proselytizing is that it changes from 
serious technical and operational evaluation into purely religious fervor.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


--------------152ADBFD33EA181060980680
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 2/1/2021 10:08 AM, Alessandro Vesely
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:379e4493-1287-9dd5-5c8f-ae5adf949cbd@tana.it">On Mon
      01/Feb/2021 17:38:07 +0100 Dave Crocker wrote:
      <br>
      <blockquote type="cite" style="color: #0000a0;">
        Consider the challenges to ensuring a DMARC pass.  That's a
        pretty high barrier to entry against generating reports.
        <br>
      </blockquote>
      <br>
      Well, if a mail site is unable to get a DMARC pass, they have more
      urgent problems to solve than setting up aggregate report
      generation.
    </blockquote>
    <p><br>
    </p>
    <p>No, they probably don't have more urgent problems. Sites choose
      not to adopt DMARC for a variety of reasons. It's probably a good
      idea to respect that variety.<br>
    </p>
    <p>The model that a receiving site is not allowed to report DMARC
      traffic unless that site is also generating DMARC authentication
      is Procrustean.  And as I noted, is likely counter-productive.</p>
    <p>I understand the zeal that drives a lot of the effort to promote
      DMARC, but the danger with aggressive proselytizing is that it
      changes from serious technical and operational evaluation into
      purely religious fervor.<br>
    </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>

--------------152ADBFD33EA181060980680--


From nobody Mon Feb  1 10:15: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 C8DE93A1384 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:15:45 -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 tsR6MukKRuuy for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:15:44 -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 B1E113A113F for <dmarc@ietf.org>; Mon,  1 Feb 2021 10:15:44 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id j11so7863407plt.11 for <dmarc@ietf.org>; Mon, 01 Feb 2021 10:15:44 -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=PxTexJxbJGv78sxxx1Y5Ullzub+thLxEg1CfS63KUDA=; b=Dv57ZBOCOFtEe6O19EnssICPgigFK/l7KXX60LB1ZPcoWOqaOq5oVr8+YqHaawWaQE VY91ziHNQBhU2g0DH1/KkMsVr4TGkPoEKPoUcp5zFM5AT2ysO2cBBueMkBxUMsNxZNXM zI3lgKuVTi3Hye7+Sw7PNMbns1/bVWbgL3r/RYwuda/EpjV8hubdKtot8M0EmGPOi0NR HaFErDJ9V2vCFw5IQwH1oBOPh8tcqLIMSzhjaGQrxveFO1ScY8L3V1dS5fMKaAlrqkpm 7o/WYvrdTggiTDqQtEyWsIXZ0ROUArj5Bs75nYaq41Zu/z4kAXUeNTt519RGzcj3RagD iYUA==
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=PxTexJxbJGv78sxxx1Y5Ullzub+thLxEg1CfS63KUDA=; b=OHgLg8ugo+SaBjDB/UbL3k2RUlIBKATx61pAdBz7JsR9Qge0YmE8e2e6htiQJsnyXg 2DfS282F0aZ1y/B/3Cs12K+dOk7bifIT2LgverIwBwXAHRWErB1gi/nMcsvnAzphROkV NZ1h9rJV5tihxh00q9c1eY9XSR7NUKEKTHyeQ05c5HbTlZ3lQC3RQk+gSK+pqLAKRjcF rTdICZSoFNuILI008nAC9jcAb0WwrnN7x5vU/3VHrqylFNQarneqPJAVJ0spqx4RXVKN xmJ61ulQxUTxrumL1xTPuyklct1JW9p04ZH2YMQ+iaPND/mqwx0dFCGXKGtp5CkOwSJy NaFw==
X-Gm-Message-State: AOAM530qLRoCuYRvL4yB5z3F5SguvpOrwJvE7rhaNvW/ZQU+t1HwOxbl SjZKM0lGJOE4tqvqBSqAOr1OIdQQ/ujhqA==
X-Google-Smtp-Source: ABdhPJyLpOHSVxDBru2TUtOjYGRbrBwmiCSmZchgGFHmltKfBnN4dAYRy7HazdQE79aG3VodD0ABVw==
X-Received: by 2002:a17:902:523:b029:dc:1aa4:28e7 with SMTP id 32-20020a1709020523b02900dc1aa428e7mr19015972plf.4.1612203343572;  Mon, 01 Feb 2021 10:15:43 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id o13sm19465897pfp.101.2021.02.01.10.15.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 10:15:42 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, 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> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com> <316980c7-631c-4e94-c22d-7d23e99baa36@mtcc.com> <6af16adc-eae4-9800-92cf-6a7daf6e5064@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <413b657b-bbbf-854c-649c-f14c5f0272cd@mtcc.com>
Date: Mon, 1 Feb 2021 10:15: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: <6af16adc-eae4-9800-92cf-6a7daf6e5064@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/_8W16QM7Kpz-Xx5BLgxC6G4JgrE>
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: Mon, 01 Feb 2021 18:15:46 -0000

On 2/1/21 9:25 AM, Dave Crocker wrote:
> On 2/1/2021 9:12 AM, Michael Thomas wrote:
>> On 2/1/21 8:38 AM, Dave Crocker wrote:
>>> Mostly this will discourage reporting. Legitimate reporting. 
>>
>> Versus illegitimate ones you'd assumedly want to ignore.
>>
>
> So, it's probably a good thing I emphasized:
>
> "It should take a very, very substantial record of reporting problems 
> to justify such a barrier."
>
Meanwhile in 2021, the internet is a dangerous place where the default 
posture is to assume that if something can be gamed it will be gamed.

Mike


From nobody Mon Feb  1 10:16:16 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 152313A1386 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:16:14 -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 6NNgC0ptYW6L for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:16:12 -0800 (PST)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (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 862CF3A1384 for <dmarc@ietf.org>; Mon,  1 Feb 2021 10:16:12 -0800 (PST)
Received: by mail-pg1-x52c.google.com with SMTP id i7so12610640pgc.8 for <dmarc@ietf.org>; Mon, 01 Feb 2021 10:16:12 -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=5o57IoxtuodcfeCyYenDnPP8SlHqlbhMDuWTVrcpAQo=; b=WQezF4/X+5AqUdMVWwS9lUKbkX0/HYQ3VnhB1bOrWT+cd3fzoCB2UebejljU+3FX6X 5PKGZP3/kytsfGaG6SziF5ZuVh6qCe7UY9fndEEFDNpUUPSWMfQmGXamBn1sAzRjCLWt lOimQXz3eLmyoPSmbSczHHprc7U5DoN0ysL8NzDUYqLujBiJjt+lhQ80RUziW2j5PQgB bZjuhO0glI7aLjd/kFqzxqqzBXr4tewPjjCONnhZxDe7kYtirDFPpI4XiWIudOcu+TcJ 0CobvDF1/8DBWC/ua08USkqjAdFmStlljA3kgLkNiFOBjO2NtV0tNcDTdQDYipz+bUU8 srXA==
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=5o57IoxtuodcfeCyYenDnPP8SlHqlbhMDuWTVrcpAQo=; b=fbi3PNjt7rnWZ+7JwxUVU1lNgn3FpTWcsia2iku1Vk5Vyv1+M0F0jZr4sGvyD65MJT sz8xQUiyE30MW6YsONg8UmMkYB7LS7bj4HDTtGthChT3g344silu5is6HL57BotKCQG4 7qvj7oOljr4ytlRanQfQJgxqY1EL694z4e4stTfMagrQtDCeILK3SVATvvt5UP4HZBVQ yWv+SScRDuJ56utiduAjDR0FFO+8mPGIfKUz3b++tdDRjBFMZULprTaZdrzYLEoQfjfJ Y/HoDggryYSvpOdiZt5ZagVskzNVwIqdeNtR+h/sDO6E7932ZvOEElA0njWAGQ9pnCng +kIA==
X-Gm-Message-State: AOAM530W96lUWOp5RtyiHrBSiwZtRoaSAKxgU93duLHDf0adjemUEQQB ruswtqWuAKZy4/0Lesh3FcTBkzvswvYhQA==
X-Google-Smtp-Source: ABdhPJx4gWDXLkL9r/GcokszMz03liOOQ6Qpjl79JJiVSDrzw+uv4IDi8EKKZ11DMMYP25dg73dchg==
X-Received: by 2002:a65:6290:: with SMTP id f16mr18201992pgv.69.1612203371648;  Mon, 01 Feb 2021 10:16:11 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id p1sm18305316pfn.21.2021.02.01.10.16.10 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 10:16:11 -0800 (PST)
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> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com> <379e4493-1287-9dd5-5c8f-ae5adf949cbd@tana.it>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <7b0628bd-a47c-97c4-70bd-366cc92626b6@mtcc.com>
Date: Mon, 1 Feb 2021 10:16:09 -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: <379e4493-1287-9dd5-5c8f-ae5adf949cbd@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/1OLi3xuwsyys1afjEwXIGk7Euqo>
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: Mon, 01 Feb 2021 18:16:14 -0000

On 2/1/21 10:08 AM, Alessandro Vesely wrote:
> On Mon 01/Feb/2021 17:38:07 +0100 Dave Crocker wrote:
>>
>> Consider the challenges to ensuring a DMARC pass.  That's a pretty 
>> high barrier to entry against generating reports.
>
>
> Well, if a mail site is unable to get a DMARC pass, they have more 
> urgent problems to solve than setting up aggregate report generation.
>
+1

Mike


From nobody Mon Feb  1 10:19: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 1482D3A1387 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:19:44 -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, FREEMAIL_FROM=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 ljvvvzKgI-Fo for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:19:43 -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 DEEE03A1386 for <dmarc@ietf.org>; Mon,  1 Feb 2021 10:19:42 -0800 (PST)
Received: by mail-ot1-x333.google.com with SMTP id v1so17254692ott.10 for <dmarc@ietf.org>; Mon, 01 Feb 2021 10:19:42 -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=iLeS+mcDrIyzuR6cQlzMhGkFl0D7dW4TuOuNstGmUkw=; b=c2YPvXcP1IldviwMcMuMk1n3+Ic0vqUA2z5j3H9gyTbpcS0kpl3Z4QWb0+1zoUAWCM 0VGV1fCAeM+IhGUt9vUDwTlE7uQEQcP9Rwu1y2rAS5VusD1jBNMA7zEhVyS7Au+uonm/ 5lLYBB4925qfvtPKSXDmrzlaasT3/DaYa5b/VSpqUqdoEq5UnDaDJflFNn30JOPfp9+A 4bxKvC0suQUW2v9MXwJxVQ6rA5rQXjxBRy3I3iFNKrsoxArXzhwq6WpyMmSXwLIHjdKV inDlKgxhKuzzU2wErjCbY8Mb6errncDWjOO4gwIy3dL3Vt9j5NtPLekmH8cUvj5xBcjd JNoQ==
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=iLeS+mcDrIyzuR6cQlzMhGkFl0D7dW4TuOuNstGmUkw=; b=C/OsElxk+NovFKVQqS9JgvbdYrnHDl3iGujHB/r1kEqyilr7sjbh2PbvL83r9lCPwZ 9Com2/KnoYWyw0zQb/xW3whXufLbgQXDeM5xT091xdI6OAUHQNgJH6kz5eeoAEA/G8Gz s0cKnpReuXSqV+B/OK5xTvO6E44eRwPgMQyNdo/eemxsAoolKo5BApL+Tv41QN02PNgL fpx+pk3X+FdCdKQeuu6i0vsuXj5G0AEG95Z257fPESRig5lFHKozV8RqJbme61NLqNyN 5xd6elPZuGu+4q6cHcCL8n/GhSJ+jRecidAeAK3nPlnJeFdSwVMuGcXHib7ecugeSHgj 5FQg==
X-Gm-Message-State: AOAM533m5ip9zUXeo69+iKpQ3FbuUvqPgSMVFCBi19RpCpefKinIbDnl Pnkw32YAot0pToLGODR3+4pS2DnvMrxIYQ==
X-Google-Smtp-Source: ABdhPJz62XTR2V8em4B45x8ZEPl8B9AllU3tH29CguNNTOKFdTfzZcJ21Cj9WXK5PXw6+w6oTu7l3w==
X-Received: by 2002:a05:6830:15cc:: with SMTP id j12mr12703004otr.145.1612203581976;  Mon, 01 Feb 2021 10:19:41 -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 v77sm4218331oie.16.2021.02.01.10.19.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 10:19:41 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, 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> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com> <316980c7-631c-4e94-c22d-7d23e99baa36@mtcc.com> <6af16adc-eae4-9800-92cf-6a7daf6e5064@gmail.com> <413b657b-bbbf-854c-649c-f14c5f0272cd@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <ccda986e-5eab-83a2-3a7a-e629902e78bb@gmail.com>
Date: Mon, 1 Feb 2021 10:19:40 -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: <413b657b-bbbf-854c-649c-f14c5f0272cd@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/NmIoXgWe4xbXtnuLvar47e8dpfc>
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: Mon, 01 Feb 2021 18:19:44 -0000

On 2/1/2021 10:15 AM, Michael Thomas wrote:
>
> On 2/1/21 9:25 AM, Dave Crocker wrote:
>> So, it's probably a good thing I emphasized:
>>
>> "It should take a very, very substantial record of reporting problems 
>> to justify such a barrier."
>>
> Meanwhile in 2021, the internet is a dangerous place where the default 
> posture is to assume that if something can be gamed it will be gamed.


Perhaps you'd put that comment into both a cost/benefit tradeoff 
consideration and in technical and operational terms that reflects 
practical limits?

d/

-- 

Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Mon Feb  1 10:25: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 3E1EC3A1438 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:25:21 -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, 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 YAPGV56wKNbR for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:25:19 -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 D21C63A13FA for <dmarc@ietf.org>; Mon,  1 Feb 2021 10:25:16 -0800 (PST)
Received: by mail-pj1-x1030.google.com with SMTP id kx7so101544pjb.2 for <dmarc@ietf.org>; Mon, 01 Feb 2021 10:25:16 -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=VnqjQTY59vG9dmPLLZIkyS39Tsip5Io7Xrinh8T+Eog=; b=j13cqf8WfTk2ouNV7RYuDGAmRZFTWkBipCVQZ8n87PY+cQUDPcGlRl0CL4LJZ71kjT eyWENkZFkI93KL3uGyPx0udQ/z0OPpE8MleFF/JeeqjDVH74UA8gWIY+Gr/Z/yf4qD6n 6UAA29CAgCs1T1+dOaHbbNmqXTrXibONcEZMvKq3BKWOdI86Pfu5W3HYCe3tp9FSKJiG 7DrXgLF2E/NR+/3T643291wW2EhMXbI6JtLJM5wKfrE37edESEialaPvy3jwZKrIfptE uVDX27Xfon4iPlOfrgu512gMCTuN6BuDWLJTRT9tn+FwC48vdcX+qBzfAzUmxoz8c2en tzag==
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=VnqjQTY59vG9dmPLLZIkyS39Tsip5Io7Xrinh8T+Eog=; b=toU+NWC9EPpbXX+Nsv9yEvYa8L/7epzaN4zh6m4DYLwNIf1NAMtfBTg105pTB2OFWk pihxApMHe8NcdxsDbzd0vIBO5eYxqKJajQpB6MHRx4G7l64TAGygiAud3Xccs6m7D6lu GPGNQdvGo0u4X7psBRhAHPAtIp1+m3QQirXmF7iAyaQgyNoWMyNy/WqoW9peyA0K3EWE uFA/NonTYe09g0NBJyhNRyo7JXcfutsUrjq4VUYivmYNFEwfe9UdqjwTL/MZtvdSXnQf CCIE7tBKRn0doGpQa/Z4Ilch7D/yVzU0Qa5+75lCORjeh6QEuK4ufdVyHYkLIom9iRLC JsIw==
X-Gm-Message-State: AOAM532VUc0DHwdionZBE0HRNP3swGsWwkAXbudKp9Yb+s7OxO/t3CB8 UJMSZJYTpXL8Mgz1JB09OGh2V/drsBWMsg==
X-Google-Smtp-Source: ABdhPJyUCTZh8nHOjyfLvzjmuZUkitIsroljB8iAQM6Poxt/+lD6YXpsmYCTiPIYO/xCys8NLaVhaw==
X-Received: by 2002:a17:902:b58f:b029:e1:6a9:f744 with SMTP id a15-20020a170902b58fb02900e106a9f744mr19046593pls.1.1612203915743;  Mon, 01 Feb 2021 10:25:15 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id bk18sm82664pjb.41.2021.02.01.10.25.14 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 10:25:14 -0800 (PST)
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> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com> <379e4493-1287-9dd5-5c8f-ae5adf949cbd@tana.it> <9aea1615-64a5-a310-b8c7-83ec0c316dae@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <2f1cd9ea-487c-10a5-3fdf-2f4135574b51@mtcc.com>
Date: Mon, 1 Feb 2021 10:25:13 -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: <9aea1615-64a5-a310-b8c7-83ec0c316dae@gmail.com>
Content-Type: multipart/alternative; boundary="------------A4C498D7CA80A693B3171748"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/hImOet_x0sKykRZ_Sd60lbO3PQ8>
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: Mon, 01 Feb 2021 18:25:28 -0000

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


On 2/1/21 10:13 AM, Dave Crocker wrote:
> On 2/1/2021 10:08 AM, Alessandro Vesely wrote:
>> On Mon 01/Feb/2021 17:38:07 +0100 Dave Crocker wrote:
>>> Consider the challenges to ensuring a DMARC pass.  That's a pretty 
>>> high barrier to entry against generating reports.
>>
>> Well, if a mail site is unable to get a DMARC pass, they have more 
>> urgent problems to solve than setting up aggregate report generation. 
>
>
> No, they probably don't have more urgent problems. Sites choose not to 
> adopt DMARC for a variety of reasons. It's probably a good idea to 
> respect that variety.
>
> The model that a receiving site is not allowed to report DMARC traffic 
> unless that site is also generating DMARC authentication is 
> Procrustean.  And as I noted, is likely counter-productive.
>
There is no such thing as "DMARC authentication". The paragraph quoted 
is poorly written and should be rewritten to say that the report should 
pass either SPF or DKIM authentication as I wrote in issue #98. This has 
nothing to do with the DMARC at all. And if requiring authentication is 
"religious fervor", I really don't know what to say.

Mike


> I understand the zeal that drives a lot of the effort to promote 
> DMARC, but the danger with aggressive proselytizing is that it changes 
> from serious technical and operational evaluation into purely 
> religious fervor.
>
>
> 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

--------------A4C498D7CA80A693B3171748
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 2/1/21 10:13 AM, Dave Crocker wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:9aea1615-64a5-a310-b8c7-83ec0c316dae@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div class="moz-cite-prefix">On 2/1/2021 10:08 AM, Alessandro
        Vesely wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:379e4493-1287-9dd5-5c8f-ae5adf949cbd@tana.it">On Mon
        01/Feb/2021 17:38:07 +0100 Dave Crocker wrote: <br>
        <blockquote type="cite" style="color: #0000a0;"> Consider the
          challenges to ensuring a DMARC pass.  That's a pretty high
          barrier to entry against generating reports. <br>
        </blockquote>
        <br>
        Well, if a mail site is unable to get a DMARC pass, they have
        more urgent problems to solve than setting up aggregate report
        generation. </blockquote>
      <p><br>
      </p>
      <p>No, they probably don't have more urgent problems. Sites choose
        not to adopt DMARC for a variety of reasons. It's probably a
        good idea to respect that variety.<br>
      </p>
      <p>The model that a receiving site is not allowed to report DMARC
        traffic unless that site is also generating DMARC authentication
        is Procrustean.  And as I noted, is likely counter-productive.</p>
    </blockquote>
    <p>There is no such thing as "DMARC authentication". The paragraph
      quoted is poorly written and should be rewritten to say that the
      report should pass either SPF or DKIM authentication as I wrote in
      issue #98. This has nothing to do with the DMARC at all. And if
      requiring authentication is "religious fervor", I really don't
      know what to say.</p>
    <p>Mike<br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:9aea1615-64a5-a310-b8c7-83ec0c316dae@gmail.com">
      <p>I understand the zeal that drives a lot of the effort to
        promote DMARC, but the danger with aggressive proselytizing is
        that it changes from serious technical and operational
        evaluation into purely religious fervor.<br>
      </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" moz-do-not-send="true">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" moz-do-not-send="true">dave.crocker2@redcross.org</a></pre>
      <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>

--------------A4C498D7CA80A693B3171748--


From nobody Mon Feb  1 10:52:20 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 263863A140D for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:52:16 -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, FREEMAIL_FROM=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 LXWGYreeI88l for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 10:52:14 -0800 (PST)
Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (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 B126C3A1402 for <dmarc@ietf.org>; Mon,  1 Feb 2021 10:52:14 -0800 (PST)
Received: by mail-ot1-x32f.google.com with SMTP id f6so17317952ots.9 for <dmarc@ietf.org>; Mon, 01 Feb 2021 10:52: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=LCMusnIPY8LWnTuVjBjG55H9SAHIwIL06DAAshbUzpM=; b=a3EH4/5e0CbhOH/sslcu8S/QbrDXt4RBRJgQ8BiV/QEJWXrReK/Ouam8i6Z1ca2R3C aN9/FdT+72OdJsy7LYPa7BGiveuuKeD7dVGMrsA//x+2hiT/XPSkTeps8/qyZdIRQBaK QLP1J7U0+ak+/KMJfV4A0rnf2e+Eusms/i0AJpD/Og2SADcC4ZHxV0j9mhsZcBOoTPp4 0HAT6c40GeocAYqA0XYs1p8uahmwa+pDSo/RlA5wtiATRr3JGn40e5NKjRXTsni9t8uj xAGXGt6JJhDBUYcrJaHbSIcTIL4uV/oBPIRingGNDVgg+Fi2LLI10uMwJPmjnbpqaBux J0WQ==
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=LCMusnIPY8LWnTuVjBjG55H9SAHIwIL06DAAshbUzpM=; b=Tuwxa59QSmFbolJpoNJRn1WAHvrbboE0xAFr5mqrHQ9j5R2ClTOl/M3dhZyaC8LYeI sLSbjTs6AdTEcjntYWLmhuuvSkl07AKo0hUSjJrYT/FgW/g+usJcxgCfqo9/DG45Ljel PxxqQYzhnxz6BFQCwmFb/tv7YKQ6RGluhVMnPeJtj6IdyMWRUg/h+8FpWWQIYO/UpbU2 t2lmNy2lH1a5oiW+t09TLXJos1etildCRNeLBI+B3VJCE6y86R4C4KhWRDeZSgtVqXBz GiCC8FXekwLyQ4y7q+KRGGtCEWpfn3+OP1pvJj9mM7W3CIT/Vy67YntkQBNKjMsrcf/y 56hg==
X-Gm-Message-State: AOAM5332fUaI6+sLIjvBSkfsHL3mmXBJaWaUgiDpbHa8cvGgCqPT73FT UVMaI98u7kkheXa4Z96OwUH/Il1b7qujCg==
X-Google-Smtp-Source: ABdhPJyj129HkwVKa4UuJrbQcJP/t7Nwski8pcJd2+ABokom+bTwTHNPtlsYAuSAbSiQ/lmixsqVLg==
X-Received: by 2002:a05:6830:13ce:: with SMTP id e14mr12579406otq.356.1612205533778;  Mon, 01 Feb 2021 10:52:13 -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 q195sm3804296oic.15.2021.02.01.10.52.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 10:52:13 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, 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> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com> <379e4493-1287-9dd5-5c8f-ae5adf949cbd@tana.it> <9aea1615-64a5-a310-b8c7-83ec0c316dae@gmail.com> <2f1cd9ea-487c-10a5-3fdf-2f4135574b51@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <96336f0f-a93d-a61f-c691-ce2a01f04d11@gmail.com>
Date: Mon, 1 Feb 2021 10:52:11 -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: <2f1cd9ea-487c-10a5-3fdf-2f4135574b51@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/XHitquqX-8MBDKErE10n5hQwOjY>
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: Mon, 01 Feb 2021 18:52:19 -0000

On 2/1/2021 10:25 AM, Michael Thomas wrote:
>
>
> On 2/1/21 10:13 AM, Dave Crocker wrote:
>> The model that a receiving site is not allowed to report DMARC 
>> traffic unless that site is also generating DMARC authentication is 
>> Procrustean.  And as I noted, is likely counter-productive. 
>
> There is no such thing as "DMARC authentication".
>
Actually, there is.  DMARC's requirement for alignment with the author's 
From: field domain name asserts a specific bit of authenticated 
semantics that does not exist elsewhere.


> The paragraph quoted is poorly written and should be rewritten to say 
> that the report should pass either SPF or DKIM authentication as I 
> wrote in issue #98.
>
It might be written better, but its requirement is for support of 
applying DMARC to generated reports.  That's more than just requiring 
SPF or DKIM.

This is separate from not asserting the requirement at all, of course.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Mon Feb  1 11:48:39 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 BAD093A1417 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 11:48:37 -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=47Qc2Ilq; dkim=pass (2048-bit key) header.d=kitterman.com header.b=eTzhmIk0
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uDF6ctCN3Xxs for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 11:48:35 -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 CB0353A1412 for <dmarc@ietf.org>; Mon,  1 Feb 2021 11:48:35 -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 86A90F8020B for <dmarc@ietf.org>; Mon,  1 Feb 2021 14:48:33 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1612208913; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=gAXJZo98vFZ7jobysqdFdbwhkUzaRGnbKHk7+Jr58AA=; b=47Qc2IlqtdE/dheV+60ks/WyRbK8KmXdep2Iej+5YQDy034THR66rRhtQwGi42ECYgXaM BqL8eV2P+AKvkATCA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1612208913; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=gAXJZo98vFZ7jobysqdFdbwhkUzaRGnbKHk7+Jr58AA=; b=eTzhmIk0A222gHg/IZL03RO1+SDS02AvbA8iUTwekV3kJMMUFDlgfmxekPG6w2rmSNwdn w7wLVg3+P4aX3LY4dwx4pN9QM45A3pYFeKzNzGWqSg+Ph8dGU1soTZG9zEf0MekmTvN0ANo dqIN9JtoF5lPrX89koFUEwgprKVqPkmfL3n05hbjFTzL4fbALJkQfDdoxhe3kfuaRxp1ZTC 9jT4q3Ls7TRJE3kP9y1URYk07inw622el/w2bY36j4ToR1YiJDxO5kfh0cM6JkbK5z5YZF2 9Lum4soW/8jSKc2qoH2QAihdwTH6H6xhZEWdyrgqT6K2plK/nIScu3ISkoEg==
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 16D33F80208 for <dmarc@ietf.org>; Mon,  1 Feb 2021 14:48:33 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Mon, 01 Feb 2021 14:48:32 -0500
Message-ID: <4489192.U1a6Vm75Xl@zini-1880>
In-Reply-To: <babf1538-5172-f101-d5e4-c4fa33dea495@tana.it>
References: <20210130212339.447316D04763@ary.qy> <1654196.ygyh55z74P@zini-1880> <babf1538-5172-f101-d5e4-c4fa33dea495@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/kA1EbIKv2GokGGrOp7gn5ofubFc>
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 19:48:38 -0000

On Monday, February 1, 2021 7:17:20 AM EST Alessandro Vesely wrote:
> On Mon 01/Feb/2021 01:10:01 +0100 Scott Kitterman wrote:
> > 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.
> 
> Perhaps Courier-MTA is not so properly implemented, but when mail from is
> empty it just omits the corresponding Received-SPF: header field.
> 
> OTOH, properly implemented SPF verifiers could skip producing a Mail From
> result if the helo identity was verified successfully.
> 
> In conclusion, the idiosyncratic requirement can hardly be implemented.

I have no idea why you would think that.  If mail from is null, use 
postmaster@HELO domain  as mail from is trivial to implement.  If an SPF 
verification implementation does not correctly implement RFC 7208, the 
appropriate solution is to fix it, not add work arounds to DMARC.

That said, I don't think there's harm is using HELO results in DMARC if they 
align, but I don't think it will come up very often and isn't worth worrying 
about enough to rewrite that part of the DMARC specification.



> > 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.
> 
> It makes sense to add a section that modifies RFC 7208.  See below.

No.  Changes to SPF are out of scope for the working group.

Scott K

> On Sun 31/Jan/2021 03:27:41 +0100 Douglas Foster wrote:
> > My data, cited previously, indicates that HELO can be useful for both
> > blacklisting and whitelisting.   It should not be ignored.
> > 
> >> 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.
> 
> Does that mean that an implementation that uses the RFC5321.HELO identity
> without taking care of whether RFC5321.MailFrom is empty is *atypical*?
> 
> Please note that all the text occurring before that paragraph would suggest
> that any authenticated domain, if aligned, would do.  The quoted paragraph
> comes as a note, by surprise, without bringing any rationale.  That text
> needs to be revised whether or not we remove the idiosyncrasy.
> 
> And the only rationale learnt in this thread is that one could type whatever
> it wants in the helo/ehlo command, as if that weren't true for the whole
> SMTP session.
> >>> 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.
> 
> "Postmaster" is necessary, because SPF mechanisms can refer to the local
> part.
> 
> The SPF part I'd modify, however, is Section 2.3, where it says:
> 
>                                 If a conclusive determination about the
>     message can be made based on a check of "HELO", then the use of DNS
>     resources to process the typically more complex "MAIL FROM" can be
>     avoided.
> 
> I'd append to that sentence:
> 
>            , unless downstream filters need it anyway.
> 
> Since we're at it, that paragraph continues with the following sentence:
> 
>              Additionally, since SPF records published for "HELO"
>     identities refer to a single host, when available, they are a very
>     reliable source of host authorization status.
> 
> Isn't that the exact opposite of what many of us are claiming?  And is it
> legit for a proposed standard to quietly counter an existing proposed
> standard without some kind of rationale?
> 
> >>> 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.
> 
> OTOH, relaxing the requirement that the SPF HELO identity be used only when
> MAIL FROM is empty brings no incompatibility.  It's just a cleanup.
> 
> 
> Best
> Ale





From nobody Mon Feb  1 12:34:58 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 12F063A146D for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 12:34:57 -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 HkbR_Wp7uZle for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 12:34:56 -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 3D30A3A146B for <dmarc@ietf.org>; Mon,  1 Feb 2021 12:34:55 -0800 (PST)
Received: by mail-pl1-x632.google.com with SMTP id s15so10686761plr.9 for <dmarc@ietf.org>; Mon, 01 Feb 2021 12:34:55 -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=+VuOb/b190q5AZ6q+cIcslqtXxUBqkdJpBL72obANz8=; b=bYnJmM8EygEFyYIBxd7U/KmE18vt4tIBs/zwtdf3i+suSLGXfLjk0VNeRcmgouMunj U/D6yeCOdWoZhmhCvb2KT7NuunwrdRGggMztgRYytfziyr05dZjy5AzDTNISTlkJ0YZj GBZBuXbPgGbU56tD6W8H5S4EV1qxLt4JY64RDDtaEiDnY/Dciuhp/yFVY1EFgp2Sf78J K1O7qEJoP156/TDAOvo/5I3B9pgl9GYpPQ17YWZCjvFe9YsqiMXjph5aGerVhcYcfGuF cGiqtLvd8xTme+IyeQMxnPvg/WHDfDrGrygn3rj19GXbtY23AA3x8tAOg6XjiE6TlNTy u4lg==
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=+VuOb/b190q5AZ6q+cIcslqtXxUBqkdJpBL72obANz8=; b=Ga9vuxYAY3ShUCHSADa2OlmiguNdz2SCga5rEjygWBSzaFk+TbUDBPrCOxXDz6dqfA rz4sjOtb/JvZ9BChkXscpDt8cDifwYIhrmLQKZ2nXutSUsXKYMW4+mGJi2S5yYrtdkEO 5m9GSdRhzcZSrJJtVd5z9jyQqpaJDPZHInGwumPHd8ipz1OyxopUf5D23ohA2MFquPsB uCV9h+JBD94rimLyy2limqcGAUVGpd/xSDkQt7VcoIPvArQzY43g9O7vuIOIPLb+A6QU ln6LTqxqUeL3d9qTm4KNCWXIEaKGWRtFl6cbQqiuzH2J87MMkPtFhQCZqQ4emnxatsOF yl6Q==
X-Gm-Message-State: AOAM532m8gQfGyM5MVLgQQD8zqq2Xe1LsiQ99E8JduT9ytbtU2VSHGKI l15tPhM7fGNJqgfR3HHB/I8fXiasAojttg==
X-Google-Smtp-Source: ABdhPJxV6yXQ6dPzSmi4okwUuFsjQMgvbwS9VVL4vhoahHVQ6Hf0c3y5lH1fHfDLeoXNb1lOR+WAHw==
X-Received: by 2002:a17:902:f683:b029:de:18c7:41fa with SMTP id l3-20020a170902f683b02900de18c741famr18824805plg.57.1612211695094;  Mon, 01 Feb 2021 12:34:55 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id b18sm19664667pfi.173.2021.02.01.12.34.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 12:34:54 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, 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> <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com> <379e4493-1287-9dd5-5c8f-ae5adf949cbd@tana.it> <9aea1615-64a5-a310-b8c7-83ec0c316dae@gmail.com> <2f1cd9ea-487c-10a5-3fdf-2f4135574b51@mtcc.com> <96336f0f-a93d-a61f-c691-ce2a01f04d11@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <f4744e4a-f96e-4956-ff54-6146182f0d22@mtcc.com>
Date: Mon, 1 Feb 2021 12:34: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: <96336f0f-a93d-a61f-c691-ce2a01f04d11@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/eJf3Yo-ME8_GQ8_w8BC73XT9r48>
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: Mon, 01 Feb 2021 20:34:57 -0000

On 2/1/21 10:52 AM, Dave Crocker wrote:
> On 2/1/2021 10:25 AM, Michael Thomas wrote:
>>
>>
>> On 2/1/21 10:13 AM, Dave Crocker wrote:
>>> The model that a receiving site is not allowed to report DMARC 
>>> traffic unless that site is also generating DMARC authentication is 
>>> Procrustean.  And as I noted, is likely counter-productive. 
>>
>> There is no such thing as "DMARC authentication".
>>
> Actually, there is.  DMARC's requirement for alignment with the 
> author's From: field domain name asserts a specific bit of 
> authenticated semantics that does not exist elsewhere.
>
>
>> The paragraph quoted is poorly written and should be rewritten to say 
>> that the report should pass either SPF or DKIM authentication as I 
>> wrote in issue #98.
>>
> It might be written better, but its requirement is for support of 
> applying DMARC to generated reports.  That's more than just requiring 
> SPF or DKIM.
>
> This is separate from not asserting the requirement at all, of course.
>
The entire thrust of the paragraph needs to be rewritten to what the 
senders and receivers must do. It does not require invoking the policy 
lookup since it can make the determination to reject reports that do not 
authenticate with either SPF or DKIM itself. The section also needs to 
clarify whether spoofing the envelope-to domain in the report contents 
is allowed or not. I do not think it should be.

Mike


From nobody Mon Feb  1 13:58:32 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 33A663A150E for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 13:58: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 MlpIbnZo9K45 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 13:58:29 -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 ACDE03A150D for <dmarc@ietf.org>; Mon,  1 Feb 2021 13:58:29 -0800 (PST)
Received: by mail-qt1-x82a.google.com with SMTP id l23so13481247qtq.13 for <dmarc@ietf.org>; Mon, 01 Feb 2021 13: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;  bh=mAnO6zgP1mt/4+iVJ+zoFQqBuJRIJP5RybSNzsyXeII=; b=jQKip06HhDbR09pZxwgpu6wJ6oVYJh5sNSmsOeJk2iPPb/9rR6qggso2pCflifqDNR 8mvn5AEwTOL4ML16ZRmIr0P7nZoiXkWnfDegiMVPDTbaaZmuXT74EIDxixdREW75539W I1ek+4EHcGlohQth3pLpSNuEUlRaSpHpLzy0YIHCak7+Bzo/E22Kml58OcIM0nIcCqBn ygfo35uNddBxCBmVftO5dUkaZ8yc/Utz7Waz7tA1waVhn6xdSYn+odp7b8G+qCbomRD2 9Xim9eVkFq02Wzeizzi87KXuBnj/WXM8LFqlU8alAPxZjed7XrsmLQvuqZjkt5Udu1Cw txDg==
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=mAnO6zgP1mt/4+iVJ+zoFQqBuJRIJP5RybSNzsyXeII=; b=Cyo1dpRN4on7vM8jElVItePQu/HjbMQmlJcZqTTnP+fqSryyBX/nfBmhBVp5SHC/sD 3n+cyXLQWtJfkoisjnR2cC2ixlXwFYVsyW4X5eoquk7eS7IUc+lGq1zrNT0MGmyU6ttJ KJOYNTyn0VNPM1r2R/P8riFPUXBIwuud5xjRHepzOqiJV7GB1u3FQJzSQfBck/Dj0ngA QIDnh7gI4ydcnP9LUQAlLzSxjpPq/iIf41y66lAnUiWaHjVq8hVb1R6Jx8grBOhtFgAt eq11yZv4tihkiw53UcdrT57iJbfvqReNjSHHQ2KAnFfOw+Z9DfIU5wHmhs/j8Uce3pPA q14w==
X-Gm-Message-State: AOAM533pOP3d0SYxeJJKEs25iflzxEMmQM+3CLAEukxxaEuTMdZ69Ztl R/OuFVVbvI8AAaMQwEPD2fAOxgOQExIMaXYXCISO1dYP3A4=
X-Google-Smtp-Source: ABdhPJz+E7ouhDSkGWLevChSifzJpPQn8OU9NhDpFbR+JcrrlhLXLByHY4I/0FzC4b0Wzf/RNA9TjsnE5Fza9/NaCbU=
X-Received: by 2002:ac8:67ca:: with SMTP id r10mr17253276qtp.267.1612216708251;  Mon, 01 Feb 2021 13:58:28 -0800 (PST)
MIME-Version: 1.0
References: <49b248dc-91a7-7f2d-ba28-72fe8d6d356a@tana.it> <20210131200238.931356D11D79@ary.qy>
In-Reply-To: <20210131200238.931356D11D79@ary.qy>
From: Dotzero <dotzero@gmail.com>
Date: Mon, 1 Feb 2021 16:58:17 -0500
Message-ID: <CAJ4XoYe54BLvHOn3vuPr9VUPmqPUTq_Pdt91jOSRsUAfL+uO5A@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000032423705ba4d74f7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/bZN38HKfpiGKLE2IejVsidd3Fu4>
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: Mon, 01 Feb 2021 21:58:31 -0000

--00000000000032423705ba4d74f7
Content-Type: text/plain; charset="UTF-8"

On Sun, Jan 31, 2021 at 3:02 PM John Levine <johnl@taugh.com> wrote:

> 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.
>

My experience is that most failure reports are provided through private
channels where there are contractual agreements in place to deal with
potential privacy and legal issues. This may be through intermediaries or
direct between the parties (sending organization and receiving
organization).

Understand that the DMARC effort came about because the original
participants felt it was useful in the private exchange of information
between senders and receivers. We felt it was better as an open standard
rather than as a private club.

>From my perspective it is unfortunate that we can't seem to find a way to
implement a system where failure reports are available other than through
private channels.

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.
>

I disagree with John about failure reports not being useful.  I have found
failure reports to be extremely useful in anti-abuse efforts. The value can
range from takedowns of images and links to maliciousness to shutting down
sources of maliciousness.In some cases it has proven useful to law
enforcement as documentation of activities.

Unfortunately, I think addressing some of this has to be beyond the scope
of the current effort.

Michael Hammer

--00000000000032423705ba4d74f7
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 Sun, Jan 31, 2021 at 3:02 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 rgb(204,204,204);padding-left:1ex">In article &lt=
;<a href=3D"mailto:49b248dc-91a7-7f2d-ba28-72fe8d6d356a@tana.it" target=3D"=
_blank">49b248dc-91a7-7f2d-ba28-72fe8d6d356a@tana.it</a>&gt; you write:<br>
&gt;Rate limiting usually implies a number of buckets.=C2=A0 They are manag=
ed by <br>
&gt;imposing limits per time periods, which can be either server-global or =
per <br>
&gt;bucket.=C2=A0 Normally, for MSA usage, one has one bucket per user.=C2=
=A0 I have never <br>
&gt;implemented failure reporting, but I&#39;d guess buckets may vary.=C2=
=A0 Besides the <br>
&gt;signing domain (which determines the report consumer), the receiving ad=
dress, <br>
&gt;the sender and the spam flag may deserve their own buckets.<br>
<br>
The only one that matters for DMARC reporting is the recipient<br>
address, since the purpose of rate limiting is to avoid overloading<br>
the recipient mail system. I wouldn&#39;t worry about trying to send a<br>
&quot;representative&quot; set of reports.<br>
<br>
Keep in mind that very few people send failure reports at all. <br></blockq=
uote><div><br></div><div>My experience is that most failure reports are pro=
vided through private channels where there are contractual agreements in pl=
ace to deal with potential privacy and legal issues. This may be through in=
termediaries or direct between the parties (sending organization and receiv=
ing organization). <br><br></div><div>Understand that the DMARC effort came=
 about because the original participants felt it was useful in the private =
exchange of information between senders and receivers. We felt it was bette=
r as an open standard rather than as a private club.<br><br></div><div>From=
 my perspective it is unfortunate that we can&#39;t seem to find a way to i=
mplement a system where failure reports are available other than through pr=
ivate channels.<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);pa=
dding-left:1ex">In my<br>
experience few of them are useful. Most of mine are ordinary mailing<br>
list messages where the failure is not surprising and does not mean<br>
that anything needs to be fixed.<br></blockquote><div><br></div><div>I disa=
gree with John about failure reports not being useful.=C2=A0 I have found f=
ailure reports to be extremely useful in anti-abuse efforts. The value can =
range from takedowns of images and links to maliciousness to shutting down =
sources of maliciousness.In some cases it has proven useful to law enforcem=
ent as documentation of activities.<br><br></div><div>Unfortunately, I thin=
k addressing some of this has to be beyond the scope of the current effort.=
<br></div><div><br></div><div>Michael Hammer<br> </div></div></div>

--00000000000032423705ba4d74f7--


From nobody Mon Feb  1 15:12:04 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 9A9773A158E for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:11:58 -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=Ek08h6tl; dkim=pass (2048-bit key) header.d=taugh.com header.b=u9Du2XVP
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qnFDz8qNeUj for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:11:57 -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 C77E63A157B for <dmarc@ietf.org>; Mon,  1 Feb 2021 15:11:56 -0800 (PST)
Received: (qmail 82671 invoked from network); 1 Feb 2021 23:11:55 -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=142ed.60188abb.k2102; bh=Ex9I6mWIMVNptGB0YXBTmdBl9JnEYv0IecQf7f9sOEo=; b=Ek08h6tlgcSUjYA3ZeZ5THbcHIwXMZpzvb12c6iWuEgYLNxQuz5Y41Kzr7Fx82txoK8CPzJizsLHO5UQU5X695peNsBNww6+jxltcJ/o1e2BjenUTWjCqax4z6u0yrMkvabHpZ7MYWYUnG1bbkCYx5RoaKjw316diKuQUGaeLRreRha4CKT5kuvjUA48pyyUZ/SPn4ykavJweGyMbBTgTy3nOdc+PxUBVDbQuu7lBwz1bQeGm5gTVLi3z3BUn+IU5rM/O4Zgb9FZo+cO5IswIzx/yxGhnr2FBFyjeTEBI7yD7bQwFRZFfu33BlazcgvakrRjhkOXxsQ+8U6g0ekADA==
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=142ed.60188abb.k2102; bh=Ex9I6mWIMVNptGB0YXBTmdBl9JnEYv0IecQf7f9sOEo=; b=u9Du2XVPlgN2NWx0sGD6DjbHNVSxV85VQvtnl+tP6EBGQxm+/PJHx0wPSRGroCbMfYJ0Bg2zyQ4sEDHd/bFFcg9cAfDcSBcJhwawUWiNvCzMlvIOstyKpJ5svfiAeSzpDnEcUcLvDVNlqk1kVg1lkUjB/VYtrTyH+6CPS1Lq/RL/aK/EJGQKzFsYSaIILiZbn92W263qERdNhaFH4ZLlX4zU2vHvLF10NsrjGMSsdLO8qxiZCmmT/7fcOAv3qRGks4kSX/adhpnKb8BLc6HcwWga3b3PEUpkE236+26hrJmuEDa4oGWbMUk2uT98h2BgV8JyaympCX0GAOHa9I/I3A==
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; 01 Feb 2021 23:11:55 -0000
Received: by ary.qy (Postfix, from userid 501) id DAE426D208E1; Mon,  1 Feb 2021 18:11:54 -0500 (EST)
Date: 1 Feb 2021 18:11:54 -0500
Message-Id: <20210201231154.DAE426D208E1@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <babf1538-5172-f101-d5e4-c4fa33dea495@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/g4TSorE6DOPXbVhx70KrPifjuq8>
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 23:12:03 -0000

In article <babf1538-5172-f101-d5e4-c4fa33dea495@tana.it> you write:
>On Mon 01/Feb/2021 01:10:01 +0100 Scott Kitterman wrote:
>> 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.
>
>Perhaps Courier-MTA is not so properly implemented, but when mail from is empty 
>it just omits the corresponding Received-SPF: header field.

That's a peculiarity of Courier.  My MTA adds an SPF clause in the A-R header
whether or not there's a null bounce address.

>OTOH, properly implemented SPF verifiers could skip producing a Mail From 
>result if the helo identity was verified successfully.

No, they could not.  That's not what the SPF spec says.

>It makes sense to add a section that modifies RFC 7208.  See below.

Please, can we stop the Mission Gallop?

R's,
John


From nobody Mon Feb  1 15:21:09 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 9E1463A1586 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:21:08 -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=fSYP1o1g; dkim=pass (2048-bit key) header.d=taugh.com header.b=u53TdxuM
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qP-2NFileqJj for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:21: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 1998E3A1585 for <dmarc@ietf.org>; Mon,  1 Feb 2021 15:21:06 -0800 (PST)
Received: (qmail 84904 invoked from network); 1 Feb 2021 23:21: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=14ba4.60188ce1.k2102; bh=S/0IOC6WOiysfA5BAu5riwlCY2I84i8xSgKqGC4jxH8=; b=fSYP1o1g0WE6264eRqEVAxHAD4R7krBVnLI6sQFfVH7AJ6TsXKZK+MOf4XpM9qz7iyGdnyvmnKV/ET9vEJyjfISfVZNgPRHOPGG6J9USly/tV8iUhHwC8UdEnzzK/noqvwFWuxh4LPg5/nhbsN1EoahEjE7P23Dd37zvus7uA50LFAoGKi0mX8a9KHca1DcxTDINilQ9cCZeAmHWSy9aYe/str5dZ9vJxayh9aVX7MuQ3YBaGMFinVG5tXKVdWdZAmnzBNCYQzK8JiTRQvKEs7ZmxfqF6xTUHK6HhDGNlsYY4k3r9k7rWpNv1zL86A97Xa0n5pQBh5fIba9Ffe7/6A==
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=14ba4.60188ce1.k2102; bh=S/0IOC6WOiysfA5BAu5riwlCY2I84i8xSgKqGC4jxH8=; b=u53TdxuMWtVX2EQIBixFu9r+3PQmQts78pt+Yj4ZNbIbVrmz92QlPybuaUGnTuZDKxgHOazEfUCKs4w8jY0F5P5HkekDs3+PK8OapDj8CXGAkdrYpxBLAkVx20U/taRMPimNOxRkoJPkr4cMQ5GVLngPIppRcaO8WNiEwyRdABjUFEznUq9Qk5TyJ7c6kRhGqSJ4D+HFOiQE1SY/pNv/sr15rfEgucP/OFTQ62MXJgepG98gVgnc+jmXXbtRNvdEUH4vYIDRM2UYVFPgnY+xCOHoYHuMnMVEtJVpU5fEMeHKaAFOOh4N+Uy5Gtc93S+krw2MEXI0y8knMufghim7mA==
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; 01 Feb 2021 23:21:05 -0000
Received: by ary.qy (Postfix, from userid 501) id 1931D6D20971; Mon,  1 Feb 2021 18:21:04 -0500 (EST)
Date: 1 Feb 2021 18:21:04 -0500
Message-Id: <20210201232105.1931D6D20971@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dcrocker@gmail.com
In-Reply-To: <dc398e7b-2fc6-f418-4e66-456a6c1189d6@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/WsoLtrU7czQDEg1R9Pj0Kz0mlq0>
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: Mon, 01 Feb 2021 23:21:09 -0000

In article <dc398e7b-2fc6-f418-4e66-456a6c1189d6@gmail.com> you write:
>-=-=-=-=-=-
>
>On 1/27/2021 7:17 PM, Steven M Jones wrote:
>> 3.3. Transport
>>
>>    Email streams carrying DMARC failure reports MUST conform to the
>>    DMARC mechanism, thereby resulting in an aligned "pass". 

>Mostly this will discourage reporting.  Legitimate reporting.

It's been like this for a decade.

>Consider the challenges to ensuring a DMARC pass.

Looking at the results I get (and understanding that the results that
arrive via private agreements are likely different), I get reports
from linkedin.com and seznam.cz that are aligned via SPF and are DMARC
reject and none, respectively, and from antispamcloud.com that are
totally broken, not even multipart/report.

I find it hard to believe that if you are going to enough effort to
maintain the data to create and send reports, you can't figure out how
to install an SPF record for your reporting domain.

R's,
John


From nobody Mon Feb  1 15:21: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 695673A1586 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:21:54 -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=HjVQdmb5; dkim=pass (2048-bit key) header.d=taugh.com header.b=nEm5M515
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1bbY3-gKXsZ for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:21: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 D47213A1587 for <dmarc@ietf.org>; Mon,  1 Feb 2021 15:21:52 -0800 (PST)
Received: (qmail 85096 invoked from network); 1 Feb 2021 23:21: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=14c66.60188d0f.k2102; bh=p720LHMkp3BB8Jro63wpf3xOpIz8vUVu7H67cKye6sI=; b=HjVQdmb5ghZs9IXdViYE8is3zNlBVaWj4DS++SD85hCfq0cbcnoaJpsGANxaV1Ps66I5mUL7BCgI/5TptuX2yqeEB/HNfamnby11L9zwtZ4Eetg8beldvgF8UwoRxHyKX6KBaHUnUDn/HNeTK52goqqemkGqmp/K+Xro7bbFSslnBn9FfgrMSaIys4yyyz72Om/BpuYcQE0GlpXtv7exqEyPAlLDjduwJ1w7NAOu9JIPvQ+iBsF2jAf4o6/p4ae1v4PIIIQHZwKNVS0qwS9XvI3njdX/RKX6/4ba/9880Gg6K/SmTuu4Q2AoGzM7izTCRNHOj1/g2c8PQtJr+aWbLg==
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=14c66.60188d0f.k2102; bh=p720LHMkp3BB8Jro63wpf3xOpIz8vUVu7H67cKye6sI=; b=nEm5M515eAKo/SFAdfHLVAXVStV/jX3LzmgMt0x0kB9aXxJbk2D5tdREZg5IZzpLTJfjlWc47wVcvxFogSkJ5ASSQO7BMBGiI6PFDW5ZA5KYpWRRyKmJ1EE0viteLsl/ESSOrr1k2o63jcBrG/52/oZjro0lfyB+cvn47KiToxlx8Q9gzrSokvcotKrnK7aZXZEZ4LgODEqavVz+YJCMHWriLINxPlrJRvKp2DRNg2ZewqoOvU0P5Sxv3io1NbQ01JwhGPNr1zDCpxOBaSFLuANCBpD2cZT4q19TFiDRRWkHMI2eW6LzEfnSFABb3kjRD4oKLf+ba4cNmWv4dQAZWA==
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; 01 Feb 2021 23:21:51 -0000
Received: by ary.qy (Postfix, from userid 501) id E8D346D20989; Mon,  1 Feb 2021 18:21:50 -0500 (EST)
Date: 1 Feb 2021 18:21:50 -0500
Message-Id: <20210201232150.E8D346D20989@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dcrocker@gmail.com
In-Reply-To: <9aea1615-64a5-a310-b8c7-83ec0c316dae@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/vUcnSU0cfMxvSwBZ74xZCnvkswA>
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: Mon, 01 Feb 2021 23:21:54 -0000

In article <9aea1615-64a5-a310-b8c7-83ec0c316dae@gmail.com> you write:
>-=-=-=-=-=-
>
>On 2/1/2021 10:08 AM, Alessandro Vesely wrote:
>> On Mon 01/Feb/2021 17:38:07 +0100 Dave Crocker wrote:
>>> Consider the challenges to ensuring a DMARC pass.  That's a pretty 
>>> high barrier to entry against generating reports.
>>
>> Well, if a mail site is unable to get a DMARC pass, they have more 
>> urgent problems to solve than setting up aggregate report generation. 
>
>
>No, they probably don't have more urgent problems. Sites choose not to 
>adopt DMARC for a variety of reasons. It's probably a good idea to 
>respect that variety.
>
>The model that a receiving site is not allowed to report DMARC traffic 
>unless that site is also generating DMARC authentication is 
>Procrustean.  And as I noted, is likely counter-productive.

Ah, we have a semantic question.  I consider a message with p=none to be aligned.

R's,
John


From nobody Mon Feb  1 15:23:43 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 D5C6C3A1588 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:23: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, FREEMAIL_FROM=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 fNHU0BwlzUnn for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:23:39 -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 F32183A1587 for <dmarc@ietf.org>; Mon,  1 Feb 2021 15:23:38 -0800 (PST)
Received: by mail-oi1-x230.google.com with SMTP id m13so20757266oig.8 for <dmarc@ietf.org>; Mon, 01 Feb 2021 15:23:38 -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=HeaPL2jUggnNDB+mrLlJyl0OeT2AJ9GBsa34ZNCd3t8=; b=rgAlTQAAvkD7QmFuz/fzlpCP7hiViBGkzhGt4xQOxC1lMS0zGnPx8PNXP7iS2G+Vv1 N1fAdQq1B9fl9BY9qjteeN1f0u+VSRiQ7VsjG0XUqTFQKKATfw5jQUtQAVqixeqJdU9Z Ad+ujLgKl06FqoVfpc5AFV7LjUwkHjKaOdpd/4EFyhTlBXna60dCLUOdxqVkdU/U5YQK LQLWq3HiNJ9mEB/nKC7/HgvNuwDl/9iLVnWVVKjM2nDFwOmXqicDdWIRBBtABwVzzyLL njOe2Pih6GOcQ8UULjGHdsP+N5bMTtCklGzA2mp4OK3Iycqyhr7FbH23ajdFWMHoZdeo pTVQ==
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=HeaPL2jUggnNDB+mrLlJyl0OeT2AJ9GBsa34ZNCd3t8=; b=pM3n2aR5+j5/bRym/dC8cISu7Ul5xf2NBNdqfVuWbPZ6UUAklyUBYU/z+YVP0niQub tmqFFP0sK2ehJUZC5484d2lTkDTaUDv1Yj6utR47wdLENy3OzUCPLEBMrxAv4ck5e6Nb 8FC1sXUMzoPdvs779rC5Ie7SrF8UsCR9S2EuIdqCCJ+v3QS6I5C4SWO8s6gQy7fDkIdz 86U24aQ/6+fA7l+eEyZJ+gEr65v3wkMm+9Yi+XeCtsFde4tFTqUKZPW7ZC8liksWLqKn F7m/pcTxd9PUv69bLyCDKhHJDWCuEViQlcVxdIjx+iGaielwT805Zl5+0Kr39e9nl1fp yvLw==
X-Gm-Message-State: AOAM53110MJGuU5rEQ768RbEpgldfC7+fgmIfENsbrotxoqjg/13kPYg VnXHyN3QJWhxk2whpQXWCe6tHItUkxvCrw==
X-Google-Smtp-Source: ABdhPJwkLc7vxUKWyLI4bDbtS5hiVZxh9ORFgBKTpmLUtihwKTXZVvzyC+Z+xkmhmLd1CYjm7YyhWg==
X-Received: by 2002:a05:6808:4d7:: with SMTP id a23mr864558oie.38.1612221818069;  Mon, 01 Feb 2021 15:23:38 -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 e20sm4256427otr.14.2021.02.01.15.23.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 15:23:37 -0800 (PST)
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com>
Date: Mon, 1 Feb 2021 15:23:35 -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: <20210201232105.1931D6D20971@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/y9G4gybiAZqohvkx_o_JYZnpxgk>
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: Mon, 01 Feb 2021 23:23:42 -0000

On 2/1/2021 3:21 PM, John Levine wrote:
> I find it hard to believe that if you are going to enough effort to
> maintain the data to create and send reports, you can't figure out how
> to install an SPF record for your reporting domain.

Except that the tracking/reporting functions are completely separate 
from the 'signing' side of DMARC and could easily be different parts of 
a company.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Mon Feb  1 15:49: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 BDEEA3A15B4 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:49:43 -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 lSpnUHZ0XUj8 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:49:42 -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 298713A15B3 for <dmarc@ietf.org>; Mon,  1 Feb 2021 15:49:41 -0800 (PST)
Received: by mail-pj1-x1029.google.com with SMTP id g15so974171pjd.2 for <dmarc@ietf.org>; Mon, 01 Feb 2021 15:49:41 -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=1pu/gpJIPnjgNXy4OCHsClZfcuqbxUKzMtyAmaV+RI0=; b=nmGFNRD/926PTp3c4/Swl09UmndFIES5Qi1C8yfoYELGDRPc25TqPjwgT1W+6H3k13 WLVF17GGLtLjJ2t7/FYLOBgnguDYKt8bzo/WjacqheMelYMVBTrv2SjGykL5Izcqxjp3 e82pzskXYZGcKilEQUL9YGyqwteQsWtNN7j2L0RnwplMBbDbSF1LSbT89A6UEpP2ZvZQ 3CXbJeeYSOxfy04oXGaEbX6ISs3018jUVjnK3tKbJ3edDn5q1Po2mYuA58MMyitrBflx i8rqL6sLnOqMYi6dbkFr1P0D1IlsahUo13Wnm5z5DtTr2FWjiiSpLEOq7tux+aT3QpIP S72A==
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=1pu/gpJIPnjgNXy4OCHsClZfcuqbxUKzMtyAmaV+RI0=; b=fv/BVEiY4EKfHTU45AqBG2STiyhowNi4SGEY+FeihKoeSu2eb+kXp9DLpu1dJpf1L7 cUIU2MZKEtMBJ2hsjkXB3pxGMJvKsFbdP1pBTKsz/PSDXlbfx/quVkHhHg7sVbYT3RRE ItH4G6KmxwHoNcRPfbA2GlmyG9OzzSBOazOJCglpdWLBfw7ILEVpHU4FcM9PyGUWZcyo JZ2SQK7eaMkYKr+hk/UysMuVKtnTz+VneVs1OYVXX1bn2kseT8KPMouu1L3Ak73TXBqS fwcJOLXYvmv0tfxZGrT8P9T/ljc8C1BkHBYxs0qeVruJGa57JkLtghjAoFm214lBPjpv 5Gwg==
X-Gm-Message-State: AOAM532OpWnHybmeWgyrET0pbvXLUchyKrXi6YfEGu7briCuZIGYM9tL /pKPtSUKiw/IXByCyzTjvnmdAvwk7tevQw==
X-Google-Smtp-Source: ABdhPJxkCU5FWyjZRWhSoLOmjvgn5+YRM92ciAyZV7V2sdTtzsWfv5a0CyxBpbXvUuu/pPPJ1B+Qgg==
X-Received: by 2002:a17:902:b285:b029:e1:5b44:454 with SMTP id u5-20020a170902b285b02900e15b440454mr7132992plr.54.1612223380901;  Mon, 01 Feb 2021 15:49:40 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id mv14sm970734pjb.0.2021.02.01.15.49.39 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 15:49:40 -0800 (PST)
To: dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com>
Date: Mon, 1 Feb 2021 15:49: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: <41163cd5-be81-6fd7-07dd-7a474874429e@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/5GjnjAbzFpES0dMU9ghaj6QY5pA>
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: Mon, 01 Feb 2021 23:49:44 -0000

On 2/1/21 3:23 PM, Dave Crocker wrote:
> On 2/1/2021 3:21 PM, John Levine wrote:
>> I find it hard to believe that if you are going to enough effort to
>> maintain the data to create and send reports, you can't figure out how
>> to install an SPF record for your reporting domain.
>
> Except that the tracking/reporting functions are completely separate 
> from the 'signing' side of DMARC and could easily be different parts 
> of a company.
>
> d/
>
It strains credulity that one part of a company would want to send out 
reports when some other can't even sign their email. Both need access to 
the email stream for starters.

Mike


From nobody Mon Feb  1 15:52:26 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 9AB263A15C1 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:52: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, 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 k4SfruphtyFS for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 15:52:24 -0800 (PST)
Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (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 5F42E3A15BF for <dmarc@ietf.org>; Mon,  1 Feb 2021 15:52:24 -0800 (PST)
Received: by mail-oi1-x22d.google.com with SMTP id h192so20879833oib.1 for <dmarc@ietf.org>; Mon, 01 Feb 2021 15:52:24 -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=lPttU3aXipGZVLClxcqev480ADUR6TBP3ESPX99Oi2A=; b=MjnFrbp+HO68QFbEgmzLNYpc4fG8TTkKwMMMsk+MMmjoHuZFxWdxUyCqy0p8+1BGmh 6gNumvafVKguzpLiPt/U0HeATovJU2tylgeiKRPKW2FzKGAAPBmy8uMJ4NBfxorrgwSt 1pS23UFqfc/+kcpsX1XxB5mgqfPlPXK8AiQpI6BA8rgfkFzbmFxlqJR3L4w3MsKBkU/e EQ+Wqc7qZBXhPaHGmPNfZWVQowbzY1CrdC36oJJn9/0umbJ1xIAoiUY5JgFdj6yp7Scb 7H2xEW35H1yoCOk62Nj8wb3jaf/jF1211av5K3TdEEErHlnN84Xi4yXomiOCXmWg3HQo T9ww==
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=lPttU3aXipGZVLClxcqev480ADUR6TBP3ESPX99Oi2A=; b=n7g1dsvG3v+38UJQTFCteyaai9qbeD+53lXOKRaVGaix2E6n06ruOkocI4ZrP6RFLx ZgvEEZUH1n/hN8EdMHuuO4SUK2jYgaHUUdYQ+5HlDSxu5jJISJROn8ZxU9+7A3noM37o ma4fT7ywEXP6OEbUNtIdDotqCGTtQpUKzVjQjdyLp2xNZiSGR2zvPHXr7TqrI/RAts6j 5EJ6mOiOGprK4Zh7l+xa9TJ95DzF5+EwXL+WfY1Otiv2zkl43dNs26BFnVkORIoysWlq mMFHrk+ZFTiE2MfQKtH8oHnCIZzOLCK7dRvgrxMCFmm+yABihRAZdv6H1gfnxioyzwP6 J18Q==
X-Gm-Message-State: AOAM531KAycfRkf33oBIT0L6kjAHuuEYtLjGErqzIbcmZ682lea4LDtM m7dyxZJpyrJ5Cg5/q764feLh/g3DP6z2rA==
X-Google-Smtp-Source: ABdhPJziJdUdQIcAh1T/EhKp7wy8e4PYPyJ5GrgvGBQhIRXmYklanyQQjoJUjnKe23v0En1hMIeWpA==
X-Received: by 2002:aca:4c6:: with SMTP id 189mr877474oie.73.1612223543646; Mon, 01 Feb 2021 15:52:23 -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 v9sm598432oiv.41.2021.02.01.15.52.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 15:52:23 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <8ee2ca5a-75ef-16f2-ba8e-bbcf4370ea12@gmail.com>
Date: Mon, 1 Feb 2021 15:52:20 -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: <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com>
Content-Type: multipart/alternative; boundary="------------D14CCF7BF04BD60DB572A890"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/awZhAHPCNpr3D4yuDZ9nA2ZpAmw>
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: Mon, 01 Feb 2021 23:52:26 -0000

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

On 2/1/2021 3:49 PM, Michael Thomas wrote:
>>
> It strains credulity that one part of a company would want to send out 
> reports when some other can't even sign their email. Both need access 
> to the email stream for starters. 

No it doesn't.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


--------------D14CCF7BF04BD60DB572A890
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>
    <div class="moz-cite-prefix">On 2/1/2021 3:49 PM, Michael Thomas
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com">
      <blockquote type="cite" style="color: #0000a0;"><br>
      </blockquote>
      It strains credulity that one part of a company would want to send
      out reports when some other can't even sign their email. Both need
      access to the email stream for starters.
    </blockquote>
    <p>No it doesn't.</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>

--------------D14CCF7BF04BD60DB572A890--


From nobody Mon Feb  1 16:06:12 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 533263A15D9 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:06:11 -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, LOTS_OF_MONEY=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 bW10RaxBZxLH for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:06:10 -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 E94E63A15D8 for <dmarc@ietf.org>; Mon,  1 Feb 2021 16:06:09 -0800 (PST)
Received: by mail-qt1-x832.google.com with SMTP id c1so13775475qtc.1 for <dmarc@ietf.org>; Mon, 01 Feb 2021 16:06: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;  bh=OWd/ZFn/T1XAEeMYi3xUK3CSp0mp0DY7JiBmNh25xDc=; b=oSTipLKwouoRMlqiK3zdspqUsHRpP7hI7A207PMDp3S9+F9fqeNAf/+xpE5fcAimW8 sXYeiLWOSqctLlcRa/gjdC7c3k0Qg2elrR9ZR0NY29YdaN/xlRDDMS8OuQJTxfTNcNxG vmN6IWMUJDc68f3+fvkFfF7hBEI3hLGCYujOY4NgJawqXG4y+FmR7Kn+j9XZXAG9/Qqi ejjfG1DXymD3XX1dsAj/5mX+PU27FRmj5LrqgPnQGJuGOL4YaGnelitxHBGvzHzh9CBV SPcG82X/5iGITDsh1L7zzkiyNO+7QFPRcaKRELDDvqvfLR6g/IjL6bRb4hJ4gjInaQrK pXUQ==
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=OWd/ZFn/T1XAEeMYi3xUK3CSp0mp0DY7JiBmNh25xDc=; b=ppxe0XF/nBz65zw4BJthZJrtMG6QwxFieMXvSp/0XvHluygZHCL+wqfZH6odcODSll i+caW0XPyaJ/vRFMibAkap6/zWNVi4t/pyxEMJ07AdkFHa36jVOKz1LvZb7IDkVvxrtM P38vEDl2h+zUYZUA4Ulg2h+9MSx5bBw7RLMs7p0+bzBMVOgYdmuRuw49Y30D7ie8jfPg v0qFUAFBdsei554pyzA3bs5s1669V20yYAKEj8xE1nCEPDkMG5bkvrTDKu57tx/HwCUA lG4frgYbVDboRmaTMwNpAUVqwV9R3kqtJcn0xoGxcp8+paE6wqfYDXKftSSwjrL7q4UG zafw==
X-Gm-Message-State: AOAM53161uiCnvtQZjdz04bs3si751IRvbOwROoYgM+2CKYwVdSr1KFc sTUfnEWOCbDVYGS/Z/3IMP1A/te/1OtY2j9YTRWD9xIe
X-Google-Smtp-Source: ABdhPJzcLzlk+nGP/8OVyeuI8OXC/NQfi9Th38WBsSz5zMFBtHRu7mRzqlbdBRrVkjmdFowY3b9Ff58MUTPvVAFjqoQ=
X-Received: by 2002:ac8:564e:: with SMTP id 14mr17701224qtt.286.1612224368310;  Mon, 01 Feb 2021 16:06:08 -0800 (PST)
MIME-Version: 1.0
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com>
In-Reply-To: <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com>
From: Dotzero <dotzero@gmail.com>
Date: Mon, 1 Feb 2021 19:05:57 -0500
Message-ID: <CAJ4XoYeHxhZyAsMBJfjDn7XFSeFt39agjoFQRBTbMZ0zdvaLyg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c57b7305ba4f3ce7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/DgPYnwL9XBJZVawZdrnz1Z43YN4>
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: Tue, 02 Feb 2021 00:06:11 -0000

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

On Mon, Feb 1, 2021 at 6:49 PM Michael Thomas <mike@mtcc.com> wrote:

>
>
> On 2/1/21 3:23 PM, Dave Crocker wrote:
> > On 2/1/2021 3:21 PM, John Levine wrote:
> >> I find it hard to believe that if you are going to enough effort to
> >> maintain the data to create and send reports, you can't figure out how
> >> to install an SPF record for your reporting domain.
> >
> > Except that the tracking/reporting functions are completely separate
> > from the 'signing' side of DMARC and could easily be different parts
> > of a company.
> >
> > d/
> >
> It strains credulity that one part of a company would want to send out
> reports when some other can't even sign their email. Both need access to
> the email stream for starters.
>
> It doesn't strain my credulity at all. You are assuming a single mail
stream. I saw it at my own employer before we got centralized control of
DNS and implemented email authentication. I actually know of one company
where several hundred thousand dollars of marketing emails ended up not
getting through because a marketer thought they could evade corporate
policy and the ESP gladly took the money even though the mail was getting
rejected. It's a crazy world out there.

Michael Hammer

--000000000000c57b7305ba4f3ce7
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, Feb 1, 2021 at 6:49 PM 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"><br>
<br>
On 2/1/21 3:23 PM, Dave Crocker wrote:<br>
&gt; On 2/1/2021 3:21 PM, John Levine wrote:<br>
&gt;&gt; I find it hard to believe that if you are going to enough effort t=
o<br>
&gt;&gt; maintain the data to create and send reports, you can&#39;t figure=
 out how<br>
&gt;&gt; to install an SPF record for your reporting domain.<br>
&gt;<br>
&gt; Except that the tracking/reporting functions are completely separate <=
br>
&gt; from the &#39;signing&#39; side of DMARC and could easily be different=
 parts <br>
&gt; of a company.<br>
&gt;<br>
&gt; d/<br>
&gt;<br>
It strains credulity that one part of a company would want to send out <br>
reports when some other can&#39;t even sign their email. Both need access t=
o <br>
the email stream for starters.<br>
<br></blockquote><div>It doesn&#39;t strain my credulity at all. You are as=
suming a single mail stream. I saw it at my own employer before we got cent=
ralized control of DNS and implemented email authentication. I actually kno=
w of one company where several hundred thousand dollars of marketing emails=
 ended up not getting through because a marketer thought they could evade c=
orporate policy and the ESP gladly took the money even though the mail was =
getting rejected. It&#39;s a crazy world out there.<br><br></div><div>Micha=
el Hammer<br></div></div></div>

--000000000000c57b7305ba4f3ce7--


From nobody Mon Feb  1 16:09: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 8248A3A15D9 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:09:47 -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 qBkA-8Qt7vmh for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:09:45 -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 C27C33A15CB for <dmarc@ietf.org>; Mon,  1 Feb 2021 16:09:45 -0800 (PST)
Received: by mail-pl1-x635.google.com with SMTP id e12so2060339pls.4 for <dmarc@ietf.org>; Mon, 01 Feb 2021 16:09:45 -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=H36NMxLtOqjt3PhFhZ8qPrSoxlhyIwrJ0xudXsBmfxs=; b=X8QuiIQukQdfHVMVGf75toM47ZwVezAWFHWqdtFN2tRJRW7vWE/eZFLLvsJH4lf45I QOZ/Bloan9bgqHa53lAY7uMxiP1whEtAuUao9djmITayLs+GXBfpDpQajOi+cby1vLWJ 2dpxRMreFchzHaK0PhiPPQNH4ATbBIZ2Q/0KEZdj3Il/9NqN7N11kWrSSomuCoCyxGHV scwAWAoyKpcRRtCAlTIxRsbuwVlWFEyRq7NP5X4I6zSDEs/+Tr6WyVcgIa1YKd2ifxrj np0B2cv5HbQiL6CNisBA7SrryTyGdIzD7tLLLveR52n9xrqVeJqX6I7U1n42oeiksP2B Cr3g==
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=H36NMxLtOqjt3PhFhZ8qPrSoxlhyIwrJ0xudXsBmfxs=; b=B7gLAV7a4set9DMDK0Dzgj71ve6ijA1qMIA2C7Or2MLA0t2ahIAc1RJjkmT3FpJLDk cbNEdUuRp3E2U0s7bnCP0VnjiTP88N0OWUsNMhBBSDzRrQ71K/esSSUF7h8DPyYnu5FP uwHByUFH4pSHhm4joCvhXNROKp47TFQRHgHmoKIzlo9glDURPggru6ZhjhznR7p+I219 DIDD2FKCbltAcSO6IsmY/g5iizawDXewbHFOxWaAEjeZwOt3EslREn87bEU3ioK6sQTL 5Rk79uxeNbqqtI/jeQlplyrcXKDosBMoGaiVXXfP2/SK1bUXiXYxppa9c1nnzPbmoTTA zvCA==
X-Gm-Message-State: AOAM5307NTlvxu0GEffE2NRgtG9Kv9w4/YDs29ZGVApxSRqM8gZkERHt h/gd8jS8jxS4t3tJR9ZcJM3ZYOaKJMaz+Q==
X-Google-Smtp-Source: ABdhPJxl7L8iz2F0FqPxPlAoHS3iNSNfyM3zP4sEl8IRgI2N5rKn9Kcwy+uiRBtF4kEDZnnXBKyxvg==
X-Received: by 2002:a17:902:9f8b:b029:e0:425:b856 with SMTP id g11-20020a1709029f8bb02900e00425b856mr20141792plq.82.1612224584790;  Mon, 01 Feb 2021 16:09:44 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id np7sm542242pjb.10.2021.02.01.16.09.43 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 16:09:44 -0800 (PST)
To: dmarc@ietf.org
References: <20210201232150.E8D346D20989@ary.qy>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <31971dd1-082f-ace3-c0a9-8bddc8677d6a@mtcc.com>
Date: Mon, 1 Feb 2021 16:09:42 -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: <20210201232150.E8D346D20989@ary.qy>
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/szJPa5g4ZsNAjm3CbgkgD8LMUK0>
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: Tue, 02 Feb 2021 00:09:48 -0000

On 2/1/21 3:21 PM, John Levine wrote:
> In article <9aea1615-64a5-a310-b8c7-83ec0c316dae@gmail.com> you write:
>> -=-=-=-=-=-
>>
>> On 2/1/2021 10:08 AM, Alessandro Vesely wrote:
>>> On Mon 01/Feb/2021 17:38:07 +0100 Dave Crocker wrote:
>>>> Consider the challenges to ensuring a DMARC pass.  That's a pretty
>>>> high barrier to entry against generating reports.
>>> Well, if a mail site is unable to get a DMARC pass, they have more
>>> urgent problems to solve than setting up aggregate report generation.
>>
>> No, they probably don't have more urgent problems. Sites choose not to
>> adopt DMARC for a variety of reasons. It's probably a good idea to
>> respect that variety.
>>
>> The model that a receiving site is not allowed to report DMARC traffic
>> unless that site is also generating DMARC authentication is
>> Procrustean.  And as I noted, is likely counter-productive.
> Ah, we have a semantic question.  I consider a message with p=none to be aligned.

This is why that paragraph needs to be made a (sub) section stating its 
motivation and done in terms of what the requirements are on the sender 
and the receiver of the report. It has nothing at all to with the DMARC 
protocol. That's what I tried to clarify in #98.

Mike


From nobody Mon Feb  1 16:11: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 0FDB13A15DC for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:11:37 -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 huoZ4qfsoJRo for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:11: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 677223A15D9 for <dmarc@ietf.org>; Mon,  1 Feb 2021 16:11:35 -0800 (PST)
Received: by mail-vs1-xe32.google.com with SMTP id i12so7189394vsq.6 for <dmarc@ietf.org>; Mon, 01 Feb 2021 16:11: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 :cc; bh=fyUSrOsoN2SVodiThoN1KtDvbTQbXAV51f0Y82eKv4A=; b=J2oEMsOuUkRF0GlqH91vL35jgeuFdWWs9dTXfUBGrtnZRW/Kalv8HsRte++A+2mCde usmbOkkOPaC6suNv66HGR895SbTGrGfSW2liNtamjWlC24hrF9V781wR6i8WPocd6wih wJdphP6W5ZtCtjA8sATCvq3WKc/rRuHRl8bXMyB7cI8hCOsTGfmgZGSdXR2NpFRQmPKN 9iIpqbxV1X9/ycVr6v8SPuKKRhWRBbjM+tCwXYevsgu++piZZggdFvVXrK46D2NZBtAE pfrR8p2az2QmlRlYeirxWrTi8pSHGFk0wje/cCXnExU/FYS0KGwdHTSbKrDR9y73HJ9g CaGQ==
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=fyUSrOsoN2SVodiThoN1KtDvbTQbXAV51f0Y82eKv4A=; b=mS2HmsDkLbbKAuhfq9LrzwyWm46tijsnmyjpDTHMMzxXo/jY5UZqo9tL3vuHKPxLl8 cTnhgN09JFLh8TWPQfdQYO7WpFLyN472xrCd6C8Qpqxlcdh7Nj+66uX/8d1mSq1PzF7W zj4wfXmq+hY8sB82yD6tdRA7nSkCoB6/BvNZMIwG8EkDRyViLY6hR+zNJaSp+2W2XNVD Qrf2lbE8KLpRd+WsF8dEQF+Ax50vIy7euSyYycRA4T9GS2i6EVuSTt2UgwrpNiWIffCd Qe0dFSQNQtFx02K3pQXyWWAKWfXm4TINLoFP054bXZRrE2qiGasiz9cDMRRaaZQUXtiz 73uQ==
X-Gm-Message-State: AOAM533GM+Vpf9S177YKTRBuLbTk+Bdfres34u23ecs0cesn9aN5SSxG j+/KJ0h04EsNdIcu82cYpYS58iLQRMVldSMSti0=
X-Google-Smtp-Source: ABdhPJz8SiOHohzmZIvi0+xYxR4GvEkPXtp/bfRr4xTAniAj1X2laH6ZyuH3GEF1hh4meIXTKpfxJI8qCW4Tgqxl27Y=
X-Received: by 2002:a67:c29e:: with SMTP id k30mr11049420vsj.45.1612224694321;  Mon, 01 Feb 2021 16:11:34 -0800 (PST)
MIME-Version: 1.0
References: <20210130212339.447316D04763@ary.qy> <1654196.ygyh55z74P@zini-1880> <babf1538-5172-f101-d5e4-c4fa33dea495@tana.it> <4489192.U1a6Vm75Xl@zini-1880>
In-Reply-To: <4489192.U1a6Vm75Xl@zini-1880>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 1 Feb 2021 19:11:22 -0500
Message-ID: <CAH48ZfxB8OoA=3YCdj9mCf3sBzRo8Cu0Tg0z70_tCqQ6QmsCTg@mail.gmail.com>
To: Scott Kitterman <sklist@kitterman.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000034045505ba4f50d0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/xTXgDCoXMA4bx8L8ONMuqEZ92M4>
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, 02 Feb 2021 00:11:37 -0000

--00000000000034045505ba4f50d0
Content-Type: text/plain; charset="UTF-8"

I think I finally understand the complexities of this issue.   SPF is two
different validations, largely unrelated.

Test One:
A connection comes in and a server asserts a HELO name.   Before
proceeding, the recipient was to check if the HELO name is plausible or
fraudulent.    One way to do this would be to forward-confirm the HELO DNS
name to the source IP.  An alternate method is to use SPF to see if the SPF
policy says that the HELO domain can send from the Source IP.   I do not
understand why the domain owner would be able to configure the SPF policy
but not the host name in DNS.   Perhaps for organizations with 1000s of
servers, creating a DNS entry for each machine seemed onerous.   In
practice, the large organizations do have DNS entries for each server, and
they encourage others to do the same.

A recipient who gets a FAIL result from this HELO test could decide to
reject the connection without ever proceeding to MAILFROM.  This is why the
specification suggests testing HELO before MAILFROM.   We know that
internal host names, such as "mail.example.local", will fail both of these
tests because the local domain cannot be published in DNS.   I expect that
any attempt to require a PASS from this test will encounter an unacceptable
number of false positives, so I do not see it as particularly useful.
But the option exists.

Test Two:
If the conversation proceeds past HELO to MAILFROM, then the second
validation is performed:   Is the Source IP is authorized to send on behalf
of the SMTP domain?   When the SMTP address is null, then
postmaster@HeloDomain serves as a proxy for performing this test.

We have two different tests, and two paths for performing the second test.
 Organizations have the choice of whether to implement one, both, or
neither test.   But the two tests are complementary, not mutually exclusive.

HELO test violations will have nothing to do with message flow path, since
the test only examines whether the adjacent server name can be plausibly
linked to the adjacent IP address.  A DKIM signature is not a third way of
answering this question, because a DKIM signature cannot be reliably
associated with the server that applied the signature.   Nor do I think we
want a third solution to this question.  Consequently, the HEL:O test is
unrelated to DMARC.  The SMTP Address test is appropriate to DMARC, whether
it is evaluated using a supplied name or a derived name based on
postmaster@helodomain.

DF

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

<div dir=3D"ltr">I think I finally understand the complexities of this issu=
e.=C2=A0 =C2=A0SPF is two different validations, largely unrelated.<div><br=
></div><div>Test One:</div><div>A connection comes in and a server asserts =
a HELO name.=C2=A0 =C2=A0Before proceeding, the recipient was to check if t=
he HELO name is plausible or fraudulent.=C2=A0 =C2=A0 One way to do this wo=
uld be to forward-confirm the HELO DNS name to the source IP.=C2=A0 An alte=
rnate method is to use SPF to see if the SPF policy says that the HELO doma=
in can send from the Source IP.=C2=A0 =C2=A0I do not understand why the dom=
ain owner=C2=A0would be able to configure the SPF policy but not the host n=
ame in DNS.=C2=A0 =C2=A0Perhaps for organizations with 1000s of servers, cr=
eating a DNS entry for each machine seemed onerous.=C2=A0 =C2=A0In practice=
, the large organizations do have DNS entries for each server, and they enc=
ourage others to do the same.</div><div><br></div><div>A recipient who gets=
 a FAIL result from this=C2=A0HELO test could decide to reject=C2=A0the con=
nection without ever proceeding to MAILFROM.=C2=A0 This is why the specific=
ation suggests testing HELO before MAILFROM.=C2=A0 =C2=A0We know that inter=
nal host names, such as &quot;mail.example.local&quot;, will fail both of t=
hese tests because the local domain cannot be published in DNS.=C2=A0 =C2=
=A0I expect=C2=A0that any=C2=A0attempt to require=C2=A0a PASS from this tes=
t will encounter=C2=A0an unacceptable number of false positives, so I do no=
t see it as particularly useful.=C2=A0 =C2=A0 But the option exists.</div><=
div><br></div><div>Test Two:</div><div>If the conversation proceeds past HE=
LO to MAILFROM, then the second validation is performed:=C2=A0 =C2=A0Is the=
 Source IP is authorized to send on behalf of the SMTP domain?=C2=A0 =C2=A0=
When the SMTP address is null, then postmaster@HeloDomain serves as a proxy=
 for performing this test.</div><div><br></div><div>We have two different t=
ests, and two paths for performing the second test.=C2=A0 =C2=A0Organizatio=
ns have the choice of whether to implement one, both, or neither test.=C2=
=A0 =C2=A0But the two tests are complementary, not mutually exclusive.</div=
><div><br></div><div>HELO test violations will have nothing to do with mess=
age=C2=A0flow path, since the test only examines whether the adjacent serve=
r name can be plausibly linked to the adjacent IP address.=C2=A0 A DKIM sig=
nature is not a third way of answering this question,=C2=A0because a DKIM s=
ignature cannot be reliably associated with the server that applied the sig=
nature.=C2=A0 =C2=A0Nor do I think we want a third solution to this questio=
n.=C2=A0 Consequently, the HEL:O test is unrelated to DMARC.=C2=A0 The SMTP=
 Address test is appropriate to DMARC, whether it is evaluated using a supp=
lied name or a derived name based on postmaster@helodomain.</div><div><br><=
/div><div>DF</div><div><br></div><div><br></div></div>

--00000000000034045505ba4f50d0--


From nobody Mon Feb  1 16:13:04 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 13F443A15D9 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:13:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 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, LOTS_OF_MONEY=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 PUsDsK9zBhlF for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:13:01 -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 B47993A1488 for <dmarc@ietf.org>; Mon,  1 Feb 2021 16:13:01 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id t25so13594930pga.2 for <dmarc@ietf.org>; Mon, 01 Feb 2021 16:13:01 -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=uU9yrn9S+vzDseTuOIjzB4ZUr0zUTIvtFDD0zavJw/g=; b=RJdTojy9by+tPSpMuih2IKYYsZYhsIt/Mtrj+y8hQywLajRmIZCY3J/FMCWOtJpmeT Me19yMLb96KxzdUJqATXM6DXVqdRtpVPqtsO63UfNEBD+1sNmPcUbka8Od4a9obNnvTy W36sxNDqgE4LCQK8FaBYAsnh+JWCCxpuLXvHdRRC57aYUYnF5rEXx6RAoZ3u+Evmffvt p0VGpqhkq6Yzq1zXIrHi6F0tl/h0+lHaccPkj+AUD+jzRe8LjsWm1PHm+O1oLXzoPtNX u2tPg8s6EbBoqst69gE9zxWYX9JGkmYsoVuDe1ZNHdyOjjmPvfnexFQxYcTqgbspShVh KWSg==
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=uU9yrn9S+vzDseTuOIjzB4ZUr0zUTIvtFDD0zavJw/g=; b=NAira8QvO5PVjIeFY2aI1m4jPzrLSztJ9ZKaxLOvJ7t1YeEsqCubRj7sZ9tZYhjkWm k+4J/JoLJE9LVm9ept6t07P93kFtoB+bt5SsSUQs81Dw4XifTXTkO6rWkdr+MtEM2APh xT8xI/2Z089YpWrGacSTN9x5PNHZBwo87uxMG5n0dwK6shIVp7gtbtUHjIyX4OleDJja HABk411BPIhSMXXhVXYASWx/ERobHD/DUvClw65iB0c9Ot6d4pT25JacimkI5ayWjeeP BycqFWY6O0lEjKXtEth4KJk2Ld1LzxtaaqVSkyptmuLcFeo/wiwJ6ipYXpIS0OPiUklo 5hRQ==
X-Gm-Message-State: AOAM531uzSVTo6CwmGJ9PLIsCrk/fKVJNFBRu+cninEEdRHdj5COjvGi FdnEYyzHPxoq1jTRZ72FXjg0dwI1sV0dtw==
X-Google-Smtp-Source: ABdhPJwnnWXkCwjcW2Tv4cy0eHVwEDq5h0EAg3SfB+2JjnHS+xAE7QclhIRc5YUhknKabB/lGhVtNQ==
X-Received: by 2002:a63:7e10:: with SMTP id z16mr19541816pgc.263.1612224780833;  Mon, 01 Feb 2021 16:13:00 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id v1sm20291783pga.63.2021.02.01.16.12.59 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 16:13:00 -0800 (PST)
To: dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com> <CAJ4XoYeHxhZyAsMBJfjDn7XFSeFt39agjoFQRBTbMZ0zdvaLyg@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <38f5c417-3c7d-72c9-2590-391c07226164@mtcc.com>
Date: Mon, 1 Feb 2021 16:12: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: <CAJ4XoYeHxhZyAsMBJfjDn7XFSeFt39agjoFQRBTbMZ0zdvaLyg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------A744D667EA4A5547DE1CFCD8"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/44_PIGAjlBuw_cKjktrxDtvT9VM>
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: Tue, 02 Feb 2021 00:13:03 -0000

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


On 2/1/21 4:05 PM, Dotzero wrote:
>
>
> On Mon, Feb 1, 2021 at 6:49 PM Michael Thomas <mike@mtcc.com 
> <mailto:mike@mtcc.com>> wrote:
>
>
>
>     On 2/1/21 3:23 PM, Dave Crocker wrote:
>     > On 2/1/2021 3:21 PM, John Levine wrote:
>     >> I find it hard to believe that if you are going to enough effort to
>     >> maintain the data to create and send reports, you can't figure
>     out how
>     >> to install an SPF record for your reporting domain.
>     >
>     > Except that the tracking/reporting functions are completely
>     separate
>     > from the 'signing' side of DMARC and could easily be different
>     parts
>     > of a company.
>     >
>     > d/
>     >
>     It strains credulity that one part of a company would want to send
>     out
>     reports when some other can't even sign their email. Both need
>     access to
>     the email stream for starters.
>
> It doesn't strain my credulity at all. You are assuming a single mail 
> stream. I saw it at my own employer before we got centralized control 
> of DNS and implemented email authentication. I actually know of one 
> company where several hundred thousand dollars of marketing emails 
> ended up not getting through because a marketer thought they could 
> evade corporate policy and the ESP gladly took the money even though 
> the mail was getting rejected. It's a crazy world out there.


So we're supposed to ignore security considerations because... some 
companies are a mess? That's what this really boils down to. If we're 
writing specs for the least common denominator we might just as well 
stop. But we're not, nor have we ever.

Mike


--------------A744D667EA4A5547DE1CFCD8
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 2/1/21 4:05 PM, Dotzero wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJ4XoYeHxhZyAsMBJfjDn7XFSeFt39agjoFQRBTbMZ0zdvaLyg@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 Mon, Feb 1, 2021 at 6:49
            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"><br>
            <br>
            On 2/1/21 3:23 PM, Dave Crocker wrote:<br>
            &gt; On 2/1/2021 3:21 PM, John Levine wrote:<br>
            &gt;&gt; I find it hard to believe that if you are going to
            enough effort to<br>
            &gt;&gt; maintain the data to create and send reports, you
            can't figure out how<br>
            &gt;&gt; to install an SPF record for your reporting domain.<br>
            &gt;<br>
            &gt; Except that the tracking/reporting functions are
            completely separate <br>
            &gt; from the 'signing' side of DMARC and could easily be
            different parts <br>
            &gt; of a company.<br>
            &gt;<br>
            &gt; d/<br>
            &gt;<br>
            It strains credulity that one part of a company would want
            to send out <br>
            reports when some other can't even sign their email. Both
            need access to <br>
            the email stream for starters.<br>
            <br>
          </blockquote>
          <div>It doesn't strain my credulity at all. You are assuming a
            single mail stream. I saw it at my own employer before we
            got centralized control of DNS and implemented email
            authentication. I actually know of one company where several
            hundred thousand dollars of marketing emails ended up not
            getting through because a marketer thought they could evade
            corporate policy and the ESP gladly took the money even
            though the mail was getting rejected. It's a crazy world out
            there.</div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>So we're supposed to ignore security considerations because...
      some companies are a mess? That's what this really boils down to.
      If we're writing specs for the least common denominator we might
      just as well stop. But we're not, nor have we ever.<br>
    </p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------A744D667EA4A5547DE1CFCD8--


From nobody Mon Feb  1 16:16:55 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 53CCC3A15E6 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:16:53 -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, FREEMAIL_FROM=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 7i6H6740WZnw for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:16:51 -0800 (PST)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 D26133A15E9 for <dmarc@ietf.org>; Mon,  1 Feb 2021 16:16:51 -0800 (PST)
Received: by mail-ot1-x32e.google.com with SMTP id h14so18215601otr.4 for <dmarc@ietf.org>; Mon, 01 Feb 2021 16:16:51 -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=EDER7haobZ21WvpBJwQpFrL+Xyg+q07hsPRkrDmrogc=; b=P0ET/qwOBH49Q+GUMZVfvPTNzECsjJ/cJMwl2hOY2S2jLehsGVOXQZUBBBQcX2Aayz Y/WvkN6sKbilzlNPIHRlr247yLtvCzRTpZ4WBoCvGYfqezJxjLvwB7HB7mAAfjSqBroH bD8nDYebCiO7WnY7eEmklKBVxIw6om3Rzh70CEhzG0h/4R9vzSVcxDBELwWsM66dC5i8 rR3taJlZsarKLArwtPC3uIkFcQr0+SO2BgvI973aIoqIBxYLGWQ0vY/TkwGrDtuJmWxw NCILKtWVD3wkEVKWLE++rsopvxj01AWI/B9gppFcc/hTIlhU0wzh+/FDBVKyX3/5Env2 COow==
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=EDER7haobZ21WvpBJwQpFrL+Xyg+q07hsPRkrDmrogc=; b=UowWjAeGMpqioAIarrLO8q2Bqw9tEb+n324PNlm7CHjN03IiwCI31bZ+35ch7DFzu5 Fo6LmAubxQHDtalbT16mUxBwRFINxVJJlq/PXSJ9fn226fn2bVBqpE3CX7r7iboa7gL9 8eJk6FvwwZUm7xTo7KmVvE46c/AzZUnlRyD1AWRFj761fq3YYQkaEp2R2/mhxEFow8IK 7lVgc9UcrP1C6/ptAQZsA5Ag3XY3TX+xH3UME0pRSikqhP2XYEadZzFdkprsrs30C/A2 CBc0Ta1TXHcdS+1Hu+GOaLbbMLt0fqhPoliWV4myMfuz60UVBIRrfVQZRKXDRPRsZivt Zm7A==
X-Gm-Message-State: AOAM531dEHCdyw6AG0QKvHiYN3BKFYGhAGcRmkISqeBvtW3YtS2cqCQ3 p1aRuR5JCHPTh+J+sqc8pbXfAj5MnxJjkg==
X-Google-Smtp-Source: ABdhPJzOxUhexKknTynyXCXd+oILjo9NAVHS1icabQTX03qCcc0Ohmhz686Mkqx9Mqy0QU4oPvDj5A==
X-Received: by 2002:a05:6830:1318:: with SMTP id p24mr13269041otq.302.1612225011087;  Mon, 01 Feb 2021 16:16:51 -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 y10sm4526357ooy.11.2021.02.01.16.16.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 16:16:50 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com> <CAJ4XoYeHxhZyAsMBJfjDn7XFSeFt39agjoFQRBTbMZ0zdvaLyg@mail.gmail.com> <38f5c417-3c7d-72c9-2590-391c07226164@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <16430b47-2496-b461-e292-ea6a7d945e71@gmail.com>
Date: Mon, 1 Feb 2021 16:16:48 -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: <38f5c417-3c7d-72c9-2590-391c07226164@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/vQh_chF2U7Q6YdW3Xae9Ck7gfss>
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: Tue, 02 Feb 2021 00:16:53 -0000

On 2/1/2021 4:12 PM, Michael Thomas wrote:
> So we're supposed to ignore security considerations because... some 
> companies are a mess?


we're supposed to balance purported security considerations with 
pragmatic, real-world operational limits.

cost/benefit.  not an unusual concept.

d/


-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Mon Feb  1 16:41:26 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 10A143A1605 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:41: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.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 MoENN3diEsug for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 16:41:23 -0800 (PST)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (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 1CC763A1604 for <dmarc@ietf.org>; Mon,  1 Feb 2021 16:41:22 -0800 (PST)
Received: by mail-pl1-x629.google.com with SMTP id b8so11397063plh.12 for <dmarc@ietf.org>; Mon, 01 Feb 2021 16:41:22 -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=xF2efYthROIsDCbl+Z6BeXs50cD7c2S9LwwSe4kW/aw=; b=lvMCUScWgRMUTmMBzoxmhKS1aIj7i1Fpj7NrzpP4t1v7PFfTzSOiA/pKyxvRm6Pj/5 yz512d2KKaxUktN5ning3USz7oA5VFY+7IoMUEZ02YMO31r/BIvCgS5xSW8iQUcwpZhu bXxstsg2f0ZTNvFxUDUPMM0IG/zEgLUJhiz2thxRxQHYUUQoHcQFPj/73+G11y8Ypvv+ iu7KJb/b+geqwPTUBOU4urb0eYN75GaUuTEjqHKVWGKbBEvka5IC63TyE1ymZPWrPVsp 1TRoQk5oBFNV05C87egxrhX69/fgdwBuTdD6N/pS+M5uDFsOqyrkSQiHOtt59QjGprFA ZFKg==
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=xF2efYthROIsDCbl+Z6BeXs50cD7c2S9LwwSe4kW/aw=; b=X5jb2gOTuWdd8AHuKW1GdrGKPn0sze0ls6uBYUv+MLNEfhl/4XxKNE5d0T9uAnJyiS eKnsyrLYIqJABoEm3TRCkwQvInKNvLLcJvqRlV8J7NLfhoXwuGHroUsDKGDoxDBZ86cf QYQL21b7RDq9t+KPl0LMQS96T67EmmDv8st3ujZ8Elo7lNfMdAwOAm7cLqLj5+jQyevg b3F/m8YGonWGt8pMyPNufmMZcDUCRfVIX54q09DBrcrut0QpZ+pVeXS2jNg169MkMK+7 84+NuFHdTOLwsjFxLB9WnGWeFBTPvV1PtcpfEg+qMpGEi0FtfaSacFkjUd4CMQAA56ji 74JQ==
X-Gm-Message-State: AOAM531lH7tbOCD24UMzgHcNKL0QQXtWYDSQh4qDm6oInOknxPwLRScO MQZZWpD3QuFprIGRsq6ZEUd0InDwXCixng==
X-Google-Smtp-Source: ABdhPJw7v/R75NbItAy90AKwJ+I039CKCzQkobz+hcF5/XUGteEXZhB4fGX6SGRk3fzprEntdBDC/A==
X-Received: by 2002:a17:90a:206:: with SMTP id c6mr1521595pjc.50.1612226482158;  Mon, 01 Feb 2021 16:41:22 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id n15sm20264311pgl.31.2021.02.01.16.41.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 16:41:21 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com> <CAJ4XoYeHxhZyAsMBJfjDn7XFSeFt39agjoFQRBTbMZ0zdvaLyg@mail.gmail.com> <38f5c417-3c7d-72c9-2590-391c07226164@mtcc.com> <16430b47-2496-b461-e292-ea6a7d945e71@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <0c02a7f2-6078-5821-332f-5bd169a0b358@mtcc.com>
Date: Mon, 1 Feb 2021 16:41: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
In-Reply-To: <16430b47-2496-b461-e292-ea6a7d945e71@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/M0uQQdATklhXNEbJPK0rZNFqbko>
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: Tue, 02 Feb 2021 00:41:25 -0000

On 2/1/21 4:16 PM, Dave Crocker wrote:
> On 2/1/2021 4:12 PM, Michael Thomas wrote:
>> So we're supposed to ignore security considerations because... some 
>> companies are a mess?
>
>
> we're supposed to balance purported security considerations with 
> pragmatic, real-world operational limits.
>
> cost/benefit.  not an unusual concept.
>
We have no means of evaluating what you're complaining about. It's a 
Chimera, and a long tailed one at that.

Mike


From nobody Mon Feb  1 17:23: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 3A1473A1645 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 17:23: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, 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 vnktzBucNLcS for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 17:23:05 -0800 (PST)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (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 213463A1641 for <dmarc@ietf.org>; Mon,  1 Feb 2021 17:23:04 -0800 (PST)
Received: by mail-ot1-x335.google.com with SMTP id t25so8206908otc.5 for <dmarc@ietf.org>; Mon, 01 Feb 2021 17:23:04 -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=wABgTUJoZksmgmZiF1R2ni6mZyP1NvrKZbymQ2vjWwg=; b=QJN7O6b741jcuNtzlYGUbEIy+ydanDDFnuJM4VSQKgg+D8yLP/YQjnUp7uxs5u7sZ+ 4jj+7W+IqJfTFlrVq4XG5qkpXoSainrSIt0yfqybzN1MGF99T8y/X8iBkatEfkKXY3+G +HtTSVQRrd/1wIgCOKlnOkdAhe0WViXDVfAQ8lOoIDSfIwjuetU2BOJvrYQkuxtKZl8P mect2EI8g00ivfO7K86Lkz93hRg6VNEg04JbI5OkVmIJ8nwu//ZwGBK2Vw7G6aWqxbH0 tqjplhiE+78/In2Ql7u4jnaD6qDNH7a0glsdmhDlFm8sGOh3n8uldTCq7m2KSC4yE294 ad5w==
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=wABgTUJoZksmgmZiF1R2ni6mZyP1NvrKZbymQ2vjWwg=; b=O79wGcR71OElaC6p4crV9d1Z8jJaKB/U6pcY9Ad8yNqvAf/AiDHnghtgEd5DSVtGh0 //YsWS54sCh78mzqvlYEn33tpx+17mc98407LtueJDbtvxrEidOEMlVzkzLht5MGir82 dcTvWNCavJUw/H36IpXES6OzOIonWkdH1joGSToVlXCToCX9vB/y8Rpggn+Ztbl0DBEV cA/Vnr8kAiR3ghv6MAfdHuvl3ouowxOrfyHGtBWOi59kU34SALoXE7fhE9rGRaXEG9ww 1EpguP65GgveLNvio1rWjuecChzMFVgMiFVdNbXK6g5kXBoQoskZoMmrT45jpUM4W6TP f29Q==
X-Gm-Message-State: AOAM533/i6vkaDFJty/+YnYUR36D8G2dQ23tSoGxoBwBAzaC7LaUo6li htDvynQ+69zfqkYKdxq9rZmr110jrRUGNA==
X-Google-Smtp-Source: ABdhPJyfE7rYrDCenRQucz6OCoEgTBUSUG6a28gsNPx5pr71ahBpFhmDqcSXgykcxBUpk+Jv97B3TA==
X-Received: by 2002:a9d:3604:: with SMTP id w4mr5144222otb.107.1612228984137;  Mon, 01 Feb 2021 17:23:04 -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 g23sm4426242otk.72.2021.02.01.17.23.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 17:23:03 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <044c4a55-facb-9053-1ae9-0b8d87c7ca3a@mtcc.com> <CAJ4XoYeHxhZyAsMBJfjDn7XFSeFt39agjoFQRBTbMZ0zdvaLyg@mail.gmail.com> <38f5c417-3c7d-72c9-2590-391c07226164@mtcc.com> <16430b47-2496-b461-e292-ea6a7d945e71@gmail.com> <0c02a7f2-6078-5821-332f-5bd169a0b358@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <03b6ee7b-33c5-10a6-8b1c-3db6ba3c2666@gmail.com>
Date: Mon, 1 Feb 2021 17:23:00 -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: <0c02a7f2-6078-5821-332f-5bd169a0b358@mtcc.com>
Content-Type: multipart/alternative; boundary="------------733FA65986853C4086803379"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/myO8pwcC_HcldUPOcPuP5MVd4GU>
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: Tue, 02 Feb 2021 01:23:07 -0000

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

On 2/1/2021 4:41 PM, Michael Thomas wrote:
>> we're supposed to balance purported security considerations with 
>> pragmatic, real-world operational limits.
>> cost/benefit.  not an unusual concept.
> We have no means of evaluating what you're complaining about. It's a 
> Chimera, and a long tailed one at that. 


You're probably right.  Far better to offer requirements as absolutes, 
unanchored by practical concerns.

Except that cost/benefit isn't an illusion or fabrication, but is a 
common practice, so attempting to claim it is otherwise is gaslighting.

And gaslighting is a method that creates a hostile work environment.

It's a shame the working group management hasn't put serious effort into 
curbing such behavior.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


--------------733FA65986853C4086803379
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 2/1/2021 4:41 PM, Michael Thomas
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:0c02a7f2-6078-5821-332f-5bd169a0b358@mtcc.com">
      <blockquote type="cite" style="color: #0000a0;">we're supposed to
        balance purported security considerations with pragmatic,
        real-world operational limits.
        <br>
        cost/benefit.  not an unusual concept.
        <br>
      </blockquote>
      We have no means of evaluating what you're complaining about. It's
      a Chimera, and a long tailed one at that.
    </blockquote>
    <p><br>
    </p>
    <p>You're probably right.  Far better to offer requirements as
      absolutes, unanchored by practical concerns.</p>
    <p>Except that cost/benefit isn't an illusion or fabrication, but is
      a common practice, so attempting to claim it is otherwise is
      gaslighting.</p>
    <p>And gaslighting is a method that creates a hostile work
      environment. <br>
    </p>
    <p>It's a shame the working group management hasn't put serious
      effort into curbing such behavior.</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>

--------------733FA65986853C4086803379--


From nobody Mon Feb  1 17:38:53 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 50E6F3A165A for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 17:38:51 -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=gcGrXvtS; dkim=pass (2048-bit key) header.d=taugh.com header.b=CVo8309K
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-h3Wkd5JxFe for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 17:38: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 31C083A1659 for <dmarc@ietf.org>; Mon,  1 Feb 2021 17:38:48 -0800 (PST)
Received: (qmail 18004 invoked from network); 2 Feb 2021 01:38:47 -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=464f.6018ad27.k2102; bh=xPU3UCnWt7mu5aGWf5T7sbd/PdvCk2q2e5JgLfOIPkI=; b=gcGrXvtSdFQyFP4QX7Un6fUAIQkvJV3rCsRc9Wpxlf20/yxx0oaZ4Dywet/XI+988QyRaT0PUQCcB2bte23UNYfKQiTJ1IdxYL41PNBxvqJcLmi9lJgKNzVr1zLUTkBGlBP9AoLwEXVOzy1wNAZMDIx2fqRznkls+g+YFFOW2/MB62waCjQUKc8Lc4yxNgvfK72gmN7ksv+1/N8jRLhB5tyYXoiWlTEAk7Z7X19S7oC520iuEBD9C4cJ2l7nEmDKjsL9j/EIkGBzvgBMwc1Q9adkmLbZ+/gJSSr6/EJgciNuvm9Y1ig7GlxKLuMtH0dj8QZKCXR8PyciHDGKQSjJSA==
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=464f.6018ad27.k2102; bh=xPU3UCnWt7mu5aGWf5T7sbd/PdvCk2q2e5JgLfOIPkI=; b=CVo8309K1+GfUUfpEht4HGMNUJZKby4SGGZRoLiML6MZfXcZw7WEKWYea4URql8kYNoUxN5vNLH5+nXcJsFbioN+5LnVoNi6YZPrXdNX5AZ5Dn48ZAKyZL3tyBCi4B5ILxBg2CHX6zdd2d5sS57VNaereG9oZRBOv7Kw/GOv2Y5JztAHHGq3OYtabbi4QZjcKvCg29YG6hojPtnlcs1zLm1ZLL21QJQcBeXlCLSZ4HDjxVF48yClsFxG4U2tjCTt+IsS3aIS3VzxY9lcFbB1SQO17Of9H2k+jXJmKqb4cDUkfcrSAi/c6r+HDI0+ydagKxrUEmPX/rIE8p/7UZ43og==
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 Feb 2021 01:38:47 -0000
Received: by ary.qy (Postfix, from userid 501) id EF1C86D21BAF; Mon,  1 Feb 2021 20:38:46 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id A80FA6D21B90; Mon,  1 Feb 2021 20:38:46 -0500 (EST)
Date: 1 Feb 2021 20:38:46 -0500
Message-ID: <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Dave Crocker" <dcrocker@gmail.com>
Cc: dmarc@ietf.org
In-Reply-To: <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com>
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9zXyCYeNNCoM1tGWFIur_LUOohk>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 01:38:51 -0000

On Mon, 1 Feb 2021, Dave Crocker wrote:

> On 2/1/2021 3:21 PM, John Levine wrote:
>> I find it hard to believe that if you are going to enough effort to
>> maintain the data to create and send reports, you can't figure out how
>> to install an SPF record for your reporting domain.
>
> Except that the tracking/reporting functions are completely separate from the 
> 'signing' side of DMARC and could easily be different parts of a company.

I took a look at my aggregate reports.  The DMARC policies of the senders 
are all over the place, some none, a few quarantine, some reject, a few 
small sites (trouble.is, gspam.co.il) have no DMARC record, one has 
neither SPF nor dmarc (itdseciron04.utep.edu). I'd say about 3/4 of the 
reports have DKIM signatures, the rest that have SPF records are aligned.

One was from MAILER-DAEMON@esa1.hc1512-92.c3s2.iphmx.com and 
esa1.hc1512-92.c3s2.iphmx.com indeed has an SPF record.

So I would say that from my small sample, a lot of people have figured out 
how to send aligned reports, either by using their regular signing engines 
or with an SPF record for the host that sends the reports.  On the other 
hand, for reasons we've discussed that are evident to anyone familiar with 
DMARC, there's little reason to worry about fake reports, and 
authentication doesn't help even if there were.

If we want to document existing practice, I guess we would say that 
reports should be authenticated and aligned if practical, but it's OK to 
send them if not.

R's,
John

PS: Does anyone have a contact at antispamcloud.com aka hosteurope.de ? 
They send a lot of impressively broken failure reports.


From nobody Mon Feb  1 17:42:31 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 549463A165F for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 17:42:30 -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, FREEMAIL_FROM=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 nMjx60bekrXu for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 17:42:29 -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 17DA43A1654 for <dmarc@ietf.org>; Mon,  1 Feb 2021 17:42:29 -0800 (PST)
Received: by mail-ot1-x32c.google.com with SMTP id h14so18371881otr.4 for <dmarc@ietf.org>; Mon, 01 Feb 2021 17:42:29 -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=/vD7WoQqjrSg5ZVABfjazd/6amj1T8V1e4HTEE26KYU=; b=kr7ATpz96diwnezt4HZmkFT4q8MdjXtY2s5HoJe3nWN3x7CUsTa2YibRCz6ZMaEQj5 fFIfnPuyixR+WoU0oM1JnCl7YXcGSTABsCyDei2cme308ie/pE51ELq4gC+UKjc/HwnX gHvChjUu20ZJv6LU0Yfjbr1MlfeY9x3p9udZCtT6PfEdq/94o3hQ2GOxZQYizZkIWo8v ynldwqrLDa/6X1i5/io+phwGRkAzC68wkQSfXIJlq6ai9TLU/bHiHg3/ulNXEUNYgWLY Su0lsHFJjO3dTmgjFcAB0+Kic3UnF/lhzgzohShZL4JrKenEClstx/+1LqY+aINP3wuc SnLA==
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=/vD7WoQqjrSg5ZVABfjazd/6amj1T8V1e4HTEE26KYU=; b=rGbv7lp1NnoCSvoIQ4k1RCYwux5xaxpEuRgH1eOsGm25KUsKCcXFrFxbG+wKM61/P4 ciaAcVjg9TPWDa6TmhrMhUDFpNeRKg1vjEhOqdpxxpQK8/qcs0+0+ztoH+WHFYeCxZnZ NFniV3ZjxJZrSOOzP0R9KPzGZU2Z2LPSz/+7TRYN3qQsBO2rGNJ0xgo0phLC6yG1d9VK QAnTplg66n7ubq6HPCB1cJlqmNcGouJRqaLddvS89okGuF82kCQJ5bqhY6tVw6hgVC/v Tbx4aeFRXDkHuQb2rVyERcb+h4o7EzuyiTAAB5UsCPisFVHivsXTnuiNLKM9a3oEX/4e MPaA==
X-Gm-Message-State: AOAM531IEBhfFeBZirHXvzv5vURsXP159stvlLGGTR7rU53yQpJsW5qg beyGcQQ64/SIywaj6rMU4Klt/52DuGo3SQ==
X-Google-Smtp-Source: ABdhPJz9eN11ov/1Qf2z5mI0j9t+vxY0RR1Rlsf/tvrbLy+YUhmsST8ffxY1yB7p1PFRSL/fbWCJiw==
X-Received: by 2002:a05:6830:1dc8:: with SMTP id a8mr13856852otj.26.1612230148351;  Mon, 01 Feb 2021 17:42:28 -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 33sm4255319ota.69.2021.02.01.17.42.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 17:42:27 -0800 (PST)
To: John R Levine <johnl@taugh.com>
Cc: dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com>
Date: Mon, 1 Feb 2021 17:42:25 -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: <92b361a1-d9a5-9389-46b-3725d885c02@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/y3BHNo1XsL8CjsvIqaZ6hqVqfNM>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 01:42:30 -0000

On 2/1/2021 5:38 PM, John R Levine wrote:
> So I would say that from my small sample, a lot of people have figured 
> out how to send aligned reports,

and, to be thorough, some/alot have not.


> either by using their regular signing engines or with an SPF record 
> for the host that sends the reports.  On the other hand, for reasons 
> we've discussed that are evident to anyone familiar with DMARC, 
> there's little reason to worry about fake reports, and authentication 
> doesn't help even if there were.

exactly.


> If we want to document existing practice, I guess we would say that 
> reports should be authenticated and aligned if practical, but it's OK 
> to send them if not.
exactly.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Mon Feb  1 17:58: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 AFC913A1668 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 17:58:27 -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 ahKWwApCuPK4 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 17:58:26 -0800 (PST)
Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (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 9DE003A1667 for <dmarc@ietf.org>; Mon,  1 Feb 2021 17:58:26 -0800 (PST)
Received: by mail-pj1-x1035.google.com with SMTP id nm1so1281803pjb.3 for <dmarc@ietf.org>; Mon, 01 Feb 2021 17:58:26 -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=R2ubTZrrXM6ZZqo1EmT5YxY+CKDdFFzWdo4VJ8Sp5RM=; b=Q0B7tzzIfvOQseHqeAgLmWSBKk0UeUKaa6/uTtQ7Tprdck5yoOVDVtgf7avbBCRFrO i14TpzlmVS/8J9s2xfrNgSqSUUsDXRSM5bRtT9VSiYV5+N6EWT0r9yr7ueqkEA/HjB4E /rBjWruH9Q45JZRqI9BcLF+lgAKGaTZVFeroM+Ek74P0GCrBnwcqIzTUVFJEv81DnBve CKLgxS5mvHbmk19r0zSXymXDcD3IpryDZpJu9GNmdtPnoFW5V70hbSbFRy7qFtdD9RYE vdSyU3auV7fpjo+brKex8M4kF/87A6TvhoSZGI7sE3BFtij2FxBCoSWpBPfLB7TcLeJ3 DQqw==
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=R2ubTZrrXM6ZZqo1EmT5YxY+CKDdFFzWdo4VJ8Sp5RM=; b=ho6t9ZKtzCwXPM4+tg2HzJqazighhsgEimBwvtPaxU8bmj05M0bYyUMpaWg0RSHOEC V8KBpwXQA4l9hK+svZcXrVS4sFoi7v21E8jioA7v3iGO0DLJpnQRWmpwhhXUrhrL/Myq q+zihHQv4DFOygJbOiowroV/l1i8v4mksAOwhaJZ1PHJ1DI1ekZoNkSZK24++LT91u6A Hy8DZhBawZsxklzkSv2VWdfNuQ3wUJnGZP/75cQn07LqbOOe5jTv/jCjropoaTbfFbsd fTPIl0OkW0c5aFmydomocZRfWmNI8hYJq0Uvg5luxscn8teLHuNDYAtMJ31ebdlKjt6G 16cA==
X-Gm-Message-State: AOAM530H9zIxhxasJnaZ5KDzvT5t2n/OCAiDkZsrs4Q5vvQlPkc498/a 8D2SXUritA3f4Vd08ig/jATJ4BZOmxVlAA==
X-Google-Smtp-Source: ABdhPJwByRugyYF21aVUZV6UAZ0PVPbF2UHhyp30QU3ztWt6c1Jeu0JfxZqIGftjfyW7tYiKRw6hGg==
X-Received: by 2002:a17:90a:d317:: with SMTP id p23mr1749393pju.14.1612231105605;  Mon, 01 Feb 2021 17:58:25 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id 6sm19096384pfz.34.2021.02.01.17.58.24 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 17:58:25 -0800 (PST)
To: dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com>
Date: Mon, 1 Feb 2021 17:58: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: <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@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/6SxmJKE_3N05PE6oPVZSULmESuU>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 01:58:28 -0000

On 2/1/21 5:42 PM, Dave Crocker wrote:
> On 2/1/2021 5:38 PM, John R Levine wrote:
>> So I would say that from my small sample, a lot of people have 
>> figured out how to send aligned reports,
>
> and, to be thorough, some/alot have not.
>
This, on the other hand, should be measurable. Saying that we should 
ignore authentication requirements should require extraordinary proof 
that it is needed for practical as well as security reasons. The burden 
of proof is on the nay-sayers, especially since it is so trivial to 
implement these days.

Mike


From nobody Mon Feb  1 18:05:13 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 68CEC3A166E for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:05: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, 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 Djqt6nvFp4QU for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:05:11 -0800 (PST)
Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (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 EFE163A166C for <dmarc@ietf.org>; Mon,  1 Feb 2021 18:05:10 -0800 (PST)
Received: by mail-ot1-x334.google.com with SMTP id i20so18387683otl.7 for <dmarc@ietf.org>; Mon, 01 Feb 2021 18:05:10 -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=ftHH+5RgQ9m19Mv6zYYCCVhKczF61QjpNGu2wFxnRhE=; b=mjDnYoYTww8I6efgtsQGlz1CEmPyc1vllcFnVmUkeF0eJUF+T8wT+bzlgprZzaV5wi VeAC1BIDfFxvNHjCDdNNyAEZuyR+k0KZnocXp2km4MwCiXZOYElQKn3vo0ImU6QHIcjL 9lqhGrobSge+AqU8kzKXQj9QN9qTZjXD7WpBLI/gIdWGrUwxxtdE6U9yZ++0Ox94z2S6 EStOh0O0LT5/4+LK9He1UA3PqkIWIYdVl66Ly2m6yX0hb7MzyK0rQ4YCl8Br78KXR+DD gxIgVW2Hw59Llj/Al8svdlTWzz048h4FbnDi7vS1DQW67ONh21Z885KKTOQjjpEuaYmO IKnw==
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=ftHH+5RgQ9m19Mv6zYYCCVhKczF61QjpNGu2wFxnRhE=; b=dtbIyEWiupwbzXE8K+byAtfjOclBVoz+Hk0QHSUgbYKZFMejAQVjFM5fweaMPNl9AR G0R8i2No6ajHTGD8+kXbD5EJ/6dk83DZ5j4YnI+O11tJT6zHwy6OnhOki52I1aNCqplt tLrVMmgvXPrinbg2QvpY4px47/1GJWY1jqX3mFl/3MPA5SydtyVPXkYkpg60PsWYchYi YbRGh6y5zwQlQ5i0p2VkWqnw1S7TmyH5atxvmaH44UXR35u5uU/LPZOrxcinK10wGTaL Iat/Pgn7AnHQI8lUAjkKb7FMvL0yTKORLrbMAiFKAGUF+8LhlnBozho4ZtiHLuQKEbUu iA3A==
X-Gm-Message-State: AOAM530GYPu7NQDDT6CI7eenubYs9ovtlpm8fPhuQraWFjQSpDaIl6H1 /I5W8/65NkAPfAoUBhXlhitixahhxXrbBw==
X-Google-Smtp-Source: ABdhPJy8pVVG23bHTSUyYhM7pHDpsHLppVAhnZkjKpt0kBcnmmORZr8HyjxknnBYAZ1zI1a2Ao/wqw==
X-Received: by 2002:a9d:2c2:: with SMTP id 60mr13337922otl.70.1612231509669; Mon, 01 Feb 2021 18:05:09 -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 u191sm4828544oif.6.2021.02.01.18.05.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 18:05:09 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com> <f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <554d5bd4-8a62-15d2-8f71-aa942c17e654@gmail.com>
Date: Mon, 1 Feb 2021 18:05:06 -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: <f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com>
Content-Type: multipart/alternative; boundary="------------C21544E30582F55CD967A66F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/0yNJMCztSLJpKJK7ufXxi128w10>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 02:05:12 -0000

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

On 2/1/2021 5:58 PM, Michael Thomas wrote:
> This, on the other hand, should be measurable. Saying that we should 
> ignore authentication requirements should require extraordinary proof 
> that it is needed for practical as well as security reasons. The 
> burden of proof is on the nay-sayers, especially since it is so 
> trivial to implement these days. 

Or perhaps:

    1. Barrier to adoption, for something that supposedly needs a lot
    more adoption

    2. Doesn't seem to make much difference.

I'd class those as suggesting rather strongly that the burden is on 
those that want to impose the barrier, rather than those who don't.

The problem with arbitrarily claiming a requirement, without justify it 
carefully and in a balanced matter is that it is, well, arbitrary.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


--------------C21544E30582F55CD967A66F
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>
    <div class="moz-cite-prefix">On 2/1/2021 5:58 PM, Michael Thomas
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com">This, on
      the other hand, should be measurable. Saying that we should ignore
      authentication requirements should require extraordinary proof
      that it is needed for practical as well as security reasons. The
      burden of proof is on the nay-sayers, especially since it is so
      trivial to implement these days.
    </blockquote>
    <p>Or perhaps:</p>
    <blockquote>
      <p>1. Barrier to adoption, for something that supposedly needs a
        lot more adoption<br>
      </p>
      <p>2. Doesn't seem to make much difference.</p>
    </blockquote>
    <p>I'd class those as suggesting rather strongly that the burden is
      on those that want to impose the barrier, rather than those who
      don't.</p>
    <p>The problem with arbitrarily claiming a requirement, without
      justify it carefully and in a balanced matter is that it is, well,
      arbitrary.<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>

--------------C21544E30582F55CD967A66F--


From nobody Mon Feb  1 18:13:22 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 49B103A167D for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:13:20 -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, 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 KPS81vlBFJld for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:13:18 -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 284363A169A for <dmarc@ietf.org>; Mon,  1 Feb 2021 18:13:11 -0800 (PST)
Received: by mail-pl1-x631.google.com with SMTP id j11so8975122plt.11 for <dmarc@ietf.org>; Mon, 01 Feb 2021 18:13:11 -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=DL3SR1Vg2+NmXfJEAyRkECBQinXWn+4jQBxV5scW4uk=; b=ZhRXypH8JvF1ObY42Zm1DwG/6oRu7X3wWyM+Y905aOZP3pwC8r7lGLX71sXP/XIRsy xYa7KmQoOpPAeEyjDgHStBB5EX62j+c4f1YJ5+KK0dYjnRWyyYTaQG2zaAyg87Sl0j5B YvW17ncSrzjt4l1xs794c8YFqL+BPgi8GIuHoDAMuqyc4DSub1Z9O7sILLeWK8CtQmU5 7CRI9THfX/6ukZqt0NsZK76TJAuttEeo9LRPOT0FBodCisonlI8293abpnXulimMMZQR kgjYAqLWfEHaKBgIuIDWLyeEEUAMFeS9AQ6vO+y9hotneM4qxp8EZHqs0974c4ZR++ez 4+xg==
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=DL3SR1Vg2+NmXfJEAyRkECBQinXWn+4jQBxV5scW4uk=; b=KycxJ/cixCy+DLvBX54nltJkF+kv8gYeEiWSAXEbY7RjjsPUcEYNH8KKjEs8d9I5gV biq5x8WqcBCJO5sw5MeEfgHb80821VAokZEvMo9qw5psJ2DOZBfBDDTnX0cizBRv5Vnv UuNAhlDWo9Old7beZZFRpqZU72ORS93SaDld8v58f4XPwIzP0C0/fW1akVAi7QL57epU zUihwsfOjYD8buqLeaCZyNchzWkU/Jz3B7bMj5LBX8TinRI6PlabwLUXDUqd3xAbQQNG JzG++dthdBg6UOMqwutIWT6z/7XhyHzKA447J5DQPzoGDh6fzXjsQ2ddWSHe2H2UBamV 9e0w==
X-Gm-Message-State: AOAM531osNBdS7caIzS4GRMMZv+oM3Ofz4D9eOOH1Qg5fabsyBVSqdf/ u7ylh0aNaCjCV0H8IdcCilTvVnyLASeIpg==
X-Google-Smtp-Source: ABdhPJyn3eNZi8u4KURSffISs6R+S6d7fzsRsvfCTN98dNI7T8+ldwpgpIIugRy/ItReor9elsE6XA==
X-Received: by 2002:a17:90a:cc03:: with SMTP id b3mr1857430pju.2.1612231990277;  Mon, 01 Feb 2021 18:13:10 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id lw4sm90049pjb.16.2021.02.01.18.13.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 18:13:09 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com> <f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com> <554d5bd4-8a62-15d2-8f71-aa942c17e654@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <18dbfe7b-3f74-69bd-fa54-7f9b1fb66557@mtcc.com>
Date: Mon, 1 Feb 2021 18:13: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: <554d5bd4-8a62-15d2-8f71-aa942c17e654@gmail.com>
Content-Type: multipart/alternative; boundary="------------C37EAD52443BDAABC2B2A940"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/EeSRQ7iO8RZdey6LXfcfKaK6pJo>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 02:13:20 -0000

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


On 2/1/21 6:05 PM, Dave Crocker wrote:
> On 2/1/2021 5:58 PM, Michael Thomas wrote:
>> This, on the other hand, should be measurable. Saying that we should 
>> ignore authentication requirements should require extraordinary proof 
>> that it is needed for practical as well as security reasons. The 
>> burden of proof is on the nay-sayers, especially since it is so 
>> trivial to implement these days. 
>
> Or perhaps:
>
>     1. Barrier to adoption, for something that supposedly needs a lot
>     more adoption
>
>     2. Doesn't seem to make much difference.
>
> I'd class those as suggesting rather strongly that the burden is on 
> those that want to impose the barrier, rather than those who don't.
>
> The problem with arbitrarily claiming a requirement, without justify 
> it carefully and in a balanced matter is that it is, well, arbitrary.
>
>
Because we all know how well unauthenticated data worked out for email. 
I fail to see why anybody would be in favor of digesting unauthenticated 
data when the method of authenticating it is trivial and well known. 
It's an extraordinary claim that needs to be backed up. But you don't 
need to convince me; you need to convince the security AD's and cross 
area reviewers.

Mike


--------------C37EAD52443BDAABC2B2A940
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 2/1/21 6:05 PM, Dave Crocker wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:554d5bd4-8a62-15d2-8f71-aa942c17e654@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div class="moz-cite-prefix">On 2/1/2021 5:58 PM, Michael Thomas
        wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com">This,
        on the other hand, should be measurable. Saying that we should
        ignore authentication requirements should require extraordinary
        proof that it is needed for practical as well as security
        reasons. The burden of proof is on the nay-sayers, especially
        since it is so trivial to implement these days. </blockquote>
      <p>Or perhaps:</p>
      <blockquote>
        <p>1. Barrier to adoption, for something that supposedly needs a
          lot more adoption<br>
        </p>
        <p>2. Doesn't seem to make much difference.</p>
      </blockquote>
      <p>I'd class those as suggesting rather strongly that the burden
        is on those that want to impose the barrier, rather than those
        who don't.</p>
      <p>The problem with arbitrarily claiming a requirement, without
        justify it carefully and in a balanced matter is that it is,
        well, arbitrary.<br>
      </p>
      <br>
    </blockquote>
    <p>Because we all know how well unauthenticated data worked out for
      email. I fail to see why anybody would be in favor of digesting
      unauthenticated data when the method of authenticating it is
      trivial and well known. It's an extraordinary claim that needs to
      be backed up. But you don't need to convince me; you need to
      convince the security AD's and cross area reviewers.<br>
    </p>
    <p>Mike<br>
    </p>
  </body>
</html>

--------------C37EAD52443BDAABC2B2A940--


From nobody Mon Feb  1 18:24:29 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 3FA3A3A1692 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:24:27 -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, FREEMAIL_FROM=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 Q9i2yKI0wjOj for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:24:25 -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 CB2DF3A168E for <dmarc@ietf.org>; Mon,  1 Feb 2021 18:24:25 -0800 (PST)
Received: by mail-ot1-x32d.google.com with SMTP id i20so18420508otl.7 for <dmarc@ietf.org>; Mon, 01 Feb 2021 18:24:25 -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=PlH9pyiFroqY7BbZvCd6rnTyP0IB4TLHiA/Be9ReEPU=; b=EhJ3R9jaPgE0IYZsRXPdW3ofGqPhVCsW8uWD1w19/N26uo2AX5fQAf0vcFMm9kUZId RoHJ2u+MKWm07oNdfdKS63ZAdyoHJy/xggKilbZ2Xsih4Mv24my3WU36BRhVcRVjHhd6 UKhoilQyUsEwTQFs6gYWigbwTTTN76UEjmcQxC2sBoIH9SW2FsguJRGs34HS5Qiei+P9 LRyOxc/uuiN+FaNgXdtkKa+DVCTf/bStop5It7df4e3j9rvAnUQzZVjABa4b4DjXDMaU loofglhgyu3YYDJlpG/9rMoOfn5NfpJA7/vqtsUmXrTQNPMIrW+a2r41H7p0Z7epLDJ4 59+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-transfer-encoding :content-language; bh=PlH9pyiFroqY7BbZvCd6rnTyP0IB4TLHiA/Be9ReEPU=; b=hiHzP3p/5D/EoZQoyYTPjBVMqzvS2Homx1wzsoni0pTEDj/41/fUeSqKEt/4ghqi/H 2FXPdJGmzoCdiFdECXRv+U98o3Q9Ny6Ru4YW0N0DOKmpsyVVZohf2Z8yk7U5RDPnV82E FocW6ghgNsUfsAvpPoH1HfBgLTCf6spMTMhgFDlf5Ap729x1BYb/8IQ3CjSt6Lb3GO2B vt5g1BEunVCB2P+l8m942atE6WTZlnZQD7dVul1hTqt5lasIYaxGu8BBcKx574LxmnA/ +yPRY5G8hnDZ6Eu8ZvcPKpgzKJl1O2+Z42oF1+epXRFP59293sQ93mtwXPJxMz6WjVGw H2VQ==
X-Gm-Message-State: AOAM531JEJF3tioH04m+KJy5N23KHxbc8OQdV/zS25c3zFoZXbDvxMRm uldq8CzURCdvcXF/EaBQPgT4BGMV1IXxiw==
X-Google-Smtp-Source: ABdhPJzL6wO/iq84LIBBdwGewSxP+S85YD4X5SqvbFM/SpWBi0lxXUu5YrfL7qg5OlCbW3dvHTZVeg==
X-Received: by 2002:a9d:61d0:: with SMTP id h16mr13303600otk.1.1612232664947;  Mon, 01 Feb 2021 18:24:24 -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 i26sm4467517oov.47.2021.02.01.18.24.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 18:24:24 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com> <f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com> <554d5bd4-8a62-15d2-8f71-aa942c17e654@gmail.com> <18dbfe7b-3f74-69bd-fa54-7f9b1fb66557@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <1babf085-abd2-fc76-3167-231ef7e9fada@gmail.com>
Date: Mon, 1 Feb 2021 18:24:22 -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: <18dbfe7b-3f74-69bd-fa54-7f9b1fb66557@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/pY8f7SlyNv-WgRAfVB8MGcoPL0w>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 02:24:27 -0000

On 2/1/2021 6:13 PM, Michael Thomas wrote:
> Because we all know how well unauthenticated data worked out for 
> email. I fail to see why anybody would be in favor of digesting 
> unauthenticated data when the method of authenticating it is trivial 
> and well known. It's an extraordinary claim that needs to be backed 
> up. But you don't need to convince me; you need to convince the 
> security AD's and cross area reviewers.


DMARC has been deployed for 6 or 7 years.  Where is this onerous abuse 
on reporting that you feel is inevitable?

I suspect you've assumed the incentives for sending problematic reports 
are the same as the incentives for abuse of generic mail, while they are 
likely quite different.

And no, it isn't trivial at all.  Setting this stuff up properly takes 
skill and effort, which means it's expensive.  And often is fragile.  
Hence the need to attend thoughtfully to pragmatics.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Mon Feb  1 18:32:05 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 2B6CA3A16B2 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:32:02 -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 Ww0YvOke3dFZ for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:32:00 -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 DBFE93A16BC for <dmarc@ietf.org>; Mon,  1 Feb 2021 18:31:59 -0800 (PST)
Received: by mail-vs1-xe33.google.com with SMTP id q23so3842527vsg.4 for <dmarc@ietf.org>; Mon, 01 Feb 2021 18:31: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=Kgm6Rxewtr85wGcOYt9+DXyFJ+N1u1f9ZUtjfErl9Cg=; b=L+GqIIZ63Efe98nbeY68P5EnHAVvxnLkOi+zXv/TuPPoIaSlYpls0utf9ZZL5X+fZY KzParKMdYNcp06Fa9QTEDP0b6+nYqLX8Hs4lpmk3cV1hHAGXbbRT89ev3CNIY4gDoiGx 1Fg9ZJ2E8Vsd3QewrEEPqRMUNoKHV7aHbHQQnEauT1wGalP61KTMgmDyMZFtJAA6dYvk gYFHHkLB8wf6ICSRGFIs/cXKv/a+cbEWGI/H7jK/W1ZnDvppoFM8ar1a75qU2MXHh5kl BYdvgTlmmzaLlx75G/dAMQhEoHXfgD8jG/UgdlX7YjP3dwDixxpsmDXWs/ndkdWZpnrn J99Q==
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=Kgm6Rxewtr85wGcOYt9+DXyFJ+N1u1f9ZUtjfErl9Cg=; b=eIqyroczqO7qmLrwel8D5K+qgGsex0lTaxw87vAJkfr85hYk+QooFaOe2A2orCF5tS 4hK7SPQmVdJUQXeNXr57c8vVpE8NGCs2krbC9vhp21xuqd/11lCXn0Y/hffCr5L6v5zG CwKhxgdir5+/did3gdD5ztqYdQtdZRjwFCML42IeEWc3JeHNQ1Ix9N1FsL1pf9TN3qmr 6lyxqsrZS0P3KxvrYdd7SWeWB7UjJa2g4SCKRL3tTwR/OwBtoy+9Q1/S+7+9iBxOtycF JXMikS3jX/J7vUKcFkbqxFVak66OXE/m+5ikNAxnJ9DF+BtbXwP7QEM8K0+0M+KDulp/ aJVw==
X-Gm-Message-State: AOAM5329vgtlvQJx/ViDRDsPA9R58tAXU5Ls/0z7HWiWiMsQi44bn5mv JF1IJY3wnUUit8LuYw6rCgswGdIMSAptBRnZrp+i+OsKSo4=
X-Google-Smtp-Source: ABdhPJx3MFCIcZk5t/yKrVYjnRdjih9AZvyYWbXMQfjG9LyJzzQJ1Aqp9mXYa4mEvfXA1PfhCFuBl6iIA1FRyex7hs4=
X-Received: by 2002:a67:87c2:: with SMTP id j185mr10854004vsd.25.1612233118619;  Mon, 01 Feb 2021 18:31:58 -0800 (PST)
MIME-Version: 1.0
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com> <f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com> <554d5bd4-8a62-15d2-8f71-aa942c17e654@gmail.com> <18dbfe7b-3f74-69bd-fa54-7f9b1fb66557@mtcc.com>
In-Reply-To: <18dbfe7b-3f74-69bd-fa54-7f9b1fb66557@mtcc.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 1 Feb 2021 21:31:48 -0500
Message-ID: <CAH48ZfwseVXQY6s4PyVrSGLXu8suOQkBA7pvW+EOjkWp674_pg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000549a5905ba51466c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9oZrMJlmm4ItFJfZ0iXKneEv4TU>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 02:32:05 -0000

--000000000000549a5905ba51466c
Content-Type: text/plain; charset="UTF-8"

Michael, let it go.

If someone stops you to say "your zipper is down", you will not ask them
for proof of identity, you will excuse yourself and investigate the
problem.   By my reckoning, DMARC reports are a lot like that.

Source Alpha says, "Server X is sending unauthenticated mail for Domain
Y."   Several possbilities exist:
- You already distrust information coming from Source Alpha, so you reject
or discard the information.
- You already have enough data to investigate, so you ignore this report.
- You decide to investigate this report, which produces one of three
outcomes:
     - Server X has a problem, and you fix it.
     - Server X is not your server, so you confirm that it is not your
problem.
     - Source Alpha is wrong, so you add a rule to reject or discard future
reports from that source.

I do not see any reason for a DMARC report to flow indirectly, so I would
be suspicious of any reports that appeared to come that way.   This means
all I really need is an SPF PASS.

But I do not need positive identification of the source.

On Mon, Feb 1, 2021 at 9:13 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 2/1/21 6:05 PM, Dave Crocker wrote:
>
> On 2/1/2021 5:58 PM, Michael Thomas wrote:
>
> This, on the other hand, should be measurable. Saying that we should
> ignore authentication requirements should require extraordinary proof that
> it is needed for practical as well as security reasons. The burden of proof
> is on the nay-sayers, especially since it is so trivial to implement these
> days.
>
> Or perhaps:
>
> 1. Barrier to adoption, for something that supposedly needs a lot more
> adoption
>
> 2. Doesn't seem to make much difference.
>
> I'd class those as suggesting rather strongly that the burden is on those
> that want to impose the barrier, rather than those who don't.
>
> The problem with arbitrarily claiming a requirement, without justify it
> carefully and in a balanced matter is that it is, well, arbitrary.
>
> Because we all know how well unauthenticated data worked out for email. I
> fail to see why anybody would be in favor of digesting unauthenticated data
> when the method of authenticating it is trivial and well known. It's an
> extraordinary claim that needs to be backed up. But you don't need to
> convince me; you need to convince the security AD's and cross area
> reviewers.
>
> Mike
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr">Michael, let it go.<div><br></div><div>If someone stops yo=
u to say &quot;your zipper is down&quot;, you will not ask them for proof o=
f identity, you will excuse yourself and investigate the problem.=C2=A0 =C2=
=A0By my reckoning, DMARC reports are a lot like that.=C2=A0 =C2=A0</div><d=
iv><br></div><div>Source Alpha says, &quot;Server X is sending unauthentica=
ted mail for Domain Y.&quot;=C2=A0 =C2=A0Several possbilities exist:</div><=
div>- You already distrust information coming=C2=A0from Source Alpha, so yo=
u reject or discard the information.</div><div>- You already have enough da=
ta to investigate, so you ignore this report.</div><div>- You decide to inv=
estigate this report, which produces one of three outcomes:</div><div>=C2=
=A0 =C2=A0 =C2=A0- Server X has a problem, and you fix it.</div><div>=C2=A0=
 =C2=A0 =C2=A0- Server=C2=A0X is not your server, so you confirm that it is=
 not your problem.</div><div>=C2=A0 =C2=A0 =C2=A0- Source Alpha is wrong, s=
o you add a rule to reject or discard future reports from that source.</div=
><div><br></div><div>I do not see any reason for a DMARC report to flow ind=
irectly, so I would be suspicious of any reports that appeared to come that=
 way.=C2=A0 =C2=A0This means all I really need is an SPF PASS.</div><div><b=
r></div><div>But I do not need positive identification of the source.</div>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Mon, Feb 1, 2021 at 9:13 PM Michael Thomas &lt;<a href=3D"mailto:mike@mt=
cc.com">mike@mtcc.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 2/1/21 6:05 PM, Dave Crocker wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div>On 2/1/2021 5:58 PM, Michael Thomas
        wrote:<br>
      </div>
      <blockquote type=3D"cite">This,
        on the other hand, should be measurable. Saying that we should
        ignore authentication requirements should require extraordinary
        proof that it is needed for practical as well as security
        reasons. The burden of proof is on the nay-sayers, especially
        since it is so trivial to implement these days. </blockquote>
      <p>Or perhaps:</p>
      <blockquote>
        <p>1. Barrier to adoption, for something that supposedly needs a
          lot more adoption<br>
        </p>
        <p>2. Doesn&#39;t seem to make much difference.</p>
      </blockquote>
      <p>I&#39;d class those as suggesting rather strongly that the burden
        is on those that want to impose the barrier, rather than those
        who don&#39;t.</p>
      <p>The problem with arbitrarily claiming a requirement, without
        justify it carefully and in a balanced matter is that it is,
        well, arbitrary.<br>
      </p>
      <br>
    </blockquote>
    <p>Because we all know how well unauthenticated data worked out for
      email. I fail to see why anybody would be in favor of digesting
      unauthenticated data when the method of authenticating it is
      trivial and well known. It&#39;s an extraordinary claim that needs to
      be backed up. But you don&#39;t need to convince me; you need to
      convince the security AD&#39;s and cross area reviewers.<br>
    </p>
    <p>Mike<br>
    </p>
  </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>

--000000000000549a5905ba51466c--


From nobody Mon Feb  1 18:33: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 6D6183A169B for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:33:44 -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 3lYNp1xdyo0s for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:33:43 -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 805733A1690 for <dmarc@ietf.org>; Mon,  1 Feb 2021 18:33:43 -0800 (PST)
Received: by mail-pl1-x632.google.com with SMTP id g3so11618027plp.2 for <dmarc@ietf.org>; Mon, 01 Feb 2021 18:33: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=RiqRe63PcvOLbDsDxCxNA86eAThR7IsHAMgUx4IjVPM=; b=JTK8KvE/eZ+vr386AkSOeBaBnydrCDL+7/dIiiW7LEdbRvGMnXfoznTYUaB9JxyHQB 7fJamwypNzoTp+VGr/+0RPFtSSTor6tle+q6CBEWzwrBtUsB7Ro2ZOO3Bnm2fST3mmKr t415OQxjTtBrnFUvc1Qh5wDFY9VbvjxV+UBUrVRNJBIaTevqoIQ3pdE3DXlwpCZ4l8+C q9wHwhd4m8jqfR2/uQmYXeFCkhG9yGbU04ED9Tnbn6zwib9W7/G/s6TyJSmontF9IOwy Q/Fhw+i955lvN8hd7HorkaYFiMtmQGrojkxiqdYypmXroIjKbEI/VyqWI7CRjE2ZVJ1y j+ig==
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=RiqRe63PcvOLbDsDxCxNA86eAThR7IsHAMgUx4IjVPM=; b=o9e2iOAqikOcFMjX5ZwBWlJje/pXMMGt9RDDm30OyKYurF7CCKqRX37mmLrt1Gtq3d iLKxudXWojS95AkONsilM/MkKBBIa6zfqeQO1tIuCnmeLZJHrYyKZTrvxIQwwrps1y/m Un3dkQas6y4Gyw2aERI13UF+J+e7zoaMNPgmR726wbCJvdRa5TsXA561yBg4YzuIfeK1 Z1lQ66eZaQuFV3Xomyk8AnmEavkjqW3zZqgioX8bVrD3gyHPjHLVPvvyrwFSuIn1ZOzo aXZNK7YOhAk4aFWUg2dMRHAIcGHPikSfrQMkGZmq4gOaf86fVN/PrCjXOBMjF7qSvM+S u6TA==
X-Gm-Message-State: AOAM530z92ofuqCrmuOdMMM8VCdtf4zV1glx1HpfcrgE1+05DYEdvdin tQAiorSYcYGZfpXIwuHYhBL//3fmfK5hKg==
X-Google-Smtp-Source: ABdhPJx2sRR1Mm9+eTOsRFou7id4qjXnMcLrHkaA8doOLt5bS8nXNB74Utw2iywcNzry3mb9XxofAw==
X-Received: by 2002:a17:90a:4548:: with SMTP id r8mr1910294pjm.16.1612233222508;  Mon, 01 Feb 2021 18:33:42 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id i9sm19737145pfo.146.2021.02.01.18.33.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 18:33:41 -0800 (PST)
To: Dave Crocker <dcrocker@gmail.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com> <f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com> <554d5bd4-8a62-15d2-8f71-aa942c17e654@gmail.com> <18dbfe7b-3f74-69bd-fa54-7f9b1fb66557@mtcc.com> <1babf085-abd2-fc76-3167-231ef7e9fada@gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <bb6d4047-e51a-48a5-3e23-3e03c7a73ce1@mtcc.com>
Date: Mon, 1 Feb 2021 18:33: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: <1babf085-abd2-fc76-3167-231ef7e9fada@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/qRbLzbxSR1_nJ2J00NontjijNNw>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 02:33:44 -0000

On 2/1/21 6:24 PM, Dave Crocker wrote:
> On 2/1/2021 6:13 PM, Michael Thomas wrote:
>> Because we all know how well unauthenticated data worked out for 
>> email. I fail to see why anybody would be in favor of digesting 
>> unauthenticated data when the method of authenticating it is trivial 
>> and well known. It's an extraordinary claim that needs to be backed 
>> up. But you don't need to convince me; you need to convince the 
>> security AD's and cross area reviewers.
>
>
> DMARC has been deployed for 6 or 7 years.  Where is this onerous abuse 
> on reporting that you feel is inevitable?

Email was around for 20 years until spam became a problem. We know how 
this plays out: bad guys do the least amount of work possible until they 
have to react. When it becomes a barrier as p=reject does, they take 
action to protect their turf. Plugging an obvious security hole with a 
well known and trivial set of authentication mechanisms to prevent 
forgery should be the default posture. Anybody who is against that needs 
to explain in depth why it should not be the case. Especially since it's 
part of DMARC now.

Mike, security related specs thumbing their nose at security is a very 
peculiar stance.


From nobody Mon Feb  1 18:37: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 625A63A16A0 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:37:40 -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 5K5mHgQBi6oJ for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:37:39 -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 552773A169F for <dmarc@ietf.org>; Mon,  1 Feb 2021 18:37:39 -0800 (PST)
Received: by mail-pl1-x62e.google.com with SMTP id d13so11622540plg.0 for <dmarc@ietf.org>; Mon, 01 Feb 2021 18:37: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=vvBrAK5sGMsLcGsp/rybCv2bc4x34Y2lxbnVfMEnTSQ=; b=GgEpQrc5Q2KgpoI6+oG9bUCZan42Bq4XqMRtx58TDbcA4MeKTm+5SAZlfZHSKwW780 N0TZHhyoJbFjGT3PcbnVhXMNN2ZpujW8mM174akY12YtwndJLT1N3zWlKtCjCVvGEAez sHAHfrdIkfD3vXpUcGEG0CvuJITzEhyOgPxWEhJIBra0eqPGi9cASF6zSi041njNhAxd yH/x/TWs9HJkcJXfQHoeXEcL+4jp4vHTlIi7hW1oJ9tyLIopyZvU82akoHHt8c9lK+Lz mCxUb8czqYlQsNs8/T8k3VqnKKkMsyw8nIUqaqAACAPT4A7Az3lIsESjdbAe9l4vOJON o9OQ==
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=vvBrAK5sGMsLcGsp/rybCv2bc4x34Y2lxbnVfMEnTSQ=; b=X3Go3lKVVpFhI+57xz7dfvdUJFQn9BqpRIWo+K6UC09Io82XEp5shhiXzwqX7UVR91 UWJDrwmvtdxR3I/FJlwkinOj4ff5eqNjiTJC9Bd9an9zhQROFmp+PUApNpVt1rNnSnmE 5VV9/0SG7fsvFAktFB4Hb92sUEhkEP08dJ1qxFqDN05DrX1CVPkPfRZSWVBnHuEERAKO QHL3OjTspUts4efh2eLzEht4PV5Cl5QlKeCTwp3jwO7+lKEW/u9VmMgWnHmwu8q3XhMl +D9es8dWxnEdYBlVgHEtU/LadqxJGKe/ZmLvFW49XzI/OJX+EquXP+4+x75ZCm6FgwsN ZJNw==
X-Gm-Message-State: AOAM5311yRuHtutm3WCZGXqd5OzC8e7qJIRu6qJOzt7HF2e5OvXzRQ7Z YQpVqKoWfSOmoy9bgfexoZE0q1y1UytlUg==
X-Google-Smtp-Source: ABdhPJyiY+AIAjxQvUyA+uP6DoqcBXw/fpcty6E9w6VA+JRLPeF0Gw4c7+JxyDAhvJSzU0c7QtJCGQ==
X-Received: by 2002:a17:902:ec83:b029:df:e942:93c0 with SMTP id x3-20020a170902ec83b02900dfe94293c0mr20028715plg.55.1612233458417;  Mon, 01 Feb 2021 18:37:38 -0800 (PST)
Received: from mike-mac.lan (107-182-37-188.volcanocom.com. [107.182.37.188]) by smtp.gmail.com with ESMTPSA id g5sm19903960pfm.115.2021.02.01.18.37.37 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 18:37:37 -0800 (PST)
To: dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com> <f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com> <554d5bd4-8a62-15d2-8f71-aa942c17e654@gmail.com> <18dbfe7b-3f74-69bd-fa54-7f9b1fb66557@mtcc.com> <CAH48ZfwseVXQY6s4PyVrSGLXu8suOQkBA7pvW+EOjkWp674_pg@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <e6665089-1bb3-3ca4-0cce-b1afbd7b1296@mtcc.com>
Date: Mon, 1 Feb 2021 18:37: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: <CAH48ZfwseVXQY6s4PyVrSGLXu8suOQkBA7pvW+EOjkWp674_pg@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/g5ZfUq8u7sYTIpcgUk5TgHPQrmM>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 02:37:40 -0000

On 2/1/21 6:31 PM, Douglas Foster wrote:
> Michael, let it go.
>
> If someone stops you to say "your zipper is down", you will not ask 
> them for proof of identity, you will excuse yourself and investigate 
> the problem.   By my reckoning, DMARC reports are a lot like that.
>
1. This is already part of DMARC, though it can use some work

2. If somebody says your zipper is down, they can clock you when you 
look down to check to steal your wallet. Do not underestimate what 
attackers can do with unauthenticated data.

Mike


From nobody Mon Feb  1 18:42:32 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 308363A169A for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:42:31 -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, FREEMAIL_FROM=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 R5V33mSU5YR4 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:42:29 -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 C7BD83A165C for <dmarc@ietf.org>; Mon,  1 Feb 2021 18:42:29 -0800 (PST)
Received: by mail-ot1-x329.google.com with SMTP id v1so18461166ott.10 for <dmarc@ietf.org>; Mon, 01 Feb 2021 18:42:29 -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=kUm0Zgse4cGUC70LmCTy+A/iJ6u80QTpDlYPaHLOVoo=; b=qcS1CXLOfFNT2Jzo+XE1hqPKMEKWpKOLZGiZiD9Tv2oFzIQJemiwkc8iphnDN8HRfQ v6tj0I40spwD8sBfQV6I11QiKpkSuoxS4nbu57b7kXe7uk3L9BQwv6Vhy10uKhZC80CD GnjQjuQ90y5vsOksyv5+pR8Z3ifX1vewVb97fQB+ONrFCvmeWS8LR4WyNp3ILiGcvfJr sxthLSWHQxBUI47LrtDBy3I0UF4q3fLV3u8R9Ct2SlEu8clfg9fSKL+HiJym740297Vp DT+iDDZupoWJ3ctDQJCA9LNuVrs1LBxwpVJKWLe0rm4yZ4u8vWcD1hcqcFWPbIhZTLBU d+xA==
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=kUm0Zgse4cGUC70LmCTy+A/iJ6u80QTpDlYPaHLOVoo=; b=KArvFxW9KapXRrOk88VCab0KvXEnkcXSpVddBHUbdWDiqrNKhGyKcK8y8MbBFsso6S Xmk6zEE+u+edhbKUAoPSM7LUoYpS99a94ABhYdLU2RZ5SUMoBAqRbIZSKzTcHvpPt3+x 2xu+Cyf0HxSJ1WlwEEaftnxaoKifHiGLNLGhmBUoWi6UUCDTh/grrJg5aDTYL3j6WDfL sbdB+Am20v9mJs12llLrM+R2K/e+EwnfAZGpagZvo/rzWWUrjJG6FRU8zPE6K1htKVI+ iBb5bf+ChyQ1dS0VokOBuOZcP+p6jJTRqpE1BrwR+xDqb66vi70qhBK6lQOMNOe8Z/oV YdLg==
X-Gm-Message-State: AOAM533RAB2h6hd+HbHQyoEcwbFy/TLP0h1Jd2ccX7/MDYl/IvFP+qH2 Q+yDE//ZaF2SFaypuoh1S2mtPQvFK4IbMQ==
X-Google-Smtp-Source: ABdhPJyuLm/RgU3qf0QHZHvXX14IJ1qaRmynj5ktjXOPsuhQHFvGgyfE43kGlUn0ssv1cvRQXp+S3w==
X-Received: by 2002:a05:6830:92:: with SMTP id a18mr13837208oto.23.1612233748889;  Mon, 01 Feb 2021 18:42:28 -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 e20sm4350415otr.14.2021.02.01.18.42.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 18:42:28 -0800 (PST)
To: Michael Thomas <mike@mtcc.com>, dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com> <f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com> <554d5bd4-8a62-15d2-8f71-aa942c17e654@gmail.com> <18dbfe7b-3f74-69bd-fa54-7f9b1fb66557@mtcc.com> <1babf085-abd2-fc76-3167-231ef7e9fada@gmail.com> <bb6d4047-e51a-48a5-3e23-3e03c7a73ce1@mtcc.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <dcace17c-6ca0-1a73-f96e-a1158c5c4fc8@gmail.com>
Date: Mon, 1 Feb 2021 18:42:25 -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: <bb6d4047-e51a-48a5-3e23-3e03c7a73ce1@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/ySy4WXJsNaTIS1boIti94jZ2C_Q>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 02:42:31 -0000

On 2/1/2021 6:33 PM, Michael Thomas wrote:
>
> On 2/1/21 6:24 PM, Dave Crocker wrote:
>> DMARC has been deployed for 6 or 7 years. Where is this onerous abuse 
>> on reporting that you feel is inevitable?
>
> Email was around for 20 years until spam became a problem. 

Perhaps you missed the difference in scale between all of the last 5-7 
years versus pretty much all of that 20 years?

In other words, just to keep this simple:  They not in the least 
comparable.  Also, cf, my previous reference to incentives.


> We know how this plays out: bad guys do the least amount of work 
> possible until they have to react. When it becomes a barrier as 
> p=reject does, they take action to protect their turf. Plugging an 
> obvious security hole with a well known and trivial set of 
> authentication mechanisms to prevent forgery should be the default 
> posture. Anybody who is against that needs to explain in depth why it 
> should not be the case. Especially since it's part of DMARC now.
>
> Mike, security related specs thumbing their nose at security is a very 
> peculiar stance.
>
Mechanical application of a high-level script, without attending to the 
details that make the script actually work in a specific case, tends to 
lead to counter-productive decisions.  cf my earlier reference to 
barriers to entry and lack of damaging effect.

And flamboyant, aggressively hostile language like 'thumbing their nose' 
is not merely wrong, it is another attempt at gaslighting.  cf my 
earlier reference to hostile work environment.

sigh.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Mon Feb  1 18:44:41 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 436B33A16A4 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:44: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 (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 c2qLDSXOijd1 for <dmarc@ietfa.amsl.com>; Mon,  1 Feb 2021 18:44:38 -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 4FF913A16A3 for <dmarc@ietf.org>; Mon,  1 Feb 2021 18:44:38 -0800 (PST)
Received: by mail-ua1-x92c.google.com with SMTP id o31so1706725uae.2 for <dmarc@ietf.org>; Mon, 01 Feb 2021 18:44: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 :cc; bh=g4ILD3zJOV2FjR0FWXwLg8BdiS5eWS4W5fmAiovyxYo=; b=Tw6FP3KAsMD5/J89C2VdfIzW5GJrenVIPE2/Knqxh1m2yfm8L6lLri9Z0vzCGFzBT3 eWqEC+t7zJjvEdCh8NfqW29mZIdKe9uzVoX26Bwjta68pzRgZ/yOD+MQwWtSiC94db3p msr+JoKgmZS5PvnPMr9mBlqwTGMTkUu3HqDeGe7vwcng5C93/cPfBI3VkPcAb4YgAq+X cxYGTd/Y71uo8Tyfvk+oW0Ev2t4FVm4f00F9+AF9YRRvxNndL2fIRxwhgcqe3zggsEHa 8L4NQp0Dfq+wmF5tmYEGmipVBOZMQrhCowz80Db2nFIPta1GLJzeN7xV9eL5drZSnqDO YJ/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:cc; bh=g4ILD3zJOV2FjR0FWXwLg8BdiS5eWS4W5fmAiovyxYo=; b=abKgsH/ML6b+BpvNCtonPTNqX10h1hZjtVa93xbs0a2QGE8nS/slqSBDyBh6xVLDnR nwiaMCWjETjKcJsamjYehrFDC+3rKxBEgvUZScst0l2wnt7yvPR7AO/22wfC4/pu8sP/ ecnFdrS+YqYOt+XKO3SzdJqZnRXvFkeSs0VwQppKMKJRi+amWjnTY3FqX3ZByB4vs1a1 1c642FErNgHh/b0UnKjYQXDocTQ5S1g/9qAtFW2ohflfITIF4jkqVYgjEOOdNvnxQ/z/ uqI0Dt9AvXKkergUVDMUbdxENeyXPm2yKk164QtLZmbcBI6AKxZTQ/LZIHaLdeH0IKBQ WtaA==
X-Gm-Message-State: AOAM532e/MZCQmNrAh07mnVOTE9xiIXv+6VCqlmZTDb31U5nwF/GwliD PQGW52KGDPaBD+jdI3+IF2AVI3gxvseXOEhk3r7MPA==
X-Google-Smtp-Source: ABdhPJz7s0o7bFB8bBpM4VvNTBivEHFwk1EE1nAoqf9/JrNPDtKVXTyC2WsxeLRS6OT4xu0B2TNGjSxgWo6dZcdLgdE=
X-Received: by 2002:ab0:14a9:: with SMTP id d38mr4512935uae.47.1612233877239;  Mon, 01 Feb 2021 18:44:37 -0800 (PST)
MIME-Version: 1.0
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com> <f28780c0-8533-3a49-d5e3-99fcbbb446ed@mtcc.com> <554d5bd4-8a62-15d2-8f71-aa942c17e654@gmail.com> <18dbfe7b-3f74-69bd-fa54-7f9b1fb66557@mtcc.com> <CAH48ZfwseVXQY6s4PyVrSGLXu8suOQkBA7pvW+EOjkWp674_pg@mail.gmail.com> <e6665089-1bb3-3ca4-0cce-b1afbd7b1296@mtcc.com>
In-Reply-To: <e6665089-1bb3-3ca4-0cce-b1afbd7b1296@mtcc.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 1 Feb 2021 18:44:26 -0800
Message-ID: <CAOZAAfOSzcAZoKVDNEUGnB+Kjy+xB67-1Bhjr3PhDALDaCeYGA@mail.gmail.com>
To: Michael Thomas <mike@mtcc.com>, IETF DMARC WG <dmarc@ietf.org>
Cc: Douglas Foster <dougfoster.emailstandards@gmail.com>, Dave Crocker <dcrocker@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000008c49f705ba5173ac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/esLPsA6aSedDKWOqT5FklViBflI>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 02:44:40 -0000

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

All-- this thread is unproductive and becoming increasingly combative.

Per our discussion on list decorum and BCP 94 warnings (
https://mailarchive.ietf.org/arch/msg/dmarc/ub6xFEU15w0HAW82ZEnHr_mS180/):

    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=
 others
to
    respect the warning.

This is an official BCP 94 warning. Everyone please disengage from this
thread.

Seth, as Chair

On Mon, Feb 1, 2021 at 6:37 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 2/1/21 6:31 PM, Douglas Foster wrote:
> > Michael, let it go.
> >
> > If someone stops you to say "your zipper is down", you will not ask
> > them for proof of identity, you will excuse yourself and investigate
> > the problem.   By my reckoning, DMARC reports are a lot like that.
> >
> 1. This is already part of DMARC, though it can use some work
>
> 2. If somebody says your zipper is down, they can clock you when you
> look down to check to steal your wallet. Do not underestimate what
> attackers can do with unauthenticated data.
>
> Mike
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


--=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.

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

<div dir=3D"ltr">All-- this thread is unproductive and becoming increasingl=
y combative.<div><br></div><div>Per our discussion on list decorum and BCP =
94 warnings (<a href=3D"https://mailarchive.ietf.org/arch/msg/dmarc/ub6xFEU=
15w0HAW82ZEnHr_mS180/">https://mailarchive.ietf.org/arch/msg/dmarc/ub6xFEU1=
5w0HAW82ZEnHr_mS180/</a>):</div><div><br></div><div>=C2=A0 =C2=A0 Finally, =
several members of this working group seem to be very effective at<br>=C2=
=A0 =C2=A0 antagonizing each other. If a thread is spiralling, and a BCP 94=
 warning is<br>=C2=A0 =C2=A0 given and not heeded, all active participants =
in the thread after the<br>=C2=A0 =C2=A0 warning has been issued will be su=
spended, even if it=E2=80=99s to tell others to<br>=C2=A0 =C2=A0 respect th=
e warning.<br></div><div><br></div><div>This is an official BCP 94 warning.=
 Everyone please disengage from this thread.</div><div><br></div><div>Seth,=
 as Chair</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Mon, Feb 1, 2021 at 6:37 PM 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 so=
lid rgb(204,204,204);padding-left:1ex"><br>
On 2/1/21 6:31 PM, Douglas Foster wrote:<br>
&gt; Michael, let it go.<br>
&gt;<br>
&gt; If someone stops you to say &quot;your zipper is down&quot;, you will =
not ask <br>
&gt; them for proof of identity, you will excuse yourself and investigate <=
br>
&gt; the problem.=C2=A0 =C2=A0By my reckoning, DMARC reports are a lot like=
 that.<br>
&gt;<br>
1. This is already part of DMARC, though it can use some work<br>
<br>
2. If somebody says your zipper is down, they can clock you when you <br>
look down to check to steal your wallet. Do not underestimate what <br>
attackers can do with unauthenticated data.<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><div style=3D"text=
-align:left"><span style=3D"vertical-align:baseline"><br></span></div></spa=
n><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"><img src=3D"https://valimail-logos.s3.a=
mazonaws.com/valimail-logo-primary.svg" style=3D"height: 27px; width: 160px=
;"></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>

--0000000000008c49f705ba5173ac--


From nobody Tue Feb  2 03:40: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 AFAA23A19C9 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 03:40:13 -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 ohhqLPHmb4La for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 03:40: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 EA4B13A19C8 for <dmarc@ietf.org>; Tue,  2 Feb 2021 03:40:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612266008; bh=i9dI18J7hniF3QfpmnYa9lQsFw/TEoniheOUYX9qipk=; l=1279; h=To:References:From:Date:In-Reply-To; b=CATrFCkK0+yXMRJYe2i/iJtyFvO3Yx2e2PrUxBE4g3hhK4vu0+cdhjid0+uucrYwG gFJp3+raIDQmZv0WTN1GCW+PgpIn/MhH6p33rL5rRQul+mOGDJo/8jWAW9+hCJndjY jkJKCN9D7tntMzIH6psljLauz2NESnn8x/AyVn2RU8r6gHs7VL3HljQf1qusZ
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 00000000005DC083.0000000060193A18.00001C8F; Tue, 02 Feb 2021 12:40:08 +0100
To: John R Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210131200238.931356D11D79@ary.qy> <e7e27e1f-b6e6-96b6-e12e-672084562b8a@tana.it> <41bc91e9-8c9a-e2bd-a351-602436f3f5bb@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <14646a55-66a6-974e-baf8-55d8503c4f96@tana.it>
Date: Tue, 2 Feb 2021 12:40: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: <41bc91e9-8c9a-e2bd-a351-602436f3f5bb@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/aQQCrCV0tKKxViK1KcNhYcG5mqE>
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: Tue, 02 Feb 2021 11:40:14 -0000

On Mon 01/Feb/2021 17:29:23 +0100 John R Levine wrote:
>> 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.
>>
>>   Reporters SHOULD rate limit the number of failure reports sent to any
>>   recipient to avoid overloading recipient systems.
>>
>> Not MUST?
> 
> You might have other ways to prevent mailbombing, e.g., only sending failure 
> reports to people who you know have bigger mail systems than you do.


Right.  However, Murray recalled Section 6.3 of SMTP:

                           Whatever mechanisms are used, servers MUST
    contain provisions for detecting and stopping trivial loops.


Mailbombing in general is not a loop.  Two report generators reporting each 
other's failure to authenticate a failure report /is/ a loop.  So it deserves a 
MUST.  Perhaps:

    Reporters SHOULD rate limit the number of failure reports sent to any
    recipient to avoid overloading recipient systems.  In addition,
    reporters MUST ensure that such rate limiting or any other means
    can effectively stop possible mail loops.

?



Best
Ale
-- 



















From nobody Tue Feb  2 03:59:39 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 26FE03A19F8 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 03:59:38 -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 EtdK6PPpDqL7 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 03:59:36 -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 3343F3A19FA for <dmarc@ietf.org>; Tue,  2 Feb 2021 03:59:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612267172; bh=NNgvTKU9xUgWrafKKACVTum4tVA/KSJGFF7ZxcnGSfM=; l=1459; h=To:References:From:Date:In-Reply-To; b=B/T3G6KLXh3LXJeaFplLtH/uX8Qk+l+cxGRUvC01MG9bE3ZrLXJQkLyBiX9AL6Glv yk+h0pNKUHtfpogxlg/vL9NyQl3gO0mjS+oSoUJXVLdKIeFixcYh1Ti9wKBWYhmUIL P89rEJE6x1QtwAaHqOdKv19MU7nMmiUaYgmg4wUsqGzFaxPN/8Jyi0f5e0Fsy
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.0000000060193EA4.00001F1B; Tue, 02 Feb 2021 12:59:32 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210201231154.DAE426D208E1@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <2e39680f-ed2d-fa38-daaa-7e0627cf0fc7@tana.it>
Date: Tue, 2 Feb 2021 12:59:31 +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: <20210201231154.DAE426D208E1@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/KAErBJwljLW_csRColMW_VLTFDg>
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, 02 Feb 2021 11:59:38 -0000

On Tue 02/Feb/2021 00:11:54 +0100 John Levine wrote:
> In article <babf1538-5172-f101-d5e4-c4fa33dea495@tana.it> you write:
>>On Mon 01/Feb/2021 01:10:01 +0100 Scott Kitterman wrote:
>>> 
>>> 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.
>>
>> Perhaps Courier-MTA is not so properly implemented, but when mail from is empty 
>> it just omits the corresponding Received-SPF: header field.
> 
> That's a peculiarity of Courier.


Yes.  Configured as at mine, it writes three Received-SPF: fields, for helo, 
mfrom, and, as a non-standard extension, for From:.  As I said, the one for 
mfrom is only written in case mfrom is not-empty.


> My MTA adds an SPF clause in the A-R header whether or not there's a null
> bounce address.

How can it report, say, fail for helo and pass for mfrom in just one clause?


>> OTOH, properly implemented SPF verifiers could skip producing a Mail From 
>> result if the helo identity was verified successfully.
> 
> No, they could not.  That's not what the SPF spec says.


                                If a conclusive determination about the
    message can be made based on a check of "HELO", then the use of DNS
    resources to process the typically more complex "MAIL FROM" *can* be
    avoided.
                         https://tools.ietf.org/html/rfc7208#section-2.3
                         (my emphasis)


Best
Ale
-- 





















From nobody Tue Feb  2 04:58: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 77B983A1A89 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 04:57: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 TL8wVKBSOsh3 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 04:57: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 0A7A63A1A88 for <dmarc@ietf.org>; Tue,  2 Feb 2021 04:57:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612270674; bh=hGdAZwqQ2kEHV6Ep+OxJaf5YRv0X3Y6XoDKsIwEP83k=; l=3573; h=To:References:From:Date:In-Reply-To; b=C0NYzB4nelMb0PndjVVofioGFGO6GU+/fh6cCE66mae+9Hz/d9KPITkbeowhWnT9I OoLbF+4Saq9fVkfxpV4ETWLP/xeEr0tk0lZZw3KsjTUtBzGwkO7W5+T8OU5k6VAueo 0wWIelmzUh5PyOA6aiv74DHFfWYt7deUXQnTKCIwESWR0iPBaw4i6b4EbJDlD
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 00000000005DC083.0000000060194C52.00002554; Tue, 02 Feb 2021 13:57:54 +0100
To: dmarc@ietf.org
References: <20210130212339.447316D04763@ary.qy> <1654196.ygyh55z74P@zini-1880> <babf1538-5172-f101-d5e4-c4fa33dea495@tana.it> <4489192.U1a6Vm75Xl@zini-1880> <CAH48ZfxB8OoA=3YCdj9mCf3sBzRo8Cu0Tg0z70_tCqQ6QmsCTg@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <1ac5cc72-66c7-eb6c-e034-6cb8e49b576e@tana.it>
Date: Tue, 2 Feb 2021 13:57:52 +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: <CAH48ZfxB8OoA=3YCdj9mCf3sBzRo8Cu0Tg0z70_tCqQ6QmsCTg@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/3qRYdUUscsNS1_EEZ5oP05tuwA0>
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, 02 Feb 2021 12:58:00 -0000

On Tue 02/Feb/2021 01:11:22 +0100 Douglas Foster wrote:
> I think I finally understand the complexities of this issue.   SPF is two 
> different validations, largely unrelated.
> 
> Test One:
> A connection comes in and a server asserts a HELO name.   Before proceeding, 
> the recipient was to check if the HELO name is plausible or fraudulent.    One 
> way to do this would be to forward-confirm the HELO DNS name to the source IP.


That is the method described as iprev in Section 2.7.3 of RFC 8601, a.k.a. 
Forward-confirmed reverse DNS (FCrDNS).  Like many other authentication 
methods, it is not considered by DMARC.


> An alternate method is to use SPF to see if the SPF policy says that the HELO 
> domain can send from the Source IP.   I do not understand why the domain 
> owner would be able to configure the SPF policy but not the host name in DNS.


To configure reverse DNS one needs a delegation of the relevant arpa subdomain, 
which ISPs don't routinely provide.  By contrast, A, AAA, MX, and TXT records 
can be defined by every domain owner.  In theory, each label having any of A, 
AAA, or MX resource records, deserves an SPF record as well.


> Perhaps for organizations with 1000s of servers, creating a DNS entry for 
> each machine seemed onerous.   In practice, the large organizations do have DNS 
> entries for each server, and they encourage others to do the same.


Google, for one, don't care to define an SPF record for every server.  DMARC's 
discarding the result of helo verification is certainly not an incentive.


> A recipient who gets a FAIL result from this HELO test could decide to 
> reject the connection without ever proceeding to MAILFROM.


Rejecting EHLO can be problematic, since the command does not start a mail 
transaction.  Implementations may delay 5xx replies until MAIL or RCPT commands.


> [...]
> I expect that any attempt to require a PASS from this test will encounter an
> unacceptable number of false positives, so I do not see it as particularly
> useful.

To /require/ a pass on helo is very different from /discarding/ a pass on helo.


> Test Two:
> If the conversation proceeds past HELO to MAILFROM, then the second validation 
> is performed:   Is the Source IP is authorized to send on behalf of the SMTP 
> domain?   When the SMTP address is null, then postmaster@HeloDomain serves as a 
> proxy for performing this test.


Testing postmaster@HeloDomain is exactly the same test done for helo.  When the 
SMTP address is null, then the test is not performed.


> HELO test violations will have nothing to do with message flow path, since the 
> test only examines whether the adjacent server name can be plausibly linked to 
> the adjacent IP address.  A DKIM signature is not a third way of answering this 
> question, because a DKIM signature cannot be reliably associated with the 
> server that applied the signature.   Nor do I think we want a third solution to 
> this question.  Consequently, the HELO test is unrelated to DMARC.  The SMTP 
> Address test is appropriate to DMARC, whether it is evaluated using a supplied 
> name or a derived name based on postmaster@helodomain.


That makes no sense.  There is no difference between evaluating HELO and 
evaluating "a derived name based on postmaster@helodomain".  It is an HELO test 
in both cases.  Either it is reliable or it is not.  Asserting that a test is 
reliable only when there are no other means to authenticate a message is an 
idiosyncrasy.



Best
Ale
-- 




















From nobody Tue Feb  2 07:42:27 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 EB7983A1BA6 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 07:42:25 -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 (1024-bit key) header.d=isdg.net header.b=jcwqaYkx; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=zTDlaUgM
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gLbWvDXnvh0Q for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 07:42:23 -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 6F7CD3A1262 for <dmarc@ietf.org>; Tue,  2 Feb 2021 07:42:23 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5470; t=1612280538; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=4v33hnWx5G6QZGvM6L5dDxnuc1ci VUDq6L3MpH5t+dA=; b=jcwqaYkxt3nrH7cTqCPMbaH+lALmLeRp/+H5asSX6RxI j0rpLMnGIokJa5qk4eP3OeYHLdxKZwQrn3ODbvc93R1b/m7Xzwysy/9NzNhmj3q0 Rz7MGKEoyXS4YrmjDe9eg1t0MsuB7rHGa4l040DiakK0+sCzW3+0ViivueDvuv4=
Received: by mail.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Tue, 02 Feb 2021 10:42:18 -0500
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SELECTOR_DNS_PERM_FAILURE) header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  dmarc=dkim-fail 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 608735401.16691.2868; Tue, 02 Feb 2021 10:42:07 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5470; t=1612280502; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=4v33hnW x5G6QZGvM6L5dDxnuc1ciVUDq6L3MpH5t+dA=; b=zTDlaUgMXzHBKljMrtDW3/L 6Yb5KE4BxyF4jW+bFpkCzv7M31spz9VHPmdfzVmZdKyElbgGJ0bNryMnRyYNxqBo PkxXoAdtWUB5NRkmP3Jv5fjpPHfzPrTOJK1YA7OCDkeNFdSySdLSY5KtGk+cNBbp +s/kuRZBK5zomf58LYhY=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Tue, 02 Feb 2021 10:41:42 -0500
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.10) with ESMTP id 1292430971.1.24652; Tue, 02 Feb 2021 10:41:42 -0500
Message-ID: <601972CC.5000604@isdg.net>
Date: Tue, 02 Feb 2021 10:42:04 -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: Douglas Foster <dougfoster.emailstandards@gmail.com>
CC: Scott Kitterman <sklist@kitterman.com>, IETF DMARC WG <dmarc@ietf.org>, 'Hector Santos' <winserver@icloud.com>
References: <20210130212339.447316D04763@ary.qy> <1654196.ygyh55z74P@zini-1880> <babf1538-5172-f101-d5e4-c4fa33dea495@tana.it> <4489192.U1a6Vm75Xl@zini-1880> <CAH48ZfxB8OoA=3YCdj9mCf3sBzRo8Cu0Tg0z70_tCqQ6QmsCTg@mail.gmail.com>
In-Reply-To: <CAH48ZfxB8OoA=3YCdj9mCf3sBzRo8Cu0Tg0z70_tCqQ6QmsCTg@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/s_HDbkQS3Tbpfhs9Tu4pO-a1A_Q>
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, 02 Feb 2021 15:42:26 -0000

On 2/1/2021 7:11 PM, Douglas Foster wrote:
> I think I finally understand the complexities of this issue.   SPF is
> two different validations, largely unrelated.
>
> Test One:
> A connection comes in and a server asserts a HELO name.   Before
> proceeding, the recipient was to check if the HELO name is plausible
> or fraudulent.    One way to do this would be to forward-confirm the
> HELO DNS name to the source IP.  An alternate method is to use SPF to
> see if the SPF policy says that the HELO domain can send from the
> Source IP.   I do not understand why the domain owner would be able to
> configure the SPF policy but not the host name in DNS.

There is a history of Machine Host Name and IP misconfiguration -- 
EASILY possible by simply moving a machine or trying to use many 
machines correctly and generically with one configuration profile.  If 
rDNS is not available for the host, its all part of the unreliability. 
  Unless you write SMTP code for outbound mailing, its hard to see 
this. You can try to automate the smtp client design so that the EHLO 
is always correct with the IP, but there will be MANY times where it 
won't be right for ABC customer for their XYZ reasons.  Its possible 
but its not without optional fields to override an automated logic.

> Test Two:
> If the conversation proceeds past HELO to MAILFROM, then the second
> validation is performed:   Is the Source IP is authorized to send on
> behalf of the SMTP domain?   When the SMTP address is null, then
> postmaster@HeloDomain serves as a proxy for performing this test.

That's one theory possible, but the main thing to remember that a 
BOUNCE is required in the name of mail delivery and notifications when 
delivery fails. You still have the unreliable nature of HELO checking 
and a bounce is too important to be making it dependent on an 
unreliable HELO SPF check.

Many systems do a variety of RFC5322 checks for a BOUNCE message after 
it is accepted or maybe at the DATA state.   It would be nice if we 
could enforce DSN (RFC3464) but that is not possible.  Its optional 
and the old way of doing BOUNCE messages, formats and layouts varies. 
  Inconsistent.  There are some keep addresses that "must" or "should" 
exist in the 5322.From, like the user part has "Mailer-Daemon" and 
"postmaster" when the 5321.MailFrom is NULL.  If not, it could be 
rejected then.

Finally......

Back in early days of LMAP "Lightweight MTA Authentication Protocol" 
[1] , 2003, 2004, Meng Wong made his version of a LMAP protocol called 
SPF. Before SPF, there were others like DMP "Designated Mailers 
Protocols" [2] and RMX [3]. SPF is a merge of these two LMAP methods.

My wcSMTP was among the early LMAP explorers (wcSMTP had DMP support 
before SPF came). I did an LMAP analysis and provided it to Meng Wong. 
  We had an email conversation about the need to document SPF 
CheckHost() for HELO (despite its unreliability and ambiguity) but do 
not enforce HELO checking because there will a wide degree of 
different implementations possible when it comes to HELO checking and 
the order of checking the identities.  For example, in wcSMTP, the 
order is as follows:

1- RCPT TO
2- MAIL FROM
3- EHLO/HELO (optional which is OFF by default)

Before any extended, DNS overhead augmented technology is performed, 
RCPT TO is checked for validity and existence. So when the client 
issues MAIL FROM, the following response is issued by wcSMTP:

C: MAIL FROM:<return-address>
S: 250 <return-path>... Sender validation pending. Continue.

Then the RCPT TO issued:

C: RCPT TO:<forwarding-address>

If the RCPT TO address is good, then it now checks the envelope 
parameters against a suite of protocols that include RBL, SPF, CBV and 
local rules filters.

But if the RCPT TO address is not good, then a 550 is issued because 
there is no need to check for any DNS related policies.  If SPF fails 
here, DATA is never reached -- its considered an optimizer and 
remember please, SPF predated DKIM POLICIES (SSP, ADSP and DMARC).  In 
additional, there is the PRA and SUBMITTER protocol that wcSMTP SPF 
implementation considers.  PRA/SUBMITTER provides the 5322.From 
address at the SMTP level.  It can be used to for SPF checking. Its 
optional.  But now with DMARC, I think PRA/SUBMITTER can play a big 
role and enhance these DMARC SMTP/SPF checking adjustment. Its 
unfortunate there isn't another "mail engineer" that can see the 
benefit of these protocols used together. SPF doesn't need to change, 
DMARC does!!!

Here is the LMAP analysis I did. wcSMTP follows the concepts this 
analysis to help optimize LMAP protocols checking at the SMTP level:

https://secure.winserver.com/public/antispam/lmap/draft-LmapAnalysis1-2.htm

I hope this helps your understanding of the complexity of all this, 
but for me, there are some basic filter concepts that can be applied 
and I do for my wcSMTP package before all the extra DNS overhead can 
be applied.

-- 
Hector Santos,
https://secure.santronics.com
https://twitter.com/hectorsantos

[1] Lightweight MTA Authentication Protocol (LMAP) Discussion and 
Applicability Statement, 
https://secure.winserver.com/public/ietf/drafts/draft-irtf-asrg-lmap-discussion-00.txt

[2] Designated Mailers Protocol (DMP), 
https://tools.ietf.org/html/draft-fecyk-dmp-01

[3] The RMX DNS RR and method for lightweight SMTP sender 
authorization, https://tools.ietf.org/html/draft-danisch-dns-rr-smtp-03



From nobody Tue Feb  2 08:59:22 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 4C48E3A0C58 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 08:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.146
X-Spam-Level: *
X-Spam-Status: No, score=1.146 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, PDS_OTHER_BAD_TLD=1.997, SPF_PASS=-0.001, URIBL_ABUSE_SURBL=1.25, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=P/U42xXg; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=dV1pAswh
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id adIdphJaROuk for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 08:59:16 -0800 (PST)
Received: from mail.winserver.com (ftp.catinthebox.net [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 1C91D3A0C17 for <dmarc@ietf.org>; Tue,  2 Feb 2021 08:59:15 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3540; t=1612285148; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=RXKnJXouru8DkK3LXpE1P5fSNy9G /BBO+VFXttNXPNw=; b=P/U42xXgK6E49NLKGKJ8Uct+3Z2IDTU6pgO4l7NOUXt/ 7SB/XIIo4hc9cyIQcs5dwVZtCQswkg37PvxLTAuSpitKldXCC1xBhOFsI67RTrpb +ZjkEqHSiMbp7BdWAJurFC2+iSimwcsFJcz/ZpCXlYsVt9OnCJltsLZ+Zewi+1Q=
Received: by mail.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Tue, 02 Feb 2021 11:59:08 -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 613355729.16691.3852; Tue, 02 Feb 2021 11:59:07 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3540; t=1612285122; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=RXKnJXo uru8DkK3LXpE1P5fSNy9G/BBO+VFXttNXPNw=; b=dV1pAswh9yz3XWenbqsQbK2 MGv9G5RBq1gHzUK95bV7FXe5hkbQlDu+GHxugrSfA3ihvJvTrIaQymVJxPBafyT+ 8XniBO3OH6qwJ9invLIBmXMCk41BqBhRmF+sn/edtsa/oyXE+IrU4Gy7m2eBaXWF PiH4yGVeIT90tH7EB8gs=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Tue, 02 Feb 2021 11:58:42 -0500
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.10) with ESMTP id 1297050346.1.25104; Tue, 02 Feb 2021 11:58:41 -0500
Message-ID: <601984D8.7050304@isdg.net>
Date: Tue, 02 Feb 2021 11:59:04 -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: Alessandro Vesely <vesely@tana.it>,  "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
CC: 'Hector Santos' <winserver@icloud.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> <920ee8e1-2947-379e-5798-2a6818e69526@tana.it>
In-Reply-To: <920ee8e1-2947-379e-5798-2a6818e69526@tana.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YbC9DLoVJ-YG4SyFcWf66HvWDnc>
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, 02 Feb 2021 16:59:21 -0000

This is real legit "feasible" proposal so let see where it goes ....

On 1/30/2021 5:41 AM, Alessandro Vesely wrote:>

>> Anyway, I'll let consensus fall where it may.

The solution is to consider the PRA/SUBMITTER protocols which was part 
of the SenderID protocol and many MTA clients already supported:

SUBMITTER https://tools.ietf.org/html/rfc4405
PRA https://tools.ietf.org/html/rfc4407

When the ESMTP Extension SUBMITTER is enabled, the client add can a 
SUBMITTER= parameter to the MAIL FROM. Example of a complete session 
this morning:

C: EHLO oscar.ultrashed.buzz
S: 250-mail.winserver.com, Pleased to meet you.
S: 250-SIZE 10240000
S: 250-8BITMIME
S: 250-SUBMITTER
S: 250-AUTH CRAM-MD5 DIGEST-MD5 LOGIN PLAIN PLAIN-MD5 SHA-1
S: 250-AUTH=LOGIN
S: 250-HELP
S: 250 STARTTLS
C: MAIL 
FROM:<27188-46690-410393-7123-hector.santos=santronics.com@mail.ultrashed.buzz> 
BODY=8BITMIME SUBMITTER=Easysheds@ultrashed.buzz
S: 250 
<27188-46690-410393-7123-hector.santos=santronics.com@mail.ultrashed.buzz>... 
Sender validation pending. Continue. (8BITMIME ok)
C: RCPT TO:<hector.santos@santronics.com>
** WCX Process: wcsap ret: 550 (63 msecs) (Rejected by WCSAP RBL Host 
bl.spamcop.net)
S: 550 Return Path not verifiable.
C: QUIT
S: 221 closing connection
** Completed. Elapsed Time: 530 msecs


Our wcSMTP supports the SUBMITTER SMTP Service Extension (RFC4405). 
The keyword SUBMITTER is advertised.  The client uses RFC4407 
Purported Responsible Address (PRA) to extra the PRA which is usually 
the 5322.From address and issues the MAIL FROM:

C: MAIL 
FROM:<27188-46690-410393-7123-hector.santos=santronics.com@mail.ultrashed.buzz> 
BODY=8BITMIME SUBMITTER=Easysheds@ultrashed.buzz

So here we can see the 5322.From is different from the 5321.MailFrom 
return path, a subdomain but different.

My proposal is for the SMTP server to use this opportunity to do a 
DMARC look up for ultratrashed.buzz domain. Lets do this now:

v=DMARC1; p=none; fo=1; rua=mailto:info@ultrashed.buzz; 
ruf=mailto:info@ultrashed.buzz;

And there is no DMARC record for the subdomain.

And note the EHLO subdomain, "oscar" vs "mail" for the return path.

But how does this help?


Well, the receiver now knows the there is a DMARC record and therefore:

1) The message MUST be signed but we won't know this until the payload 
is transferred,

2) SPF is expected. There is no SPF record any of three domains, and

3) The p=none means he doesn't really care if it alignment fails or 
they are not sure but its not reject|quarantine which means they don't 
expect alignment enforcement.

But considering there is DMARC record but no SPF record means there is 
a problem with this transaction. It can be refused probably on that 
basis. But as you can see, it was rejected but for RBL reasons. :-)

We SHOULD consider the two protocols (PRA/SUBMITTER) for DMARC/SPF 
integration. This extra bit of information help at SMTP before the 
potentially high overhead payload is transferred. That was the main 
MS-patented (frivolous) reason for this optimization -- to avoid the 
payload transfer overhead.

But the beauty of this proposal is that it is not new! There are 
clients out there that do support it and will extract the PRA and 
issue it at SMTP MAIL FROM state:

C: MAIL FROM:<return-path> [SUBMITTER=pra]

At the point, the SMTP client has some awareness of the payload and 
DMARC expectations.


-- 
Hector Santos,
https://secure.santronics.com
https://twitter.com/hectorsantos




From nobody Tue Feb  2 09:20: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 6DDE43A0C86 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 09:20: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 XBLBNUBtfN2I for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 09:20: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 6B4B43A0C80 for <dmarc@ietf.org>; Tue,  2 Feb 2021 09:20:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612286400; bh=KCtRp0f57GmSTaXR64YgDEQwpUWdDheMt/uWnJGwNCQ=; l=1612; h=To:Cc:References:From:Date:In-Reply-To; b=AA6tX4NXyXQkMITLhMVcvTUqCFypL032mKwf/PlzkNrhl4rYx3FPe4epO7mTVa0qM RpIHPn9n4e2t/SBX+OaaDRP5Qo/7vW3deJt6psCf5bTFXAFfS6x4h8iF/OV+mLoqKh DAxb8B+Ku/3KPuV8k0KaJ/IJbV68y1pqfxaRLwrqrcljY0H9/lc1B5PxmtgPh
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Original-Cc: 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 00000000005DC042.00000000601989C0.00004195; Tue, 02 Feb 2021 18:20:00 +0100
To: Dave Crocker <dcrocker@gmail.com>, John R Levine <johnl@taugh.com>
Cc: dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <1021a8e4-ca5f-5fb3-2661-b4668b4bafd5@tana.it>
Date: Tue, 2 Feb 2021 18:19: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: <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@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/xT1hUgqGFc_TaeSPy2GssbunT-I>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 17:20:04 -0000

On Tue 02/Feb/2021 02:42:25 +0100 Dave Crocker wrote:
> On 2/1/2021 5:38 PM, John R Levine wrote:
> 
>> If we want to document existing practice, I guess we would say that reports 
>> should be authenticated and aligned if practical, but it's OK to send them if 
>> not.
> exactly.


I changed it again, for failure reports, like so:

3.3.  Transport

    Email streams carrying DMARC failure reports SHOULD conform to the
    DMARC mechanism, thereby resulting in an aligned "pass".  This
    requirement is a MUST in case the sending host has a DMARC record
    featuring a ruf= tag.  Indeed, special care must be taken of
    authentication in that case, as failure to authenticate failure
    reports may result in mail loops.

    Reporters SHOULD rate limit the number of failure reports sent to any
    recipient to avoid overloading recipient systems.  Again, in case the
    reports being sent are in turn at risk of being reported for DMARC
    authentication failure, reporters MUST make sure that possible mail
    loop are stopped.


Some comments upthread allude to the reporter's policy.  To be clear, the DMARC 
mechanism which results in an aligned pass is meant to say that the report is 
SPF or DKIM authenticated , the authenticated identifier is aligned with From:, 
and a DMARC record has been discovered.  The value of p= is irrelevant.

Indeed, from a security perspective, a faked failure report is not much 
different from an abusive message.  To wit, a bad actor could send one or the 
other, directly to the victim or, respectively, to a server that will report to 
the victim.


Best
Ale
-- 


















From nobody Tue Feb  2 09:24: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 710363A0C93 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 09:24:36 -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, FREEMAIL_FROM=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 VS3ieFs44A4P for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 09:24:35 -0800 (PST)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (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 1E6A03A0C8F for <dmarc@ietf.org>; Tue,  2 Feb 2021 09:24:35 -0800 (PST)
Received: by mail-oi1-x22a.google.com with SMTP id k142so9132630oib.7 for <dmarc@ietf.org>; Tue, 02 Feb 2021 09:24: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=cYzrd39I7eSRGGxrIf303+JS0d8DoSU7TNEiIl2Kfks=; b=X5HocYyROzDl28SRzYWS1cogF6rsp0SpMczY+HEg+gW/vQ2pv1EyX64HFWBfQNdJll ZquRfzMvuFZRmPG+kWUmAjAb2wsQ+C6s/9sFOb9gZzudDHkjuSXP7qrl9kvT0M0LXnED +MElNXwBPFf0Cvfdbba/0vyy3EKiMBIMWxaH+0rEaTyLM5fBcvJ6qCdjtcC46OkenR8D NRhFjHFI2EfbQkOxIkwcbBPDnKFdi16FYQyjEZAae0tHNow37Nfo/b/4E6XcDYHZxPDy oB5ndHOSQ5Qgn7rko4eyYHeVYXAZ9+Ug/klFD4+vJ3PMNkQOHQL2YDH4LUb0kkxRSO+c PoFA==
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=cYzrd39I7eSRGGxrIf303+JS0d8DoSU7TNEiIl2Kfks=; b=dpT5k5B7mwieZzKnFnBp9tB9C9HZb2kIFNDeLkmCxFPt0q+yZf9zv5uZ/qGhB81FDJ QB48ECjnj3TRifwsyM8C59U+sKcHR2FLJk5W73cv+BthblSUBvfK7MwZQuM0YDR7M9wL mXX7QCFqoiuX5eDgV1VScYSNZDY0mhfOeIHC/pw6nyQdL1GxbHHub8EZgXqSLTqcvrzz dnrfO8FeUu3JlnDGXFtPjb///hJsMRrHLf9hWG5FMyg3GwIhZ5gNvJJTWetXDICbN2hG fcsbU2NREkhcHvt/RHHBpdeqSxqjGieZ46WOLjXDiJl8Dr1qHDV+hRTKU5L5AX9izmlY Zu3g==
X-Gm-Message-State: AOAM532qsYEL+m7zEz5PzDgYWYWIVbrRjw+g5PqPXsRr8C0gLNsmBw6e 8fRWRz0FymOMr7eUFXJIEMV6WV5BIB1qyA==
X-Google-Smtp-Source: ABdhPJymTPyVKGrK8rNgJOiiNMs+luvVutuKVkNgtgekMiH9zwh0kay99A/0+Nuix2xcURoKbb75zA==
X-Received: by 2002:aca:a98d:: with SMTP id s135mr3475423oie.136.1612286674089;  Tue, 02 Feb 2021 09:24:34 -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 l3sm4842074ooa.12.2021.02.02.09.24.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Feb 2021 09:24:33 -0800 (PST)
To: Alessandro Vesely <vesely@tana.it>, John R Levine <johnl@taugh.com>
Cc: dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com> <1021a8e4-ca5f-5fb3-2661-b4668b4bafd5@tana.it>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <0fd34931-e3c4-e5a5-3cb2-cb82697f50e6@gmail.com>
Date: Tue, 2 Feb 2021 09:24:32 -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: <1021a8e4-ca5f-5fb3-2661-b4668b4bafd5@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/ZNItgOcMkweHCYrCBlhj-_a9rIk>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 17:24:36 -0000

On 2/2/2021 9:19 AM, Alessandro Vesely wrote:
> On Tue 02/Feb/2021 02:42:25 +0100 Dave Crocker wrote:
>> On 2/1/2021 5:38 PM, John R Levine wrote:
>>
>>> If we want to document existing practice, I guess we would say that 
>>> reports should be authenticated and aligned if practical, but it's 
>>> OK to send them if not.
>> exactly.
>
>
> I changed it again, for failure reports, like so:
>
> 3.3.  Transport
>
>    Email streams carrying DMARC failure reports SHOULD conform to the
>    DMARC mechanism, thereby resulting in an aligned "pass".  This

"conform to" seems odd wording; it's not immediately obvious what it 
means here.

Perhaps:

  SHOULD provide DMARC-based authentication, to produce their own 
aligned "pass"


> requirement is a MUST in case the sending host has a DMARC record

'sending host' is ambiguous in this context.


> featuring a ruf= tag.  Indeed, special care must be taken of
>    authentication in that case, as failure to authenticate failure
>    reports may result in mail loops.
>

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Tue Feb  2 09:39:56 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 909AB3A0D31 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 09:39:50 -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, 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 ofp11VKSlKuP for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 09:39: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 5E5B13A0CB8 for <dmarc@ietf.org>; Tue,  2 Feb 2021 09:39:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612287583; bh=EMtifhSbAvAsWWoGC3U1xNygZjiKCMPZ6h3LsOn1uaw=; l=1398; h=To:Cc:References:From:Date:In-Reply-To; b=CG0BAYHANDk+QSWbmdVwlUV77phmoCL29nwgGCjmSwBO/JCLV3HWIhrSvRR9GF6rT F0UgtR7fZ4NfRKO5ZhBwwBLjTaBYCrlIuP0nkWS1okVS86a4xtWugCWxngwgIQY21z GXgOUec+sJwX6ze/Ve6srjHt8ugsMmIgFkJjKU4S6xfLOGFy5WfI5CIMY8nD5
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Original-Cc: 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 00000000005DC026.0000000060198E5F.000043CE; Tue, 02 Feb 2021 18:39:43 +0100
To: Dave Crocker <dcrocker@gmail.com>, John R Levine <johnl@taugh.com>
Cc: dmarc@ietf.org
References: <20210201232105.1931D6D20971@ary.qy> <41163cd5-be81-6fd7-07dd-7a474874429e@gmail.com> <92b361a1-d9a5-9389-46b-3725d885c02@taugh.com> <b83c7574-3aa9-bd39-1a9b-3be6fa4f47ec@gmail.com> <1021a8e4-ca5f-5fb3-2661-b4668b4bafd5@tana.it> <0fd34931-e3c4-e5a5-3cb2-cb82697f50e6@gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <e6f7fa8e-9ea4-1e0a-1cd2-0fa040379bad@tana.it>
Date: Tue, 2 Feb 2021 18:39: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: <0fd34931-e3c4-e5a5-3cb2-cb82697f50e6@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/ek9wrzzRYDL63_j0YDL8vZXEip8>
Subject: Re: [dmarc-ietf] DMARC'ed reports, was 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: Tue, 02 Feb 2021 17:39:54 -0000

On Tue 02/Feb/2021 18:24:32 +0100 Dave Crocker wrote:
> On 2/2/2021 9:19 AM, Alessandro Vesely wrote:
>>
>> I changed it again, for failure reports, like so:
>>
>> 3.3.  Transport
>>
>>    Email streams carrying DMARC failure reports SHOULD conform to the
>>    DMARC mechanism, thereby resulting in an aligned "pass".  This
> 
> "conform to" seems odd wording; it's not immediately obvious what it means here.
> 
> Perhaps:
> 
>   SHOULD provide DMARC-based authentication, to produce their own aligned "pass"
> 
> 
>> requirement is a MUST in case the sending host has a DMARC record
> 
> 'sending host' is ambiguous in this context.


Is this better:

3.3.  Transport

    Email streams carrying DMARC failure reports SHOULD provide DMARC-
    based authentication, so as to produce "dmarc=pass".  This
    requirement is a MUST in case the report is sent through a host
    having a DMARC record with a ruf= tag.  Indeed, special care must be
    taken of authentication in that case, as failure to authenticate
    failure reports may result in mail loops.

    Reporters SHOULD rate limit the number of failure reports sent to any
    recipient to avoid overloading recipient systems.  Again, in case the
    reports being sent are in turn at risk of being reported for DMARC
    authentication failure, reporters MUST make sure that possible mail
    loop are stopped.



Best
Ale
-- 


















From nobody Tue Feb  2 09:49:15 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 34C123A0CC7 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 09:49:14 -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=Aj33m1GB; dkim=pass (2048-bit key) header.d=taugh.com header.b=ig7Wrcoy
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VRfp3ovWfDKi for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 09:49: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 7AEBD3A0CC4 for <dmarc@ietf.org>; Tue,  2 Feb 2021 09:49:12 -0800 (PST)
Received: (qmail 60833 invoked from network); 2 Feb 2021 17:49: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:mime-version:content-type:content-transfer-encoding:cleverness; s=ed9d.60199096.k2102; bh=u5LR74786h+tiZ9mc6lLJgO2D9ZC65OEqqabG+iFtSc=; b=Aj33m1GB5BRcleLwpETssyUFa3TxURhEgmsfpIFixAP+sXfDBeYJRUH+ct4ZYvCfsfAjZXe6ZEdSsY25bMVu3mgGiAgVRNfZfdRZnOrIW3Q2WvhC002UtepNQBVJ/t9ne2nkQMaoZPgm1oAAjTiIjNqO5guQb1zeCGUQieG6UsRrk0IyyOtrz/Z/7ICIbzHgAorInAXRKQ11wumvT4ZEfur5EZmF8/s89fsNLXBA4S5hgmq8ShSLL8fVQAd/97hg3cn+BxaYuUyBy5x1a25RmzC8AwURLRlek0DSOgygU5GVq9NOifudeOlJWXHPEeK32vVgBBBhb87FJeN0+1sgQA==
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=ed9d.60199096.k2102; bh=u5LR74786h+tiZ9mc6lLJgO2D9ZC65OEqqabG+iFtSc=; b=ig7Wrcoy8KsAk6YCEWq8u+uD0cSFjAlNr1vQTikaYFHqkPYdB1geQN5ULdcqOTKD7F9xE+1VJ9XixjRBjVhlaoD4riHbI19VsSMs8pGZIa4VxdFbiQcqx0lE/td4d0pmWvNwuBmw11KsBK83cwEWCa+L+/HVbAsNO41EMwb15erKAD2TIUNYcSggumxM5eOw8BE2P6i5K0anDImkCBREN09tVV9NcW45VSODYX+3AqpRc+MsfbA3j6Lc5jkMNmKBkX1vdLM0pCWe5fgzYe6jH9aYZnPQWlJbiB7SO9XwI8hqd7g3/49hvGw4VmPVId4JqmIZfwS9/TAQ9sFMa4T5wg==
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 Feb 2021 17:49:09 -0000
Received: by ary.qy (Postfix, from userid 501) id 517906D2C88B; Tue,  2 Feb 2021 12:49:08 -0500 (EST)
Date: 2 Feb 2021 12:49:08 -0500
Message-Id: <20210202174909.517906D2C88B@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <2e39680f-ed2d-fa38-daaa-7e0627cf0fc7@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/9eghICgpldyoZ-0TXt7UUS4mTio>
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, 02 Feb 2021 17:49:14 -0000

In article <2e39680f-ed2d-fa38-daaa-7e0627cf0fc7@tana.it> you write:
>> My MTA adds an SPF clause in the A-R header whether or not there's a null
>> bounce address.
>
>How can it report, say, fail for helo and pass for mfrom in just one clause?

It doesn't.  It reports whatever the SPF library returns.

I'm fairly sure that every DMARC implementation uses an SPF library and uses
whatever the SPF library returns, so I don't see the point of this argument.

>>> OTOH, properly implemented SPF verifiers could skip producing a Mail From 
>>> result if the helo identity was verified successfully.
>> 
>> No, they could not.  That's not what the SPF spec says.

Sorry, that's not what the DMARC spec says.

Once again, what problem are we solving here?  Can we stop now?

R's,
John


From nobody Tue Feb  2 10:17: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 43BA83A0D3C for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 10:17:44 -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 ejQvtIq9w77q for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 10:17: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 46DAE3A0CD4 for <dmarc@ietf.org>; Tue,  2 Feb 2021 10:17:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612289857; bh=IHNkPaBaEcRDS0xwKXnp7qkjfUk9uTf3LcvkhMR1ES8=; l=1678; h=To:References:From:Date:In-Reply-To; b=DOxi+DSwpMuEGMZ9beWnovzpGOtIgL4pWoR44QNUx7PujAyYGE7k0bap5+XQKDaiR OKYoNJ9mPdBLs6ByocYoPh232QIuN0GPCPGlhChB9gCQTePukT2xIgGHWUv9lH0IvH GIOcOnDV/NrXpflngoGdo+HB3LGxyW2lTPy/WEQBaAeo91gX8VvrH/Yabf+hr
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.0000000060199740.00004825; Tue, 02 Feb 2021 19:17:36 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210202174909.517906D2C88B@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <286b8e6c-67b4-2c16-1632-16bf8cd95b78@tana.it>
Date: Tue, 2 Feb 2021 19:17: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: <20210202174909.517906D2C88B@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/XhwdFqr70Zp6PMegxna-K9yZMj8>
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, 02 Feb 2021 18:17:44 -0000

On Tue 02/Feb/2021 18:49:08 +0100 John Levine wrote:
> In article <2e39680f-ed2d-fa38-daaa-7e0627cf0fc7@tana.it> you write:
>>> My MTA adds an SPF clause in the A-R header whether or not there's a null
>>> bounce address.
>>
>>How can it report, say, fail for helo and pass for mfrom in just one clause?
> 
> It doesn't.  It reports whatever the SPF library returns.
> 
> I'm fairly sure that every DMARC implementation uses an SPF library and uses
> whatever the SPF library returns, so I don't see the point of this argument.


An SPF library implements the check_host() function.  It's up to the client to 
call it multiple times.  Is that client DMARC-aware?  As you may have guessed, 
my question is intended to understand how does a DMARC implementation actually 
ascertain whether an "spf=pass helo=smtp.example.com" is enough to validate 
"From: user@example.com".


>>>> OTOH, properly implemented SPF verifiers could skip producing a Mail From 
>>>> result if the helo identity was verified successfully.
>>> 
>>> No, they could not.  That's not what the SPF spec says.
> 
> Sorry, that's not what the DMARC spec says.


My point is that the DMARC spec says something inconsistent, namely that SPF 
helo results are reliable but typically they are not.


> Once again, what problem are we solving here?  Can we stop now?


We can stop now and get back on it later.  That idiosyncrasy is going to stay 
there until we fix it.  I'd suggest to fix it by accepting an aligned helo pass 
unconditionally.  However, it can also be fixed by an explanation, as long as 
it is something more persuasive than "one can type anything at helo".


Best
Ale
-- 
















From nobody Tue Feb  2 11:13:47 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 C20083A0DDA for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 11:13:46 -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=e9B5qX5F; dkim=pass (2048-bit key) header.d=taugh.com header.b=G4Kfux66
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JxvQttNEUy96 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 11:13: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 AA9883A108F for <dmarc@ietf.org>; Tue,  2 Feb 2021 11:13:44 -0800 (PST)
Received: (qmail 689 invoked from network); 2 Feb 2021 19:13: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=2ad.6019a467.k2102; bh=Qhra+OSb9xUTYL4lyiN0U1jPi/CF50IJlJT3U5ErMPw=; b=e9B5qX5F3WNTOKiVgoB7I0fPnZxOTE2TLEoOpfNfvNnVBAoIvzmLIvdxWbe4lVc+N7aaE8rUWE1emCrFK/VgA901mZ6GyX6UNZx9SO9BEKXyHfMcFm7M2YKnHNm6C6ox9QdfrXNN6ZWsAbwfLEhCzxLWWYI0Jnc8v2JP6o5FdG1kDioabc+l0WBUkAWAIkRsC4AvFz/LBOTBIND2xe55AauZtsVcUWp55kN5lWEyCN82rdb78sEQeaLOBzrYw8f9duJ9oZYBWdE4BEqxnAnx52PsxzvNAcHaoY363B9MxLUOy1FsS0HTzJJ2ZTG+w+BPU/FPy6RlKSNaEoIFUqzV4Q==
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=2ad.6019a467.k2102; bh=Qhra+OSb9xUTYL4lyiN0U1jPi/CF50IJlJT3U5ErMPw=; b=G4Kfux66udo9aZM5oAi48S7DvNSUIKjkJllAy0IzblUOitJ9czvBJhzMhmoCGs9x20o3MR07zae9vMHUc3W0slCbepZksWsfNPQOHLLBKqeCCgRIdsRoh2ew+VAW6qj8dJa5rQSYl62sqUHd7fe5wP0HDA8dLMg6ZBIloP2tyVFmiWD7CDnBpbWSe6/saQTSJ7K/Iu6RFZG00JYbIxu3oHTU3hi+nisT3j13MRHJjy4a9F+lz6MdP2dAM3a7gc+kS4CW82tZoZZRXmCcW+ELJDf0JWSnfCAjz5LRb9jukeSDH+LY+4dxGdnLOHEn54KOf6yosdoI4aosHZwr4cOPOQ==
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 Feb 2021 19:13:42 -0000
Received: by ary.qy (Postfix, from userid 501) id 57E316D2D8D7; Tue,  2 Feb 2021 14:13:42 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 1A9176D2D8B9; Tue,  2 Feb 2021 14:13:42 -0500 (EST)
Date: 2 Feb 2021 14:13:42 -0500
Message-ID: <18d01d3d-9a22-fe33-fa36-8f3a92cce4@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
In-Reply-To: <286b8e6c-67b4-2c16-1632-16bf8cd95b78@tana.it>
References: <20210202174909.517906D2C88B@ary.qy> <286b8e6c-67b4-2c16-1632-16bf8cd95b78@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/tcb76WmSeFrHGKXrhcX8xsLoMXk>
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, 02 Feb 2021 19:13:47 -0000

> An SPF library implements the check_host() function.  It's up to the client 
> to call it multiple times.  Is that client DMARC-aware?  As you may have 
> guessed, my question is intended to understand how does a DMARC 
> implementation actually ascertain whether an "spf=pass helo=smtp.example.com" 
> is enough to validate "From: user@example.com".

I use the opendmarc library and libspf2.  For the SPF check, I give it the 
IP address, the HELO, and the MAIL FROM, and it gives me a result.  I then 
pass that result to the DMARC library along with the DKIM results. 
Looking at the code, I see I tell it whether SPF checked HELO or MAIL FROM 
by simply checking whether MAIL FROM was null, but I don't know what the 
DMARC libary does with that.  Maybe Murray remembers.

There is some commented out code to not pass a HELO result to DMARC, don't 
remember why I turned it off.

Again, I believe this is typical of what DMARC validators do.  It's 
existing practice and I see no reason to change it.  Can we stop 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 Tue Feb  2 11:42:07 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 E483E3A110F for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 11:42: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_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 vyL2z2NKwXbE for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 11:42:05 -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 5607D3A110D for <dmarc@ietf.org>; Tue,  2 Feb 2021 11:42:04 -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=7+MKsRFtF8bQx6jUJRVzjZ5U+XYpBgEkdxwuqGeHkoU=; b=P02cQEwe07prK5n3AXl5Xqv/qG vg9OGaO9T8/Apg0+L6HrgS7pxCOonrAsRfXveEh4EWKSXGGWHP3pNcvuoMdiFMNG6DMfpIsDT+27p M3W5U7rKq0v42C3R5IyNQTbL+XGZuYT8j9TvKDx7RA0F4hyzaIXj4OXrpAFdFl6qamH4=;
Received: from [2601:647:4400:1261:589f:60c4:bcd4:9d97] (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 1l71Ym-0006sE-0J; Tue, 02 Feb 2021 11:42:00 -0800
From: "Jim Fenton" <fenton@bluepopcorn.net>
To: "John R Levine" <johnl@taugh.com>
Cc: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
Date: Tue, 02 Feb 2021 11:41:59 -0800
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <4A21A4F6-4021-4C38-A707-0141593A3849@bluepopcorn.net>
In-Reply-To: <18d01d3d-9a22-fe33-fa36-8f3a92cce4@taugh.com>
References: <20210202174909.517906D2C88B@ary.qy> <286b8e6c-67b4-2c16-1632-16bf8cd95b78@tana.it> <18d01d3d-9a22-fe33-fa36-8f3a92cce4@taugh.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/8--4uSquZcb-PhIc8r7wzHQlM14>
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, 02 Feb 2021 19:42:07 -0000

On 2 Feb 2021, at 11:13, John R Levine wrote:

>> An SPF library implements the check_host() function.  It's up to the 
>> client to call it multiple times.  Is that client DMARC-aware?  As 
>> you may have guessed, my question is intended to understand how does 
>> a DMARC implementation actually ascertain whether an "spf=pass 
>> helo=smtp.example.com" is enough to validate "From: 
>> user@example.com".
>
> I use the opendmarc library and libspf2.  For the SPF check, I give it 
> the IP address, the HELO, and the MAIL FROM, and it gives me a result. 
>  I then pass that result to the DMARC library along with the DKIM 
> results. Looking at the code, I see I tell it whether SPF checked HELO 
> or MAIL FROM by simply checking whether MAIL FROM was null, but I 
> don't know what the DMARC libary does with that.  Maybe Murray 
> remembers.
>
> There is some commented out code to not pass a HELO result to DMARC, 
> don't remember why I turned it off.

I’m lost in a double negative here: did you turn off passing a HELO 
result to DMARC, or did you turn off not passing a HELO result?

> Again, I believe this is typical of what DMARC validators do.  It's 
> existing practice and I see no reason to change it.  Can we stop now?

If you found that you needed to turn off something that’s part of the 
DMARC spec, it would be good to understand why.

-Jim


From nobody Tue Feb  2 11:54:42 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 83E083A1123 for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 11:54:41 -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=REp8xM5f; dkim=pass (2048-bit key) header.d=taugh.com header.b=MMl0cZO6
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k2A8sd54ryrz for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 11:54:40 -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 B66E23A109D for <dmarc@ietf.org>; Tue,  2 Feb 2021 11:54:39 -0800 (PST)
Received: (qmail 11643 invoked from network); 2 Feb 2021 19:54:34 -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=2d78.6019adfa.k2102; bh=DqFu58y0XYhpqWHtXXQeluKbS1M5Ugfo7O83YqEdVnc=; b=REp8xM5fC0mbFTkJOEWyG1XxFvM9lfE9cd0BbqCVCZjzz5HFHX+GG6wDgyKBapaZ1ohEA04oo1yp4wAJDSc2iduphs6YQTzeDkJtth0LT2PTABCqMrnlSe8BqeGLsPVJ8Z8G/Gj0ee1Fn6cnh9HN5zTwhI+YrvM9Jkb9qZMS62dLHVQ6/Vb7sReb9FK9axfMcYjF/L3D/KWva00GeYmsVmz58BS7Jgx6FeLXTvYe/4aSYspHWvWlLloZytRhU6ARGQ0MapxKgEO7wtB/zq/zXtHaSBnSamECOtvPRJ8T43Htbf4p4TaI0I3YGnBbS8ElgzdAS8Pniw+aDff+I4bZng==
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=2d78.6019adfa.k2102; bh=DqFu58y0XYhpqWHtXXQeluKbS1M5Ugfo7O83YqEdVnc=; b=MMl0cZO6ng27AhqedsoiGBSI+l534rKEIkChPwFZm2Gac86kh6Qc37W0t9rGus+i9F80boYIHoJe1TZGB10xCa/lO0SuDR5FTrVey3x9qhMh70vRvgR1L1am+WrWSjz3FssKgFqoA2xhaLvq8DTpaoP0yPBt0DcJrITU06kdiNU5bfGoqDW1EGBsVzOvUH2baG9vyw3+LNSeVy7gqzSp7QmWVath7AASLYMbBRJD6dtVN0p0SRsyKBybKmx3ZrUs8jBbaM9Uufs9JWmqABqUQJJcaRnnB4lKeDXB8qJILpoPjLmrmoDxNFK95/zBNBJZcdk9pMbmxBANoxFC6kmw2g==
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 Feb 2021 19:54:34 -0000
Received: by ary.qy (Postfix, from userid 501) id 0FA586D2DB9F; Tue,  2 Feb 2021 14:54:33 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 5E7F56D2DB81; Tue,  2 Feb 2021 14:54:33 -0500 (EST)
Date: 2 Feb 2021 14:54:33 -0500
Message-ID: <40a52ab3-748a-c898-aa66-b335b720c73e@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Jim Fenton" <fenton@bluepopcorn.net>
Cc: dmarc@ietf.org
In-Reply-To: <4A21A4F6-4021-4C38-A707-0141593A3849@bluepopcorn.net>
References: <20210202174909.517906D2C88B@ary.qy> <286b8e6c-67b4-2c16-1632-16bf8cd95b78@tana.it> <18d01d3d-9a22-fe33-fa36-8f3a92cce4@taugh.com> <4A21A4F6-4021-4C38-A707-0141593A3849@bluepopcorn.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-328617930-1612295673=:21435"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/8uDeM9WNr9PGNVBU4ruDBnx7Nv4>
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, 02 Feb 2021 19:54:42 -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-328617930-1612295673=:21435
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

>> There is some commented out code to not pass a HELO result to DMARC, don't 
>> remember why I turned it off.
>
> I’m lost in a double negative here: did you turn off passing a HELO result to 
> DMARC, or did you turn off not passing a HELO result?

The live code uses whichever result it has.  The commented out code only 
used a MAIL FROM result.

>> Again, I believe this is typical of what DMARC validators do.  It's 
>> existing practice and I see no reason to change it.  Can we stop now?
>
> If you found that you needed to turn off something that’s part of the DMARC 
> spec, it would be good to understand why.

I believe that what I am doing matches the spec.

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


From nobody Tue Feb  2 16:30: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 031D33A10AD for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 16:30:38 -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 CeP_PpU6Zd6v for <dmarc@ietfa.amsl.com>; Tue,  2 Feb 2021 16:30:36 -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 400913A10AB for <dmarc@ietf.org>; Tue,  2 Feb 2021 16:30:36 -0800 (PST)
Received: by mail-vs1-xe2b.google.com with SMTP id b10so6111014vsa.8 for <dmarc@ietf.org>; Tue, 02 Feb 2021 16:30:36 -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=3blrH9Lx/RE+ug9CHDVFOev8r3zmd3xZlhiRvEbGLS0=; b=lLT+kwHeiFqiuwuqGPCcGhvvT1u3e2NLsoSCwQSJTBquW68wM6TVmEwX1a8s/is41/ XkYMjX7d1SQiKd3OdM1Em/bWmk1FQxaPYM2iODLbKFcYaGjVyK07JBepXyXwLEZAr3Yj JYgsmafM96wrTDlMZYn34b3XH79pE0tEr2up6Z1xq94A2MEaaKlH6IeBQ4Mcuev882TD nj1TXvXGGtjD/lmpssr7xpjOb5zIEvri2DflAc8J1bMU05U4BETHBCtFry7U2bF9AIjA B9w0XkXr7mAig6M+Umg8eEk5YeQRe+gGK4K3QvgKdtgpQyw6b+Rao8z5yq4kotLSOTmK jmLw==
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=3blrH9Lx/RE+ug9CHDVFOev8r3zmd3xZlhiRvEbGLS0=; b=pr/fXiBlYcEj33OWXgWh8NDKWxeDTqHxO7BBgIlUOL3FHzCeRrnUJHfb00sX29KuYM spIzFJxztDpaXL5Fj/l+EZ8gPXx19W+eCEblt1sed9GaXr/48cDE2CyHLa/BCy3+kG+g AOS0Zj7f91v9Du3uGW4H2b/IOUHhUTfowj2OAKIZYf152qZrpqLWXYmKMMGjNdjMmCW0 0CHx6xCQkU3SlxIB2FHUzbEy1kxLaGIiJ8Yaaysudt8HCrLRMo7TB/EKHcPL2XGGqlpB y8AviH85yNB/dnTzhgcrKvLY3OjDQB7tNRD8WzittL2jVZxkpAFC9hXF4B1cGXJnGI7V 4CXQ==
X-Gm-Message-State: AOAM532ef9CqT3EisPh3RrfoZiPkYFsXt+SRAV2ERgbqtgMOjECcW5qi wsKQUE0Y8h9bst7Ap1dnWYoe+OfDZxcgk7Dk+MWg7NJGxHOcJQ==
X-Google-Smtp-Source: ABdhPJzErOnDJMzO/11HAL/4CpITu7KTBSXEICTkPKnU56PVRbVEhGFnTe4tzcdsBSFOYqCODkn3/EhByQcTazHgPBs=
X-Received: by 2002:a67:c29e:: with SMTP id k30mr235570vsj.45.1612312235016; Tue, 02 Feb 2021 16:30:35 -0800 (PST)
MIME-Version: 1.0
References: <20210201231154.DAE426D208E1@ary.qy> <2e39680f-ed2d-fa38-daaa-7e0627cf0fc7@tana.it>
In-Reply-To: <2e39680f-ed2d-fa38-daaa-7e0627cf0fc7@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 2 Feb 2021 19:30:23 -0500
Message-ID: <CAH48Zfxekq2ucYeOLTJT-fdoLNVWtnRaSi7C4p_eF_oZXEPMpw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000009051705ba63b2ab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PVJ1IR3I3xcaqVsAZSubg9bbjtg>
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, 03 Feb 2021 00:30:38 -0000

--00000000000009051705ba63b2ab
Content-Type: text/plain; charset="UTF-8"

Yes, it is true that the spec says

    If a conclusive determination about the
    message can be made based on a check of "HELO", then the use of DNS
    resources to process the typically more complex "MAIL FROM" *can* be
    avoided.

However, it carefully avoids defining "definitive", which means the
interpretation of "definitive" is site-specific.   To my interpretation,
"definitive" means a local policy to whitelist or blacklist based
exclusively on the HELO parameters.   Such as decision will certainly allow
other operations to be omitted.

This interpretation is supported by the previous paragraph:

   It is RECOMMENDED that SPF verifiers not only check the "MAIL FROM"
   identity but also separately check the "HELO" identity by applying
   the check_host() function (Section 4
<https://tools.ietf.org/html/rfc7208#section-4>) to the "HELO"
identity as the
   <sender>.


and the subsequent paragraph:


     SPF verifiers MUST check the "MAIL FROM" identity if a "HELO" check

   either has not been performed or has not reached a definitive policy
   result by applying the check_host() function to the "MAIL FROM"
   identity as the <sender>.


We really have two different tests, which appear in the same document
because they exploit the same technology.


The limitations of Received-SPF become very conspicuous and problematic:

- The identifiers are only provided in comment text, which is optional
and has been omitted in the wild.

- Although comment text implementations appear to be standardized,
this is still less reliable than structured data.

- Even when the comment text can be parsed, only domain names are
provided, and the test type is not documented,

so there is no way to know whether the result is based on HELO or SMTP Address.

- Received-SPF needs to report two results for entities which perform
both tests, but multiple results simply create ambiguity..

- The Received-SPF cannot be linked to a specific Received entry.
The assumption is that it will only be used

 within a single ADMD, where the perimeter is known and all internal
MTAs are trusted.


We have integrated Received-SPF into A-R without improvement, and A-R
has been integrated into ARC without significant redesign.

Then we are hoping that a third-party organization will trust an ARC
which is based on this weak foundation.


DF


>

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

<div dir=3D"ltr"><div dir=3D"ltr">Yes, it is true that the spec says<div><b=
r></div><div>=C2=A0 =C2=A0 If a conclusive determination about the<br>=C2=
=A0 =C2=A0 message can be made based on a check of &quot;HELO&quot;, then t=
he use of DNS<br>=C2=A0 =C2=A0 resources to process the typically more comp=
lex &quot;MAIL FROM&quot; *can* be<br>=C2=A0 =C2=A0 avoided.<br></div><div>=
<br></div><div>However, it carefully avoids defining &quot;definitive&quot;=
, which means the interpretation of &quot;definitive&quot; is site-specific=
.=C2=A0 =C2=A0To my=C2=A0interpretation, &quot;definitive&quot; means a loc=
al policy to whitelist or blacklist based exclusively on the HELO parameter=
s.=C2=A0 =C2=A0Such as decision will certainly allow other operations=C2=A0=
to be omitted.</div><div><br></div><div>This interpretation is supported by=
 the previous paragraph:</div><div><br></div><div><pre class=3D"gmail-newpa=
ge" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-bef=
ore:page;color:rgb(0,0,0)">   It is RECOMMENDED that SPF verifiers not only=
 check the &quot;MAIL FROM&quot;
   identity but also separately check the &quot;HELO&quot; identity by appl=
ying
   the check_host() function (<a href=3D"https://tools.ietf.org/html/rfc720=
8#section-4">Section 4</a>) to the &quot;HELO&quot; identity as the
   &lt;sender&gt;.  </pre><pre class=3D"gmail-newpage" style=3D"font-size:1=
3.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0=
)"><br></pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;marg=
in-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">and the su=
bsequent paragraph:</pre><pre class=3D"gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)=
"><br></pre></div><div><span style=3D"color:rgb(0,0,0);font-size:13.3333px"=
>=C2=A0 =C2=A0</span>=C2=A0=C2=A0<span style=3D"color:rgb(0,0,0);font-size:=
13.3333px">SPF verifiers MUST check the &quot;MAIL FROM&quot; identity if a=
 &quot;HELO&quot; check</span><br></div><div><pre style=3D"font-size:13.333=
3px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">  =
 either has not been performed or has not reached a definitive policy
   result by applying the check_host() function to the &quot;MAIL FROM&quot=
;
   identity as the &lt;sender&gt;.</pre><pre style=3D"font-size:13.3333px;m=
argin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></p=
re><pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break=
-before:page;color:rgb(0,0,0)">We really have two different tests, which ap=
pear in the same document because they exploit the same technology.</pre><p=
re style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-befo=
re:page;color:rgb(0,0,0)"><br></pre><pre style=3D"font-size:13.3333px;margi=
n-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">The limitat=
ions of Received-SPF become very conspicuous and problematic:</pre><pre sty=
le=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:pag=
e;color:rgb(0,0,0)">- The identifiers are only provided in comment text, wh=
ich is optional and has been omitted in the wild.</pre><pre style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(=
0,0,0)">- Although comment text implementations appear to be standardized, =
this is still less reliable than structured data.</pre><pre style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(=
0,0,0)"><span style=3D"font-size:13.3333px;font-family:Arial,Helvetica,sans=
-serif">- Even when the comment text can be parsed, only domain names are p=
rovided, and the test type is not documented, </span><br></pre><pre style=
=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;=
color:rgb(0,0,0)">so there is no way to know whether the result is based on=
 HELO or SMTP Address.</pre><pre style=3D"font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">- Received-SPF need=
s to report two results for entities which perform both tests, but multiple=
 results simply create ambiguity..</pre><pre style=3D"font-size:13.3333px;m=
argin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">- The R=
eceived-SPF cannot be linked to a specific Received entry.   The assumption=
 is that it will only be used</pre><pre style=3D"font-size:13.3333px;margin=
-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"> within a si=
ngle ADMD, where the perimeter is known and all internal MTAs are trusted.<=
/pre><pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;bre=
ak-before:page;color:rgb(0,0,0)"><br></pre><pre style=3D"font-size:13.3333p=
x;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">We h=
ave integrated Received-SPF into A-R without improvement, and A-R has been =
integrated into ARC without significant redesign.</pre><pre style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(=
0,0,0)">Then we are hoping that a third-party organization will trust an AR=
C which is based on this weak foundation.</pre><pre style=3D"font-size:13.3=
333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">=
<br></pre><pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0p=
x;break-before:page;color:rgb(0,0,0)">DF</pre></div></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"><br>
</blockquote></div>
</div>

--00000000000009051705ba63b2ab--


From nobody Wed Feb  3 03:51: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 AA3CC3A08F4 for <dmarc@ietfa.amsl.com>; Wed,  3 Feb 2021 03:51:37 -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 UUUfkUXsTIKg for <dmarc@ietfa.amsl.com>; Wed,  3 Feb 2021 03:51:35 -0800 (PST)
Received: from mail-vk1-xa30.google.com (mail-vk1-xa30.google.com [IPv6:2607:f8b0:4864:20::a30]) (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 B64203A08ED for <dmarc@ietf.org>; Wed,  3 Feb 2021 03:51:35 -0800 (PST)
Received: by mail-vk1-xa30.google.com with SMTP id e1so5559911vkd.10 for <dmarc@ietf.org>; Wed, 03 Feb 2021 03:51: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=4huM2KkJJ4GujD7r7SSyqlXTrE14Q0rWkWYqHKARxkg=; b=hRX3FnoQjvh6AQLCWpK9/+zp0I3Ybm0gHlB02NoJML75c5IWVQPJ1ARnVUtzJLEXRH 6BL1erllFRDiCiUnMO0y3H/0mWzVRQdqKSRdnIhuXpadxuegEDWpdkeZdbEzqY6HWRWV Rk7QCcsYdJAPzuNriqHFZc3Gc1fi+Lozu1TIKeWAOcrFqXYwMGspsFSEk8PgLuFBj8Jb smW97OVPEfoR2FOOZMAh7/eDvT4xNnT/pPhstuOLXigc3TglJu63I0FKuu++610mLi+u ofAC8YfoZNmkNHSpxZdE0eE6mxWw4cGvRdhEJ6OS8B3FSsbXFIdISlu4+sdkkYWZ9Q2u XJqQ==
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=4huM2KkJJ4GujD7r7SSyqlXTrE14Q0rWkWYqHKARxkg=; b=HwS2jBq9lEb0PB7mKGkSsm8zVCr0gfZrJhJ3topN49Exf8gEM+QHDGR5Dy49K5h/G0 TSNRakX5MNOjeNNpIE16YBzq/CUpQiHAr/Zx/QgJu0L7I/OqL+6gt5ir98obDhT7iQ4Q GkY/BoQiUe2kyMMskFojxXNKHQ1cagWtVHv/WnfDUa2av4Zd8tg7VhqIkrZerVRRT2s2 EbPUBwUGiXqbmeSrWxcy7tCQFrnHK+fSizVFNtFfFpEULxUU+I1s63u46AWbY9Up2MKc x0wfUQxJ6BVbRyez01LuXFz7ayiou+VcvfJPfoUityvcXAXd1MKR706HGSDGDGWA8kBs F4KA==
X-Gm-Message-State: AOAM533wg3AV61nnxW+Aiyhs6+MHWNvCPeL6yoSl5dXxRYymLbGuh5GQ m8GPSskoZRf4WrH8GtMA620ZLEhYu7m5XxW07L/cbHyCfwA=
X-Google-Smtp-Source: ABdhPJxGcD0aW6N0fVpWZd2Iz8mcK9IDDeT+1ccZ9Kh/CMiZXxEGPtghsRwsd+gmKMpRatNrBi7EdaMvjz34WTC2mr8=
X-Received: by 2002:a1f:3112:: with SMTP id x18mr1259038vkx.4.1612353094541; Wed, 03 Feb 2021 03:51:34 -0800 (PST)
MIME-Version: 1.0
References: <20210202174909.517906D2C88B@ary.qy> <286b8e6c-67b4-2c16-1632-16bf8cd95b78@tana.it> <18d01d3d-9a22-fe33-fa36-8f3a92cce4@taugh.com> <4A21A4F6-4021-4C38-A707-0141593A3849@bluepopcorn.net> <40a52ab3-748a-c898-aa66-b335b720c73e@taugh.com>
In-Reply-To: <40a52ab3-748a-c898-aa66-b335b720c73e@taugh.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 3 Feb 2021 06:51:22 -0500
Message-ID: <CAH48ZfyRzbgkFbD=F-iHWaZM70c=VH1XSi_0EqC4-twvgBH8Jw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000073e56005ba6d3579"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9FcjE0N-XzT52noc5RpsMd6SgI0>
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, 03 Feb 2021 11:51:38 -0000

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

I believe that most code is validating the MailFrom parameter if it is
supplied, and validating the HELO name only if MAILFROM is null.   This is
based mostly on the way SPF has been discussed over the last 15 years,
coupled with the observed behavior of a limited number of
product implementations..

If we are to argue that HELO and MAILFROM tests are interchangeable, we
have to deal with the situation where the domains are different and the
results are different.    SPF has 7 possible results, so there are 49
possible combinations of these two tests, 42 of which are divergent.   (If
we factor in NXDOMAIN as a separate result, which even RFC 7208 says is
probably appropriate for HELO, the number of divergent results is even
greater.)

To merge the tests, we would need to define a winning result for all of the
divergent result pairs, and then demonstrate that our winning result can be
considered appropriate for all installations.   Such an undertaking has not
been attempted, and I cannot imagine it achieving consensus.

The result needed for DMARC is the result I believe is actually being
produced by most installations:   The result is evaluated based on MAILFROM
when it is not null, and evaluated using HELO domain when MAILFROM is
null.   Of course, using HELO as a proxy for MAILFROM only works for bounce
messages being returned from installations hosting a single mail domain on
a matching host domain.   For everyone else, DMARC will only verify
automatic messages that are signed with the From address domain.  The DMARC
specification should make this clear to the reader.

- - -

To correct an earlier comment of mine:

fcDNS on HELO and SPF HELO tests can be used together quite effectively.
 fcDNS validates that the server is reporting a valid host name, limits the
allowed results to a single DNS domain, and demonstrates that the domain
being used for SPF HELO is the correct one.  However, fcDNS does not
demonstrate that the server is authorized to send mail.   SPF defines the
servers which are allowed to send mail for the domain, but may include IP
addresses from other domains, either directly or through Include clauses.
 When the host name is verified with both fcDNS and SPF HELO, the evaluator
knows that the server is in the reported domain and authorized by that
domain to send mail.

Note that this is also different from fcDNS on the Reverse DNS name, as
reported with the "iprev" test result.  We really do not have a way to
report test results for the HELO name.  It would seem desireable to add
test result indicators for both fcDNS HELO and fcDNS SPF.

Doug Foster



.

On Tue, Feb 2, 2021 at 2:54 PM John R Levine <johnl@taugh.com> wrote:

> >> There is some commented out code to not pass a HELO result to DMARC,
> don't
> >> remember why I turned it off.
> >
> > I=E2=80=99m lost in a double negative here: did you turn off passing a =
HELO
> result to
> > DMARC, or did you turn off not passing a HELO result?
>
> The live code uses whichever result it has.  The commented out code only
> used a MAIL FROM result.
>
> >> Again, I believe this is typical of what DMARC validators do.  It's
> >> existing practice and I see no reason to change it.  Can we stop now?
> >
> > If you found that you needed to turn off something that=E2=80=99s part =
of the
> DMARC
> > spec, it would be good to understand why.
>
> I believe that what I am doing matches the spec.
>
> 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
>

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

<div dir=3D"ltr"><div dir=3D"ltr">I believe=C2=A0that most code is validati=
ng the MailFrom parameter if it is supplied, and validating the HELO name o=
nly if MAILFROM is null.=C2=A0 =C2=A0This is based mostly on the way SPF ha=
s been discussed over the last 15 years, coupled with the observed behavior=
 of a limited number of product=C2=A0implementations..<div><br></div><div>I=
f we are to argue that HELO and MAILFROM tests are interchangeable, we have=
 to deal with the situation where the domains are different and the results=
 are different.=C2=A0 =C2=A0 SPF has 7 possible results, so there are 49 po=
ssible combinations of these two tests, 42 of which are divergent.=C2=A0 =
=C2=A0(If we factor in NXDOMAIN as a separate result, which even RFC 7208 s=
ays is probably appropriate for HELO, the number of divergent results is ev=
en greater.)</div><div><br></div><div>To merge the tests, we would need to =
define a winning result for all of the divergent result pairs, and then dem=
onstrate that our winning result can be considered appropriate=C2=A0for all=
 installations.=C2=A0 =C2=A0Such an undertaking has not been attempted, and=
 I cannot imagine it achieving consensus.</div><div><br></div><div>The resu=
lt needed for DMARC is the result I believe is actually being produced by m=
ost installations:=C2=A0 =C2=A0The result is evaluated based on MAILFROM wh=
en it is not null, and evaluated using HELO domain when MAILFROM is null.=
=C2=A0 =C2=A0Of course, using HELO as a proxy for MAILFROM only works for b=
ounce messages being returned from installations hosting a single mail doma=
in on a matching host domain.=C2=A0 =C2=A0For everyone else, DMARC will onl=
y verify automatic messages that are signed with the From address domain.=
=C2=A0 The DMARC specification should make this clear to the reader.</div><=
div><br></div><div>- - -</div><div><br></div><div>To correct an earlier com=
ment of mine:=C2=A0 =C2=A0</div><div><br></div><div>fcDNS on HELO and SPF H=
ELO tests can be used together quite effectively.=C2=A0 =C2=A0fcDNS validat=
es that the server is reporting a valid host name, limits the allowed resul=
ts to a single DNS domain, and demonstrates that the domain being used for =
SPF HELO is the correct one.=C2=A0 However, fcDNS does not demonstrate that=
 the server is authorized to send mail.=C2=A0 =C2=A0SPF defines the servers=
 which are allowed to send mail for the domain, but may include IP addresse=
s from other domains, either directly or through Include clauses.=C2=A0 =C2=
=A0When the host name is verified with both fcDNS and SPF HELO, the evaluat=
or knows that the server is in the reported domain and authorized by that d=
omain to send mail.</div><div><br></div><div>Note that this is also differe=
nt from fcDNS on the Reverse DNS name, as reported with the &quot;iprev&quo=
t; test result.=C2=A0 We really do not have a way to report test results fo=
r the HELO name.=C2=A0 It would seem desireable to add test result indicato=
rs for both fcDNS HELO and fcDNS SPF.</div><div><br></div><div>Doug Foster<=
/div><div><br></div><div><br></div><div><br></div><div>.</div></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Feb 2=
, 2021 at 2:54 PM John R 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">&gt;&gt; There is some commented out code to not pass a HELO res=
ult to DMARC, don&#39;t <br>
&gt;&gt; remember why I turned it off.<br>
&gt;<br>
&gt; I=E2=80=99m lost in a double negative here: did you turn off passing a=
 HELO result to <br>
&gt; DMARC, or did you turn off not passing a HELO result?<br>
<br>
The live code uses whichever result it has.=C2=A0 The commented out code on=
ly <br>
used a MAIL FROM result.<br>
<br>
&gt;&gt; Again, I believe this is typical of what DMARC validators do.=C2=
=A0 It&#39;s <br>
&gt;&gt; existing practice and I see no reason to change it.=C2=A0 Can we s=
top now?<br>
&gt;<br>
&gt; If you found that you needed to turn off something that=E2=80=99s part=
 of the DMARC <br>
&gt; spec, it would be good to understand why.<br>
<br>
I believe that what I am doing matches the spec.<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>
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></div>

--00000000000073e56005ba6d3579--


From nobody Wed Feb  3 08:55: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 5F8533A0BC7 for <dmarc@ietfa.amsl.com>; Wed,  3 Feb 2021 08:55: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=Jgz2I8xk; dkim=pass (2048-bit key) header.d=taugh.com header.b=x/+QvM4H
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLSBEpw0EJJH for <dmarc@ietfa.amsl.com>; Wed,  3 Feb 2021 08:55: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 821BE3A0BC5 for <dmarc@ietf.org>; Wed,  3 Feb 2021 08:55:47 -0800 (PST)
Received: (qmail 24803 invoked from network); 3 Feb 2021 16:55:46 -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=60e1.601ad592.k2102; bh=75LaLi7R0rboh+IN8nKS9v7qnfa0AGZsf3+7ge2U8II=; b=Jgz2I8xkkH1ayQ7QD8UrJzp3khsCMrQDIoZSZigpa67i0EJnlmN426cxSIXTYtnrmxXn7+TmSfLCv9HpGXHtBHHgyP4eY7vKKe5LXeYjdY8SCeKVxR6mtrtdDGrrhw4LRzCpSsu3hAadBD3/Qmo27zZJiN9fICpLP8ZZIhmWuyAg4BFuJfFcEmwVe4jBqsIW8FAuRYblhS7J9eZCFq4ViqAAGvPB766cCfTe8Ic0bEAv83Tf8Qwlm/Sa1c2u9RJXiu/qDJauO81TKaL6ILyVY1MFxVmeyYbdCwGuEKJSTSAThTt3kgG5nNeUpRd6Xhjvsk794eZ1Ks9pW8fnGY2n1A==
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=60e1.601ad592.k2102; bh=75LaLi7R0rboh+IN8nKS9v7qnfa0AGZsf3+7ge2U8II=; b=x/+QvM4HwmitfZDEdEWj1RGd4yCrVUlYfmQoEhqxeNOCoA7oNv44HNoec2ZeZAQ12UmyarIrx1cXCuxSzROkGi7bFZ/KGPZdMfQ+YcbHizhHCSHfd1eS9/bgZqmHC5dRhzih+RdmzZ3+xatVuv6oyZD7qCCGQcZYd4QhEtwW2P7lxd0qGv9QxQv+lV6hHpGHGDcXzGI0ZQEvAeMaiM4nyzCApl4FhnammFW+/oAj33zTGrovE4Y1/Dr9Ri9RP/KAvyhfxC4t7BSdQq8nF8+kMxCLu2S1D+AX/aL+zIkJoCRV0su00gJ/ofhtsiCI3YmvcOrJdrHD4MZH41RzNycN7g==
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; 03 Feb 2021 16:55:46 -0000
Received: by ary.qy (Postfix, from userid 501) id 0A8966D4BFFF; Wed,  3 Feb 2021 11:55:45 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id D58FE6D4BFE1; Wed,  3 Feb 2021 11:55:45 -0500 (EST)
Date: 3 Feb 2021 11:55:45 -0500
Message-ID: <a869fa7-bff9-dbd7-3b77-dbe8f12f3653@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
In-Reply-To: <14646a55-66a6-974e-baf8-55d8503c4f96@tana.it>
References: <20210131200238.931356D11D79@ary.qy> <e7e27e1f-b6e6-96b6-e12e-672084562b8a@tana.it> <41bc91e9-8c9a-e2bd-a351-602436f3f5bb@taugh.com> <14646a55-66a6-974e-baf8-55d8503c4f96@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/BEQGkQCfY4Y0aZW60o7JeWlz5vE>
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: Wed, 03 Feb 2021 16:55:50 -0000

On Tue, 2 Feb 2021, Alessandro Vesely wrote:
>                          Whatever mechanisms are used, servers MUST
>   contain provisions for detecting and stopping trivial loops.

I can tell you from bitter experience that rate limiting is the *ONLY* 
reliable way to stop trivial loops.  Whatever else you try, something will 
eventually change or delete the thing you try to use to recognize loops.

As a concrete example, I get a lot of failure reports from 
antispamcloud.com which are not multipart/report and which software would 
not recognize as a failure report.  Nonetheless, if they got into a 
reporting loop, it would be annoying, and rate limiting would stop them.

> Mailbombing in general is not a loop.  Two report generators reporting each 
> other's failure to authenticate a failure report /is/ a loop.

Sometimes mailbombing is a loop, sometimes it isn't.  If the loop is so 
slow that it doesn't trigger rate limits, it's not likely to be a 
practical 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 Feb  3 09:44: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 5C78C3A0CB4 for <dmarc@ietfa.amsl.com>; Wed,  3 Feb 2021 09:43: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 7P8zKHD83-K4 for <dmarc@ietfa.amsl.com>; Wed,  3 Feb 2021 09:43: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 BDB263A0CB2 for <dmarc@ietf.org>; Wed,  3 Feb 2021 09:43:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612374235; bh=ukE0xkixjCUOtQeEw+TyPXzLM35+/r6OwxkjOHKYZnI=; l=1944; h=To:References:From:Date:In-Reply-To; b=DYY0FJgNVb1hEtMaRDSdIIxhzb2bs7Ma//iBqlzj0vWtynzVPIRPJs82CVpFIfUXQ Zi/DD3GMPcj5ebYkOuC6klD5qxjHgC4bP/bSVFS1OgCj0t8PkZI9xAN6L3ApKfA/P8 qL44KE0B5KbVw5j+jzWpqV/zxayY0ZPFjQidA3INwJ6nFVE8Km+mSy/3oNiu0
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 00000000005DC083.00000000601AE0DB.00001C5B; Wed, 03 Feb 2021 18:43:55 +0100
To: John R Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210202174909.517906D2C88B@ary.qy> <286b8e6c-67b4-2c16-1632-16bf8cd95b78@tana.it> <18d01d3d-9a22-fe33-fa36-8f3a92cce4@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <b396cf21-05f4-a1a4-5abc-78c5aa276473@tana.it>
Date: Wed, 3 Feb 2021 18:43: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: <18d01d3d-9a22-fe33-fa36-8f3a92cce4@taugh.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/U-71xxLtdk7JQAX4r_5c-G1TvqI>
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, 03 Feb 2021 17:44:00 -0000

On Tue 02/Feb/2021 20:13:42 +0100 John R Levine wrote:
> 
> There is some commented out code to not pass a HELO result to DMARC, don't 
> remember why I turned it off.


Couldn't find the code you uncommented in.

Apparently, OpenDMARC reads Authentication-Results: (or Received-SPF:) and calls opendmarc_policy_store_spf() to save the result it parsed.  That way, the last value found is the one that will be used.

It seems that relies on upstream SPF filters writing a single SPF result.  If mfrom is given write its result, otherwise write helo's.  That behavior is presumably coded after DMARC's idiosyncrasy.  It would choke if applied to an unskewed SPF filter's results.


> Again, I believe this is typical of what DMARC validators do.


Yes.  Here's an example by Google.  You may note that the helo name reported in Received: must have resulted in an spf=pass, which is not reported:

ARC-Authentication-Results: i=1; mx.google.com;
        spf=neutral (google.com: 62.94.243.226 is neither permitted nor denied by best guess record for domain of user@fragolina.it) smtp.mailfrom=user@fragolina.it;
        dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=tana.it
Return-Path: <user@fragolina.it>
Received: from wmail.tana.it (wmail.tana.it. [62.94.243.226])
         by mx.google.com with ESMTP id d18si1599313edu.101.2021.02.03.08.37.32
         for <REDACTED@gmail.com>;
         Wed, 03 Feb 2021 08:38:57 -0800 (PST)


> It's existing practice and I see no reason to change it.


Software changes all the time.  If we change, this particular fix would probably be less noticeable than many other software bugs lurking amid the code.  Indeed, you have to craft a message on purpose in order to have mfrom fail while helo pass (as the example above).

We can even explicitly allow the existing behavior for historical reasons, if nobody recalls why the spec came out that way.

However, please, let's not write a quirky spec.

Best
Ale
-- 













From nobody Wed Feb  3 10:12:35 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 C15653A0D05 for <dmarc@ietfa.amsl.com>; Wed,  3 Feb 2021 10:12:33 -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=ZNkwqTaC; dkim=pass (2048-bit key) header.d=taugh.com header.b=CKah99Or
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ugdbIc-GMN1w for <dmarc@ietfa.amsl.com>; Wed,  3 Feb 2021 10:12:31 -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 EE55A3A09EA for <dmarc@ietf.org>; Wed,  3 Feb 2021 10:12:30 -0800 (PST)
Received: (qmail 44374 invoked from network); 3 Feb 2021 18:12: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=ad52.601ae78b.k2102; bh=bbYnEdizRY3k4Od162wPSnMZTyeKeQ7TQqBIf1rQyy8=; b=ZNkwqTaCKm9f+82YV1nU69u9ByV31kZfiM//N6sGLUhI1OuHEorge1ye1362omUh5iAXJUpGy5LZ2K+b4w1q1jnOO/+2OQCG7aNPxxlkcJeGFWaev7ywlBHGEJ0F33MNDx7OrpOavOyjO4g0wLcd50Mo14OLZO7qLR5t0HJq3aj7nJcOzCFtJIwTBAP2b+C1+PzFM22mYiFcxnCvg9ZZZq+XOGgzXi1T4LHEi8nDumhp1SdaKswKiIyY16Nzo7gPmix6oOja6AIeWXhEO8KuL6jPuKCrveIe0itDl9bErTPZRbOJmO96BtuvFzOeszAA6AjlHWNTbD9uAYMsn7w8iA==
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=ad52.601ae78b.k2102; bh=bbYnEdizRY3k4Od162wPSnMZTyeKeQ7TQqBIf1rQyy8=; b=CKah99Orkz6SEw10INLSCdkWb3vmGQUORQVkGP0cSTFIYJmyZ2QIu/yBar2E0nR501o4Od1nMmtAPbF5YOOsaKqV05ciMNXQxypRBl3jGruxl4QT/fDVT6r/8hM9W650LLdpIcNzTUOQavqmTlEdRRFW/Q2zHg2ku3l1M1V8+17VF1oo0rWiGH7EHsfYG3Wd7txoC6IBe1EvnAtliIAZhP1t5eDw1sAq/dMKIEjpxwYawAzA/vlvEPo7Yfrj8280Jrk9PvGJd0H2Oq4JqKKA3ITk1d12NEuEVWqYtSfOa968K29pKsbAs4tN4rPQ7kDW/BiuiLlOrQm4RCz4I/YWVQ==
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; 03 Feb 2021 18:12:27 -0000
Received: by ary.qy (Postfix, from userid 501) id 9AB746D51182; Wed,  3 Feb 2021 13:12:26 -0500 (EST)
Date: 3 Feb 2021 13:12:26 -0500
Message-Id: <20210203181226.9AB746D51182@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <b396cf21-05f4-a1a4-5abc-78c5aa276473@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/r8sGg9-yHqQ6nHErCDcIbQ4DTRU>
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, 03 Feb 2021 18:12:34 -0000

In article <b396cf21-05f4-a1a4-5abc-78c5aa276473@tana.it> you write:
>On Tue 02/Feb/2021 20:13:42 +0100 John R Levine wrote:
>> 
>> There is some commented out code to not pass a HELO result to DMARC, don't 
>> remember why I turned it off.
>
>Couldn't find the code you uncommented in.

I'm not surprised.  It's only in my MTA.

>Apparently, OpenDMARC reads Authentication-Results: (or Received-SPF:) and calls opendmarc_policy_store_spf() to save
>the result it parsed.  That way, the last value found is the one that will be used.
>
>It seems that relies on upstream SPF filters writing a single SPF result.  If mfrom is given write its result,
>otherwise write helo's.  That behavior is presumably coded after DMARC's idiosyncrasy.  It would choke if applied to an
>unskewed SPF filter's results.

Is that what its milter does?  Not surprised.

>> It's existing practice and I see no reason to change it.
>
>Software changes all the time.  If we change, ...

Urrgh. There are still MTAs that haven't been updated from RFC 821. If
you want a real standard, the closer you can make it to what the
running code does, the most likely it will work.

R's,
John


From nobody Wed Feb  3 13:55: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 1FE693A1220 for <dmarc@ietfa.amsl.com>; Wed,  3 Feb 2021 13:55:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 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, 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 HaGVRXVTRtEZ for <dmarc@ietfa.amsl.com>; Wed,  3 Feb 2021 13:55: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 D73D53A121F for <dmarc@ietf.org>; Wed,  3 Feb 2021 13:55:49 -0800 (PST)
Received: by mail-pg1-x52a.google.com with SMTP id g15so665621pgu.9 for <dmarc@ietf.org>; Wed, 03 Feb 2021 13:55:49 -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=5AuIpLb467h4RvbnYTDJpD6NwW28C1oaaViJjh/ISO0=; b=HQiQCvnMDvf+JlppOaQkvESXmgVdvxIvPMUb4fKFwJh3lsTlQw329konb0pwKDlL8p q7slBmCeAHgodrMVkpfY2pvmuEjcN025NSKHNhuYmcOlMDEeh3XBR+FJoOxKbBfv/Dl7 b9PwRPVJRENVe9Rf4A7jQi/rJuQNujkBLtBL9q3AUY1thDl13R4AkUesPrS+bRh6gxD8 78anY1dYolMCojiFh2yowJdz7zZRMOUz23mLrla0HuS4uA1VmYL3W9+Nm9oKKLVLcez4 BpK4sBUxDnbQdmEIH5y+FK+wk5cS2CVvEOFJIS5OiQVMPhCsnuy5vZoC/lg1ZgdFPNG9 TEjA==
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=5AuIpLb467h4RvbnYTDJpD6NwW28C1oaaViJjh/ISO0=; b=rQu2ZTLggu/5ml9INF7xDIJwe30EA/OBIjhqlYVTb/Sf/OuKrpvILTrHjg6b+yWFTY 4p5CfH2A1xUHTeqHknF+78NIZCjCji77zrVOL8dEzMP0oj+4SzB1mE3aaCBfJPMDL6X2 AVCbr3cqDo5DuyApWyocuewk4301kAS6Usbj12xjW45niADc9ikdPPSKj+LyWd7Qo4DZ bXx7vDxeN7hRtBC9Mr+LVs+X6qc6CebvNHbydILtZFc2jRbARGAtt6u1l2WpCEkzAbBJ Ik3Y/KTce3x+mItPu8xVVxNW6JxATIiih/JXSEXt+gpE/wvJWCkyytmskZsCLzP5uywZ cCPg==
X-Gm-Message-State: AOAM532C2I47dqwJrww09mYlctbYu+6iFIbCch90sUSJdC+ZDFNdLb0E F4+50pnk3DKgaltS5qIVZY90hgCYMkBptg==
X-Google-Smtp-Source: ABdhPJyt12CvvGyALoNJRiLtJx6xfvYKndTpyiHUprr6ws6CTTPCO2o61KeK5RyjEuz1cTZAjt5fAQ==
X-Received: by 2002:a65:62d3:: with SMTP id m19mr5940458pgv.180.1612389348690;  Wed, 03 Feb 2021 13:55:48 -0800 (PST)
Received: from mike-mac.lan (107-182-44-214.volcanocom.com. [107.182.44.214]) by smtp.gmail.com with ESMTPSA id h15sm284853pfo.84.2021.02.03.13.55.47 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 03 Feb 2021 13:55:47 -0800 (PST)
To: "dmarc@ietf.org" <dmarc@ietf.org>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <69fcf7af-ced7-2d1f-b13e-1ee4296919fb@mtcc.com>
Date: Wed, 3 Feb 2021 13:55: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
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/2LxChaaMihKhlz_iddFqvgyrkro>
Subject: [dmarc-ietf] so long again
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 03 Feb 2021 21:55:51 -0000

I came here wondering what ARC was which I got answered and for which I 
wrote a blog post saying that we should just give up on the mailing list 
problem.

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

The same crap that drove me away the last time is still raging on and 
I'm tired of getting singled out. I did however write a history of DKIM 
and SSP that some here might enjoy since DMARC is pretty much SSP. Mark 
and Murray have been giving me some insight to their back story which 
I'd encourage them to write up too.

https://rip-van-webble.blogspot.com/2021/01/storing-asymmetric-keys-in-client.html

Mike


From nobody Thu Feb  4 04:50:30 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 2F13D3A1405 for <dmarc@ietfa.amsl.com>; Thu,  4 Feb 2021 04:50:29 -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 YZyNBTyeq8Wo for <dmarc@ietfa.amsl.com>; Thu,  4 Feb 2021 04:50: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 4E7E73A1403 for <dmarc@ietf.org>; Thu,  4 Feb 2021 04:50:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612443024; bh=XESHsBhWGdM5o8R+E1RJD+OCgxb6GKyUZppeIB88ElI=; l=1228; h=To:References:From:Date:In-Reply-To; b=ABCNdXWpwDrqyou2lqH2NdlvWa/tedpByW/m7wKEYBdecAmNn4Sa+MmUm5X1J7GAn lbPL+33Rv+68cfdVxft7CE8MKlL6LTU04Fl9qRIgh8LxjRsKbr0Od1A5YfS95VvhSe Z+WeAsexR0DNxSkkyV3KMoVkjAQIQqBTbydJK7u9iDEIM+EARoqGPx6EkZUjk
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 00000000005DC0C0.00000000601BED8F.00006311; Thu, 04 Feb 2021 13:50:23 +0100
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210203181226.9AB746D51182@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <e169f069-376d-7072-2538-c77bbe7b7540@tana.it>
Date: Thu, 4 Feb 2021 13:50: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: <20210203181226.9AB746D51182@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/Ks6ZMEOuGQ-KvBCuCHNpcKiC7jQ>
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, 04 Feb 2021 12:50:29 -0000

On Wed 03/Feb/2021 19:12:26 +0100 John Levine wrote:
> In article <b396cf21-05f4-a1a4-5abc-78c5aa276473@tana.it> you write:
>>On Tue 02/Feb/2021 20:13:42 +0100 John R Levine wrote:
>>> It's existing practice and I see no reason to change it.
>>
>>Software changes all the time.  If we change, ...
> 
> Urrgh. There are still MTAs that haven't been updated from RFC 821. If
> you want a real standard, the closer you can make it to what the
> running code does, the most likely it will work.


How about this:

     NOTE: Historically, SPF was focused on the mfrom identifier.  The helo
     identifier was retrofitted later, in order to account for delivery status
     notifications.  Earlier DMARC specifications followed suit.  Subsequently,
     it turned out that SPF records for the helo identifier are actually sharper
     than those for mfrom, thereby making successful helo verifications very
     reliable.  However, in the vast majority of cases the mfrom identifier is
     aligned with the main DMARC identifier, while the helo identifier often
     does not have a corresponding SPF record.  Therefore, the common practice
     of using just the SPF result of mfrom unless empty is still a valid
     heuristic.

?


Best
Ale
-- 










From nobody Thu Feb  4 08:43:13 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 B6D793A165C for <dmarc@ietfa.amsl.com>; Thu,  4 Feb 2021 08:43:11 -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=GF33uJ9H; dkim=pass (2048-bit key) header.d=taugh.com header.b=e2dUk91F
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5FygwQ75LIn for <dmarc@ietfa.amsl.com>; Thu,  4 Feb 2021 08:43:09 -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 252813A1657 for <dmarc@ietf.org>; Thu,  4 Feb 2021 08:43:08 -0800 (PST)
Received: (qmail 58425 invoked from network); 4 Feb 2021 16:43:07 -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=e437.601c241b.k2102; bh=ZC2VK1pb1rmnOir0zaHXAiXyWU+pYw94sZ3ec4lAQUk=; b=GF33uJ9H0zQ3cXg+Bti+Kvu2uy9SQbMqERbxYU1g6qUCh0Vd/aA332pvb5CdRvd98GNKHgCChv7L1S2gPIsS6NQcdBungzv6DeOVaAlT7lYwp7AFQNPRd+Fqiq+bj+YFkBVc3KwJRWeoltZtWWS7HEPimvzZF2uBgC61w1GGBCsNnKbVoo3IrKBx8g04HDfYbAflDWlKwxvcTsbV/4bLq+fT51ZoDNK8HZx3roQcndGka3Daua3jAB+xNs+OlhftkYYh6X4AaeiEeZi2qqLvxIXWzN8sbMhRU0HzBvm2JPa09xvt8KSZHrjLiCiX4xtCyNcyBamGIMKsBv0/XdCkQw==
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=e437.601c241b.k2102; bh=ZC2VK1pb1rmnOir0zaHXAiXyWU+pYw94sZ3ec4lAQUk=; b=e2dUk91FqNHX/pDGd9wU1dzVr8TQEsAfy20g621YbpBvxefd/kssxJfoNApcLgapMw7nO0yte+N78OHPpGWci1cKGj6vMueDF+HJxR6wGcP7iww+OK0BgKRSTv0vyiTHSne6/y9hwpMCj+s3vQr9ue//eAJiduCOlfriEWByDRHaJhM6N8S89VvO5HQDtsQOCnIYQWXKiEBdgSo0aI9NRlarysazHhVkxUJwkKAgVtlzn9eEACm5Zs5GTWvPrVpJI1MsYbbQPkszFrhNry6kTYKSGPTiC3y0j5bamnqdhSnDQbnjlH5yFTV7BYiQvUA35Q7wpgKQPqTrTYmSEqJXfw==
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 Feb 2021 16:43:07 -0000
Received: by ary.qy (Postfix, from userid 501) id 8B4C16D5F662; Thu,  4 Feb 2021 11:43:06 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 4082B6D5F644; Thu,  4 Feb 2021 11:43:06 -0500 (EST)
Date: 4 Feb 2021 11:43:06 -0500
Message-ID: <b9c3487-44ed-a132-d42-47364fd819b4@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
In-Reply-To: <e169f069-376d-7072-2538-c77bbe7b7540@tana.it>
References: <20210203181226.9AB746D51182@ary.qy> <e169f069-376d-7072-2538-c77bbe7b7540@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/pB2rBLgvKxsHpmUF9OXHCDBrqJw>
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, 04 Feb 2021 16:43:12 -0000

I really do not see anything to change here, and we have a lot of other 
tickets to work on.  Please, can we stop and close this one?


> On Wed 03/Feb/2021 19:12:26 +0100 John Levine wrote:
>> In article <b396cf21-05f4-a1a4-5abc-78c5aa276473@tana.it> you write:
>>> On Tue 02/Feb/2021 20:13:42 +0100 John R Levine wrote:
>>>> It's existing practice and I see no reason to change it.
>>> 
>>> Software changes all the time.  If we change, ...
>> 
>> Urrgh. There are still MTAs that haven't been updated from RFC 821. If
>> you want a real standard, the closer you can make it to what the
>> running code does, the most likely it will work.
>
>
> How about this:
>
>    NOTE: Historically, SPF was focused on the mfrom identifier.  The helo
>    identifier was retrofitted later, in order to account for delivery status
>    notifications.  Earlier DMARC specifications followed suit. 
> Subsequently,
>    it turned out that SPF records for the helo identifier are actually 
> sharper
>    than those for mfrom, thereby making successful helo verifications very
>    reliable.  However, in the vast majority of cases the mfrom identifier is
>    aligned with the main DMARC identifier, while the helo identifier often
>    does not have a corresponding SPF record.  Therefore, the common practice
>    of using just the SPF result of mfrom unless empty is still a valid
>    heuristic.
>
> ?
>
>
> Best
> Ale
>

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


From nobody Fri Feb  5 14:50:40 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 1A7553A0CF8 for <dmarc@ietfa.amsl.com>; Fri,  5 Feb 2021 14:50:38 -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=BCT4gL1Z; dkim=pass (2048-bit key) header.d=kitterman.com header.b=TnAuFeCc
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QfS3be0lXGit for <dmarc@ietfa.amsl.com>; Fri,  5 Feb 2021 14:50:36 -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 860603A0CF6 for <dmarc@ietf.org>; Fri,  5 Feb 2021 14:50:36 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 241BEF80279 for <dmarc@ietf.org>; Fri,  5 Feb 2021 17:50:35 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1612565434; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=DEVHl9jTaJOArQU3ntu1iqhLWKrzmdr5TbXD/Hrkgzc=; b=BCT4gL1ZM/Rn7ETdvIbWV1zEGMDxnB/IXdc2mwePuAzY2PSJDvTQzFyIApnzmIC1Y5/OZ uodDNtJ9+UpDTf/Dw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1612565434; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=DEVHl9jTaJOArQU3ntu1iqhLWKrzmdr5TbXD/Hrkgzc=; b=TnAuFeCcuRy8Fri/T4B0JS+jgnc423UqIa7qrxyUyNXDVK2gi1sydGoqvVetnsUolWzHO vAg2WZBMknNnvx+E2SuIM1dhF91srC+IxhbnPDLgYRUlEjyIJX72Pc+6gCzvFxdnmLGBpv+ /k5dYaRRsHIZ9BcBcEQ7QfecSdC46O2S1mZ1P3cYMGuKX7tlT8tKSh98CZDaZF3R6XIlWi6 1VoSultgq6915cAonnwgfl3Og4L08ooMOdtOvZuKq0ueMHAiS/73VmhvC3SZZh6PuP7gjiX Uy5jUm8kdiBonOjFAUEDxqI/Z7QoejHUMY/yKm0k3Apuoe3/SbYe77dGdT2Q==
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 C7AD5F80025 for <dmarc@ietf.org>; Fri,  5 Feb 2021 17:50:34 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Fri, 05 Feb 2021 17:50:34 -0500
Message-ID: <2086207.knHnThfGgH@zini-1880>
In-Reply-To: <e169f069-376d-7072-2538-c77bbe7b7540@tana.it>
References: <20210203181226.9AB746D51182@ary.qy> <e169f069-376d-7072-2538-c77bbe7b7540@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/g6kIwhvQvNcanVOyXC-DijPsHF8>
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, 05 Feb 2021 22:50:38 -0000

On Thursday, February 4, 2021 7:50:22 AM EST Alessandro Vesely wrote:
> On Wed 03/Feb/2021 19:12:26 +0100 John Levine wrote:
> > In article <b396cf21-05f4-a1a4-5abc-78c5aa276473@tana.it> you write:
> >>On Tue 02/Feb/2021 20:13:42 +0100 John R Levine wrote:
> >>> It's existing practice and I see no reason to change it.
> >>
> >>Software changes all the time.  If we change, ...
> >>
> > Urrgh. There are still MTAs that haven't been updated from RFC 821. If
> > you want a real standard, the closer you can make it to what the
> > running code does, the most likely it will work.
> 
> How about this:
> 
>      NOTE: Historically, SPF was focused on the mfrom identifier.  The helo
>      identifier was retrofitted later, in order to account for delivery
> status notifications.  Earlier DMARC specifications followed suit. 
> Subsequently, it turned out that SPF records for the helo identifier are
> actually sharper than those for mfrom, thereby making successful helo
> verifications very reliable.  However, in the vast majority of cases the
> mfrom identifier is aligned with the main DMARC identifier, while the helo
> identifier often does not have a corresponding SPF record.  Therefore, the
> common practice of using just the SPF result of mfrom unless empty is still
> a valid heuristic.
> 
> ?

I really think we should just stop.  Independently of if your note is a good 
idea (I really don't think it's needed), it's also inaccurate.  As written it 
implies that HELO checking was added to SPF after DMARC was developed.  HELO 
checking was added in 2004 or earlier.  When was DMARC defined?

Please just stop.

Scott K



From nobody Sat Feb  6 11:53:41 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 7A1C73A24BB for <dmarc@ietfa.amsl.com>; Sat,  6 Feb 2021 11:53:40 -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 Ueb8U-N3_di8 for <dmarc@ietfa.amsl.com>; Sat,  6 Feb 2021 11:53:39 -0800 (PST)
Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (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 2EF693A2481 for <dmarc@ietf.org>; Sat,  6 Feb 2021 11:53:39 -0800 (PST)
Received: by mail-qv1-xf2f.google.com with SMTP id j13so5187199qvu.10 for <dmarc@ietf.org>; Sat, 06 Feb 2021 11:53:39 -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=vcDKl/0u7OmrI+COR4zni8jASsEgz5AozbA4FXQQEnw=; b=fQMZpng6atMWXDW1p2DdnpnjGkbRQdiUGm7NFW7rGIRWxsMgLBffYGZavmra9J2IfI pJhjCNofsCWDPBPXgxFli2IYaxJ6JCji4J1eA0FEs1LnJEgvqw4ZzIisyDKZ01gzJPn5 iVbK1HyfBIgPn/4cXIXevKD6uhhZVoAjYFg14Io4f6YWdQow3CMdTJQUyheOzq0oKOdR gtG31Etuf4T2n2vrO4qntq0qtJI4ft2CbENJJmE5CZlGq+8lnkAtkTyYOeDWmabIIkUa fDd8cUfPBnqEVxXpYRV0cGPtXmSn51IwCB6tcyONTajyjrTXONQMUbQzlOSNOh4uxvcm JZXQ==
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=vcDKl/0u7OmrI+COR4zni8jASsEgz5AozbA4FXQQEnw=; b=SwY02LrLmWxozwAPa0gngAM8ETbs0s/NKqWTc/zRqtRLqlTcVvxR26PbgoeLBgT3yE rJCyZMtrXzRJY98xPsh1Cipv7Gf+sLrFZ59x48hvG8Y3eacW6sK9UGZsfh5VS5hpZh+j M94QWf5jO7xMq2+jARuKj5rD5Qbr41J68YOnPcG1tZHRtxQzYEW3yoVN2DqN50YTF4KV s8dYUhpNvnIS64Cfao7PIt7Q45ae8ZoWfr9OtlCpEHkKSSKAsoZQqVF1mLNtmHjQfdid TRwR/1v45QQ+FtzxyECezeIvfiznttAyS0S8IcdhiJEAZTQGB4ShjEmCslsJujloL+B/ dFJQ==
X-Gm-Message-State: AOAM530IrHhyCSguA3XJzmmoq3tSUVN/P2qoynmQ9i1Q+C3q1/fyy0oF T8twywsUaHokqDDHrhL0JAPBZacLcELwrgk/R5HpWIu4
X-Google-Smtp-Source: ABdhPJzg/7V/G1cHm+4VVE2DxBRYzTQgTm09YzY1tQIy6otH2nRw2SH+oBq+HxnleC3e9XzXw6Tmfh5F+s8fMyP4Ofg=
X-Received: by 2002:ad4:5047:: with SMTP id m7mr10192660qvq.26.1612641218096;  Sat, 06 Feb 2021 11:53:38 -0800 (PST)
MIME-Version: 1.0
References: <20210203181226.9AB746D51182@ary.qy> <e169f069-376d-7072-2538-c77bbe7b7540@tana.it> <b9c3487-44ed-a132-d42-47364fd819b4@taugh.com>
In-Reply-To: <b9c3487-44ed-a132-d42-47364fd819b4@taugh.com>
From: Dotzero <dotzero@gmail.com>
Date: Sat, 6 Feb 2021 14:53:27 -0500
Message-ID: <CAJ4XoYfUZXuPy6a+U=GnZ43um0Ruv5FMBQYHZqoK4tmmH+zUhw@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="000000000000f46f9905bab04a99"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/b037LC32e1wU8FC5ReiwmRnXxbU>
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, 06 Feb 2021 19:53:41 -0000

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

On Thu, Feb 4, 2021 at 11:43 AM John R Levine <johnl@taugh.com> wrote:

> I really do not see anything to change here, and we have a lot of other
> tickets to work on.  Please, can we stop and close this one?
>

+1 Could we have a show of consensus on closing this.

Mihael Hammer

--000000000000f46f9905bab04a99
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 Thu, Feb 4, 2021 at 11:43 AM John =
R Levine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</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">I really do =
not see anything to change here, and we have a lot of other <br>
tickets to work on.=C2=A0 Please, can we stop and close this one?<br></bloc=
kquote><div>=C2=A0</div><div>+1 Could we have a show of consensus on closin=
g this.</div><div><br></div><div>Mihael Hammer<br></div></div></div>

--000000000000f46f9905bab04a99--


From nobody Sat Feb  6 15:57:52 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 319433A2D80 for <dmarc@ietfa.amsl.com>; Sat,  6 Feb 2021 15:57: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, 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 ZyxQqScelXVR for <dmarc@ietfa.amsl.com>; Sat,  6 Feb 2021 15:57:49 -0800 (PST)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 C4E1D3A2D7F for <dmarc@ietf.org>; Sat,  6 Feb 2021 15:57:49 -0800 (PST)
Received: by mail-io1-xd2f.google.com with SMTP id n14so11286391iog.3 for <dmarc@ietf.org>; Sat, 06 Feb 2021 15:57:49 -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=YHM7aT6nhyxpDrVxCXdgKXPF77pCmC7vo6lsaqM/fZU=; b=YMxYplWyktykMVSH8vmPWgx87JzB3lYRT/vcJyfyk/lSkOErA5qR+9MSNymjzU3TZn Wa7wL2ZddOCJLAacf1sccaV+VuzLFexf033+xA9DgPGprXDKgfykZxa79AVXv39epvrs c+OLL4fdh0a0tw99lbGVbpZIO4Gp0q9ByHyDs=
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=YHM7aT6nhyxpDrVxCXdgKXPF77pCmC7vo6lsaqM/fZU=; b=f3qjSZhuhVmM1hBYyRrm96LY+9juzLUZZ8J07rVDbU64CWurRsiJLBPNblaNqIgEJU 8QuiBn9h/WWOcc+C+k2Nd267Ux1ZMcfqaPbyTX3nNB0D3GFn1W7MyUPstYZhJb60cvwR XYVUu9eCEZv2QWohR0KCaeRKDu675l996GmW0/EKIZ0/7d+Kxct3MICdwsZw9vodVFbr eLWQiJK1fXY0kmEvTCq8qE3y/QVujQaz7EEsVECalDaaRqIDEoe6Oc5KguVDStHedljc X/F1urMPSQnylevcqBboQI8EZCF43f0NPPQ5oBOjxS9EhwMcybogTLWGB2Ao7NXO5bRR vbwA==
X-Gm-Message-State: AOAM532FtOqrqL3NlHM0q0xHuYtNNUAQ/IOmvrlAtn+APGCUUFvyC2vH +Qli06M18ev0P7UccRCz8+n9UDS1AqEX2DYLOo+pJQ==
X-Google-Smtp-Source: ABdhPJw9v+eAa9PLhW4RYQhZjRFvjYm9UaTturj2Hi6g48WcdCv72ZOlRYMDIIt/U4MUpGQOMxR+aw25KsK1iOECz1Q=
X-Received: by 2002:a5d:9552:: with SMTP id a18mr10188599ios.154.1612655867763;  Sat, 06 Feb 2021 15:57:47 -0800 (PST)
MIME-Version: 1.0
References: <20210203181226.9AB746D51182@ary.qy> <e169f069-376d-7072-2538-c77bbe7b7540@tana.it> <b9c3487-44ed-a132-d42-47364fd819b4@taugh.com> <CAJ4XoYfUZXuPy6a+U=GnZ43um0Ruv5FMBQYHZqoK4tmmH+zUhw@mail.gmail.com>
In-Reply-To: <CAJ4XoYfUZXuPy6a+U=GnZ43um0Ruv5FMBQYHZqoK4tmmH+zUhw@mail.gmail.com>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Sat, 6 Feb 2021 15:57:30 -0800
Message-ID: <CABuGu1pkSqJtf+rz-pzRSEJ=C4C77c+qyLjgobMqR_Z2fmYRqw@mail.gmail.com>
To: Dotzero <dotzero@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000024b60505bab3b495"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/K-Zogd2EAXnQ6LKhzY29rw0NdjQ>
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, 06 Feb 2021 23:57:51 -0000

--00000000000024b60505bab3b495
Content-Type: text/plain; charset="UTF-8"

On Sat, Feb 6, 2021 at 11:53 AM Dotzero <dotzero@gmail.com> wrote:

>
> On Thu, Feb 4, 2021 at 11:43 AM John R Levine <johnl@taugh.com> wrote:
>
>> I really do not see anything to change here, and we have a lot of other
>> tickets to work on.  Please, can we stop and close this one?
>>
>
> +1 Could we have a show of consensus on closing this.
>

+1 - now, if only we had a real voting system :-P

--Kurt

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

<div dir=3D"ltr"><div dir=3D"ltr">On Sat, Feb 6, 2021 at 11:53 AM Dotzero &=
lt;<a href=3D"mailto:dotzero@gmail.com">dotzero@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"><br></div><div class=3D"gmail_=
quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Feb 4, 2021 at 11:43 A=
M John R Levine &lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_blank">jo=
hnl@taugh.com</a>&gt; wrote:<br></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">I really do not see anything to change here, and we have a lot=
 of other <br>
tickets to work on.=C2=A0 Please, can we stop and close this one?<br></bloc=
kquote><div>=C2=A0</div><div>+1 Could we have a show of consensus on closin=
g this.</div></div></div></blockquote><div><br></div><div>+1 - now, if only=
 we had a real voting system :-P</div><div><br></div><div>--Kurt=C2=A0</div=
></div></div>

--00000000000024b60505bab3b495--


From nobody Sat Feb  6 17:16:03 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 B13FE3A2DF5 for <dmarc@ietfa.amsl.com>; Sat,  6 Feb 2021 17:16:02 -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, FREEMAIL_FROM=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 MeQm_5XgLTHD for <dmarc@ietfa.amsl.com>; Sat,  6 Feb 2021 17:16:01 -0800 (PST)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 8CFAB3A2DF4 for <dmarc@ietf.org>; Sat,  6 Feb 2021 17:16:01 -0800 (PST)
Received: by mail-ot1-x32e.google.com with SMTP id 100so4138544otg.3 for <dmarc@ietf.org>; Sat, 06 Feb 2021 17:16:01 -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=cWu9aK+1N0WUjfSNzQCoBOjguxEhHXhIwSIl7B3JZ4c=; b=kMlb75W9MYYtsyDbQkz2Rr8GqILAdMYFi/uz7wQPOr+t71XIBRlGsYJp8FTrEGA2ZN 1ViI57K/LeJcUIC3qCWrlWdfuINm9TVJMERgY2QYmsSxdlKZdRbAkPlFTIwHh1EjQMNH l1E8c+5MhbJNTiuc34v8WbmBmOYIfv8echYFK9HA1d3QOGEi1Xrhf74wmIQ+6fj3sQLr LiW3+M+RKZ6SPxFGCJ/VxJnQVGWPirApndeJMjECqL16MgwkgmHG1iVFSAgNiKiMK4GN q6sh3+7VYJ2+aJaktDTcBnT7VCg+9GuJVXUocVgKpJ/SIemMv+y9x3HwuIH4fOJ0L5Nl vu5g==
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=cWu9aK+1N0WUjfSNzQCoBOjguxEhHXhIwSIl7B3JZ4c=; b=EsxAme4Rh/e6dgragbB9iza3ZKyn0bF1LMucTRLV43nErjUyJoCDAvuouCKln2kpHG 6oawb050kseHmuP1msNmYsdtafxTSKSUvzc8gneD3lKso4NCXfXK8HxyTd0OTN/8xYVT TpSb6bzaLUszN75UaUhq8JWxKVY4DoFq4Tta919z1Ktdfl6dx3Kh5yZSoosr1rVhbEdi bsyWiWCDmyq7YWjcFKFEAMNBGrxHcNfDVlEGSSViWJ/P8ePXlyRWAtJGIQbWtX9H6IwX e6cnC5zt+yG4oMWxzAXrx66Q/Op8LXxpPaIlxvn2C5O/LZqAOSxndgaRPxp760loS4Lg NnGQ==
X-Gm-Message-State: AOAM530ZkY1BwmwQL2KJI7s0i/vztT1jzJWv1pTVgiIquhkCY4U0NAv5 /OMh1sQp+VdaMiQ/l5JhowP95wqfqjn0eA==
X-Google-Smtp-Source: ABdhPJwfXTUO6RBXoWSeQH1t515EEPudZ/S0Fc106Aa8CaIgcoSF9vTP3GbmlX9672rcN2FVqtBLIw==
X-Received: by 2002:a9d:135:: with SMTP id 50mr8367305otu.267.1612660560626; Sat, 06 Feb 2021 17:16:00 -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 k15sm2835545otp.10.2021.02.06.17.15.59 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 06 Feb 2021 17:15:59 -0800 (PST)
To: IETF DMARC WG <dmarc@ietf.org>
References: <20210203181226.9AB746D51182@ary.qy> <e169f069-376d-7072-2538-c77bbe7b7540@tana.it> <b9c3487-44ed-a132-d42-47364fd819b4@taugh.com> <CAJ4XoYfUZXuPy6a+U=GnZ43um0Ruv5FMBQYHZqoK4tmmH+zUhw@mail.gmail.com> <CABuGu1pkSqJtf+rz-pzRSEJ=C4C77c+qyLjgobMqR_Z2fmYRqw@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <b730ab9c-aa5e-e80d-5cee-69cd6aee3a7b@gmail.com>
Date: Sat, 6 Feb 2021 17:15:58 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <CABuGu1pkSqJtf+rz-pzRSEJ=C4C77c+qyLjgobMqR_Z2fmYRqw@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/2yXikIuOPfcrVmfiuu0UWdrMPC8>
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, 07 Feb 2021 01:16:03 -0000

On 2/6/2021 3:57 PM, Kurt Andersen (b) wrote:
>
> +1 - now, if only we had a real voting system :-P

Yeah, 'cause this one is really close, and it's hard to tell what the 
decision is...


d/

ps.  +1

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Sun Feb  7 03:00: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 9B4F33AFBC9 for <dmarc@ietfa.amsl.com>; Sun,  7 Feb 2021 03:00:13 -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 JTpp9PUPkSIa for <dmarc@ietfa.amsl.com>; Sun,  7 Feb 2021 03:00:11 -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 2FBCF3AFBCE for <dmarc@ietf.org>; Sun,  7 Feb 2021 03:00:10 -0800 (PST)
Received: (qmail 58074 invoked by uid 100); 7 Feb 2021 11:00:09 -0000
Date: 7 Feb 2021 10:59:44 -0000
Message-ID: <20210207105944.58059.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/U4zrfWfX4Sc9RzeXvVRs_sw_xbw>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Feb 7 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, 07 Feb 2021 11:00:14 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
 15 (19.7%) |  96904 (18.2%) | Dave Crocker <dcrocker@gmail.com>
 15 (19.7%) |  79306 (14.9%) | Alessandro Vesely <vesely@tana.it>
 14 (18.4%) |  92783 (17.4%) | Michael Thomas <mike@mtcc.com>
 14 (18.4%) |  73447 (13.8%) | John Levine <johnl@taugh.com>
  6 ( 7.9%) |  75576 (14.2%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  3 ( 3.9%) |  23105 ( 4.3%) | Dotzero <dotzero@gmail.com>
  3 ( 3.9%) |  22486 ( 4.2%) | Scott Kitterman <sklist@kitterman.com>
  2 ( 2.6%) |  18960 ( 3.6%) | Hector Santos <hsantos@isdg.net>
  1 ( 1.3%) |  27068 ( 5.1%) | Brotman, Alex <alex_brotman@comcast.com>
  1 ( 1.3%) |  11416 ( 2.1%) | Seth Blank <seth@valimail.com>
  1 ( 1.3%) |   6040 ( 1.1%) | Kurt Andersen (b) <kboth@drkurt.com>
  1 ( 1.3%) |   5018 ( 0.9%) | Jim Fenton <fenton@bluepopcorn.net>


From nobody Sun Feb  7 04:34:49 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 F321F3A086E for <dmarc@ietfa.amsl.com>; Sun,  7 Feb 2021 04:34: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, 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 l5eBuKRha-ye for <dmarc@ietfa.amsl.com>; Sun,  7 Feb 2021 04:34:45 -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 64FC93A085E for <dmarc@ietf.org>; Sun,  7 Feb 2021 04:34:45 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id b10so6108704vsa.8 for <dmarc@ietf.org>; Sun, 07 Feb 2021 04:34: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;  bh=/gk2wIvcN4pb8ROBAsGYQ5ncmz1eEioSzPkq9GwvKFo=; b=XNR3XPxFTyHD64jdM+wchYarH+qxE7LdXYQUg+TJXt+/HatNTgo0AljXN0xkq1iytt Szzfg0+lSRzW8w4lYN1JIT5EqQ6gJn37L0quK3GacBGZ9lN45w3gVRBlnYChspe1yCJI TwSB5jDY6pEqqJfmiwBeGkhtSa7X6GbcVjQGFn0xchRpUG/Nj1FpCjc3N9KjPt9QPRtG 0WUnmO1qNLln6rS6TddhU7ilt32bxvQdiHrYHynwDimuKtxLfK8uIjfDZE3gU9lr9HGo jErndeSxKMtzlbfNsADuJ/uHmY3Y13WwNFlWKg8/OjJ35kzfIeyYbsE+Db1/cmpn2B1x SVFA==
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=/gk2wIvcN4pb8ROBAsGYQ5ncmz1eEioSzPkq9GwvKFo=; b=ldHjpl8uDqNY3eF032d3YJptSjovXCMoJfM68f2lE2ZoEq07sEqagjDRBiOQ6CSsJB E/w9QC8l0YDk5hYvscucoOjtVMMveoS7Zu69NQsE9CALAMo+FFSNnUVD2PYk/pB1OBOR HGmijOmpZGabwvR1aNauwBTm/fE8QvosZkqbOAnfMZazwEQS1VxC2ah8cJDU0OkC7FoX Db2vWz/g2xuBkgN4x8saGtptMby5rr2p/9c8JBHZ1Elc9XnUQyTEPxlYzyYvLVxaJxNC iVuEzOMMoYupsBBfud4U20BrmdIcdSUd4ny9OSfznbf0hJs/2h0dbrbA3pcFLM3Je32v e1DQ==
X-Gm-Message-State: AOAM532v6K1AdUetTtLocQ7yWkw50srtQ46WGKpbKvO0gT74aDOgyGZp awCg+a60w89NGk3HTLgBnwgs1FOaIPCea4QX14pMiMtDSw8=
X-Google-Smtp-Source: ABdhPJxH/nZF+F9JyhjGqrfInM7+9yjw2bT/YNbTGwPeKKlOsPVPkzEXFg2u8Qm5ZADFkLMk7ZZ5uOS2nv585fDISFg=
X-Received: by 2002:a67:87c2:: with SMTP id j185mr7933699vsd.25.1612701284300;  Sun, 07 Feb 2021 04:34:44 -0800 (PST)
MIME-Version: 1.0
References: <20210203181226.9AB746D51182@ary.qy> <e169f069-376d-7072-2538-c77bbe7b7540@tana.it> <b9c3487-44ed-a132-d42-47364fd819b4@taugh.com> <CAJ4XoYfUZXuPy6a+U=GnZ43um0Ruv5FMBQYHZqoK4tmmH+zUhw@mail.gmail.com> <CABuGu1pkSqJtf+rz-pzRSEJ=C4C77c+qyLjgobMqR_Z2fmYRqw@mail.gmail.com> <b730ab9c-aa5e-e80d-5cee-69cd6aee3a7b@gmail.com>
In-Reply-To: <b730ab9c-aa5e-e80d-5cee-69cd6aee3a7b@gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sun, 7 Feb 2021 07:34:33 -0500
Message-ID: <CAH48ZfxPG29hdqj4CN-HHdEk6uzOv_fG3nSB1KdmXWLSP7bHRA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002dfadb05babe47bb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/mGEBmCjw5aPflryACeviW5qEaZ0>
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, 07 Feb 2021 12:34:47 -0000

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

"We have a lot of other topics" is the wrong reason to call for consensus.
 The important question is "Ale, have we addressed your concerns?"

I agree with many that for DMARC, our primary interest is whether SPF
validation of MAILFROM produces a PASS.

However, I also see that a cautious recipient may choose to also require
SPF HELO = PASS and / or fcDNS HELO = PASS ( VERIFIED ).   Getting a PASS
on these multiple criteria increases the confidence in the PASS result, but
also increases the likelihood of ambiguous results and false rejects.
Therefore:
 - Recipients need to be cautious about enforcing rules so strictly that
sender configuration errors produce unwanted disposition decisions.
 - Senders need to be careful to ensure that they configure their policy to
produce both SPF MAILFROM = PASS and SPF HELO=PASS.

Altogether, I think some wordsmithing is needed to communicate those
points.   I do not have such wording at this moment, but will begin
thinking about what I would propose.   Perhaps those who are anxious to
move on will be able to produce text sooner.

I have also raised a concern about the inadequacy of reporting these
results, since "Recevied-SPF: pass" is currently a compliant header.   We
can defer this issue to a later ticket, but we need to be thinking about
the problem.   If this requires no change, I would like some discussion of
why that might be the case.

DF


On Sat, Feb 6, 2021 at 8:16 PM Dave Crocker <dcrocker@gmail.com> wrote:

> On 2/6/2021 3:57 PM, Kurt Andersen (b) wrote:
> >
> > +1 - now, if only we had a real voting system :-P
>
> Yeah, 'cause this one is really close, and it's hard to tell what the
> decision is...
>
>
> d/
>
> ps.  +1
>
> --
> 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
>

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

<div dir=3D"ltr">&quot;We have a lot of other topics&quot; is the wrong rea=
son to call for consensus.=C2=A0 =C2=A0The important question is &quot;Ale,=
 have we addressed your concerns?&quot;<div><br></div><div>I agree with man=
y that for DMARC, our primary interest is whether SPF validation of MAILFRO=
M produces a PASS.=C2=A0 =C2=A0</div><div><br></div><div>However, I also se=
e that a cautious recipient may choose to also require SPF HELO =3D PASS an=
d / or=C2=A0fcDNS=C2=A0HELO=C2=A0=3D PASS ( VERIFIED ).=C2=A0 =C2=A0Getting=
 a PASS on these multiple criteria increases the confidence in the PASS res=
ult, but also increases the likelihood of ambiguous results and false rejec=
ts.=C2=A0 Therefore:</div><div>=C2=A0- Recipients need to be cautious about=
 enforcing rules so strictly that sender configuration=C2=A0errors produce =
unwanted disposition decisions.=C2=A0 =C2=A0</div><div>=C2=A0- Senders need=
 to be careful=C2=A0to ensure that they configure their policy to produce b=
oth SPF MAILFROM =3D PASS and SPF HELO=3DPASS.=C2=A0 =C2=A0</div><div><br><=
/div><div>Altogether, I think some wordsmithing is needed to communicate th=
ose points.=C2=A0 =C2=A0I do not have such wording at this moment, but will=
 begin thinking about what I=C2=A0would propose.=C2=A0 =C2=A0Perhaps those =
who are anxious to move on will be able to produce text sooner.</div><div><=
br></div><div>I have also raised a concern about the inadequacy of reportin=
g these results, since &quot;Recevied-SPF: pass&quot; is currently a compli=
ant=C2=A0header.=C2=A0 =C2=A0We can defer this issue to a later ticket, but=
 we need to be thinking about the problem.=C2=A0 =C2=A0If this requires no =
change, I would like=C2=A0some discussion of why that might be the case.</d=
iv><div><br></div><div>DF</div><div>=C2=A0</div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Feb 6, 2021 at 8:16=
 PM Dave Crocker &lt;<a href=3D"mailto:dcrocker@gmail.com">dcrocker@gmail.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=
">On 2/6/2021 3:57 PM, Kurt Andersen (b) wrote:<br>
&gt;<br>
&gt; +1 - now, if only we had a real voting system :-P<br>
<br>
Yeah, &#39;cause this one is really close, and it&#39;s hard to tell what t=
he <br>
decision is...<br>
<br>
<br>
d/<br>
<br>
ps.=C2=A0 +1<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>
_______________________________________________<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>

--0000000000002dfadb05babe47bb--


From nobody Mon Feb  8 06:50: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 DB7FD3A1645 for <dmarc@ietfa.amsl.com>; Mon,  8 Feb 2021 06:50: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 12YP0QlQU-8o for <dmarc@ietfa.amsl.com>; Mon,  8 Feb 2021 06:50:27 -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 962B33A1744 for <dmarc@ietf.org>; Mon,  8 Feb 2021 06:50:27 -0800 (PST)
Received: by mail-qk1-x729.google.com with SMTP id v206so2914690qkb.3 for <dmarc@ietf.org>; Mon, 08 Feb 2021 06:50:27 -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=81I2zVEyN5rzk+TTesFdUiCHpB5HBD9K0WOYNFqUbFQ=; b=gV/5IRQ+T4Zx2BX/sPXLtIOFJIsigagqSGK59pFQVb6oe1/rVc1tPP4PaB+GIlm8cZ lciu1rOhHp4IUQxFbZ6T3vDFGXaGnppA0BwsEASJyvJhSzBuCkmfOQTMREQ71BHhaktp xRrVKoJb3+mWSonh4bCnegFYHh8x4JNUQM++eNPOkynA7U3+OjE3rQL3zRAV1tl7EIz0 Me1dzPqn93J42A/G+QRWZPSkCjAHJwiXvplSyC6R344VokfLSvSOFbadPM2rF5bUixkL VvAnYanVu6kS0VeHmg/8QVqVBz17zEX5RMh4rrBGutJK5X2VUzOR/NmRDn/iiA2IkUT8 sUtQ==
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=81I2zVEyN5rzk+TTesFdUiCHpB5HBD9K0WOYNFqUbFQ=; b=nIWZC2N2Dh3pnXfcZNOWqrp+XiyQx7GBWwubIAs3xT8JKmowL41W6otE4I9miBiAje QcBv45ri802GCiPF+fL2CPJtbykzc3sJQfYANMfflSmtNEljtpH9it0z8+YaEow+n7wP /OrS/dvy4iz7dmTbhNmi6d1giAThxQpqpSqX1J5FKCs3+e+Mq9y6WFojMpHW0Vn8Q40w EoPrKivCFLC8yaJ3Lkv1HEPaKE5L1KPutQaZFt2waBTJ9w9u+AzEQCxKoeSWuDtfskx0 NhVSJTNyTiqBNE15JI18dzNHjShgn7zYZTtMtEVb0J7WKagRKsyTtAy4AK11vMXdUZF+ Gwow==
X-Gm-Message-State: AOAM530i1EfrpCeXVLtnc/d4jjthWjBV8qrzDr9O4wcYWXhw5hFwPpwO eR/VozbfNdRvhQIvAVn3JpNdCdvGQyZCvZ9blrcI6eqEnMnCvw==
X-Google-Smtp-Source: ABdhPJz3FfhPZmoiVOE96Yc5P++tezGQCrfBp67vo2Vkyn6EOM5gruTHcluC9M9zo+4NY6B2H5yp+pvCH1WEr/87YY0=
X-Received: by 2002:a05:620a:210e:: with SMTP id l14mr17918653qkl.387.1612795825837;  Mon, 08 Feb 2021 06:50:25 -0800 (PST)
MIME-Version: 1.0
References: <20210203181226.9AB746D51182@ary.qy> <e169f069-376d-7072-2538-c77bbe7b7540@tana.it> <b9c3487-44ed-a132-d42-47364fd819b4@taugh.com> <CAJ4XoYfUZXuPy6a+U=GnZ43um0Ruv5FMBQYHZqoK4tmmH+zUhw@mail.gmail.com> <CABuGu1pkSqJtf+rz-pzRSEJ=C4C77c+qyLjgobMqR_Z2fmYRqw@mail.gmail.com> <b730ab9c-aa5e-e80d-5cee-69cd6aee3a7b@gmail.com> <CAH48ZfxPG29hdqj4CN-HHdEk6uzOv_fG3nSB1KdmXWLSP7bHRA@mail.gmail.com>
In-Reply-To: <CAH48ZfxPG29hdqj4CN-HHdEk6uzOv_fG3nSB1KdmXWLSP7bHRA@mail.gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Mon, 8 Feb 2021 09:50:09 -0500
Message-ID: <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004b723f05bad44ac3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/hoV-e1QSG-UH27QOrOjd6zU3p_Y>
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, 08 Feb 2021 14:50:30 -0000

--0000000000004b723f05bad44ac3
Content-Type: text/plain; charset="UTF-8"

On Sun, Feb 7, 2021 at 7:35 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> "We have a lot of other topics" is the wrong reason to call for
> consensus.   The important question is "Ale, have we addressed your
> concerns?"
>
> I agree with many that for DMARC, our primary interest is whether SPF
> validation of MAILFROM produces a PASS.
>

That's only partially correct. For DMARC, the SPF validation of MAILFROM
must produce a PASS and the identifier must align with the RFC5322.From
header domain. Absent both the PASS verdict and the alignment, the
<policy_evaluated> section of the aggregate report will show "fail" for
SPF, even if the <results> bit of the <auth_results> section shows "pass"
in the <spf> sub-section.


> However, I also see that a cautious recipient may choose to also require
> SPF HELO = PASS and / or fcDNS HELO = PASS ( VERIFIED ).   Getting a PASS
> on these multiple criteria increases the confidence in the PASS result, but
> also increases the likelihood of ambiguous results and false rejects.
> Therefore:
>  - Recipients need to be cautious about enforcing rules so strictly that
> sender configuration errors produce unwanted disposition decisions.
>  - Senders need to be careful to ensure that they configure their policy
> to produce both SPF MAILFROM = PASS and SPF HELO=PASS.
>

The likelihood of a HELO identifier both passing an SPF check and aligning
with the RFC5322.From identifier is, I would venture, so small as to be
immeasurable for shared services such as ESPs, mailing list servers, and
the like. Perhaps they could eventually be convinced of a need to publish
SPF records, but that wouldn't do much of anything to change the
<policy_evaluated> results for DMARC. Getting an SPF pass verdict alone for
these identifiers isn't enough to alter the DMARC validation results; the
identifiers must align, too. From a practical standpoint, I don't believe
SPF MAILFROM=pass/SPF EHLO=fail would be useful information to mailbox
providers for the significant volume of mail routing to their customers
from shared services; I get quite a lot of such mail to my Gmail mailbox
each day, wanted mail that is correctly routed to my Inbox.

Beyond all that, though, SPF can fail for both the MAILFROM and the EHLO
identifier on any given message, but if the message is DKIM signed in a way
that aligns with the RFC5322.From domain and the DKIM validation check
passes, then the message will correctly be described as having gotten a
DMARC pass verdict. We've spent quite a lot of time on this list discussing
authentication checks that can, by themselves, result in a DMARC pass
verdict, but that cannot, by themselves, result in a DMARC fail verdict. A
message has to fail SPF validation/alignment checks and DKIM
validation/alignment checks in order to fail DMARC. I am not suggesting
that the DMARC spec be updated to require that both SPF and DKIM both pass
and align in order for DMARC to pass, because while I believe it to be best
practice for senders to align both SPF and DKIM identifiers, I believe it
would cause too much breakage in existing running code and sender
configurations to be worth it to mandate such things.


> Altogether, I think some wordsmithing is needed to communicate those
> points.   I do not have such wording at this moment, but will begin
> thinking about what I would propose.   Perhaps those who are anxious to
> move on will be able to produce text sooner.
>
> I have also raised a concern about the inadequacy of reporting these
> results, since "Recevied-SPF: pass" is currently a compliant header.   We
> can defer this issue to a later ticket, but we need to be thinking about
> the problem.   If this requires no change, I would like some discussion of
> why that might be the case.
>
>
>
What the message recipient does with all this authentication information is
left as a local policy decision, a decision that is likely to be made using
more data points than just the SPF, DKIM, and DMARC validation verdicts.
The DMARC spec does not mandate that a message passing DMARC checks be
accepted, nor does it mandate that a message failing DMARC checks be
rejected, even in the relevant policy published by the domain owner is
"p=reject", and I am absolutely not suggesting that the DMARC spec be
written in such a way as to mandate such behaviors. In my opinion, the text
that should appear in the DMARC spec to sum up these points is "A DMARC
pass verdict means only that the message can be reliably associated by the
recipient with the identity on which the DMARC validation check was
performed, and a DMARC fail verdict means that it cannot be so associated."

-- 

*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.

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

<div dir=3D"ltr"><div dir=3D"ltr">On Sun, Feb 7, 2021 at 7:35 AM Douglas Fo=
ster &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;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">&quot;W=
e have a lot of other topics&quot; is the wrong reason to call for consensu=
s.=C2=A0 =C2=A0The important question is &quot;Ale, have we addressed your =
concerns?&quot;<div><br></div><div>I agree with many that for DMARC, our pr=
imary interest is whether SPF validation of MAILFROM produces a PASS.=C2=A0=
 =C2=A0</div></div></blockquote><div><br></div><div>That&#39;s only partial=
ly correct. For DMARC, the SPF validation of MAILFROM must produce a PASS a=
nd the identifier must align with the RFC5322.From header domain. Absent bo=
th the PASS verdict and the alignment, the &lt;policy_evaluated&gt; section=
 of the aggregate report will show &quot;fail&quot; for SPF, even if the &l=
t;results&gt; bit of the &lt;auth_results&gt; section shows &quot;pass&quot=
; in the &lt;spf&gt; sub-section.</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><br></div><div>However, =
I also see that a cautious recipient may choose to also require SPF HELO =
=3D PASS and / or=C2=A0fcDNS=C2=A0HELO=C2=A0=3D PASS ( VERIFIED ).=C2=A0 =
=C2=A0Getting a PASS on these multiple criteria increases the confidence in=
 the PASS result, but also increases the likelihood of ambiguous results an=
d false rejects.=C2=A0 Therefore:</div><div>=C2=A0- Recipients need to be c=
autious about enforcing rules so strictly that sender configuration=C2=A0er=
rors produce unwanted disposition decisions.=C2=A0 =C2=A0</div><div>=C2=A0-=
 Senders need to be careful=C2=A0to ensure that they configure their policy=
 to produce both SPF MAILFROM =3D PASS and SPF HELO=3DPASS.=C2=A0 =C2=A0</d=
iv></div></blockquote><div><br></div><div>The likelihood of a HELO identifi=
er both passing an SPF check and aligning with the RFC5322.From identifier =
is, I would venture, so small as to be immeasurable for shared services suc=
h as ESPs, mailing list servers, and the like. Perhaps they could eventuall=
y be convinced of a need to publish SPF records, but that wouldn&#39;t do m=
uch of anything to change the &lt;policy_evaluated&gt; results for DMARC. G=
etting an SPF pass verdict alone for these identifiers isn&#39;t enough to =
alter the DMARC validation results; the identifiers must align,=C2=A0too. F=
rom a practical standpoint, I don&#39;t believe SPF MAILFROM=3Dpass/SPF EHL=
O=3Dfail would be useful information to mailbox providers for the significa=
nt volume of mail routing to their customers from shared services; I get qu=
ite a lot of such mail to my Gmail mailbox each day, wanted mail that is co=
rrectly routed to my Inbox.</div><div><br></div><div>Beyond all that, thoug=
h, SPF can fail for both the MAILFROM and the EHLO identifier on any given =
message, but if the message is DKIM signed in a way that aligns with the RF=
C5322.From domain and the DKIM validation check passes, then the message wi=
ll correctly be described as having gotten a DMARC pass verdict. We&#39;ve =
spent quite a lot of time on this list discussing authentication checks tha=
t can, by themselves, result in a DMARC pass verdict, but that cannot, by t=
hemselves, result in a DMARC fail verdict. A message has to fail SPF valida=
tion/alignment checks and DKIM validation/alignment checks in order to fail=
 DMARC. I am not suggesting that the DMARC spec be updated to require that =
both SPF and DKIM both pass and align in order for DMARC to pass, because w=
hile I believe it to be best practice for senders to align both SPF and DKI=
M identifiers, I believe it would cause too much breakage in existing runni=
ng code and sender configurations to be worth it to mandate such things.</d=
iv><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 di=
r=3D"ltr"><div><br></div><div>Altogether, I think some wordsmithing is need=
ed to communicate those points.=C2=A0 =C2=A0I do not have such wording at t=
his moment, but will begin thinking about what I=C2=A0would propose.=C2=A0 =
=C2=A0Perhaps those who are anxious to move on will be able to produce text=
 sooner.</div><div><br></div><div>I have also raised a concern about the in=
adequacy of reporting these results, since &quot;Recevied-SPF: pass&quot; i=
s currently a compliant=C2=A0header.=C2=A0 =C2=A0We can defer this issue to=
 a later ticket, but we need to be thinking about the problem.=C2=A0 =C2=A0=
If this requires no change, I would like=C2=A0some discussion of why that m=
ight be the case.</div><div><br></div><div><br></div></div></blockquote><di=
v><br></div><div>What the message recipient does with all this authenticati=
on information is left as a local policy decision, a decision that is likel=
y to be made using more data points than just the SPF, DKIM, and DMARC vali=
dation verdicts. The DMARC spec does not mandate that a message passing DMA=
RC checks be accepted, nor does it mandate that a message failing DMARC che=
cks be rejected, even in the relevant policy published by the domain owner =
is &quot;p=3Dreject&quot;, and I am absolutely not suggesting that the DMAR=
C spec be written in such a way as to mandate such behaviors. In my opinion=
, the text that should appear in the DMARC spec to sum up these points is &=
quot;A DMARC pass verdict means only that the message can be reliably assoc=
iated by the recipient with the identity on which the DMARC validation chec=
k was performed, and a DMARC fail verdict means that it cannot be so associ=
ated.&quot;<br></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-space:pre-wrap;font-size:small;font-famil=
y:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baseline;whit=
e-space:pre-wrap;font-size:small;font-family:Arial"> | Sr. Technical Progra=
m Manager</span></div><span style=3D"vertical-align:baseline;white-space:pr=
e-wrap;font-size:small;font-family:Arial"><div style=3D"text-align:left"><s=
pan style=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"vertic=
al-align:baseline"> <a href=3D"mailto:todd.herr@valimail.com" target=3D"_bl=
ank">todd.herr@valimail.com</a></span></div></span><span><div><span><b>p:</=
b></span><span> 703.220.4153 </span><span></span></div><div style=3D"text-a=
lign:left"><span style=3D"vertical-align:baseline"><br></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"><img src=3D"https://valimail-logos.s3.ama=
zonaws.com/Valimail__Tag_DarkBlue_TM.png" style=3D"height: 35px; width: 159=
px;">`</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 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 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></div>

--0000000000004b723f05bad44ac3--


From nobody Tue Feb  9 17:28:09 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 D9A8C3A1142 for <dmarc@ietfa.amsl.com>; Tue,  9 Feb 2021 17:28:08 -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.249, 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=MIlHfNM6; dkim=pass (2048-bit key) header.d=taugh.com header.b=M7iDpPRD
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OSKIqvY9bAsn for <dmarc@ietfa.amsl.com>; Tue,  9 Feb 2021 17:28: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 B99363A1141 for <dmarc@ietf.org>; Tue,  9 Feb 2021 17:28:06 -0800 (PST)
Received: (qmail 4198 invoked from network); 10 Feb 2021 01:28: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=1063.602336a5.k2102; bh=G2McoNJNBXzGxtUxhAHDnK/VT3u3awRkVA+AYU+4LC0=; b=MIlHfNM6KmTURcYNJ25GjJ7KidhvQnKpDyzNzuwHJqrha4nQizQTXEDi+XZ7hOY/ZF9I2L6vrpc3pXjcYjxDQkmy3hmVlnJhrInyvGA1VMlQRvcYHQAItCl+acP6YCE/Y1Wd95d1/oF1UPxO7dueEPF66mqquNjoXFLN7t5CuJ7lEXD/i+rPhBfMFyNtlHEAU4foUAj7YDhyUoD6ZpQf+M8Xh6HLThYeR4PtEB9FsdwwjOHg9A7vxNA5zWVkwNZkqG5xvqU2ZnuzmvN5vHN8E/xndjOck8Ny1qQUnmI1ln9kBAyAkNewueHd20gN7IWF1iYknRNN4qOzwoCiNq4WtQ==
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=1063.602336a5.k2102; bh=G2McoNJNBXzGxtUxhAHDnK/VT3u3awRkVA+AYU+4LC0=; b=M7iDpPRDkh/1zHqLHZ7ET3GjR1duZQQea4MUMrNPFdXh24k/KXiaWR2KyeT8yVEDpshSfOu7J4XHYlJgzUMdfoi92hAnPbjFkwYUGLizGJHSy/cPthT/pWm7/Y+iSmWnXrmhEqP4jRprm2/m9URPqDDQ00bdflQ9lKzCZZXSlqz3FLnaK+h69A1eMtGBD/9070DPK2a6gJtERlH6SmfdBw57PuuJ6X3jmOzH+nuhPFhI4deOoAxPEAqq7Zj2c1yx3QrmJb91KrCvRAxh2sth6xhxX3FITjVOwTspF0tj2UhsFBcpn/OvD4trvV3kpLtTlNYuajynpGa7O35E9FrQcA==
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; 10 Feb 2021 01:28:05 -0000
Received: by ary.qy (Postfix, from userid 501) id B47F96DAC4C6; Tue,  9 Feb 2021 20:28:04 -0500 (EST)
Date: 9 Feb 2021 20:28:04 -0500
Message-Id: <20210210012804.B47F96DAC4C6@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: todd.herr@valimail.com
In-Reply-To: <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@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/xoPtktORM7KLmYfRIkhs_BH_OTg>
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, 10 Feb 2021 01:28:09 -0000

In article <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com> you write:
>
>The likelihood of a HELO identifier both passing an SPF check and aligning
>with the RFC5322.From identifier is, I would venture, so small as to be
>immeasurable for shared services such as ESPs, mailing list servers, and
>the like. ...

Agreed.  You can do it on your hobby linux box but not at any sort of scale.

Once again, there is nothing to fix here.  Can we close this now?

R's,
John


From nobody Tue Feb  9 19:13: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 815CD3A1289 for <dmarc@ietfa.amsl.com>; Tue,  9 Feb 2021 19:13: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=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 7NZIUFb9auds for <dmarc@ietfa.amsl.com>; Tue,  9 Feb 2021 19:13:50 -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 EB5943A1285 for <dmarc@ietf.org>; Tue,  9 Feb 2021 19:13:49 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id y123so373545vsy.13 for <dmarc@ietf.org>; Tue, 09 Feb 2021 19:13: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=NMnbhwmhOYiIaMZjsnA1CKSZ8sqy3009faqahV3KDk0=; b=m66idfgCN+k1tVWj4MLcoVdunyB3IEjWE10d/5Qi6lylUaWelPrIAA5q0tnIOsE+Bo d9JMUyJgGunozxfrpHeRNDG4MG5vJuaTzbcg/0TDFYOHEHVc/oClmHveMB3VKw+ev/k7 sv1Qd6igbewWAcA8FtXM/P0+Lh+uT4AdsNP4D0BcYkDhNJY6E9uz5TIecoR5v8wJfijb 5CGhkD1o+J2/BruETKh455iRffNqx48TY10AkSidceBqkRg3lVkP1G0v2lUyPkCpk8hT AR5hHgDOrdGXocMJ/U1VUYpGF5fGpfL/BI3rROZcTaVKdHxxZ7uYySW31ZH6w4dgmo86 4MNQ==
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=NMnbhwmhOYiIaMZjsnA1CKSZ8sqy3009faqahV3KDk0=; b=KNjQMaWLsvq9m0wJg/RjCPLdtf6Pu2ZEaZFOzZ6ZhkzOTttkT3IKgVG+mciHZ8T4kq H55ixRCiOs/ZbSaXiPiBYJSc00yZq5WYMthhkCZiQ/bb9O1dXPEM8cbkoGvI2/GIt2w1 VM9i+YUXvx5V727H6KPfAi4bPNLoZCxaBIul/pkwyZsnw75lO5YMg378lMmqFe+4B7Gi CwvQpm83G9PjRvqCYJxYUOvUPT9opEP0AXlDt40XEkvXUQHPJSKY4UJhQZtBQ/kGTWW1 U5B64YqYzolsx0xc7kA1D4KBsSrfXtbflbX0K7QDuNoiw1GDfsA6VLh7n9ELMZrDsyse HKZA==
X-Gm-Message-State: AOAM531Skn/l38v/SXooOn9HPHA2Ll9Psq8NojZ4KeO0cnJfZ3TdTVhu gD2+sJ28U6ocWaO9TrJOA4e8iqXltucEcsaVbQ50BW/IArlVTA==
X-Google-Smtp-Source: ABdhPJwZC4wpETP3f633AdCfyrlcqwzXLFSHEBplQ8n/fYgv3+RGzcX9PbXjILEsTsTDLXpaMzdX7lcmLE3Rngvq3wA=
X-Received: by 2002:a67:87c2:: with SMTP id j185mr734912vsd.25.1612926828807;  Tue, 09 Feb 2021 19:13:48 -0800 (PST)
MIME-Version: 1.0
References: <20210203181226.9AB746D51182@ary.qy> <e169f069-376d-7072-2538-c77bbe7b7540@tana.it> <b9c3487-44ed-a132-d42-47364fd819b4@taugh.com> <CAJ4XoYfUZXuPy6a+U=GnZ43um0Ruv5FMBQYHZqoK4tmmH+zUhw@mail.gmail.com> <CABuGu1pkSqJtf+rz-pzRSEJ=C4C77c+qyLjgobMqR_Z2fmYRqw@mail.gmail.com> <b730ab9c-aa5e-e80d-5cee-69cd6aee3a7b@gmail.com> <CAH48ZfxPG29hdqj4CN-HHdEk6uzOv_fG3nSB1KdmXWLSP7bHRA@mail.gmail.com> <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com>
In-Reply-To: <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 9 Feb 2021 22:13:37 -0500
Message-ID: <CAH48ZfxFsQ5ntE05QYRqP5P3Na6vuDjNAQKAdjZe7Kvt7evKuw@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="000000000000ae09a105baf2ca95"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4CBYFUiphPPTqc0MR5NeNbdFI4E>
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, 10 Feb 2021 03:13:53 -0000

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

The chairs can introduce another topic whenever they want.   This does not
seem like a pre-requisite to any of the other pending topics.

My interest is interoperability:    We want recipient requirements and
sender compliance measures to align.

RFC 7208 says that recipients MAY want to use SPF HELO and SPF MAILFROM
together.  An argument can be made that this is not necessary:   SPF
MAILFROM shows that the server is authorized to send messages for the
specific domain in the MAILFROM, while SPF HELO says only that the server
is authorized to send message for the server domain and an unknowable set
of other domains.  Therefore a PASS from SPF MAILFROM should make SPF HELO
unnecessary and redundant.    Does either the DMARC document or the SPF
document say this anywhere?

RFC 7208 can be misunderstood to suggest that SPF MAILFROM and SPF HELO are
equivalent and interchangeable, which they are not, for the reason just
mentioned.   Shouldn't we also make this clear?

Senders are motivated to ensure that their mail is delivered, which makes
them interested in all of the factors which can maximize delivery and
minimize rejection.    SPF HELO might be one of those reasons.   Do we
mention this as an additional measure that senders might want to consider,
or do we keep silent?

Todd's assertion is that SPF HELO will cause an excessive number of false
positives.   I share Todd's expectation that this will be true, but I have
no data on that point yet.  I am just beginning to collect that data,
because it seems like an interesting question.

A second assumption is that no significant recipients are evaluating SPF
MAILFROM and SPF HELO together in a way that would be of interest to
senders. This may also be true, but I don't think this is something that
can be tested.

A third assumption is that the current behavior related to SPF HELO will
continue indefinitely.

To maximize interoperability:
- Recipients can be encouraged to ignore SPF HELO as unnecessary and the
likely source of false positives.
- Senders can be encouraged to ensure SPF HELO compliance to prevent false
positives.

That interoperability outcome seems worth some comment in our final
document, since it created the confusion that led to ticket #1.

The original question and these comments are exclusively about the SPF side
of the DMARC evaluation, which presumes that the DKIM signature is missing
or invalid.   I was neither proposing a new block algorithm nor proposing a
new allow algorithm.  But I do think that we need to anticipate how people
are likely to use our documents, with the goal of minimizing incompatible
interpretations.   Ale's question demonstrates that such interpretation
problems are possible, even on a small and well-informed sample set.

DF

DF

On Mon, Feb 8, 2021 at 9:50 AM Todd Herr <todd.herr=
40valimail.com@dmarc.ietf.org> wrote:

> On Sun, Feb 7, 2021 at 7:35 AM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> "We have a lot of other topics" is the wrong reason to call for
>> consensus.   The important question is "Ale, have we addressed your
>> concerns?"
>>
>> I agree with many that for DMARC, our primary interest is whether SPF
>> validation of MAILFROM produces a PASS.
>>
>
> That's only partially correct. For DMARC, the SPF validation of MAILFROM
> must produce a PASS and the identifier must align with the RFC5322.From
> header domain. Absent both the PASS verdict and the alignment, the
> <policy_evaluated> section of the aggregate report will show "fail" for
> SPF, even if the <results> bit of the <auth_results> section shows "pass"
> in the <spf> sub-section.
>
>
>> However, I also see that a cautious recipient may choose to also require
>> SPF HELO = PASS and / or fcDNS HELO = PASS ( VERIFIED ).   Getting a PASS
>> on these multiple criteria increases the confidence in the PASS result, but
>> also increases the likelihood of ambiguous results and false rejects.
>> Therefore:
>>  - Recipients need to be cautious about enforcing rules so strictly that
>> sender configuration errors produce unwanted disposition decisions.
>>  - Senders need to be careful to ensure that they configure their policy
>> to produce both SPF MAILFROM = PASS and SPF HELO=PASS.
>>
>
> The likelihood of a HELO identifier both passing an SPF check and aligning
> with the RFC5322.From identifier is, I would venture, so small as to be
> immeasurable for shared services such as ESPs, mailing list servers, and
> the like. Perhaps they could eventually be convinced of a need to publish
> SPF records, but that wouldn't do much of anything to change the
> <policy_evaluated> results for DMARC. Getting an SPF pass verdict alone for
> these identifiers isn't enough to alter the DMARC validation results; the
> identifiers must align, too. From a practical standpoint, I don't believe
> SPF MAILFROM=pass/SPF EHLO=fail would be useful information to mailbox
> providers for the significant volume of mail routing to their customers
> from shared services; I get quite a lot of such mail to my Gmail mailbox
> each day, wanted mail that is correctly routed to my Inbox.
>
> Beyond all that, though, SPF can fail for both the MAILFROM and the EHLO
> identifier on any given message, but if the message is DKIM signed in a way
> that aligns with the RFC5322.From domain and the DKIM validation check
> passes, then the message will correctly be described as having gotten a
> DMARC pass verdict. We've spent quite a lot of time on this list discussing
> authentication checks that can, by themselves, result in a DMARC pass
> verdict, but that cannot, by themselves, result in a DMARC fail verdict. A
> message has to fail SPF validation/alignment checks and DKIM
> validation/alignment checks in order to fail DMARC. I am not suggesting
> that the DMARC spec be updated to require that both SPF and DKIM both pass
> and align in order for DMARC to pass, because while I believe it to be best
> practice for senders to align both SPF and DKIM identifiers, I believe it
> would cause too much breakage in existing running code and sender
> configurations to be worth it to mandate such things.
>
>
>> Altogether, I think some wordsmithing is needed to communicate those
>> points.   I do not have such wording at this moment, but will begin
>> thinking about what I would propose.   Perhaps those who are anxious to
>> move on will be able to produce text sooner.
>>
>> I have also raised a concern about the inadequacy of reporting these
>> results, since "Recevied-SPF: pass" is currently a compliant header.   We
>> can defer this issue to a later ticket, but we need to be thinking about
>> the problem.   If this requires no change, I would like some discussion of
>> why that might be the case.
>>
>>
>>
> What the message recipient does with all this authentication information
> is left as a local policy decision, a decision that is likely to be made
> using more data points than just the SPF, DKIM, and DMARC validation
> verdicts. The DMARC spec does not mandate that a message passing DMARC
> checks be accepted, nor does it mandate that a message failing DMARC checks
> be rejected, even in the relevant policy published by the domain owner is
> "p=reject", and I am absolutely not suggesting that the DMARC spec be
> written in such a way as to mandate such behaviors. In my opinion, the text
> that should appear in the DMARC spec to sum up these points is "A DMARC
> pass verdict means only that the message can be reliably associated by the
> recipient with the identity on which the DMARC validation check was
> performed, and a DMARC fail verdict means that it cannot be so associated."
>
> --
>
> *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
>

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

<div dir=3D"ltr">The chairs can introduce another topic whenever they want.=
=C2=A0 =C2=A0This does not seem like a pre-requisite to any of the other pe=
nding topics.<div><br></div><div>My interest is interoperability:=C2=A0 =C2=
=A0 We want recipient requirements and sender compliance measures to align.=
</div><div><br></div><div>RFC 7208 says that recipients MAY want to use SPF=
 HELO and SPF MAILFROM together.=C2=A0 An argument can be made that this is=
 not necessary:=C2=A0 =C2=A0SPF MAILFROM shows that the server is authorize=
d to send messages for the specific domain in the MAILFROM, while SPF HELO =
says only that the server is authorized to send message for the server doma=
in and an unknowable set of other domains.=C2=A0 Therefore a PASS from SPF =
MAILFROM should make SPF HELO unnecessary and redundant.=C2=A0 =C2=A0 Does =
either the DMARC document or the SPF document say this anywhere?</div><div>=
<br></div><div>RFC 7208 can be misunderstood to suggest that SPF MAILFROM a=
nd SPF HELO are equivalent and interchangeable, which they are not, for the=
 reason just mentioned.=C2=A0 =C2=A0Shouldn&#39;t we also make this clear?<=
/div><div><br></div><div>Senders are motivated to ensure that their mail is=
 delivered,=C2=A0which makes them interested in all of the=C2=A0factors whi=
ch can maximize delivery and minimize rejection.=C2=A0 =C2=A0 SPF HELO migh=
t be one of those reasons.=C2=A0 =C2=A0Do we mention this as an additional =
measure that senders might=C2=A0want to consider, or do we keep silent?</di=
v><div><br></div><div>Todd&#39;s assertion is that SPF HELO will cause an e=
xcessive number of false positives.=C2=A0 =C2=A0I share Todd&#39;s expectat=
ion that this will be true, but I have no data on that point yet.=C2=A0 I a=
m just beginning to collect that data, because it seems like an interesting=
 question.</div><div><br></div><div>A second assumption is that no signific=
ant recipients are evaluating SPF MAILFROM and SPF HELO together in a way t=
hat would be of interest to senders. This may also be true, but I don&#39;t=
 think this is something that can be tested.</div><div><br></div><div>A thi=
rd assumption is that the current behavior related to SPF HELO will continu=
e indefinitely.</div><div><br></div><div>To maximize interoperability:<br><=
/div><div>- Recipients can be encouraged to ignore SPF HELO as unnecessary =
and the likely source of false positives.</div><div>- Senders can be encour=
aged to ensure SPF HELO compliance to prevent false positives.</div><div><b=
r></div><div>That interoperability outcome seems worth some comment in our =
final document, since it created the confusion that led to ticket #1.</div>=
<div><br></div><div>The original question and these comments are exclusivel=
y about the SPF side of the DMARC evaluation, which presumes that the DKIM =
signature is missing or invalid.=C2=A0 =C2=A0I was neither proposing a new =
block algorithm nor proposing a new allow algorithm.=C2=A0 But I do think t=
hat we need to anticipate how people are likely to use our documents, with =
the goal of minimizing incompatible interpretations.=C2=A0 =C2=A0Ale&#39;s =
question demonstrates that such interpretation problems are possible, even =
on a small and well-informed sample set.</div><div><br></div><div>DF=C2=A0=
=C2=A0</div><div>=C2=A0=C2=A0<br></div><div>DF</div></div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Feb 8, 2021 at =
9:50 AM Todd Herr &lt;todd.herr=3D<a href=3D"mailto:40valimail.com@dmarc.ie=
tf.org">40valimail.com@dmarc.ietf.org</a>&gt; wrote:<br></div><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 dir=3D"ltr">On S=
un, Feb 7, 2021 at 7:35 AM Douglas Foster &lt;<a href=3D"mailto:dougfoster.=
emailstandards@gmail.com" target=3D"_blank">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;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr">&quot;We have a lot of ot=
her topics&quot; is the wrong reason to call for consensus.=C2=A0 =C2=A0The=
 important question is &quot;Ale, have we addressed your concerns?&quot;<di=
v><br></div><div>I agree with many that for DMARC, our primary interest is =
whether SPF validation of MAILFROM produces a PASS.=C2=A0 =C2=A0</div></div=
></blockquote><div><br></div><div>That&#39;s only partially correct. For DM=
ARC, the SPF validation of MAILFROM must produce a PASS and the identifier =
must align with the RFC5322.From header domain. Absent both the PASS verdic=
t and the alignment, the &lt;policy_evaluated&gt; section of the aggregate =
report will show &quot;fail&quot; for SPF, even if the &lt;results&gt; bit =
of the &lt;auth_results&gt; section shows &quot;pass&quot; in the &lt;spf&g=
t; sub-section.</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 dir=3D"ltr"><div><br></div><div>However, I also see that a =
cautious recipient may choose to also require SPF HELO =3D PASS and / or=C2=
=A0fcDNS=C2=A0HELO=C2=A0=3D PASS ( VERIFIED ).=C2=A0 =C2=A0Getting a PASS o=
n these multiple criteria increases the confidence in the PASS result, but =
also increases the likelihood of ambiguous results and false rejects.=C2=A0=
 Therefore:</div><div>=C2=A0- Recipients need to be cautious about enforcin=
g rules so strictly that sender configuration=C2=A0errors produce unwanted =
disposition decisions.=C2=A0 =C2=A0</div><div>=C2=A0- Senders need to be ca=
reful=C2=A0to ensure that they configure their policy to produce both SPF M=
AILFROM =3D PASS and SPF HELO=3DPASS.=C2=A0 =C2=A0</div></div></blockquote>=
<div><br></div><div>The likelihood of a HELO identifier both passing an SPF=
 check and aligning with the RFC5322.From identifier is, I would venture, s=
o small as to be immeasurable for shared services such as ESPs, mailing lis=
t servers, and the like. Perhaps they could eventually be convinced of a ne=
ed to publish SPF records, but that wouldn&#39;t do much of anything to cha=
nge the &lt;policy_evaluated&gt; results for DMARC. Getting an SPF pass ver=
dict alone for these identifiers isn&#39;t enough to alter the DMARC valida=
tion results; the identifiers must align,=C2=A0too. From a practical standp=
oint, I don&#39;t believe SPF MAILFROM=3Dpass/SPF EHLO=3Dfail would be usef=
ul information to mailbox providers for the significant volume of mail rout=
ing to their customers from shared services; I get quite a lot of such mail=
 to my Gmail mailbox each day, wanted mail that is correctly routed to my I=
nbox.</div><div><br></div><div>Beyond all that, though, SPF can fail for bo=
th the MAILFROM and the EHLO identifier on any given message, but if the me=
ssage is DKIM signed in a way that aligns with the RFC5322.From domain and =
the DKIM validation check passes, then the message will correctly be descri=
bed as having gotten a DMARC pass verdict. We&#39;ve spent quite a lot of t=
ime on this list discussing authentication checks that can, by themselves, =
result in a DMARC pass verdict, but that cannot, by themselves, result in a=
 DMARC fail verdict. A message has to fail SPF validation/alignment checks =
and DKIM validation/alignment checks in order to fail DMARC. I am not sugge=
sting that the DMARC spec be updated to require that both SPF and DKIM both=
 pass and align in order for DMARC to pass, because while I believe it to b=
e best practice for senders to align both SPF and DKIM identifiers, I belie=
ve it would cause too much breakage in existing running code and sender con=
figurations to be worth it to mandate such things.</div><div><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><br></d=
iv><div>Altogether, I think some wordsmithing is needed to communicate thos=
e points.=C2=A0 =C2=A0I do not have such wording at this moment, but will b=
egin thinking about what I=C2=A0would propose.=C2=A0 =C2=A0Perhaps those wh=
o are anxious to move on will be able to produce text sooner.</div><div><br=
></div><div>I have also raised a concern about the inadequacy of reporting =
these results, since &quot;Recevied-SPF: pass&quot; is currently a complian=
t=C2=A0header.=C2=A0 =C2=A0We can defer this issue to a later ticket, but w=
e need to be thinking about the problem.=C2=A0 =C2=A0If this requires no ch=
ange, I would like=C2=A0some discussion of why that might be the case.</div=
><div><br></div><div><br></div></div></blockquote><div><br></div><div>What =
the message recipient does with all this authentication information is left=
 as a local policy decision, a decision that is likely to be made using mor=
e data points than just the SPF, DKIM, and DMARC validation verdicts. The D=
MARC spec does not mandate that a message passing DMARC checks be accepted,=
 nor does it mandate that a message failing DMARC checks be rejected, even =
in the relevant policy published by the domain owner is &quot;p=3Dreject&qu=
ot;, and I am absolutely not suggesting that the DMARC spec be written in s=
uch a way as to mandate such behaviors. In my opinion, the text that should=
 appear in the DMARC spec to sum up these points is &quot;A DMARC pass verd=
ict means only that the message can be reliably associated by the recipient=
 with the identity on which the DMARC validation check was performed, and a=
 DMARC fail verdict means that it cannot be so associated.&quot;<br></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"text=
-align:left"><span style=3D"vertical-align:baseline;white-space:pre-wrap;fo=
nt-size:small;font-family:Arial"><b>Todd Herr</b></span><span style=3D"vert=
ical-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 styl=
e=3D"text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b></sp=
an><span style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@val=
imail.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><div style=3D"text-align:left"><span style=3D"vertical-align:baseline">=
<br></span></div></span><p dir=3D"ltr" style=3D"color:rgb(34,34,34);font-fa=
mily:Arial,Helvetica,sans-serif;font-size:small;background-color:rgb(255,25=
5,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><img src=3D"https=
://valimail-logos.s3.amazonaws.com/Valimail__Tag_DarkBlue_TM.png" style=3D"=
height: 35px; width: 159px;">`</p><p dir=3D"ltr" style=3D"background-color:=
rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font c=
olor=3D"#666666" face=3D"Arial"><span style=3D"font-size:10.6667px;white-sp=
ace:pre-wrap">This email and all data transmitted with it contains confiden=
tial and/or proprietary information intended solely for the use of individu=
al(s) authorized to receive it. If you are not an intended and authorized r=
ecipient you are hereby notified of any use, disclosure, copying or distrib=
ution of the information included in this transmission is prohibited and ma=
y be unlawful. Please immediately notify the sender by replying to this ema=
il 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">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>

--000000000000ae09a105baf2ca95--


From nobody Tue Feb  9 20:19:44 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 51DF53A1333 for <dmarc@ietfa.amsl.com>; Tue,  9 Feb 2021 20:19:43 -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=kDoQBmWX; dkim=pass (2048-bit key) header.d=kitterman.com header.b=kfsIBmvd
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9PmMA7lJIAhq for <dmarc@ietfa.amsl.com>; Tue,  9 Feb 2021 20:19:40 -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 D49F03A1331 for <dmarc@ietf.org>; Tue,  9 Feb 2021 20:19:40 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 2A6D9F8023A for <dmarc@ietf.org>; Tue,  9 Feb 2021 23:19:39 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1612930778; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=tFzJ1IonD2hHv3b4HAi3bkm/1IiEbvxFPkuw+2MPPL8=; b=kDoQBmWXuJxGAnRxRHERUXFGEDrr4+wbsec8CQFc9je/mRZUmk73usMLR38SslV6scnXM xv2pCmf6vXfqg7GBw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1612930778; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=tFzJ1IonD2hHv3b4HAi3bkm/1IiEbvxFPkuw+2MPPL8=; b=kfsIBmvdrA/4Iz+qTNarZSYoT4dctWN2fyVhY3nBrRIulmwwmlluKcCckPz4UUsl1PvHS ugcmu7rjyUD7dQpsSkKo2/2HE18rIgbqrS3SRWdHUm9M2jmM4WygPBMbxyal+lW6kzzeLSn D7FX5D4MWxSMtfFS6gn4XHctqf0NqGvoyAHfgv7IpTU7drRIqt7XAFZPYiMTGbwUwhzC3iT ub+Kp6Zy2tjvR8rm54IMc9iuPwhG/I2e0+TrwZVCaml4yynYksFW/iLwqv3LeWTZAsgBMTp dar20WDzVxu0XTY8XmbRcdXJ7wNRyf6Iw+t+aOUgXMUX+Im5eQDE08NxuMeg==
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 B484AF801F9 for <dmarc@ietf.org>; Tue,  9 Feb 2021 23:19:38 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Tue, 09 Feb 2021 23:19:38 -0500
Message-ID: <2285569.RditZUVBbg@zini-1880>
In-Reply-To: <CAH48ZfxFsQ5ntE05QYRqP5P3Na6vuDjNAQKAdjZe7Kvt7evKuw@mail.gmail.com>
References: <20210203181226.9AB746D51182@ary.qy> <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com> <CAH48ZfxFsQ5ntE05QYRqP5P3Na6vuDjNAQKAdjZe7Kvt7evKuw@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/Qf_Z1dz5YHBzUGPbcsLro0v4HYY>
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, 10 Feb 2021 04:19:43 -0000

No one has demonstrated that if someone has implemented SPF (RFC 7208) without 
worrying about DMARC that there are any associated problems for DMARC.  
Anything else about SPF is out of scope for this working group.

Scott K

On Tuesday, February 9, 2021 10:13:37 PM EST Douglas Foster wrote:
> The chairs can introduce another topic whenever they want.   This does not
> seem like a pre-requisite to any of the other pending topics.
> 
> My interest is interoperability:    We want recipient requirements and
> sender compliance measures to align.
> 
> RFC 7208 says that recipients MAY want to use SPF HELO and SPF MAILFROM
> together.  An argument can be made that this is not necessary:   SPF
> MAILFROM shows that the server is authorized to send messages for the
> specific domain in the MAILFROM, while SPF HELO says only that the server
> is authorized to send message for the server domain and an unknowable set
> of other domains.  Therefore a PASS from SPF MAILFROM should make SPF HELO
> unnecessary and redundant.    Does either the DMARC document or the SPF
> document say this anywhere?
> 
> RFC 7208 can be misunderstood to suggest that SPF MAILFROM and SPF HELO are
> equivalent and interchangeable, which they are not, for the reason just
> mentioned.   Shouldn't we also make this clear?
> 
> Senders are motivated to ensure that their mail is delivered, which makes
> them interested in all of the factors which can maximize delivery and
> minimize rejection.    SPF HELO might be one of those reasons.   Do we
> mention this as an additional measure that senders might want to consider,
> or do we keep silent?
> 
> Todd's assertion is that SPF HELO will cause an excessive number of false
> positives.   I share Todd's expectation that this will be true, but I have
> no data on that point yet.  I am just beginning to collect that data,
> because it seems like an interesting question.
> 
> A second assumption is that no significant recipients are evaluating SPF
> MAILFROM and SPF HELO together in a way that would be of interest to
> senders. This may also be true, but I don't think this is something that
> can be tested.
> 
> A third assumption is that the current behavior related to SPF HELO will
> continue indefinitely.
> 
> To maximize interoperability:
> - Recipients can be encouraged to ignore SPF HELO as unnecessary and the
> likely source of false positives.
> - Senders can be encouraged to ensure SPF HELO compliance to prevent false
> positives.
> 
> That interoperability outcome seems worth some comment in our final
> document, since it created the confusion that led to ticket #1.
> 
> The original question and these comments are exclusively about the SPF side
> of the DMARC evaluation, which presumes that the DKIM signature is missing
> or invalid.   I was neither proposing a new block algorithm nor proposing a
> new allow algorithm.  But I do think that we need to anticipate how people
> are likely to use our documents, with the goal of minimizing incompatible
> interpretations.   Ale's question demonstrates that such interpretation
> problems are possible, even on a small and well-informed sample set.
> 
> DF
> 
> DF
> 
> On Mon, Feb 8, 2021 at 9:50 AM Todd Herr <todd.herr=
> 
> 40valimail.com@dmarc.ietf.org> wrote:
> > On Sun, Feb 7, 2021 at 7:35 AM Douglas Foster <
> > 
> > dougfoster.emailstandards@gmail.com> wrote:
> >> "We have a lot of other topics" is the wrong reason to call for
> >> consensus.   The important question is "Ale, have we addressed your
> >> concerns?"
> >> 
> >> I agree with many that for DMARC, our primary interest is whether SPF
> >> validation of MAILFROM produces a PASS.
> > 
> > That's only partially correct. For DMARC, the SPF validation of MAILFROM
> > must produce a PASS and the identifier must align with the RFC5322.From
> > header domain. Absent both the PASS verdict and the alignment, the
> > <policy_evaluated> section of the aggregate report will show "fail" for
> > SPF, even if the <results> bit of the <auth_results> section shows "pass"
> > in the <spf> sub-section.
> > 
> >> However, I also see that a cautious recipient may choose to also require
> >> SPF HELO = PASS and / or fcDNS HELO = PASS ( VERIFIED ).   Getting a PASS
> >> on these multiple criteria increases the confidence in the PASS result,
> >> but
> >> also increases the likelihood of ambiguous results and false rejects.
> >> 
> >> Therefore:
> >>  - Recipients need to be cautious about enforcing rules so strictly that
> >> 
> >> sender configuration errors produce unwanted disposition decisions.
> >> 
> >>  - Senders need to be careful to ensure that they configure their policy
> >> 
> >> to produce both SPF MAILFROM = PASS and SPF HELO=PASS.
> > 
> > The likelihood of a HELO identifier both passing an SPF check and aligning
> > with the RFC5322.From identifier is, I would venture, so small as to be
> > immeasurable for shared services such as ESPs, mailing list servers, and
> > the like. Perhaps they could eventually be convinced of a need to publish
> > SPF records, but that wouldn't do much of anything to change the
> > <policy_evaluated> results for DMARC. Getting an SPF pass verdict alone
> > for
> > these identifiers isn't enough to alter the DMARC validation results; the
> > identifiers must align, too. From a practical standpoint, I don't believe
> > SPF MAILFROM=pass/SPF EHLO=fail would be useful information to mailbox
> > providers for the significant volume of mail routing to their customers
> > from shared services; I get quite a lot of such mail to my Gmail mailbox
> > each day, wanted mail that is correctly routed to my Inbox.
> > 
> > Beyond all that, though, SPF can fail for both the MAILFROM and the EHLO
> > identifier on any given message, but if the message is DKIM signed in a
> > way
> > that aligns with the RFC5322.From domain and the DKIM validation check
> > passes, then the message will correctly be described as having gotten a
> > DMARC pass verdict. We've spent quite a lot of time on this list
> > discussing
> > authentication checks that can, by themselves, result in a DMARC pass
> > verdict, but that cannot, by themselves, result in a DMARC fail verdict. A
> > message has to fail SPF validation/alignment checks and DKIM
> > validation/alignment checks in order to fail DMARC. I am not suggesting
> > that the DMARC spec be updated to require that both SPF and DKIM both pass
> > and align in order for DMARC to pass, because while I believe it to be
> > best
> > practice for senders to align both SPF and DKIM identifiers, I believe it
> > would cause too much breakage in existing running code and sender
> > configurations to be worth it to mandate such things.
> > 
> >> Altogether, I think some wordsmithing is needed to communicate those
> >> points.   I do not have such wording at this moment, but will begin
> >> thinking about what I would propose.   Perhaps those who are anxious to
> >> move on will be able to produce text sooner.
> >> 
> >> I have also raised a concern about the inadequacy of reporting these
> >> results, since "Recevied-SPF: pass" is currently a compliant header.   We
> >> can defer this issue to a later ticket, but we need to be thinking about
> >> the problem.   If this requires no change, I would like some discussion
> >> of
> >> why that might be the case.
> > 
> > What the message recipient does with all this authentication information
> > is left as a local policy decision, a decision that is likely to be made
> > using more data points than just the SPF, DKIM, and DMARC validation
> > verdicts. The DMARC spec does not mandate that a message passing DMARC
> > checks be accepted, nor does it mandate that a message failing DMARC
> > checks
> > be rejected, even in the relevant policy published by the domain owner is
> > "p=reject", and I am absolutely not suggesting that the DMARC spec be
> > written in such a way as to mandate such behaviors. In my opinion, the
> > text
> > that should appear in the DMARC spec to sum up these points is "A DMARC
> > pass verdict means only that the message can be reliably associated by the
> > recipient with the identity on which the DMARC validation check was
> > performed, and a DMARC fail verdict means that it cannot be so
> > associated."
> > 
> > --
> > 
> > *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





From nobody Wed Feb 10 01:49:56 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 A72353A0FF0 for <dmarc@ietfa.amsl.com>; Wed, 10 Feb 2021 01:49:53 -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 Xjl_8dNNr9s5 for <dmarc@ietfa.amsl.com>; Wed, 10 Feb 2021 01:49:52 -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 DD4B73A0DE7 for <dmarc@ietf.org>; Wed, 10 Feb 2021 01:49:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1612950587; bh=ZXobfUTBaoCM8gY9Ia8VA6j2D5TQZz4Ym5fZRuS7Qn8=; l=2342; h=To:References:From:Date:In-Reply-To; b=Cwr5/uR9ZWeXN1XB6kbyRNrkFtZ8xlPifQYfYZxQQL79f0R//8oEEe2nbYqezQQ+O fC9RCqZuoHOIPxO9FLWpxXdKnhYOgNTCWBOS/7OSKvhxWD4RFuB08EvBWFnum9h2Zt P8L09OVH1kiSq6sO9d0RnOurrP7AbEm+XOxPxnYqdt9xcF2muHiFpVLNO+5Du
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.000000006023AC3B.00002214; Wed, 10 Feb 2021 10:49:47 +0100
To: dmarc@ietf.org
References: <20210203181226.9AB746D51182@ary.qy> <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com> <CAH48ZfxFsQ5ntE05QYRqP5P3Na6vuDjNAQKAdjZe7Kvt7evKuw@mail.gmail.com> <2285569.RditZUVBbg@zini-1880>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <ea27d175-e436-fa40-0571-da1e0189d488@tana.it>
Date: Wed, 10 Feb 2021 10:49: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: <2285569.RditZUVBbg@zini-1880>
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/rR8yR2wNJvMjlSgAt5J2WrLpCoA>
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, 10 Feb 2021 09:49:54 -0000

Just to clarify:


On Wed 10/Feb/2021 05:19:38 +0100 Scott Kitterman wrote:
> No one has demonstrated that if someone has implemented SPF (RFC 7208) without
> worrying about DMARC that there are any associated problems for DMARC.


I think I did.  OpenDMARC, for example, seems to read a single result, either 
Authentication-Results: or Received-SPF:, assuming that it contains the mfrom 
identity unless empty.  Note that it has an option to disable SPF entirely, 
presumably as a means to tackle non-DMARC oriented SPF filters.

Google apparently works similarly.  Given a valid helo and a neutral mfrom, the 
spf= clause of its (ARC-)Authentication-Results: only reports the latter.  That 
is to say, you need a non-RFC7208 compliant SPF filter to instruct DMARC.


> On Tuesday, February 9, 2021 10:13:37 PM EST Douglas Foster wrote:
>> [...]
>> 
>> My interest is interoperability:    We want recipient requirements and
>> sender compliance measures to align.
>> 
>> RFC 7208 says that recipients MAY want to use SPF HELO and SPF MAILFROM
>> together.  An argument can be made that this is not necessary:   SPF
>> MAILFROM shows that the server is authorized to send messages for the
>> specific domain in the MAILFROM, while SPF HELO says only that the server
>> is authorized to send message for the server domain and an unknowable set
>> of other domains.


What unknowable set of other domains?  If the server has an SPF record, it 
presumably authorizes just its IP address(es).


>> Todd's assertion is that SPF HELO will cause an excessive number of false
>> positives.


I'd let Todd speak for himself, but I never saw that assertion.  Todd said the 
set of messages that would get a different DMARC status in case we linearize 
the spec is immeasurable  —which I believe is true, and a valid basis to carry 
out the linearization without fear of disruption.


>> A second assumption is that no significant recipients are evaluating SPF
>> MAILFROM and SPF HELO together in a way that would be of interest to
>> senders. This may also be true, but I don't think this is something that
>> can be tested.


It makes no sense to require both values to pass simultaneously.

Linearization would be that *any* validated identifier, as long as it's 
aligned, produces a DMARC pass.


Best
Ale
-- 















From nobody Wed Feb 10 06:43:10 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 1BFCA3A0C28 for <dmarc@ietfa.amsl.com>; Wed, 10 Feb 2021 06:43:08 -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=T9MKRoc7; dkim=pass (2048-bit key) header.d=kitterman.com header.b=n5yjnGMR
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6H0QEDfEZrnt for <dmarc@ietfa.amsl.com>; Wed, 10 Feb 2021 06:43:06 -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 E22473A0C36 for <dmarc@ietf.org>; Wed, 10 Feb 2021 06:43:05 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id A1E0EF80227 for <dmarc@ietf.org>; Wed, 10 Feb 2021 09:43:04 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1612968184; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=1lc2CS+USkhkKTcKADmfPQZqRV9khPwamGX/Tkw2s70=; b=T9MKRoc7Ha98TH41ffMH2p2oEt/34F0CESjfLK7/gyuEft7xE5GQ2hCF/x+qX8MHveyBm O5E4TU9wnFYxtj2Bw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1612968184; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=1lc2CS+USkhkKTcKADmfPQZqRV9khPwamGX/Tkw2s70=; b=n5yjnGMRMC/yEWwH/0Ibda7xDaqEAevCI1wtMW5HamodQ2FxamQIiUAguc/g47Ru0HLXS bYg12VZEM+uoWPFGM5Srq6OjLcLTStMkl02Np4fmVfGb6Slz9c+hfiGQ5oTUJV9eRahX/HX CZVTz5IqNo5hLRl8kA0tiqloPWtZYOqbIIYs/t8Z0keF7WaBBU9nSi2+ldiSs+Y/TitDYF4 2cttc56ylrQoEWwYf2btqGjxVLXJO9uQqPeYirD8kjnU+tf9yOQJJEoW26yhw+FOXDWc3Pl +A8HLow2I+TpeNIUzJ1aJLGFs4UDyQdvWo5AE46ERvR8DgjT//Oj02dUVydw==
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 52BA2F8019D for <dmarc@ietf.org>; Wed, 10 Feb 2021 09:43:04 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Wed, 10 Feb 2021 09:43:04 -0500
Message-ID: <2244314.3GJdnAqG3q@zini-1880>
In-Reply-To: <ea27d175-e436-fa40-0571-da1e0189d488@tana.it>
References: <20210203181226.9AB746D51182@ary.qy> <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com> <CAH48ZfxFsQ5ntE05QYRqP5P3Na6vuDjNAQKAdjZe7Kvt7evKuw@mail.gmail.com> <2285569.RditZUVBbg@zini-1880> <ea27d175-e436-fa40-0571-da1e0189d488@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/UYjzWSNAKN0bIdLMGOcVSqbRC9M>
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, 10 Feb 2021 14:43:08 -0000

No.  Sigh.  Let's try it again.

Yes, one might actually use a HELO result for DMARC.  It gives you the same 
result as if mail from is null.  So what?

No one has given us a case where an attacker could get a aligned SPF result 
based on HELO that they couldn't also get with mail from, so it doesn't 
matter.

By problem, I mean an actual problem.  There aren't any.

Scott K

On February 10, 2021 9:49:46 AM UTC, Alessandro Vesely <vesely@tana.it> wrote:
>Just to clarify:
>
>
>On Wed 10/Feb/2021 05:19:38 +0100 Scott Kitterman wrote:
>> No one has demonstrated that if someone has implemented SPF (RFC
>7208) without
>> worrying about DMARC that there are any associated problems for
>DMARC.
>
>
>I think I did.  OpenDMARC, for example, seems to read a single result,
>either 
>Authentication-Results: or Received-SPF:, assuming that it contains the
>mfrom 
>identity unless empty.  Note that it has an option to disable SPF
>entirely, 
>presumably as a means to tackle non-DMARC oriented SPF filters.
>
>Google apparently works similarly.  Given a valid helo and a neutral
>mfrom, the 
>spf= clause of its (ARC-)Authentication-Results: only reports the
>latter.  That 
>is to say, you need a non-RFC7208 compliant SPF filter to instruct
>DMARC.




From nobody Wed Feb 10 08:49:35 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 686583A0FEF for <dmarc@ietfa.amsl.com>; Wed, 10 Feb 2021 08:49: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 (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 jvGyTkrPUX-r for <dmarc@ietfa.amsl.com>; Wed, 10 Feb 2021 08:49:32 -0800 (PST)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 9D3A03A0FEB for <dmarc@ietf.org>; Wed, 10 Feb 2021 08:49:31 -0800 (PST)
Received: by mail-lj1-x22a.google.com with SMTP id u4so3726465ljh.6 for <dmarc@ietf.org>; Wed, 10 Feb 2021 08:49:31 -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=DynI/QwkfbZoKGz7WLaHi7J3p0E8bxAi6cyUQhozYHQ=; b=ValZlRUhK+O3+TDKvrBqlp/zpmyKsV9ikIqicp1uaTdlG7O+Gr6oeTVZ9HBGtPMoTn iefMNvI2rTyqmEcM6ctxFGTKJ/GnbHmbrMCHa4wWhHJdjaAwZkDbSTHo4PAjgjZAKNIf WezEkzMJN0503SFRjp9LfhQTZv5H14KHfNxsc=
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=DynI/QwkfbZoKGz7WLaHi7J3p0E8bxAi6cyUQhozYHQ=; b=NvbnftZTlMxZ9zhhETi4oyZwAGum8HR7v/fvPW3Ejfc/L0I/fysMDomoMngfEY4iRF 1g6OR6f6cJErXyItFUnCbj5+zGkPpMuRwZTmirHvPCJFSVUxoKjTgs408bHgLu3x8C5f KtAi5gDQnESZswhz6z0nNy3X1tF5CXDNexmoKxo51V0Nybm7lwgkreIc7iMegbWtJntB ZP/oy6L5S7nIolK/LOUSDYlksXSM40Y8D+XLe/XUZfJqJmuMsHlCAXFXksUzf4EN8vCc 0m8mJ03OLs17eEqR4boWMuUTvhgawb54h3a9P/y97La8Yqg9vzN6Pq5Ghq0u32VgBhh8 Fmdw==
X-Gm-Message-State: AOAM531kN9MGSUZwYnMR5Iwe8R1LLfyhU2Lt4dp36n5yYpypAyA5IKuU 1sszTEk9zUkAkaoP1Q2E/B1+BXgHHhoixW0BWKsBBQA1keS6Lg==
X-Google-Smtp-Source: ABdhPJyt8QQF/niIVFkJrdU38dK7igUDwrqGKdHF6Z7XDwJKd3TdHmtvnF1CZXwNGsgKSvKAFm3DrelUt4a4hfxITJw=
X-Received: by 2002:a2e:b88b:: with SMTP id r11mr2503770ljp.187.1612975769521;  Wed, 10 Feb 2021 08:49:29 -0800 (PST)
MIME-Version: 1.0
References: <20210203181226.9AB746D51182@ary.qy> <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com> <CAH48ZfxFsQ5ntE05QYRqP5P3Na6vuDjNAQKAdjZe7Kvt7evKuw@mail.gmail.com> <2285569.RditZUVBbg@zini-1880> <ea27d175-e436-fa40-0571-da1e0189d488@tana.it> <2244314.3GJdnAqG3q@zini-1880>
In-Reply-To: <2244314.3GJdnAqG3q@zini-1880>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Wed, 10 Feb 2021 08:49:17 -0800
Message-ID: <CABuGu1q_jLsGP5c74_vc_SnQoozxOipaFzJ6RmeMR7jy0Vk=Xg@mail.gmail.com>
To: Scott Kitterman <sklist@kitterman.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c628a705bafe2f43"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/OSzTD2lz4PC5qV3Xjb0A_0_JXEs>
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, 10 Feb 2021 16:49:33 -0000

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

On Wed, Feb 10, 2021 at 6:43 AM Scott Kitterman <sklist@kitterman.com>
wrote:

> No.  Sigh.  Let's try it again.
>
> Yes, one might actually use a HELO result for DMARC.  It gives you the
> same
> result as if mail from is null.  So what?
>
> No one has given us a case where an attacker could get a aligned SPF
> result
> based on HELO that they couldn't also get with mail from, so it doesn't
> matter.
>
> By problem, I mean an actual problem.  There aren't any.
>
> Scott K
>

The other issue that people who are continuing this thread are ignoring is
that changing 7208 is out of scope for this WG.

--Kurt

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

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Feb 10, 2021 at 6:43 AM Scott Kit=
terman &lt;<a href=3D"mailto:sklist@kitterman.com">sklist@kitterman.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">No.=C2=A0 Sigh.=C2=A0 Let&#39;s try it again.<br>
<br>
Yes, one might actually use a HELO result for DMARC.=C2=A0 It gives you the=
 same <br>
result as if mail from is null.=C2=A0 So what?<br>
<br>
No one has given us a case where an attacker could get a aligned SPF result=
 <br>
based on HELO that they couldn&#39;t also get with mail from, so it doesn&#=
39;t <br>
matter.<br>
<br>
By problem, I mean an actual problem.=C2=A0 There aren&#39;t any.<br>
<br>
Scott K<br></blockquote><div><br></div><div>The other issue that people who=
 are continuing this thread are ignoring is that changing 7208 is out of sc=
ope for this WG.</div><div><br></div><div>--Kurt=C2=A0</div></div></div>

--000000000000c628a705bafe2f43--


From nobody Wed Feb 10 15:24:27 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 2AB3F3A0D98 for <dmarc@ietfa.amsl.com>; Wed, 10 Feb 2021 15:24: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 XpJsI0P-4agh for <dmarc@ietfa.amsl.com>; Wed, 10 Feb 2021 15:24: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 275933A0D97 for <dmarc@ietf.org>; Wed, 10 Feb 2021 15:24:24 -0800 (PST)
Received: by mail-vs1-xe2e.google.com with SMTP id d24so2080467vso.6 for <dmarc@ietf.org>; Wed, 10 Feb 2021 15:24: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=AF/Uk7wJJ5xMxz6XJ02HrSrLCeASbGyi+I30rflv3mk=; b=l3bUg7H7yel4UKDOuIdpLi/4keM7mm4ynR4SIAztPo89VM9hDLyqI/Rt7t451hpSO/ Bz/fxciRgddTFEVaS62QR+CmzNm7Yo+OOB/7W+oFAVk1L1YDks3XAaLV42/Wkd3TqIiC lNwyG7X0FBNkQejWZzzeSlJJ+Ok9MHt/xvjxNSOo+qjyxja1QMz02PUNJSvmW/dWegFJ MZKoH/RvUZNViphw7zI5/mfOTiCTM/mg9GEVMUq5nCaDgA5an21wZV2fqAB2cku4iiy6 Vavn3so5811G3xfg8O8wsSr2ZLiR1qN+l3A14+DquBFByKW5+Oj6kSjxY3d0Rl6L16uD tWfg==
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=AF/Uk7wJJ5xMxz6XJ02HrSrLCeASbGyi+I30rflv3mk=; b=s7S4cc35WRA1jGCyRZeYLjhsruklNhV9ahMAH9SGcpPCvaRJoxR19kD90zbwdb2pB3 0yq887d6sWZjTOgMNQAWlW3UgDFMbDMEmFlXM6oa4VdGmOZSItUSlQL7k9RPhPw10S/5 SJ9RZugHjEa+xHMzhbR7iKOGRTqi9ID5X/z4BZ/fWFmky8LGuz5TwGiDFYhtLR3L2owh dx2VPhjGuBXHeeQiQdmef3Eq/dTiq0Hf40hiYaD8lopOPWD71dNygeYeYMHl+M+6MoY2 3z6aVZLQ7WXkaW6nMX0qmewrTn1/hOViT0Ds7ipqb7PxkQYS7d1PyhIRgFfI1Tg0qp0i W5gQ==
X-Gm-Message-State: AOAM533maoCVBgAyw1rioU9x3uDD5LqTqNGo/pefQvtytEg+rzfsRoEy U6zViBsNlUqnKAoArupBJ8VkrQn9a7xvDKR2ptc=
X-Google-Smtp-Source: ABdhPJx9RrtouYV9pVst9RdwjB58U2O7iv5sV4sswY0BLz72P2+3/P3o2jSQknMbhgY3IO3klAKSJINglN3gJJpHK7s=
X-Received: by 2002:a67:24c5:: with SMTP id k188mr3894917vsk.16.1612999461969;  Wed, 10 Feb 2021 15:24:21 -0800 (PST)
MIME-Version: 1.0
References: <20210203181226.9AB746D51182@ary.qy> <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com> <CAH48ZfxFsQ5ntE05QYRqP5P3Na6vuDjNAQKAdjZe7Kvt7evKuw@mail.gmail.com> <2285569.RditZUVBbg@zini-1880> <ea27d175-e436-fa40-0571-da1e0189d488@tana.it> <2244314.3GJdnAqG3q@zini-1880>
In-Reply-To: <2244314.3GJdnAqG3q@zini-1880>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 10 Feb 2021 18:24:11 -0500
Message-ID: <CAH48Zfynp=BVKXeyWO=KL=TVRiUDVuvckWDgpZFbVeVjBBqjaw@mail.gmail.com>
To: Scott Kitterman <sklist@kitterman.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f4203005bb03b31e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Sl0LUyb9ogyIU6q33dxuyquDs7M>
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, 10 Feb 2021 23:24:26 -0000

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

Huh?   Are you asserting that SPF MAILFROM and SPF HELO are
interchangeable?   They are not, but they can work together.

Some scenarios to illustrate:

clientdomain.tld uses servers from hostingservice.tld
the spf for hostingservice.tld allows only server "mail.hostingservice.tld"
the spf ro clientdomain allows ANY server from hostingservice.tld

Case 1
server= mail.hostingservice.tld
SMTP = u@clientdomain.tld
FROM= u@hostingservice.tld

SPF HELO = PASS aligns with FROM, but this is not a valid alignment for
DMARC PASS.
Only SPF MAILFROM produces a correct result (SPF PASS but DMARC FAIL),
because the client domain is not authorized to send messages for the
hostingservice domain.
Ergo:   SPF HELO does not produce equivalent results to SPF MAILFROM

Case 2
server = nonmail.hostingservice.tld
SMTP = u@cllientdomain.tld
FROM = u@clientdomain.tld

SPF MAILFROM = PASS and aligns with FROM, so it appears to be a DMARC PASS.
But SPF HELO is a FAIL, because the SPF for HostingService.tld says that
this server never sends mail.
Ergo:  SPF HELO can be used along with SPF MAILFROM to produce a more
granular allow list then SPF MAILFROM alone.

DF

On Wed, Feb 10, 2021 at 9:43 AM Scott Kitterman <sklist@kitterman.com>
wrote:

> No.  Sigh.  Let's try it again.
>
> Yes, one might actually use a HELO result for DMARC.  It gives you the
> same
> result as if mail from is null.  So what?
>
> No one has given us a case where an attacker could get a aligned SPF
> result
> based on HELO that they couldn't also get with mail from, so it doesn't
> matter.
>
> By problem, I mean an actual problem.  There aren't any.
>
> Scott K
>
> On February 10, 2021 9:49:46 AM UTC, Alessandro Vesely <vesely@tana.it>
> wrote:
> >Just to clarify:
> >
> >
> >On Wed 10/Feb/2021 05:19:38 +0100 Scott Kitterman wrote:
> >> No one has demonstrated that if someone has implemented SPF (RFC
> >7208) without
> >> worrying about DMARC that there are any associated problems for
> >DMARC.
> >
> >
> >I think I did.  OpenDMARC, for example, seems to read a single result,
> >either
> >Authentication-Results: or Received-SPF:, assuming that it contains the
> >mfrom
> >identity unless empty.  Note that it has an option to disable SPF
> >entirely,
> >presumably as a means to tackle non-DMARC oriented SPF filters.
> >
> >Google apparently works similarly.  Given a valid helo and a neutral
> >mfrom, the
> >spf= clause of its (ARC-)Authentication-Results: only reports the
> >latter.  That
> >is to say, you need a non-RFC7208 compliant SPF filter to instruct
> >DMARC.
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr">Huh?=C2=A0 =C2=A0Are you=C2=A0asserting that SPF MAILFROM =
and SPF HELO are interchangeable?=C2=A0 =C2=A0They are not, but they=C2=A0c=
an work together.<div><br></div><div>Some scenarios to illustrate:<br></div=
><div><br></div><div>clientdomain.tld=C2=A0uses servers from hostingservice=
.tld</div><div>the spf for hostingservice.tld=C2=A0allows only server &quot=
;mail.hostingservice.tld&quot;</div><div>the spf ro clientdomain allows ANY=
 server from hostingservice.tld</div><div><br></div><div>Case 1</div><div>s=
erver=3D mail.hostingservice.tld</div><div>SMTP =3D u@clientdomain.tld</div=
><div>FROM=3D u@hostingservice.tld</div><div><br></div><div>SPF HELO =3D PA=
SS aligns with FROM, but this is not a valid alignment for DMARC PASS.=C2=
=A0=C2=A0</div><div>Only SPF MAILFROM produces a correct result (SPF PASS b=
ut DMARC FAIL),=C2=A0 =C2=A0=C2=A0</div><div>because the client=C2=A0domain=
 is not authorized to send messages for the hostingservice=C2=A0domain.</di=
v><div>Ergo:=C2=A0 =C2=A0SPF HELO does not produce equivalent results to SP=
F MAILFROM</div><div><br></div><div>Case 2</div><div>server =3D nonmail.hos=
tingservice.tld</div><div>SMTP =3D u@cllientdomain.tld</div><div>FROM =3D u=
@clientdomain.tld</div><div><br></div><div>SPF MAILFROM =3D PASS and aligns=
 with FROM, so it appears to be a DMARC PASS.</div><div>But SPF HELO is a F=
AIL, because the SPF for HostingService.tld says that this server never sen=
ds mail.</div><div>Ergo:=C2=A0 SPF HELO can be used along with SPF MAILFROM=
 to produce a more granular allow list then SPF MAILFROM alone.</div><div><=
br></div><div>DF</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr"=
 class=3D"gmail_attr">On Wed, Feb 10, 2021 at 9:43 AM Scott Kitterman &lt;<=
a href=3D"mailto:sklist@kitterman.com">sklist@kitterman.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">No.=C2=A0 Sigh.=
=C2=A0 Let&#39;s try it again.<br>
<br>
Yes, one might actually use a HELO result for DMARC.=C2=A0 It gives you the=
 same <br>
result as if mail from is null.=C2=A0 So what?<br>
<br>
No one has given us a case where an attacker could get a aligned SPF result=
 <br>
based on HELO that they couldn&#39;t also get with mail from, so it doesn&#=
39;t <br>
matter.<br>
<br>
By problem, I mean an actual problem.=C2=A0 There aren&#39;t any.<br>
<br>
Scott K<br>
<br>
On February 10, 2021 9:49:46 AM UTC, Alessandro Vesely &lt;<a href=3D"mailt=
o:vesely@tana.it" target=3D"_blank">vesely@tana.it</a>&gt; wrote:<br>
&gt;Just to clarify:<br>
&gt;<br>
&gt;<br>
&gt;On Wed 10/Feb/2021 05:19:38 +0100 Scott Kitterman wrote:<br>
&gt;&gt; No one has demonstrated that if someone has implemented SPF (RFC<b=
r>
&gt;7208) without<br>
&gt;&gt; worrying about DMARC that there are any associated problems for<br=
>
&gt;DMARC.<br>
&gt;<br>
&gt;<br>
&gt;I think I did.=C2=A0 OpenDMARC, for example, seems to read a single res=
ult,<br>
&gt;either <br>
&gt;Authentication-Results: or Received-SPF:, assuming that it contains the=
<br>
&gt;mfrom <br>
&gt;identity unless empty.=C2=A0 Note that it has an option to disable SPF<=
br>
&gt;entirely, <br>
&gt;presumably as a means to tackle non-DMARC oriented SPF filters.<br>
&gt;<br>
&gt;Google apparently works similarly.=C2=A0 Given a valid helo and a neutr=
al<br>
&gt;mfrom, the <br>
&gt;spf=3D clause of its (ARC-)Authentication-Results: only reports the<br>
&gt;latter.=C2=A0 That <br>
&gt;is to say, you need a non-RFC7208 compliant SPF filter to instruct<br>
&gt;DMARC.<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>

--000000000000f4203005bb03b31e--


From nobody Wed Feb 10 15:29: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 28D853A0DB8 for <dmarc@ietfa.amsl.com>; Wed, 10 Feb 2021 15:29:07 -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, FREEMAIL_FROM=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 jbYU5rQptZke for <dmarc@ietfa.amsl.com>; Wed, 10 Feb 2021 15:29:06 -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 17CA33A0DB3 for <dmarc@ietf.org>; Wed, 10 Feb 2021 15:29:06 -0800 (PST)
Received: by mail-ot1-x332.google.com with SMTP id a5so2377214otq.4 for <dmarc@ietf.org>; Wed, 10 Feb 2021 15:29:06 -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=lzcEm636YpvkEHdSKjKaVvBuUMK3dYCDiQsmf3m74NU=; b=Be6iwDyHcoJ61ZnTKPhlS6/+qvp/vOxEoxWvK1MJdyhVF++/dGptUyHIaXnMo1Hct4 FR16PUkEf6+OB+Kr08e4GPtLl/DueSS7UcKckaAqW6t5YamP07LnmOJgdsAnzVtdjd6N ygdrw0Gz4Cq73PDGos5Wdb6y0M8l7cEkz2hXni/tRQ7r8SPHg8QgOnR42LeIq9zLKz3t bi5hjeI6obVsNMhEJIfezN6yomgam4gbkz9Lio42/S8co6WDVI9oqF7Ls0k3XvCnHGVA YmkXEqs66ow5kgEPb3xipXlT+F0mZjZZPNC7Whn4TplVAKnIicB5UpWyfOX9YHWHq9PZ h8Gg==
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=lzcEm636YpvkEHdSKjKaVvBuUMK3dYCDiQsmf3m74NU=; b=mM8jNk0roU/hJmyf1EcpqnCYiPX4lWD4QEDmieD6GuxOWgoPUbzUbq3+DF8hFrC8Jw PT9XemXrjSGnhupMZCXbTfrZd8qntvtOfLQ8KuMD/GLLrIi+q0XbUb4KsTFmkiso63qJ D3/Bcudc/0WGgmJWQwBQVO1WUSNv7O+Lv1E1aPDh1cxpCmXaxcRq/nYdajUEyfKpcZAn CmA9bko293kGzfVtavPXwBPNUWL0yCNlm8dE3LcmTr8B8sfw23MPBaaEYHXRBAlcjERV 5DAhcKHKW5elNgH9u/G3Fb8x4bZdj2Ky2OHXGceUDqBGnEXueM9JkxCsgcZ7iNEUbF9w lfOg==
X-Gm-Message-State: AOAM531lHFdQjCxjNMQlF2OwdwcdApCJgxHr4FhWYALM9eN0pPbHFmtR mduhaNulQDPMuE+xqNLJv7IwLlVPy7Au9w==
X-Google-Smtp-Source: ABdhPJzDvO3h/5ZNlQjwGz6cFnapdIXjNXG2Q3NQlMpPW5L/uiuVGscmm3cZTpjh4yXnaOBqcu47CQ==
X-Received: by 2002:a05:6830:1110:: with SMTP id w16mr3866030otq.326.1612999743850;  Wed, 10 Feb 2021 15:29:03 -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 o14sm676748otl.68.2021.02.10.15.29.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 10 Feb 2021 15:29:03 -0800 (PST)
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, Scott Kitterman <sklist@kitterman.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <20210203181226.9AB746D51182@ary.qy> <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com> <CAH48ZfxFsQ5ntE05QYRqP5P3Na6vuDjNAQKAdjZe7Kvt7evKuw@mail.gmail.com> <2285569.RditZUVBbg@zini-1880> <ea27d175-e436-fa40-0571-da1e0189d488@tana.it> <2244314.3GJdnAqG3q@zini-1880> <CAH48Zfynp=BVKXeyWO=KL=TVRiUDVuvckWDgpZFbVeVjBBqjaw@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <0d7de3eb-5b14-510c-cb4a-c78bc34610d8@gmail.com>
Date: Wed, 10 Feb 2021 15:29:02 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <CAH48Zfynp=BVKXeyWO=KL=TVRiUDVuvckWDgpZFbVeVjBBqjaw@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/kl6uVMUP8y-hKYOFH7c-g0syUrg>
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, 10 Feb 2021 23:29:07 -0000

On 2/10/2021 3:24 PM, Douglas Foster wrote:
> Huh?  Are you asserting that SPF MAILFROM and SPF HELO are 
> interchangeable?   They are not, but they can work together.


Perhaps I misread, but I thought I saw that this really is out of scope 
for this working group.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Thu Feb 11 01: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 B4A343A142E for <dmarc@ietfa.amsl.com>; Thu, 11 Feb 2021 01:08:07 -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 rthCKx5ykmng for <dmarc@ietfa.amsl.com>; Thu, 11 Feb 2021 01:08: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 922E03A140F for <dmarc@ietf.org>; Thu, 11 Feb 2021 01:08:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1613034483; bh=35XOaDXJiM4BLrFyXWcd90FjiQi+ggdANAABjpqvXp8=; l=615; h=To:Cc:References:From:Date:In-Reply-To; b=C9fniGM2MbmYSykY3d2lzW2k/kanE6X3spkgqbSaaAqOmo90HTVwn7I/lr/B+++Z9 h54L/Eyam02yaNXHAMcADc+0TvSHq5FC+UfQNZt1ZWrT1ebmZBD6Gui5fH6oOzIcp3 7/I5A6nZj83cccA+VYTXRGqirVdQh/9zzalyM5hdYfT7gw00FbNK8OY/tIcoe
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 00000000005DC050.000000006024F3F3.000061D5; Thu, 11 Feb 2021 10:08:03 +0100
To: Dave Crocker <dcrocker@gmail.com>, Douglas Foster <dougfoster.emailstandards@gmail.com>, Scott Kitterman <sklist@kitterman.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <20210203181226.9AB746D51182@ary.qy> <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com> <CAH48ZfxFsQ5ntE05QYRqP5P3Na6vuDjNAQKAdjZe7Kvt7evKuw@mail.gmail.com> <2285569.RditZUVBbg@zini-1880> <ea27d175-e436-fa40-0571-da1e0189d488@tana.it> <2244314.3GJdnAqG3q@zini-1880> <CAH48Zfynp=BVKXeyWO=KL=TVRiUDVuvckWDgpZFbVeVjBBqjaw@mail.gmail.com> <0d7de3eb-5b14-510c-cb4a-c78bc34610d8@gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <25831f17-5470-ff89-5108-2a4f1121c985@tana.it>
Date: Thu, 11 Feb 2021 10:08: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: <0d7de3eb-5b14-510c-cb4a-c78bc34610d8@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/GaPu_dV9gEm4w_GrVWJZGIYH19Y>
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, 11 Feb 2021 09:08:14 -0000

On Thu 11/Feb/2021 00:29:02 +0100 Dave Crocker wrote:
> On 2/10/2021 3:24 PM, Douglas Foster wrote:
>> Huh?  Are you asserting that SPF MAILFROM and SPF HELO are interchangeable?  
>>  They are not, but they can work together.


They are not but they could be.


> Perhaps I misread, but I thought I saw that this really is out of scope for 
> this working group.


  2. Reviewing and improving the base DMARC specification

The working group will not develop additional mail authentication
technologies, but may document desirable uses of existing authentication
technologies.


Best
Ale
-- 
















From nobody Thu Feb 11 03:36:04 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 0C8913A14E0 for <dmarc@ietfa.amsl.com>; Thu, 11 Feb 2021 03:36:03 -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 k4W2zNpRYSni for <dmarc@ietfa.amsl.com>; Thu, 11 Feb 2021 03:36:01 -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 9E7A33A14DF for <dmarc@ietf.org>; Thu, 11 Feb 2021 03:36:01 -0800 (PST)
Received: by mail-vk1-xa2a.google.com with SMTP id k1so1200766vkb.11 for <dmarc@ietf.org>; Thu, 11 Feb 2021 03:36: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;  bh=lnQo7wc36xcCDf1V6Vcuoy+hMqFW58H44xoJDZziuNg=; b=ggi7LLLBS7g2McDyGdi+gfNws3kiHCkhA8VlBLG7OnZ77+2Hdm8/l2q3zb4j9bF9N9 ouoF8wRzfxaoHtDBFM7O1sJETvxknWi9ui6yAXwhlN5OioAsR6QzMXyFDF2B9JLuEksM 6b5DKJRVyiuzEvqo0U9p2w7o1YtcOgAuOy6VkBGPmMT6i2xfty8bKT5+uaFNt75Mol2u Wi5m3ueeOE3cWhyPE5fWH4MiwTIOz4UeVK/2pZ/92a6+HahzREv7dZOeoUkOCWFBvket z5MJX7DJNnQ7Ha0LMLHB31fKn7CBQX5hFIxjwPzQhHWH2o+mPS8sFyT7BwTz13jFziQC 2f9Q==
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=lnQo7wc36xcCDf1V6Vcuoy+hMqFW58H44xoJDZziuNg=; b=B/W8I6a92WOVkKAfyQ01/PZovHr94KiFWXWVbewLqcLV7AH2PATXFaxo1cwLc2k48K 9tkcxpm+nGLMUrLLP77WJN9aPHhJ7owj1ALUAxgp4Qmh6djj4Cuoz0sRbe3ePfHlaOb5 eLpqpWhLrfD7NM7EjQtAMPxM5h0jBOivOKl79+dAWPmp7lMwYvSBDjUqhz+WFMC6sMmT rpPpliIz8Twag+NjbMIA90qdnc8oCLOr9yzVun9Xdhh4JJ81dHTjXOmuAt9cpbmu5OC2 vEoia8qnia1Cm/SJM1yswCuU9Nt95cZk74AuWaTWdtjBl9xyJJ3/34HhA7k0GKVnnueF XnPA==
X-Gm-Message-State: AOAM531gJR0uQ2GWOoG1yZDc5sL1sjzAgQWPUQY6am73ngLYqxrHafsE uZS51k6VjKElPPh3Vj6iMaOo69wdl4Iy4Wd+RKMOPXzozcV80Q==
X-Google-Smtp-Source: ABdhPJzLEWyUgahruEIJb2yj3FNh6Bghgjf1+9fVSBjzz31yytowxHHoTifWtem4dhDpuCsIxDx1A3kyaffVvVVXwFE=
X-Received: by 2002:a1f:4c45:: with SMTP id z66mr4523963vka.4.1613043359363; Thu, 11 Feb 2021 03:35:59 -0800 (PST)
MIME-Version: 1.0
References: <20210203181226.9AB746D51182@ary.qy> <CAHej_8k6DA8140QB2buaRCaJfc0U9fVSC=nSAu-dWsZshCRX_Q@mail.gmail.com> <CAH48ZfxFsQ5ntE05QYRqP5P3Na6vuDjNAQKAdjZe7Kvt7evKuw@mail.gmail.com> <2285569.RditZUVBbg@zini-1880> <ea27d175-e436-fa40-0571-da1e0189d488@tana.it> <2244314.3GJdnAqG3q@zini-1880> <CAH48Zfynp=BVKXeyWO=KL=TVRiUDVuvckWDgpZFbVeVjBBqjaw@mail.gmail.com> <0d7de3eb-5b14-510c-cb4a-c78bc34610d8@gmail.com>
In-Reply-To: <0d7de3eb-5b14-510c-cb4a-c78bc34610d8@gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Thu, 11 Feb 2021 06:35:49 -0500
Message-ID: <CAH48ZfwG+7t+inQ7-ijH71buUfTsYFtNPBvsCT266v8Yk0HDOg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000071347405bb0decb9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/-8Ttxjr9gcwWTqkErVJVSFcBnnk>
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, 11 Feb 2021 11:36:03 -0000

--00000000000071347405bb0decb9
Content-Type: text/plain; charset="UTF-8"

Applying SPF to DMARC could become out of scope, if we choose to remove SPF
from DMARC and make it dependent only on DKIM.   Until then, we need to
have a shared understanding of how SPF is applied.  This question asks
whether that shared understanding exists.

SPF involves two tests, which can be used together.   This WG can insist
that for DMARC purposes, only one can be used:

    "When the sender is not null, DMARC-evaluation only considers the SPF
evaluation of the MAILFROM Address.   SPF evaluation of HELO MUST NOT be
considered for DMARC purposes."

This wording seems implied by the current language, and by those who want
to leave it untouched.  Implication is different from specification, so our
document should make this explicit.   Unfortunately, an explicit MUST NOT
requirement is hard to justify.   When two domains are involved, and both
domains have published policy information, what justification exists for
ignoring some of the available security-related information?

If we back away from MUST NOT, then we have to consider that some
recipients MAY evaluate SPF HELO and SPF MAILFROM together, just as the SPF
RFC expected them to be used, and as outlined in one of my examples.    If
some recipients MAY evaluate HELO, then senders SHOULD take care to ensure
that HELO will generate a PASS.   Our language becomes something like this:

    "When the sender is not null, DMARC-evaluation always uses the SPF
evaluation of the MAILFROM Address.   Some recipients may evaluate SPF HELO
as well.   To maximize recipient trust, senders SHOULD publish an SPF
policy which ensures that both MAILFROM and HELO will produce SPF PASS
results."

DF

On Wed, Feb 10, 2021 at 6:29 PM Dave Crocker <dcrocker@gmail.com> wrote:

> On 2/10/2021 3:24 PM, Douglas Foster wrote:
> > Huh?  Are you asserting that SPF MAILFROM and SPF HELO are
> > interchangeable?   They are not, but they can work together.
>
>
> Perhaps I misread, but I thought I saw that this really is out of scope
> for this working group.
>
>
> d/
>
> --
> Dave Crocker
> dcrocker@gmail.com
> 408.329.0791
>
> Volunteer, Silicon Valley Chapter
> American Red Cross
> dave.crocker2@redcross.org
>
>

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

<div dir=3D"ltr">Applying SPF to DMARC could become out of scope, if we cho=
ose to remove SPF from DMARC and make it dependent only on DKIM.=C2=A0 =C2=
=A0Until then, we need to have a shared understanding of how SPF is applied=
.=C2=A0 This question asks whether that shared understanding exists.<div><b=
r></div><div>SPF involves two tests, which can be used together.=C2=A0 =C2=
=A0This WG can insist that for DMARC purposes, only=C2=A0one can be used:</=
div><div><br></div><div>=C2=A0 =C2=A0 &quot;When the sender is not null, DM=
ARC-evaluation only considers the SPF evaluation of the MAILFROM Address.=
=C2=A0 =C2=A0SPF evaluation=C2=A0of HELO MUST NOT be considered for DMARC p=
urposes.&quot;</div><div><br></div><div>This wording seems implied by the c=
urrent language, and by those who want to leave it untouched.=C2=A0 Implica=
tion is different from specification, so our document should make this expl=
icit.=C2=A0 =C2=A0Unfortunately, an explicit MUST NOT requirement is hard t=
o justify.=C2=A0 =C2=A0When two domains are involved, and both domains have=
 published policy information, what justification exists for ignoring some =
of the available security-related information?</div><div><br></div><div>If =
we back away from MUST NOT, then we have to consider that some recipients M=
AY evaluate SPF HELO and SPF MAILFROM together, just as the SPF RFC expecte=
d them to be used, and as outlined in one of my examples.=C2=A0 =C2=A0 If s=
ome recipients MAY evaluate HELO, then senders SHOULD take care to ensure t=
hat HELO will generate a PASS.=C2=A0 =C2=A0Our language becomes something l=
ike this:</div><div><br></div><div><div>=C2=A0 =C2=A0 &quot;When the sender=
 is not null,=20

DMARC-evaluation always uses the SPF evaluation of the MAILFROM Address.=C2=
=A0 =C2=A0Some recipients may evaluate SPF HELO as well.=C2=A0 =C2=A0To max=
imize recipient trust, senders SHOULD publish an SPF policy which ensures t=
hat both MAILFROM and HELO will produce SPF PASS results.&quot;</div><div><=
br></div><div>DF</div></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Wed, Feb 10, 2021 at 6:29 PM Dave Crocker =
&lt;<a href=3D"mailto:dcrocker@gmail.com">dcrocker@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">On 2/10/2021 3:=
24 PM, Douglas Foster wrote:<br>
&gt; Huh?=C2=A0 Are you=C2=A0asserting that SPF MAILFROM and SPF HELO are <=
br>
&gt; interchangeable?=C2=A0 =C2=A0They are not, but they=C2=A0can work toge=
ther.<br>
<br>
<br>
Perhaps I misread, but I thought I saw that this really is out of scope <br=
>
for this working group.<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>

--00000000000071347405bb0decb9--


From nobody Thu Feb 11 05:50:48 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 017083A15F6 for <dmarc@ietfa.amsl.com>; Thu, 11 Feb 2021 05:50:47 -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=zw+OOkbJ; dkim=pass (2048-bit key) header.d=kitterman.com header.b=Xk+yS4g7
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZbTCi-RHLtlf for <dmarc@ietfa.amsl.com>; Thu, 11 Feb 2021 05:50:45 -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 49A493A15F5 for <dmarc@ietf.org>; Thu, 11 Feb 2021 05:50:45 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 2CE61F802E4 for <dmarc@ietf.org>; Thu, 11 Feb 2021 08:50:43 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1613051442; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=lNDQke2ySePIjb7nMK9R5FJbucmC4t80KHZcb710aV4=; b=zw+OOkbJx/HIMrsFFoJ8BRkmwtUg18dvOnpqmrJc8aHoGqVpTmKEg9u0zP6n1mr3TK+Iu xTz7hNS/2M3G2S3Bg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1613051442; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=lNDQke2ySePIjb7nMK9R5FJbucmC4t80KHZcb710aV4=; b=Xk+yS4g7yegZBxRKzSn8owIuKySLUBC4LbtcrzopaRDiSQt5aDU/xyOjcAQARh/hqZXAE riEixM4pykYkxYjObnoBc67uZ4Ss96zWreG7luPUGcaxl3K82sLqDhqLcPrrHCFqJewCkdR UV7krjeqobj+gpQfiUgFhIRCJXFtxvwebCMV6pExpI8buZI7PyPJWxJGJv1WkqOeb0jNUFU 29yaFqgAGkJl/z3BywPUMyGFHe1SVmDr0R7TN0Q3of9n78WyFIXkYGL5YEjCGAmLzVpXUZT nWtHHPbMZ1dhqrLdceLJ+l1wTr/4UqNHJr8io/kX5g8DqfMtV1oO1LFFNkqQ==
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 D38B6F80026 for <dmarc@ietf.org>; Thu, 11 Feb 2021 08:50:42 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Thu, 11 Feb 2021 08:50:42 -0500
Message-ID: <5450463.gl6gDTMLP0@zini-1880>
In-Reply-To: <CAH48ZfwG+7t+inQ7-ijH71buUfTsYFtNPBvsCT266v8Yk0HDOg@mail.gmail.com>
References: <20210203181226.9AB746D51182@ary.qy> <0d7de3eb-5b14-510c-cb4a-c78bc34610d8@gmail.com> <CAH48ZfwG+7t+inQ7-ijH71buUfTsYFtNPBvsCT266v8Yk0HDOg@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/pX07-gLFX_o8bV2kGU_DfgjbXJU>
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, 11 Feb 2021 13:50:47 -0000

What problem are you purporting to solve?

By problem, I mean a case were a bad actor can get a DMARC pass result if SPF 
HELO results are allowed to be used that they couldn't already get with a mail 
from result.

I don't think such a case exists which is why I think this entire line of 
argument is a waste of time.

Scott K

On Thursday, February 11, 2021 6:35:49 AM EST Douglas Foster wrote:
> Applying SPF to DMARC could become out of scope, if we choose to remove SPF
> from DMARC and make it dependent only on DKIM.   Until then, we need to
> have a shared understanding of how SPF is applied.  This question asks
> whether that shared understanding exists.
> 
> SPF involves two tests, which can be used together.   This WG can insist
> that for DMARC purposes, only one can be used:
> 
>     "When the sender is not null, DMARC-evaluation only considers the SPF
> evaluation of the MAILFROM Address.   SPF evaluation of HELO MUST NOT be
> considered for DMARC purposes."
> 
> This wording seems implied by the current language, and by those who want
> to leave it untouched.  Implication is different from specification, so our
> document should make this explicit.   Unfortunately, an explicit MUST NOT
> requirement is hard to justify.   When two domains are involved, and both
> domains have published policy information, what justification exists for
> ignoring some of the available security-related information?
> 
> If we back away from MUST NOT, then we have to consider that some
> recipients MAY evaluate SPF HELO and SPF MAILFROM together, just as the SPF
> RFC expected them to be used, and as outlined in one of my examples.    If
> some recipients MAY evaluate HELO, then senders SHOULD take care to ensure
> that HELO will generate a PASS.   Our language becomes something like this:
> 
>     "When the sender is not null, DMARC-evaluation always uses the SPF
> evaluation of the MAILFROM Address.   Some recipients may evaluate SPF HELO
> as well.   To maximize recipient trust, senders SHOULD publish an SPF
> policy which ensures that both MAILFROM and HELO will produce SPF PASS
> results."
> 
> DF
> 
> On Wed, Feb 10, 2021 at 6:29 PM Dave Crocker <dcrocker@gmail.com> wrote:
> > On 2/10/2021 3:24 PM, Douglas Foster wrote:
> > > Huh?  Are you asserting that SPF MAILFROM and SPF HELO are
> > > interchangeable?   They are not, but they can work together.
> > 
> > Perhaps I misread, but I thought I saw that this really is out of scope
> > for this working group.
> > 
> > 
> > d/
> > 
> > --
> > Dave Crocker
> > dcrocker@gmail.com
> > 408.329.0791
> > 
> > Volunteer, Silicon Valley Chapter
> > American Red Cross
> > dave.crocker2@redcross.org





From nobody Thu Feb 11 20:24: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 31C563A11B9 for <dmarc@ietfa.amsl.com>; Thu, 11 Feb 2021 20:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=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=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 t_GYGuIWMslY for <dmarc@ietfa.amsl.com>; Thu, 11 Feb 2021 20:24:28 -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 EBC693A1133 for <dmarc@ietf.org>; Thu, 11 Feb 2021 20:24:27 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id a11so3468418vsm.7 for <dmarc@ietf.org>; Thu, 11 Feb 2021 20:24: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;  bh=5TbtbL9HZ903/E0Zizw6nNjEK0Wcb2aOrX/UJtUx5KY=; b=qrK3Eh8S1l5KVoTpLoNXfQ7DwMVmW1PaW5/Oqph4JbA6hAFYWgl1RLDe1On5ev6XCb nlA+ph6Mx7NFYm9bT13RWc/OqzHbcwhPqn/whMe9od+BiXVB+NI1W65bQYtSWZs8c5zh 0BFB5SPhugQaUl3XLFl3aZGtFrDMdRQAQ2BCrdrpDvLzsWp0rDrUBpAWfI+m9AHl94ur HDUmqUl0zOb5Xknze1eWT3dDm+jsEKJbfnkcHKA4NE1qSh0e0OsbLcpNLSsAv85RB6wu PoehAe6fwOs6sHGyQzH6R3H0zwITWacsEDTPXWiXXm4UZcBCXFCOEPYitOFN7ZMo59X5 p3pQ==
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=5TbtbL9HZ903/E0Zizw6nNjEK0Wcb2aOrX/UJtUx5KY=; b=rXibdyIlgwU+hc0LQQnG2uLbYWimc7KncEI1R9Zd3myfeT7lvBNb7pI1L4kLA1PFsk mbDhZE0InW+NdvXCb97VLf+NmN1B8Als0n/6WgysCyuo8Y33CqrX2PNsYz8nfuqnZw54 LsE0xE6q0s8s8g4AdV+trskKN1gBg7hLK/CH4B3+84YqGYGB7Fxv+9CxURjIuHKg97tL Oje6a3af2AtiZBaGnfXjqhdYSMCk/ONCjQgZU9Y0ImuM0ZAkqg+XLDrSGJj84p490YPf 7lpFXH5t+YWs/9o3YfudAfQVGIZ6ZYx3Wxhdw5KA3NhTsc7dTIx8kneBYPbeZIcApHNh J1Yg==
X-Gm-Message-State: AOAM531AhwpotscVljQ+7ApO5DuvUXrCrhdcW5xuiinagVrxdhQl2Pou H6umjWWf390q7dV1RLqk9zN6xqklKp209f4UECy8AOy1Aeo=
X-Google-Smtp-Source: ABdhPJzHH0EWmHcTmD+mgELbQc+bSeWEJt88oc9tGayxE6LIpuy2GsxjkKeG/EHKWnVyP4dYkcf3Dj4pSHt+CQP4P9k=
X-Received: by 2002:a67:e888:: with SMTP id x8mr450677vsn.59.1613103865798; Thu, 11 Feb 2021 20:24:25 -0800 (PST)
MIME-Version: 1.0
References: <20210203181226.9AB746D51182@ary.qy> <0d7de3eb-5b14-510c-cb4a-c78bc34610d8@gmail.com> <CAH48ZfwG+7t+inQ7-ijH71buUfTsYFtNPBvsCT266v8Yk0HDOg@mail.gmail.com> <5450463.gl6gDTMLP0@zini-1880>
In-Reply-To: <5450463.gl6gDTMLP0@zini-1880>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Thu, 11 Feb 2021 23:24:16 -0500
Message-ID: <CAH48ZfwyMGCam8Mdk=vrYcFaEU6z0RMUoY9LD8n8JWeNi_hCLg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e8211805bb1c025e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/aFxrTAchOEclF4Qx9aK70Fr46oA>
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, 12 Feb 2021 04:24:30 -0000

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

You missed my main point.   I will restate it, and then address your threat
question.

If there are N ways to establish authentication, then a recipient only
needs to choose one of them, but a sender who wants to be validated by all
recipients must implement all of them.   One purpose of the specification
is to constrain that complexity.

So the convenient solution would be to say that SPF HELO must be ignored,
except for null sender, because doing so reduces the number of variables
that must be considered by senders.   It is also probably consistent with
the logic of many current implementations.   I just do not believe that it
is justified to tell recipients that they MUST NOT evaluate SPF HELO when
MAILFROM is present.

An alternative would be to say that SPF HELO and SPF MAILFROM should both
be evaluated.   In the long run, this is arguably the best theoretical
solution, but the fear of short-term pain from false positives probably
makes this unattractive.

So, I am back to the only solution that seems justifiable:    Senders
SHOULD comply with both MAILFROM and HELO policies because SOME recipients
may evaluate both criteria, but many will only evaluate MAILFROM because
the incremental theoretical benefit seems less than the incremental cost.

- - -

To your point about threat vectors:  DMARC alignment is based on nested
layers of trust, and the trust is broken if you skip layers.  The server
operator provides a mail server environment to a mail domain, and the mail
domain provides delivery services for an author.

SPF proves that the mail domain (indicated by the MAILFROM address) really
uses the services of the server domain, and therefore the server (indicated
by IP address, HELO, and possibly ReverseDNS) is authorized to send
messages on behalf of the mail domain.

DMARC proves that the source server for the message was authorized to speak
on behalf of the author (indicated by the From address).

You suggest that if SPF HELO passes, and aligns with FROM, then we have
established that the server is authorized to speak for the author.   This
is true, but it does not establish that the mail domain in the MAILFROM
address has that right.

When the MAILFROM domain is different from the HELO domain, this implies
that that MAILFROM domain is a client of the server domain.   The server
domain has the right to emit messages for the client, but the client domain
does not have the right to email messages claiming to be from the server
domain.

- - -

It can be asserted that the server domain should be able to use its
firewall to prevent unauthorized servers from emitting mail, and should be
able to use its outbound gateway to prevent client domains from emitting
messages from the server domain, other clients, or any unrelated domain.
These commonly implemented measures could eliminate the need for checking
SPF HELO.   Why should others check what the sender should be able to do
for themselves?
Are we prepared to make this argument?   If so, then the existing wording
stands, but needs a solid justification.

DF

On Thu, Feb 11, 2021 at 8:50 AM Scott Kitterman <sklist@kitterman.com>
wrote:

> What problem are you purporting to solve?
>
> By problem, I mean a case were a bad actor can get a DMARC pass result if
> SPF
> HELO results are allowed to be used that they couldn't already get with a
> mail
> from result.
>
> I don't think such a case exists which is why I think this entire line of
> argument is a waste of time.
>
> Scott K
>
> On Thursday, February 11, 2021 6:35:49 AM EST Douglas Foster wrote:
> > Applying SPF to DMARC could become out of scope, if we choose to remove
> SPF
> > from DMARC and make it dependent only on DKIM.   Until then, we need to
> > have a shared understanding of how SPF is applied.  This question asks
> > whether that shared understanding exists.
> >
> > SPF involves two tests, which can be used together.   This WG can insist
> > that for DMARC purposes, only one can be used:
> >
> >     "When the sender is not null, DMARC-evaluation only considers the SPF
> > evaluation of the MAILFROM Address.   SPF evaluation of HELO MUST NOT be
> > considered for DMARC purposes."
> >
> > This wording seems implied by the current language, and by those who want
> > to leave it untouched.  Implication is different from specification, so
> our
> > document should make this explicit.   Unfortunately, an explicit MUST NOT
> > requirement is hard to justify.   When two domains are involved, and both
> > domains have published policy information, what justification exists for
> > ignoring some of the available security-related information?
> >
> > If we back away from MUST NOT, then we have to consider that some
> > recipients MAY evaluate SPF HELO and SPF MAILFROM together, just as the
> SPF
> > RFC expected them to be used, and as outlined in one of my examples.
> If
> > some recipients MAY evaluate HELO, then senders SHOULD take care to
> ensure
> > that HELO will generate a PASS.   Our language becomes something like
> this:
> >
> >     "When the sender is not null, DMARC-evaluation always uses the SPF
> > evaluation of the MAILFROM Address.   Some recipients may evaluate SPF
> HELO
> > as well.   To maximize recipient trust, senders SHOULD publish an SPF
> > policy which ensures that both MAILFROM and HELO will produce SPF PASS
> > results."
> >
> > DF
> >
> > On Wed, Feb 10, 2021 at 6:29 PM Dave Crocker <dcrocker@gmail.com> wrote:
> > > On 2/10/2021 3:24 PM, Douglas Foster wrote:
> > > > Huh?  Are you asserting that SPF MAILFROM and SPF HELO are
> > > > interchangeable?   They are not, but they can work together.
> > >
> > > Perhaps I misread, but I thought I saw that this really is out of scope
> > > for this working group.
> > >
> > >
> > > 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
>

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

<div dir=3D"ltr">You missed my main point.=C2=A0 =C2=A0I will restate it, a=
nd then address your threat question.<div><br></div><div>If there are N way=
s to establish authentication, then a recipient only needs to choose one of=
 them, but a sender who wants to be validated by all recipients must implem=
ent all of them.=C2=A0 =C2=A0One purpose of the specification is to constra=
in that complexity.<div><br></div><div>So the convenient solution would be =
to say that SPF HELO must be ignored, except for null sender, because doing=
 so reduces the number of variables that must be considered by senders.=C2=
=A0 =C2=A0It is also probably consistent with the logic of many current imp=
lementations.=C2=A0 =C2=A0I just do not believe that it is justified to tel=
l recipients that they MUST NOT evaluate SPF HELO when MAILFROM is present.=
</div><div><br></div><div>An alternative would be to say that SPF HELO and =
SPF MAILFROM should both be evaluated.=C2=A0 =C2=A0In the long run, this is=
 arguably the best theoretical solution, but the fear of short-term pain fr=
om false positives probably makes this unattractive.</div><div><br></div><d=
iv>So, I am back to the only solution that seems justifiable:=C2=A0 =C2=A0 =
Senders SHOULD comply with both MAILFROM and HELO policies because SOME rec=
ipients may evaluate both criteria, but many will only evaluate MAILFROM be=
cause the incremental theoretical benefit seems less than the incremental c=
ost.</div><div><br></div><div>- - -</div><div><br></div><div>To your point =
about threat vectors:=C2=A0 DMARC alignment is based on nested layers of tr=
ust, and the trust is broken if you skip layers.=C2=A0 The server operator =
provides a mail server environment to a mail domain, and the mail domain pr=
ovides delivery services for an author.=C2=A0 =C2=A0</div><div><br></div><d=
iv>SPF proves that the mail domain (indicated by the MAILFROM address) real=
ly uses the services of the server domain, and therefore the server (indica=
ted by IP address, HELO, and possibly ReverseDNS) is authorized to send mes=
sages on behalf of the mail domain.=C2=A0 =C2=A0</div><div><br></div><div>D=
MARC proves that the source server for the message was authorized to speak =
on behalf of the author (indicated by the From address).</div><div><br></di=
v><div>You suggest that if SPF HELO passes, and aligns with FROM, then we h=
ave established that the server is authorized to speak for the author.=C2=
=A0 =C2=A0This is true, but it does not establish that the mail domain in t=
he MAILFROM address has that right.=C2=A0 =C2=A0</div><div><br></div><div>W=
hen the MAILFROM domain is different from the HELO domain, this implies tha=
t that MAILFROM domain is a client of the server domain.=C2=A0 =C2=A0The se=
rver domain has the right to emit messages for the client, but the client d=
omain does not have the right to email messages claiming to be from the ser=
ver domain.</div><div><br></div><div>- - -</div><div><br></div><div>It can =
be asserted that the server domain should be able to use its firewall to pr=
event unauthorized servers from emitting mail, and should be able to use it=
s outbound gateway to prevent client domains from emitting messages from th=
e server domain, other clients, or any unrelated domain.=C2=A0 These common=
ly implemented measures could eliminate the need for checking SPF HELO.=C2=
=A0 =C2=A0Why should others check what the sender should be able to do for =
themselves?</div><div>Are we prepared to make this argument?=C2=A0 =C2=A0If=
 so, then the existing wording stands, but needs a solid justification.</di=
v></div><div><br></div><div>DF</div></div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Thu, Feb 11, 2021 at 8:50 AM Scott K=
itterman &lt;<a href=3D"mailto:sklist@kitterman.com">sklist@kitterman.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">Wh=
at problem are you purporting to solve?<br>
<br>
By problem, I mean a case were a bad actor can get a DMARC pass result if S=
PF <br>
HELO results are allowed to be used that they couldn&#39;t already get with=
 a mail <br>
from result.<br>
<br>
I don&#39;t think such a case exists which is why I think this entire line =
of <br>
argument is a waste of time.<br>
<br>
Scott K<br>
<br>
On Thursday, February 11, 2021 6:35:49 AM EST Douglas Foster wrote:<br>
&gt; Applying SPF to DMARC could become out of scope, if we choose to remov=
e SPF<br>
&gt; from DMARC and make it dependent only on DKIM.=C2=A0 =C2=A0Until then,=
 we need to<br>
&gt; have a shared understanding of how SPF is applied.=C2=A0 This question=
 asks<br>
&gt; whether that shared understanding exists.<br>
&gt; <br>
&gt; SPF involves two tests, which can be used together.=C2=A0 =C2=A0This W=
G can insist<br>
&gt; that for DMARC purposes, only one can be used:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&quot;When the sender is not null, DMARC-evaluation=
 only considers the SPF<br>
&gt; evaluation of the MAILFROM Address.=C2=A0 =C2=A0SPF evaluation of HELO=
 MUST NOT be<br>
&gt; considered for DMARC purposes.&quot;<br>
&gt; <br>
&gt; This wording seems implied by the current language, and by those who w=
ant<br>
&gt; to leave it untouched.=C2=A0 Implication is different from specificati=
on, so our<br>
&gt; document should make this explicit.=C2=A0 =C2=A0Unfortunately, an expl=
icit MUST NOT<br>
&gt; requirement is hard to justify.=C2=A0 =C2=A0When two domains are invol=
ved, and both<br>
&gt; domains have published policy information, what justification exists f=
or<br>
&gt; ignoring some of the available security-related information?<br>
&gt; <br>
&gt; If we back away from MUST NOT, then we have to consider that some<br>
&gt; recipients MAY evaluate SPF HELO and SPF MAILFROM together, just as th=
e SPF<br>
&gt; RFC expected them to be used, and as outlined in one of my examples.=
=C2=A0 =C2=A0 If<br>
&gt; some recipients MAY evaluate HELO, then senders SHOULD take care to en=
sure<br>
&gt; that HELO will generate a PASS.=C2=A0 =C2=A0Our language becomes somet=
hing like this:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&quot;When the sender is not null, DMARC-evaluation=
 always uses the SPF<br>
&gt; evaluation of the MAILFROM Address.=C2=A0 =C2=A0Some recipients may ev=
aluate SPF HELO<br>
&gt; as well.=C2=A0 =C2=A0To maximize recipient trust, senders SHOULD publi=
sh an SPF<br>
&gt; policy which ensures that both MAILFROM and HELO will produce SPF PASS=
<br>
&gt; results.&quot;<br>
&gt; <br>
&gt; DF<br>
&gt; <br>
&gt; On Wed, Feb 10, 2021 at 6:29 PM Dave Crocker &lt;<a href=3D"mailto:dcr=
ocker@gmail.com" target=3D"_blank">dcrocker@gmail.com</a>&gt; wrote:<br>
&gt; &gt; On 2/10/2021 3:24 PM, Douglas Foster wrote:<br>
&gt; &gt; &gt; Huh?=C2=A0 Are you asserting that SPF MAILFROM and SPF HELO =
are<br>
&gt; &gt; &gt; interchangeable?=C2=A0 =C2=A0They are not, but they can work=
 together.<br>
&gt; &gt; <br>
&gt; &gt; Perhaps I misread, but I thought I saw that this really is out of=
 scope<br>
&gt; &gt; for this working group.<br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; d/<br>
&gt; &gt; <br>
&gt; &gt; --<br>
&gt; &gt; Dave Crocker<br>
&gt; &gt; <a href=3D"mailto:dcrocker@gmail.com" target=3D"_blank">dcrocker@=
gmail.com</a><br>
&gt; &gt; 408.329.0791<br>
&gt; &gt; <br>
&gt; &gt; Volunteer, Silicon Valley Chapter<br>
&gt; &gt; American Red Cross<br>
&gt; &gt; <a href=3D"mailto:dave.crocker2@redcross.org" target=3D"_blank">d=
ave.crocker2@redcross.org</a><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>

--000000000000e8211805bb1c025e--


From nobody Fri Feb 12 10:01:56 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 8B7BC3A1858 for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 10:01:47 -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=Z/MmmFIP; dkim=pass (2048-bit key) header.d=kitterman.com header.b=lbWQ3ysk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hW84PlmeaYZi for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 10:01:45 -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 E78A13A1844 for <dmarc@ietf.org>; Fri, 12 Feb 2021 10:01:44 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id AECADF80271 for <dmarc@ietf.org>; Fri, 12 Feb 2021 13:01:43 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1613152903; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=JTOcIAHyqI4UkqTN88g8rSjUhb3JfpkIH4PmLcJ/jdU=; b=Z/MmmFIPgjHZjzbBo4Ogueb5r28jpBcxZaYVHMFOmfamqGMtNUBggIrlKFc2fFNGNPSPd 329X2JaEFdq0fwDBw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1613152903; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=JTOcIAHyqI4UkqTN88g8rSjUhb3JfpkIH4PmLcJ/jdU=; b=lbWQ3yskJ28Eer8IOiWf9fah5YWEHkCy6L6Xe+WVHcJH3kGsXv7r+evEnd/EuRRsSk7lW kpr2ftrAmcvL1DOMNJ13fYIPoRx3JbA0vJyErooxcYFe39YGKPjMWD41/JoSq/YZcNORinb VUr+zG5hZqbPnPMe1kGFYuJ6XAMvF5FCv9J0fiUeeQOU/bHPp1ZuuwGMFg7avhfH5cdbGB1 vY9Bm8yfyuLweiDtrqOL4asyn1i+TRIU1JsUug/GJlgNmR8kE8MTUwWxWRuUkvjOGcKnfM/ OX22vFrsAtz7DLi2Nz6fGOJ76NdW6PedyTxvGas4tEQpnQiIuchKwyVQJEog==
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 69A19F80218 for <dmarc@ietf.org>; Fri, 12 Feb 2021 13:01:43 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Fri, 12 Feb 2021 13:01:43 -0500
Message-ID: <3044649.0BfFdxGTVy@zini-1880>
In-Reply-To: <CAH48ZfwyMGCam8Mdk=vrYcFaEU6z0RMUoY9LD8n8JWeNi_hCLg@mail.gmail.com>
References: <20210203181226.9AB746D51182@ary.qy> <5450463.gl6gDTMLP0@zini-1880> <CAH48ZfwyMGCam8Mdk=vrYcFaEU6z0RMUoY9LD8n8JWeNi_hCLg@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/ry6EkjdURjvXIyHl_R3M40195x8>
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, 12 Feb 2021 18:01:54 -0000

I didn't miss it.  I don't think it's meaningful.

In the real world, outside the IETF one of three things happens:

1.  Everything works fine.

2.  Someone depends on HELO evaluation of SPF and discovers from evaluating 
the feedback reports that's it's a problem and then doesn't to that anymore.

3.  Someone depends on HELO evaluation of SPF and doesn't discover it's a 
problem because they don't look at their feedback reports.

For case 1 and 2, there's no issue.

Case 3 doesn't care if their mail gets delivered, so its fine.

This excessive focus on irrelevant minutia is harmful to the IETF.  It makes 
participation less interesting for technically capable contributors and 
reduces the overall value of the discourse.

Many people have suggested we move on.  My prediction is you won't, but this 
is my last email on the topic.

Scott K

On Thursday, February 11, 2021 11:24:16 PM EST Douglas Foster wrote:
> You missed my main point.   I will restate it, and then address your threat
> question.
> 
> If there are N ways to establish authentication, then a recipient only
> needs to choose one of them, but a sender who wants to be validated by all
> recipients must implement all of them.   One purpose of the specification
> is to constrain that complexity.
> 
> So the convenient solution would be to say that SPF HELO must be ignored,
> except for null sender, because doing so reduces the number of variables
> that must be considered by senders.   It is also probably consistent with
> the logic of many current implementations.   I just do not believe that it
> is justified to tell recipients that they MUST NOT evaluate SPF HELO when
> MAILFROM is present.
> 
> An alternative would be to say that SPF HELO and SPF MAILFROM should both
> be evaluated.   In the long run, this is arguably the best theoretical
> solution, but the fear of short-term pain from false positives probably
> makes this unattractive.
> 
> So, I am back to the only solution that seems justifiable:    Senders
> SHOULD comply with both MAILFROM and HELO policies because SOME recipients
> may evaluate both criteria, but many will only evaluate MAILFROM because
> the incremental theoretical benefit seems less than the incremental cost.
> 
> - - -
> 
> To your point about threat vectors:  DMARC alignment is based on nested
> layers of trust, and the trust is broken if you skip layers.  The server
> operator provides a mail server environment to a mail domain, and the mail
> domain provides delivery services for an author.
> 
> SPF proves that the mail domain (indicated by the MAILFROM address) really
> uses the services of the server domain, and therefore the server (indicated
> by IP address, HELO, and possibly ReverseDNS) is authorized to send
> messages on behalf of the mail domain.
> 
> DMARC proves that the source server for the message was authorized to speak
> on behalf of the author (indicated by the From address).
> 
> You suggest that if SPF HELO passes, and aligns with FROM, then we have
> established that the server is authorized to speak for the author.   This
> is true, but it does not establish that the mail domain in the MAILFROM
> address has that right.
> 
> When the MAILFROM domain is different from the HELO domain, this implies
> that that MAILFROM domain is a client of the server domain.   The server
> domain has the right to emit messages for the client, but the client domain
> does not have the right to email messages claiming to be from the server
> domain.
> 
> - - -
> 
> It can be asserted that the server domain should be able to use its
> firewall to prevent unauthorized servers from emitting mail, and should be
> able to use its outbound gateway to prevent client domains from emitting
> messages from the server domain, other clients, or any unrelated domain.
> These commonly implemented measures could eliminate the need for checking
> SPF HELO.   Why should others check what the sender should be able to do
> for themselves?
> Are we prepared to make this argument?   If so, then the existing wording
> stands, but needs a solid justification.
> 
> DF
> 
> On Thu, Feb 11, 2021 at 8:50 AM Scott Kitterman <sklist@kitterman.com>
> 
> wrote:
> > What problem are you purporting to solve?
> > 
> > By problem, I mean a case were a bad actor can get a DMARC pass result if
> > SPF
> > HELO results are allowed to be used that they couldn't already get with a
> > mail
> > from result.
> > 
> > I don't think such a case exists which is why I think this entire line of
> > argument is a waste of time.
> > 
> > Scott K
> > 
> > On Thursday, February 11, 2021 6:35:49 AM EST Douglas Foster wrote:
> > > Applying SPF to DMARC could become out of scope, if we choose to remove
> > 
> > SPF
> > 
> > > from DMARC and make it dependent only on DKIM.   Until then, we need to
> > > have a shared understanding of how SPF is applied.  This question asks
> > > whether that shared understanding exists.
> > > 
> > > SPF involves two tests, which can be used together.   This WG can insist
> > > 
> > > that for DMARC purposes, only one can be used:
> > >     "When the sender is not null, DMARC-evaluation only considers the
> > >     SPF
> > > 
> > > evaluation of the MAILFROM Address.   SPF evaluation of HELO MUST NOT be
> > > considered for DMARC purposes."
> > > 
> > > This wording seems implied by the current language, and by those who
> > > want
> > > to leave it untouched.  Implication is different from specification, so
> > 
> > our
> > 
> > > document should make this explicit.   Unfortunately, an explicit MUST
> > > NOT
> > > requirement is hard to justify.   When two domains are involved, and
> > > both
> > > domains have published policy information, what justification exists for
> > > ignoring some of the available security-related information?
> > > 
> > > If we back away from MUST NOT, then we have to consider that some
> > > recipients MAY evaluate SPF HELO and SPF MAILFROM together, just as the
> > 
> > SPF
> > 
> > > RFC expected them to be used, and as outlined in one of my examples.
> > 
> > If
> > 
> > > some recipients MAY evaluate HELO, then senders SHOULD take care to
> > 
> > ensure
> > 
> > > that HELO will generate a PASS.   Our language becomes something like
> > 
> > this:
> > >     "When the sender is not null, DMARC-evaluation always uses the SPF
> > > 
> > > evaluation of the MAILFROM Address.   Some recipients may evaluate SPF
> > 
> > HELO
> > 
> > > as well.   To maximize recipient trust, senders SHOULD publish an SPF
> > > policy which ensures that both MAILFROM and HELO will produce SPF PASS
> > > results."
> > > 
> > > DF
> > > 
> > > On Wed, Feb 10, 2021 at 6:29 PM Dave Crocker <dcrocker@gmail.com> wrote:
> > > > On 2/10/2021 3:24 PM, Douglas Foster wrote:
> > > > > Huh?  Are you asserting that SPF MAILFROM and SPF HELO are
> > > > > interchangeable?   They are not, but they can work together.
> > > > 
> > > > Perhaps I misread, but I thought I saw that this really is out of
> > > > scope
> > > > for this working group.
> > > > 
> > > > 
> > > > 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 Fri Feb 12 10:08:03 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 26EC93A184C for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 10:08:00 -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 cLLXsOYm3GWb for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 10:07:57 -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 600A13A1804 for <dmarc@ietf.org>; Fri, 12 Feb 2021 10:07:57 -0800 (PST)
Received: by mail-vs1-xe29.google.com with SMTP id l192so52978vsd.5 for <dmarc@ietf.org>; Fri, 12 Feb 2021 10:07:57 -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=bMkjcITV6QkXnsABw7z/fztkerKKQa/eurn0cL+3eHk=; b=AUcMTJALxxQa4dbP8WIEkQhxvChx3sPd4gAVhCatcxBOyF5dVeSgoiUjRTTd0YuHj1 Kx1AZjpnk8tS4vEZzUcNKNYXO6YnW88cGwe5AGFwpW1l/mdek8ONTLwjAubMf7M7dS3Y 3HsnVLmHqNyCuK4eKWyBWaXTv0flDk8nRc9KFbqhzIExGnkrGJhXrq8M2UAq5FE59vx6 6SuIR0fwg7L6IN6ebwEzYu8HRPZ8NMdzHgYVG+k0Ar1rdi/ZS+niMQKMePTwHRe3+915 MLUHCIE5yfVkl/yjRNaga8ggYXV3cM+re6XONtGK6sSSrNyWAN8xDjXiWlJ0BUi8Wbg4 07lA==
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=bMkjcITV6QkXnsABw7z/fztkerKKQa/eurn0cL+3eHk=; b=Uu23LAyHom+X0NPn+ojbC9S4cvZbc5mTyyXtojgrbKa8t2GJlZhctDKJzeoLppsnb/ Wk5U1WQS4rzUrSL+/kcsh+lm9ogqHe4D1rH2DhKGV6vCgEzYvpwWfOUbzqwRZad5lbnT b8D2VEUQdYjTolu3wOAdH4P61RR622vf1A3lHQXAHGoZZ0FlVCuFA8ueiObgIYbwIMrU io/1tWjlxB8QL56WcXGJ0ZrAhHogx2h0i1j2x5/voeI8OZTUuxHp/gzWVTEzfecw/16e GFOQshatKJ3JePXZjuLg+/pfjBt5HKazKOyi7XER6T2o7OJrFY3G3gNvt+ZKf96HlYay fLXA==
X-Gm-Message-State: AOAM530FH37B5kUWstwmxK92SEmm8jcS7V3qCP46WFjLz9GtLqgdKGNi OKbdcVnMVktnI0NhTnhnGGaBx93IG7aEUahJk8zOmQ==
X-Google-Smtp-Source: ABdhPJw1c8qPbNtPkzpjdB23NsbsLJqOptzbckLJhODgAVBa6/t0yWhpj3PV96BoK7zJCEMVcIfDNDt3uDMpsbhk79w=
X-Received: by 2002:a67:ed84:: with SMTP id d4mr2552317vsp.52.1613153276215; Fri, 12 Feb 2021 10:07:56 -0800 (PST)
MIME-Version: 1.0
References: <20210203181226.9AB746D51182@ary.qy> <5450463.gl6gDTMLP0@zini-1880> <CAH48ZfwyMGCam8Mdk=vrYcFaEU6z0RMUoY9LD8n8JWeNi_hCLg@mail.gmail.com> <3044649.0BfFdxGTVy@zini-1880>
In-Reply-To: <3044649.0BfFdxGTVy@zini-1880>
From: Seth Blank <seth@valimail.com>
Date: Fri, 12 Feb 2021 10:07:44 -0800
Message-ID: <CAOZAAfM1yq9=iScEAwGzJT5bRMXT0VCCC1NLFBoQdtufvUmDHA@mail.gmail.com>
To: Scott Kitterman <sklist@kitterman.com>,  Douglas Foster <dougfoster.emailstandards@gmail.com>, Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>, John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary="000000000000ff59e305bb27831f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/OTBQSju5ZxwJ1WzgzHmpBdfBMkc>
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, 12 Feb 2021 18:08:00 -0000

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

As an individual, +1000 to Scott.

As Chair, this thread is unproductive, and two months passed due date to
resolve. Consensus seems clear that there isn't an issue here. If there's a
clear use case that hasn't been communicated, share it now or move on.

Seth

On Fri, Feb 12, 2021 at 10:02 AM Scott Kitterman <sklist@kitterman.com>
wrote:

> I didn't miss it.  I don't think it's meaningful.
>
> In the real world, outside the IETF one of three things happens:
>
> 1.  Everything works fine.
>
> 2.  Someone depends on HELO evaluation of SPF and discovers from
> evaluating
> the feedback reports that's it's a problem and then doesn't to that
> anymore.
>
> 3.  Someone depends on HELO evaluation of SPF and doesn't discover it's a
> problem because they don't look at their feedback reports.
>
> For case 1 and 2, there's no issue.
>
> Case 3 doesn't care if their mail gets delivered, so its fine.
>
> This excessive focus on irrelevant minutia is harmful to the IETF.  It
> makes
> participation less interesting for technically capable contributors and
> reduces the overall value of the discourse.
>
> Many people have suggested we move on.  My prediction is you won't, but
> this
> is my last email on the topic.
>
> Scott K
>
> On Thursday, February 11, 2021 11:24:16 PM EST Douglas Foster wrote:
> > You missed my main point.   I will restate it, and then address your
> threat
> > question.
> >
> > If there are N ways to establish authentication, then a recipient only
> > needs to choose one of them, but a sender who wants to be validated by
> all
> > recipients must implement all of them.   One purpose of the specification
> > is to constrain that complexity.
> >
> > So the convenient solution would be to say that SPF HELO must be ignored,
> > except for null sender, because doing so reduces the number of variables
> > that must be considered by senders.   It is also probably consistent with
> > the logic of many current implementations.   I just do not believe that
> it
> > is justified to tell recipients that they MUST NOT evaluate SPF HELO when
> > MAILFROM is present.
> >
> > An alternative would be to say that SPF HELO and SPF MAILFROM should both
> > be evaluated.   In the long run, this is arguably the best theoretical
> > solution, but the fear of short-term pain from false positives probably
> > makes this unattractive.
> >
> > So, I am back to the only solution that seems justifiable:    Senders
> > SHOULD comply with both MAILFROM and HELO policies because SOME
> recipients
> > may evaluate both criteria, but many will only evaluate MAILFROM because
> > the incremental theoretical benefit seems less than the incremental cost.
> >
> > - - -
> >
> > To your point about threat vectors:  DMARC alignment is based on nested
> > layers of trust, and the trust is broken if you skip layers.  The server
> > operator provides a mail server environment to a mail domain, and the
> mail
> > domain provides delivery services for an author.
> >
> > SPF proves that the mail domain (indicated by the MAILFROM address)
> really
> > uses the services of the server domain, and therefore the server
> (indicated
> > by IP address, HELO, and possibly ReverseDNS) is authorized to send
> > messages on behalf of the mail domain.
> >
> > DMARC proves that the source server for the message was authorized to
> speak
> > on behalf of the author (indicated by the From address).
> >
> > You suggest that if SPF HELO passes, and aligns with FROM, then we have
> > established that the server is authorized to speak for the author.   This
> > is true, but it does not establish that the mail domain in the MAILFROM
> > address has that right.
> >
> > When the MAILFROM domain is different from the HELO domain, this implies
> > that that MAILFROM domain is a client of the server domain.   The server
> > domain has the right to emit messages for the client, but the client
> domain
> > does not have the right to email messages claiming to be from the server
> > domain.
> >
> > - - -
> >
> > It can be asserted that the server domain should be able to use its
> > firewall to prevent unauthorized servers from emitting mail, and should
> be
> > able to use its outbound gateway to prevent client domains from emitting
> > messages from the server domain, other clients, or any unrelated domain.
> > These commonly implemented measures could eliminate the need for checking
> > SPF HELO.   Why should others check what the sender should be able to do
> > for themselves?
> > Are we prepared to make this argument?   If so, then the existing wording
> > stands, but needs a solid justification.
> >
> > DF
> >
> > On Thu, Feb 11, 2021 at 8:50 AM Scott Kitterman <sklist@kitterman.com>
> >
> > wrote:
> > > What problem are you purporting to solve?
> > >
> > > By problem, I mean a case were a bad actor can get a DMARC pass result
> if
> > > SPF
> > > HELO results are allowed to be used that they couldn't already get
> with a
> > > mail
> > > from result.
> > >
> > > I don't think such a case exists which is why I think this entire line
> of
> > > argument is a waste of time.
> > >
> > > Scott K
> > >
> > > On Thursday, February 11, 2021 6:35:49 AM EST Douglas Foster wrote:
> > > > Applying SPF to DMARC could become out of scope, if we choose to
> remove
> > >
> > > SPF
> > >
> > > > from DMARC and make it dependent only on DKIM.   Until then, we need
> to
> > > > have a shared understanding of how SPF is applied.  This question
> asks
> > > > whether that shared understanding exists.
> > > >
> > > > SPF involves two tests, which can be used together.   This WG can
> insist
> > > >
> > > > that for DMARC purposes, only one can be used:
> > > >     "When the sender is not null, DMARC-evaluation only considers the
> > > >     SPF
> > > >
> > > > evaluation of the MAILFROM Address.   SPF evaluation of HELO MUST
> NOT be
> > > > considered for DMARC purposes."
> > > >
> > > > This wording seems implied by the current language, and by those who
> > > > want
> > > > to leave it untouched.  Implication is different from specification,
> so
> > >
> > > our
> > >
> > > > document should make this explicit.   Unfortunately, an explicit MUST
> > > > NOT
> > > > requirement is hard to justify.   When two domains are involved, and
> > > > both
> > > > domains have published policy information, what justification exists
> for
> > > > ignoring some of the available security-related information?
> > > >
> > > > If we back away from MUST NOT, then we have to consider that some
> > > > recipients MAY evaluate SPF HELO and SPF MAILFROM together, just as
> the
> > >
> > > SPF
> > >
> > > > RFC expected them to be used, and as outlined in one of my examples.
> > >
> > > If
> > >
> > > > some recipients MAY evaluate HELO, then senders SHOULD take care to
> > >
> > > ensure
> > >
> > > > that HELO will generate a PASS.   Our language becomes something like
> > >
> > > this:
> > > >     "When the sender is not null, DMARC-evaluation always uses the
> SPF
> > > >
> > > > evaluation of the MAILFROM Address.   Some recipients may evaluate
> SPF
> > >
> > > HELO
> > >
> > > > as well.   To maximize recipient trust, senders SHOULD publish an SPF
> > > > policy which ensures that both MAILFROM and HELO will produce SPF
> PASS
> > > > results."
> > > >
> > > > DF
> > > >
> > > > On Wed, Feb 10, 2021 at 6:29 PM Dave Crocker <dcrocker@gmail.com>
> wrote:
> > > > > On 2/10/2021 3:24 PM, Douglas Foster wrote:
> > > > > > Huh?  Are you asserting that SPF MAILFROM and SPF HELO are
> > > > > > interchangeable?   They are not, but they can work together.
> > > > >
> > > > > Perhaps I misread, but I thought I saw that this really is out of
> > > > > scope
> > > > > for this working group.
> > > > >
> > > > >
> > > > > 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
>
>
>
>
> _______________________________________________
> 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.

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

<div dir=3D"ltr">As an individual,=C2=A0+1000 to Scott.<div><br></div><div>=
As Chair, this thread is unproductive, and two months passed due date to re=
solve. Consensus seems clear that there isn&#39;t an issue here. If there&#=
39;s a clear use case that hasn&#39;t been communicated, share it now or mo=
ve on.</div><div><br></div><div>Seth</div></div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 12, 2021 at 10:02 AM =
Scott Kitterman &lt;<a href=3D"mailto:sklist@kitterman.com">sklist@kitterma=
n.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">I didn&#39;t miss it.=C2=A0 I don&#39;t think it&#39;s meaningful.<br>
<br>
In the real world, outside the IETF one of three things happens:<br>
<br>
1.=C2=A0 Everything works fine.<br>
<br>
2.=C2=A0 Someone depends on HELO evaluation of SPF and discovers from evalu=
ating <br>
the feedback reports that&#39;s it&#39;s a problem and then doesn&#39;t to =
that anymore.<br>
<br>
3.=C2=A0 Someone depends on HELO evaluation of SPF and doesn&#39;t discover=
 it&#39;s a <br>
problem because they don&#39;t look at their feedback reports.<br>
<br>
For case 1 and 2, there&#39;s no issue.<br>
<br>
Case 3 doesn&#39;t care if their mail gets delivered, so its fine.<br>
<br>
This excessive focus on irrelevant minutia is harmful to the IETF.=C2=A0 It=
 makes <br>
participation less interesting for technically capable contributors and <br=
>
reduces the overall value of the discourse.<br>
<br>
Many people have suggested we move on.=C2=A0 My prediction is you won&#39;t=
, but this <br>
is my last email on the topic.<br>
<br>
Scott K<br>
<br>
On Thursday, February 11, 2021 11:24:16 PM EST Douglas Foster wrote:<br>
&gt; You missed my main point.=C2=A0 =C2=A0I will restate it, and then addr=
ess your threat<br>
&gt; question.<br>
&gt; <br>
&gt; If there are N ways to establish authentication, then a recipient only=
<br>
&gt; needs to choose one of them, but a sender who wants to be validated by=
 all<br>
&gt; recipients must implement all of them.=C2=A0 =C2=A0One purpose of the =
specification<br>
&gt; is to constrain that complexity.<br>
&gt; <br>
&gt; So the convenient solution would be to say that SPF HELO must be ignor=
ed,<br>
&gt; except for null sender, because doing so reduces the number of variabl=
es<br>
&gt; that must be considered by senders.=C2=A0 =C2=A0It is also probably co=
nsistent with<br>
&gt; the logic of many current implementations.=C2=A0 =C2=A0I just do not b=
elieve that it<br>
&gt; is justified to tell recipients that they MUST NOT evaluate SPF HELO w=
hen<br>
&gt; MAILFROM is present.<br>
&gt; <br>
&gt; An alternative would be to say that SPF HELO and SPF MAILFROM should b=
oth<br>
&gt; be evaluated.=C2=A0 =C2=A0In the long run, this is arguably the best t=
heoretical<br>
&gt; solution, but the fear of short-term pain from false positives probabl=
y<br>
&gt; makes this unattractive.<br>
&gt; <br>
&gt; So, I am back to the only solution that seems justifiable:=C2=A0 =C2=
=A0 Senders<br>
&gt; SHOULD comply with both MAILFROM and HELO policies because SOME recipi=
ents<br>
&gt; may evaluate both criteria, but many will only evaluate MAILFROM becau=
se<br>
&gt; the incremental theoretical benefit seems less than the incremental co=
st.<br>
&gt; <br>
&gt; - - -<br>
&gt; <br>
&gt; To your point about threat vectors:=C2=A0 DMARC alignment is based on =
nested<br>
&gt; layers of trust, and the trust is broken if you skip layers.=C2=A0 The=
 server<br>
&gt; operator provides a mail server environment to a mail domain, and the =
mail<br>
&gt; domain provides delivery services for an author.<br>
&gt; <br>
&gt; SPF proves that the mail domain (indicated by the MAILFROM address) re=
ally<br>
&gt; uses the services of the server domain, and therefore the server (indi=
cated<br>
&gt; by IP address, HELO, and possibly ReverseDNS) is authorized to send<br=
>
&gt; messages on behalf of the mail domain.<br>
&gt; <br>
&gt; DMARC proves that the source server for the message was authorized to =
speak<br>
&gt; on behalf of the author (indicated by the From address).<br>
&gt; <br>
&gt; You suggest that if SPF HELO passes, and aligns with FROM, then we hav=
e<br>
&gt; established that the server is authorized to speak for the author.=C2=
=A0 =C2=A0This<br>
&gt; is true, but it does not establish that the mail domain in the MAILFRO=
M<br>
&gt; address has that right.<br>
&gt; <br>
&gt; When the MAILFROM domain is different from the HELO domain, this impli=
es<br>
&gt; that that MAILFROM domain is a client of the server domain.=C2=A0 =C2=
=A0The server<br>
&gt; domain has the right to emit messages for the client, but the client d=
omain<br>
&gt; does not have the right to email messages claiming to be from the serv=
er<br>
&gt; domain.<br>
&gt; <br>
&gt; - - -<br>
&gt; <br>
&gt; It can be asserted that the server domain should be able to use its<br=
>
&gt; firewall to prevent unauthorized servers from emitting mail, and shoul=
d be<br>
&gt; able to use its outbound gateway to prevent client domains from emitti=
ng<br>
&gt; messages from the server domain, other clients, or any unrelated domai=
n.<br>
&gt; These commonly implemented measures could eliminate the need for check=
ing<br>
&gt; SPF HELO.=C2=A0 =C2=A0Why should others check what the sender should b=
e able to do<br>
&gt; for themselves?<br>
&gt; Are we prepared to make this argument?=C2=A0 =C2=A0If so, then the exi=
sting wording<br>
&gt; stands, but needs a solid justification.<br>
&gt; <br>
&gt; DF<br>
&gt; <br>
&gt; On Thu, Feb 11, 2021 at 8:50 AM Scott Kitterman &lt;<a href=3D"mailto:=
sklist@kitterman.com" target=3D"_blank">sklist@kitterman.com</a>&gt;<br>
&gt; <br>
&gt; wrote:<br>
&gt; &gt; What problem are you purporting to solve?<br>
&gt; &gt; <br>
&gt; &gt; By problem, I mean a case were a bad actor can get a DMARC pass r=
esult if<br>
&gt; &gt; SPF<br>
&gt; &gt; HELO results are allowed to be used that they couldn&#39;t alread=
y get with a<br>
&gt; &gt; mail<br>
&gt; &gt; from result.<br>
&gt; &gt; <br>
&gt; &gt; I don&#39;t think such a case exists which is why I think this en=
tire line of<br>
&gt; &gt; argument is a waste of time.<br>
&gt; &gt; <br>
&gt; &gt; Scott K<br>
&gt; &gt; <br>
&gt; &gt; On Thursday, February 11, 2021 6:35:49 AM EST Douglas Foster wrot=
e:<br>
&gt; &gt; &gt; Applying SPF to DMARC could become out of scope, if we choos=
e to remove<br>
&gt; &gt; <br>
&gt; &gt; SPF<br>
&gt; &gt; <br>
&gt; &gt; &gt; from DMARC and make it dependent only on DKIM.=C2=A0 =C2=A0U=
ntil then, we need to<br>
&gt; &gt; &gt; have a shared understanding of how SPF is applied.=C2=A0 Thi=
s question asks<br>
&gt; &gt; &gt; whether that shared understanding exists.<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; SPF involves two tests, which can be used together.=C2=A0 =
=C2=A0This WG can insist<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; that for DMARC purposes, only one can be used:<br>
&gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0&quot;When the sender is not null, DMARC-=
evaluation only considers the<br>
&gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0SPF<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; evaluation of the MAILFROM Address.=C2=A0 =C2=A0SPF evaluati=
on of HELO MUST NOT be<br>
&gt; &gt; &gt; considered for DMARC purposes.&quot;<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; This wording seems implied by the current language, and by t=
hose who<br>
&gt; &gt; &gt; want<br>
&gt; &gt; &gt; to leave it untouched.=C2=A0 Implication is different from s=
pecification, so<br>
&gt; &gt; <br>
&gt; &gt; our<br>
&gt; &gt; <br>
&gt; &gt; &gt; document should make this explicit.=C2=A0 =C2=A0Unfortunatel=
y, an explicit MUST<br>
&gt; &gt; &gt; NOT<br>
&gt; &gt; &gt; requirement is hard to justify.=C2=A0 =C2=A0When two domains=
 are involved, and<br>
&gt; &gt; &gt; both<br>
&gt; &gt; &gt; domains have published policy information, what justificatio=
n exists for<br>
&gt; &gt; &gt; ignoring some of the available security-related information?=
<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; If we back away from MUST NOT, then we have to consider that=
 some<br>
&gt; &gt; &gt; recipients MAY evaluate SPF HELO and SPF MAILFROM together, =
just as the<br>
&gt; &gt; <br>
&gt; &gt; SPF<br>
&gt; &gt; <br>
&gt; &gt; &gt; RFC expected them to be used, and as outlined in one of my e=
xamples.<br>
&gt; &gt; <br>
&gt; &gt; If<br>
&gt; &gt; <br>
&gt; &gt; &gt; some recipients MAY evaluate HELO, then senders SHOULD take =
care to<br>
&gt; &gt; <br>
&gt; &gt; ensure<br>
&gt; &gt; <br>
&gt; &gt; &gt; that HELO will generate a PASS.=C2=A0 =C2=A0Our language bec=
omes something like<br>
&gt; &gt; <br>
&gt; &gt; this:<br>
&gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0&quot;When the sender is not null, DMARC-=
evaluation always uses the SPF<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; evaluation of the MAILFROM Address.=C2=A0 =C2=A0Some recipie=
nts may evaluate SPF<br>
&gt; &gt; <br>
&gt; &gt; HELO<br>
&gt; &gt; <br>
&gt; &gt; &gt; as well.=C2=A0 =C2=A0To maximize recipient trust, senders SH=
OULD publish an SPF<br>
&gt; &gt; &gt; policy which ensures that both MAILFROM and HELO will produc=
e SPF PASS<br>
&gt; &gt; &gt; results.&quot;<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; DF<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; On Wed, Feb 10, 2021 at 6:29 PM Dave Crocker &lt;<a href=3D"=
mailto:dcrocker@gmail.com" target=3D"_blank">dcrocker@gmail.com</a>&gt; wro=
te:<br>
&gt; &gt; &gt; &gt; On 2/10/2021 3:24 PM, Douglas Foster wrote:<br>
&gt; &gt; &gt; &gt; &gt; Huh?=C2=A0 Are you asserting that SPF MAILFROM and=
 SPF HELO are<br>
&gt; &gt; &gt; &gt; &gt; interchangeable?=C2=A0 =C2=A0They are not, but the=
y can work together.<br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; Perhaps I misread, but I thought I saw that this really=
 is out of<br>
&gt; &gt; &gt; &gt; scope<br>
&gt; &gt; &gt; &gt; for this working group.<br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; d/<br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; --<br>
&gt; &gt; &gt; &gt; Dave Crocker<br>
&gt; &gt; &gt; &gt; <a href=3D"mailto:dcrocker@gmail.com" target=3D"_blank"=
>dcrocker@gmail.com</a><br>
&gt; &gt; &gt; &gt; 408.329.0791<br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; Volunteer, Silicon Valley Chapter<br>
&gt; &gt; &gt; &gt; American Red Cross<br>
&gt; &gt; &gt; &gt; <a href=3D"mailto:dave.crocker2@redcross.org" target=3D=
"_blank">dave.crocker2@redcross.org</a><br>
&gt; &gt; <br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; dmarc mailing list<br>
&gt; &gt; <a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.or=
g</a><br>
&gt; &gt; <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>
<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>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><div style=3D"text=
-align:left"><span style=3D"vertical-align:baseline"><br></span></div></spa=
n><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"><img src=3D"https://valimail-logos.s3.a=
mazonaws.com/Valimail__Tag_DarkBlue_TM.png" style=3D"height: 35px; width: 1=
59px;">`</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>

--000000000000ff59e305bb27831f--


From nobody Fri Feb 12 12:31:13 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 28C373A0E4A for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 12:31:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level: 
X-Spam-Status: No, score=-2.08 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_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_FRAUD_PHISH=0.01, T_FILL_THIS_FORM_SHORT=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=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 4GQPMa8sLt4K for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 12:31:04 -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 64CE43A0E30 for <dmarc@ietf.org>; Fri, 12 Feb 2021 12:31:04 -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 11CKM0XH024197 for <dmarc@ietf.org>; Fri, 12 Feb 2021 15:31:03 -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=H7bdHaovElKCs6AeUBjcz4pbJzGT++INDBq9ZxFBd+4=; b=OEDf/mHrWZ82NStLx7Nf2/RfCdfoDpjdZFkKbqfgR3nSeJhlC57rCEG29Fa/u9eu8nTx H4d1K9Q4Fj6S569UdRrLvCiHjpIDN8TeQF4+EIrMJT7oSJf7sBpq2uIUqrxwa4gLwhfG NQiPGGTDd2anJNulYVaiMzkPO+3gf0mU6D2hRU/7dFT7c0rTX9DnOiI3UzYGZQxw6V1X vwk8HsmX+ysNNPyVJdzbvKAiQxhB243QVjROScHPI2tfNp0GXV69Y4H0sU/nF4qBDemp ISnaGA1tUwqrPGOiQof68ca2+9YIEDzNPmG6bMKciSUQYk8+sBzeRq7wkxo0kJguzd8Y ew== 
Received: from copdcexc33.cable.comcast.com (dlppfpt-po-1p.slb.comcast.com [96.99.226.137]) by mx0b-00143702.pphosted.com with ESMTP id 36nux428jh-6 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Fri, 12 Feb 2021 15:31:02 -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; Fri, 12 Feb 2021 13:30:56 -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; Fri, 12 Feb 2021 13:30:56 -0700
Received: from NAM04-BN8-obe.outbound.protection.outlook.com (104.47.74.46) by webmail.comcast.com (96.114.158.213) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 12 Feb 2021 15:30:14 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by MN2PR11MB4256.namprd11.prod.outlook.com (2603:10b6:208:17b::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25; Fri, 12 Feb 2021 20:30:38 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::2495:cfaf:88ca:6b2d]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::2495:cfaf:88ca:6b2d%7]) with mapi id 15.20.3846.027; Fri, 12 Feb 2021 20:30:38 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: DMARC IETF <dmarc@ietf.org>
Thread-Topic: Ticket #64 - Contained Data PII Concerns
Thread-Index: AdcBfLdYcAd1ycC0TvWJKBD11cOyeg==
Date: Fri, 12 Feb 2021 20:30:38 +0000
Message-ID: <MN2PR11MB435185A171029EF4282A2BF4F78B9@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:a087:5815:a25c:3021]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3123e50b-e594-498b-80e0-08d8cf950f22
x-ms-traffictypediagnostic: MN2PR11MB4256:
x-microsoft-antispam-prvs: <MN2PR11MB425690BA922659A1220D8FF8F78B9@MN2PR11MB4256.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: rCpSnKRwj4F1CpM5f3/uXls5aEB8dDr4Ns0C6krKYShuO9yyxubmixgd7k2pAyjHlx3mjL1QOk27BM/m6VIA4Q6iHD6LKUCPfXAXphodM1B4d8tdVUUtg+48tIDZw2fRpeCa0zEujGWXwi2nA9/nHIZpocQMXKqBj0uIGiS/TiBAsySmcNbSrqVttZyIf8qXaEfuZZNCrkl246RtFtZoOaDkNR/GNrXwwdJM6pWFL6TdZHq/+M6MCSbr+CRJXItI8iMLnLQGYKaQikvdbSrDgT6aEyps3ipZyBxWllfEQsYSQQS8F8ChvQPTEiW72usb0Dapm07QCZA6J7L/vQHbM98GV0uN+Fisky88pgUZUAga6zzxmIfFAaKNfelE+v7Ljqs00lL1EU/y/7iBttJmkCNJGCsdsWiPVbqfebcnSIhDLenPVleJd614CUUsOhog4Y7t4i87rUu0VQmmuiVlyYoR8MMSqg1EzkqekoHypZLQkZl+toWjbdG9USTPonIIENzWRpf15L7NqhcHUJ9XH1bVFZF8yyCzee81SLpfZbP2TWiNP7i7G5NzJ/jQDmErSSkfQRXeoQGkDpXeQ8hqa9o9dK6W3TPQKlo1g9eJYag=
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)(346002)(39860400002)(396003)(366004)(136003)(52536014)(33656002)(55016002)(2906002)(316002)(66946007)(6916009)(86362001)(8936002)(478600001)(64756008)(71200400001)(5660300002)(7696005)(66476007)(6506007)(9686003)(66556008)(66446008)(83380400001)(8676002)(186003)(76116006); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?XYK8Oo6VsDeoSz088JwpCH7Il1t8saDIFfhnEU/HDIV6ZM4h38g04cKLzdaw?= =?us-ascii?Q?okgAG/9HRzmguedSHG8qdWFCmL9xeslY7lGWNJ7/Iv2LAMY4iHdUhSxWgUZG?= =?us-ascii?Q?SuuEaIjOj2k0qUGWBDV3uzGZaYNjQ30/6f8bT9hFUU7G7unBbQ6ri9SqAAlc?= =?us-ascii?Q?Q6NxhZlSaLzpyJ7MJOgyR0CziPAktxGjIbfTZxKt5M+hGLxWpC4wszJxpUJ1?= =?us-ascii?Q?AQFDvnpOdS/JUx7zjpGhY9U1FZxOVlO+k7wtamk0Lg1iqLpKfOYVzlNru4zn?= =?us-ascii?Q?6V9F3P9d0/Ix6hs3+txjMLlM/Fwm7tRsTKxkCI1yRPZsU6k/mvjnfVBJ2iFA?= =?us-ascii?Q?AlI2v5xhpkis+ZGreKFvnMVNVez77LSaEhWspsALrSG/IIctXMZglpkLPxBa?= =?us-ascii?Q?5tY6nsxpr17zpnffELHG2GBthyaVnWq7JIe6A/Nm40sBqKCUJQ80SOHTb4xU?= =?us-ascii?Q?7qN4aNUmmLrwR71mj7OhnA3gTynY4dEb1FV0HqLtQeRobjbrk2/SxFhYdGHL?= =?us-ascii?Q?9CWGlo7agTyouwgCQQYsqSgPYUnDy8rPIq0MkIWZi+diflcKM211ptMFZmOS?= =?us-ascii?Q?DqMqb0OIGWiCCONz7i1e07M6Aq6Ha0t4p1tg9tOqCmSqI9YKJlkNZqr0wNOm?= =?us-ascii?Q?ddIScCkaMYJx5e2K9uqH6ox2EJsnS5/Tv4lwJlLt0CiIbeA6p1izfYsM6yBj?= =?us-ascii?Q?iIwP9YXu990CF1DNkLDmQsgeZTHQ3I5sXOx8YaTfhLhUAgGiQlObvoWv9Nft?= =?us-ascii?Q?yJ0LAxhsKzb8S+1vmf9xaofTGXeVApZmMlIbJV+ddcUCdwSoAR56phPwWdEA?= =?us-ascii?Q?mi2loU+Yo8HLL2gZW006FSUTtEplRxZJYW/fRQdYEm+VHTguVH8cST22qtoB?= =?us-ascii?Q?ff8nWBbXsPWYJXWa0Im9sIqaqJAM89ZYjddsaj/HaryL6FFghrskkcl0ZUQK?= =?us-ascii?Q?rkrqLSmN5fwP+k+BzfKIEljllVYMapg55SGftj0BpOgfdHuN/dggqIuZIK0t?= =?us-ascii?Q?d1oDHmOiBUmpcG8gLwe3r2Oyn+Bh+92dZUvaAvivPGSMBnYzcOAHvTV4SMg+?= =?us-ascii?Q?ZhQ46Cp9QgFpHSd17XXgFGGohcwByvMUKS6ShTd5KkmZknYagCMWexkJqTID?= =?us-ascii?Q?iy6W+zx+qB3eYugrYLsvanbuDhv1Tz06bQjWex+POkgEeJaAC8fhUxNNh7bM?= =?us-ascii?Q?L1ZPWOxa4WXCen1jbDAhS8Xmb5YDDKNh1mkhyzPHU7rf4WUCjmlEH0TxKLnt?= =?us-ascii?Q?7yaBYGU5idAY9KjFeJ5aE7OX8rXjn1A8b17ojsJjiWMWZdkBjPSZzPE7RXJj?= =?us-ascii?Q?qTFBp7jR8l9Be5/jgab5ue5kRrqgWVDDMoO9eWLUcLh00psJCqKOTBU7yjCF?= =?us-ascii?Q?7V7Gfnw=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mplNaI4PtRCxsbKhisqqhvoTx3PjncPENzeuPKjU4hvrYrPPkn4NqHRsx7XwDNHKz3XpGjtzqD1JbrTOSEZo9m5Ah8/MbZS0fHLgtxS+UY5dx5laeTliDInmgm8+tu9Dl3FOOCYorb++BVans54vc2BxOR/Fz7BWhEBCVVP49tpHL9ylyzyjRzQ0sUdKnyma9XUOjwSwE8WjHPlEG7Qjy9iiEI4a/RViLdHzHq5pedZuP++ePfWEgl9LXIrUM+8s32K6/9lF6+KivePnEI+Vrsu2LLXdp0oUmBCzmCCxjX4M8has0vddFIFBuIhqx11qeMRPMvi10NZyF6Dz+drB9w==
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=xtQukliN6nFavVxFnB1DUhUo8Ow9mYgrt5zn8lw0nLM=; b=i6KzPesy6pxxoHdc0ahl3wcjr3lwJqdfHr7N7/05inznAvTXfDvKYEwLyKMUQGwIsXva6mOAW+NIarC5RHjxAY/z2LmSMT4q/9vzTyfUKgll/nqp+FeiRmMvx49LDS15BRXjFAhAhiayRTcqry1LBhgl5SdFNb/o7UI1s+2oFI6YqcvGuODQFd87Sx0KlygI1ophnBZS3DzZFKU2bDzAH/wGJvTHuUo5Tsuzi4hEkOh1mT6hJRnQEZUlFtzmpdabzflmmxpROj/XdR8tTlV76YgkPOUqZNnJRzXnBssU/8BvJt/6yAtBCnanWjAKWbDDAOtFgTzBBMTJGZ6LPDFO4A==
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: 3123e50b-e594-498b-80e0-08d8cf950f22
x-ms-exchange-crosstenant-originalarrivaltime: 12 Feb 2021 20:30:38.2442 (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: wvdd1UFZLye/5DJjYZPnt1E456lt8WDKaw/Bt0yL1HZhnXIBO1LQRWIbF2gV8BeKu4POqlsyLtpzqIX8V8GZ5uHUOt6E69Jk+dok9PkyUPQ=
x-ms-exchange-transport-crosstenantheadersstamped: MN2PR11MB4256
x-originatororg: comcast.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWT
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.737 definitions=2021-02-12_09:2021-02-12, 2021-02-12 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/UlPNMwUoeq0pfMe8gUJMvYn76iI>
Subject: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 12 Feb 2021 20:31:13 -0000

Hello folks,

In ticket #64 (https://trac.ietf.org/trac/dmarc/ticket/64), it was suggeste=
d that a Privacy Considerations section may alleviate some concerns about t=
he ownership of the data.  I created an initial attempt, and thought to get=
 some feedback.  I didn't think we should go too far in depth, or raise cor=
ner cases.  Felt like doing so could lead down a rabbit hole of trying to c=
over all cases. This would go within a "Privacy Considerations" section.

* Data Contained Within Reports (#64)

Within the reports is contained an aggregated body of anonymized data perta=
ining
to the sending domain.  The data is meant to aid the report processors
and domain holders in verifying sources of messages pertaining to the
5322.From Domain.  The data should not contain any identifying
characteristics about individual senders or receivers.  An entity
sending reports should not be concerned with the data contained as
it should not contain PII (NIST reference for PII definition), such as emai=
l addresses or
usernames.

Does this seem a reasonable start?  Thanks for your time.

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


From nobody Fri Feb 12 12:40:10 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 6E2E53A0DF3 for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 12:40:08 -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=ZAe6obU4; dkim=pass (2048-bit key) header.d=taugh.com header.b=rR3KwY2C
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WXAY8fm8e6kw for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 12:40: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 1D3E43A0DED for <dmarc@ietf.org>; Fri, 12 Feb 2021 12:40:06 -0800 (PST)
Received: (qmail 93740 invoked from network); 12 Feb 2021 20:40: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=16e2a.6026e7a5.k2102; bh=r5uKw//42T2lrMazZ2+MlGy0/7mo38aOv16T+R6PcTI=; b=ZAe6obU4fPp17oKQFYtowi3Knrv4/cO9JkT76ngQ/Kc+Su1yrQQ+QSmilrT42EpcbT/yY+PLvY05UFbx+iyetQm6LpB7IvvavZMCHYFDrMfx+O0cBJwFiJEAqc41va/AW1otTe3ICFaY7Xubz9E1Mm9hbrsHZ8Ueg82628c5pXXZF9ArfrT2wbDChxCz8ANdJY0p7qV31H1ZCVXXSxTz2Qi9+ylljSdEFQRBVSVXqHbXkjYilb2qyqyZpK/Mqe7CEDpHyqNw0xUMK6QTPD9Kzohf3KarCrXctPzJtCiTsYLcHlSeGQyTeTmuarDJonwQ2biLoYQEJus8pGt/1pv0AA==
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=16e2a.6026e7a5.k2102; bh=r5uKw//42T2lrMazZ2+MlGy0/7mo38aOv16T+R6PcTI=; b=rR3KwY2Cpjei5OXj1cuTOkoDGjbaB1J2rgUoandU7MfE/EanFhhQ19Jmv7cVAy503ONnefTODhqF35CD5S4VqHsjik7bUy6Bxre/pryVTP4g3d9PFKDLOO9e8NT7/eVa9efMnh6XrrSBzawI2LSGlPVN3eGujNSs5AZz14BGyR9Q7hXrEM2pO0v1maVWZ+ZTP1XbF9AZwf/3+XIZKn72EmOoIAVlmx9gsPhp8j9p2JG/5Ddn7cSFXbl8p7O/ZDmb4iMjbFC8HfSgUL8/0xuLO4eLElj2tMUwsFrsWg3Q29LUZ8571vd1VPvV8Pwj9+r8UemTn9sEaIUqZhsWg7rbfQ==
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; 12 Feb 2021 20:40:05 -0000
Received: by ary.qy (Postfix, from userid 501) id C55E46DDB347; Fri, 12 Feb 2021 15:40:04 -0500 (EST)
Date: 12 Feb 2021 15:40:04 -0500
Message-Id: <20210212204004.C55E46DDB347@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: seth@valimail.com
In-Reply-To: <CAOZAAfM1yq9=iScEAwGzJT5bRMXT0VCCC1NLFBoQdtufvUmDHA@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/MuDP7eE-9hIt_0JYCpgnj5RdFZc>
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, 12 Feb 2021 20:40:08 -0000

In article <CAOZAAfM1yq9=iScEAwGzJT5bRMXT0VCCC1NLFBoQdtufvUmDHA@mail.gmail.com> you write:
>-=-=-=-=-=-
>
>As an individual, +1000 to Scott.

I've closed this ticket.  One down, a zillion to go.

R's,
John


From nobody Fri Feb 12 12:46:33 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 640E53A0E37 for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 12:46:28 -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=bxlbSfnF; dkim=pass (2048-bit key) header.d=taugh.com header.b=zSsI27Or
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4SfaLw0gXPLf for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 12:46: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 52E023A0E79 for <dmarc@ietf.org>; Fri, 12 Feb 2021 12:46:26 -0800 (PST)
Received: (qmail 94924 invoked from network); 12 Feb 2021 20:46:25 -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=172ca.6026e921.k2102; bh=Jf0vcEx7fh8p1RelotQcCxupGo9qUJUkafW0IAD4ER8=; b=bxlbSfnFy5LsiIxjEDFHyPhL9D4lC0ymAHlfbyestlmaLzL97xWdcodktWfAAiMAcJrhClAbGF7PTJIAYHNzhS2nXlKtuiPvrxlewKgVYQTarQjc8+hJSYwyKOgPkL3xgUOlZ7tj9lGcMvZWy2epSlL686b5XUCi3AasauR1N25nlSwLkRNp/r/KMk5pVD51Pzk2R2SFjpDrGB46A37htpqXJ5i/wyXL7AjtfPSD0TG7NSs6/5oKMu0ZL+uuCZWrYmbmD2iErEH3VU5Rgpg4vmQ7GgzDlp15NkgOiXx39Uop8QYJsq0xjinH9kG8RPALcausgn/xpcT/VYc7cjZSOQ==
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=172ca.6026e921.k2102; bh=Jf0vcEx7fh8p1RelotQcCxupGo9qUJUkafW0IAD4ER8=; b=zSsI27Or3U0YYy2yDckv1az/syzo7/zJDUOcgBrs4TCdlkf7lnuqZBP8t3TiIq9AYd2yjGqom2nJ79hy5AZlk54GFAPKtWsZIfA+GWV5mY0L4FeU+6vW76ZFhFnisApSrtQ2TugMStNMVlbRIlGziQ7hxTJ4VMXKgCb8i0HzKysmad2QVxfctOwOZuHjt1rHMoRYK7o17lwX/N3gmHB+BuehpNdnWsX3sHvXVegx2dIiJFX6mqdUGQHey+JDfbWj5P3RC51KhltT5/g5HQilzXKUPO5tfpCzS6XHChNCZCO43L3rQOxlvKYzZ7hh4GH8LqO8MOXoAmClBCOPQPTHTA==
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; 12 Feb 2021 20:46:25 -0000
Received: by ary.qy (Postfix, from userid 501) id BD53A6DDB3F5; Fri, 12 Feb 2021 15:46:23 -0500 (EST)
Date: 12 Feb 2021 15:46:23 -0500
Message-Id: <20210212204624.BD53A6DDB3F5@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: Alex_Brotman@comcast.com
In-Reply-To: <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.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/UgRhdCqdVXvgHLP9fSvS0HB3LPM>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 12 Feb 2021 20:46:32 -0000

In article <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> you write:
>Hello folks,
>
>In ticket #64 (https://trac.ietf.org/trac/dmarc/ticket/64), it was suggested that a Privacy Considerations section may alleviate
>some concerns about the ownership of the data.  I created an initial attempt, and thought to get some feedback.  I didn't think
>we should go too far in depth, or raise corner cases.  Felt like doing so could lead down a rabbit hole of trying to cover all
>cases. This would go within a "Privacy Considerations" section.
>
>* Data Contained Within Reports (#64)
>
>Within the reports is contained an aggregated body of anonymized data pertaining
>to the sending domain.  The data is meant to aid the report processors
>and domain holders in verifying sources of messages pertaining to the
>5322.From Domain.  The data should not contain any identifying
>characteristics about individual senders or receivers.  An entity
>sending reports should not be concerned with the data contained as
>it should not contain PII (NIST reference for PII definition), such as email addresses or
>usernames.
>
>Does this seem a reasonable start?  Thanks for your time.

It's not clear which kind of report this is talking about.

If it's aggregate reports, they contain IP addresses of mail servers and domain names 
of SPF and DKIM identifiers, but nothing about the e-mail address or IP of the original senders.

If it's failure reports, they contain as much or as little as the reporter includes, possibly
an entire message sent by someome who may or may not be connected to the domain that receives the report.




From nobody Fri Feb 12 12:50:12 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 8796C3A0E3A for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 12:50:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level: 
X-Spam-Status: No, score=-2.09 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_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=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=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 8l94MU4-KNZc for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 12:50:09 -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 060823A0E2A for <dmarc@ietf.org>; Fri, 12 Feb 2021 12:50:08 -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 11CKlRwj007236; Fri, 12 Feb 2021 15:50:08 -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=gOR0SMCkjOfRS3ULZ5MHYnvoCk0a/iCvn/3O/XWu8Uw=; b=M/GOkQf6LwwG4oq531VFBG36zL8gDBN06F1S3SohtxtOqueg+ai4QUBDbGkoBvbzR4bg 1LUqBin0pS1Y5iyNlVczn6ZoGAou7Kgww5/4QwStD6YOezFDSfFuxTGaeHBXjQ52YExI XANas1JLGEMZ+efQ2MVhZo1aZ+GYi9krSLaJKaDnbp49lrsQ3GPDDRry+icEwgItfSVF ODXpOMCytOxpI7LCihD/s+boGq5BGLqaRzhIF+WnunGhsyZM7cpFn+FBi+6Vi9gRIT7D IhViKTPCnFv2FAs+IyexQUxueBOcz9cFFp7fFZsOPHo84r/Qd7zu6nYbBWx5EUlcAdXw Gg== 
Received: from pacdcex51.cable.comcast.com (dlppfpt-wc-1p.slb.comcast.com [96.99.226.136]) by mx0b-00143702.pphosted.com with ESMTP id 36nnkpdkyr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 12 Feb 2021 15:50:07 -0500
Received: from PACDCEX49.cable.comcast.com (24.40.2.148) by PACDCEX51.cable.comcast.com (24.40.2.150) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 12 Feb 2021 15:50:06 -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; Fri, 12 Feb 2021 15:50:06 -0500
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (104.47.55.109) by webmail.comcast.com (76.96.78.71) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 12 Feb 2021 15:49:57 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by BL0PR11MB3524.namprd11.prod.outlook.com (2603:10b6:208:73::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.29; Fri, 12 Feb 2021 20:49:55 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::2495:cfaf:88ca:6b2d]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::2495:cfaf:88ca:6b2d%7]) with mapi id 15.20.3846.027; Fri, 12 Feb 2021 20:49:55 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: John Levine <johnl@taugh.com>, "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [EXTERNAL] Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
Thread-Index: AdcBfLdYcAd1ycC0TvWJKBD11cOyegAA2haAAAAY+MA=
Date: Fri, 12 Feb 2021 20:49:55 +0000
Message-ID: <MN2PR11MB435180303B5EAD3349B189F1F78B9@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> <20210212204624.BD53A6DDB3F5@ary.qy>
In-Reply-To: <20210212204624.BD53A6DDB3F5@ary.qy>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: taugh.com; dkim=none (message not signed) header.d=none;taugh.com; dmarc=none action=none header.from=comcast.com;
x-originating-ip: [2601:43:101:380:a087:5815:a25c:3021]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3258b5e6-6280-40ad-5fb7-08d8cf97c108
x-ms-traffictypediagnostic: BL0PR11MB3524:
x-microsoft-antispam-prvs: <BL0PR11MB3524A252DDFC9AA17E22F5BEF78B9@BL0PR11MB3524.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: PnNGzSE10lj2IPCQbgmL7aWjOt3T06smPiA4UpuOdao94576yEPggElOCAOxIKFqiasBsIlPKn4Ddodeecn4fvsUGl7S34TIZoEg61klKQM6uGD1IZqaBHc+t2E0ccaBEev4ektUcM9Tw9Rz5BoD3xvgIOiGDrJ4Ya8TSAsiaiUKiC5KH4OEYvSRSGNXsE73srC5pT8eikv+DHOcQYHueL3a5XP1TpYjp1m0wk2w8PhmjKt80PalUWEAiNnEadknN02glSZ7rLE6YBQ+O7WY22tkVDdsMyXBIURJx/r6hOs7ZRR5I3/TRAtHr/sOid6i/gGmD1IcQcR8kdt/QYEbb0rc/NAWYEzNaiwgJ2WZFphhqDFnSXPpOSFj2ASzv+o2RP6s31l7b8dD4lCa8e+qbg6IWt+YrlsA0HKYQ2JkOvhwjCI9xVWNad4nR19dWaR2/55Awq0y5svHj3kW5QDGfJWsSz/m3CI+CjElyGEG6L0bDpHrsLvjq9EfoOCYu8TG9jCrzhEXBpE97dPZtOu6q7yiR/GZVtQMWYWhd0HglKNc8ajsi4JDn3Q4rguPZxbszWhr3CgTDauW6nCOlXfvs4hcgg3SSNCT1dG9dEmeDcg=
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)(346002)(136003)(39860400002)(396003)(186003)(53546011)(83380400001)(71200400001)(6506007)(55016002)(9686003)(2906002)(33656002)(52536014)(64756008)(66446008)(66946007)(45080400002)(66556008)(86362001)(7696005)(66476007)(110136005)(316002)(5660300002)(8936002)(8676002)(76116006)(478600001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?dUpBbUtGNlc4L3YrUCtNM1BZd1Y5UDRaRmp3UU1DdVEyeGtjaUp1dEtOaFB1?= =?utf-8?B?QWlSZlliMmlLK1NLa1RuVVYvaXA1VjZ0V1F4NlB5d0RpK0hmOHNvb2ZnYmta?= =?utf-8?B?elFFaGRjYXA2V1VKVzlWTW9YdVRBSWVsZ2EycnpKeVVFYkNWRWRtTGQzRWFK?= =?utf-8?B?QWREZk1Nbnh4aWZEeTE3dFFCREM5VTlyZFV5Y1dLb1B2UnByaTZEcDFrcDg0?= =?utf-8?B?UXJrcDE3MGR0V2VZZVRyajJZa2hZQVpMT0VtdmtkVlV0V1pjaVJZZ2hPUWRQ?= =?utf-8?B?T1JORXkyaTRiSHpIZzlKTWk0QmRKeitxa0p1eC9pSHNDNi9ZSW5wUm1UZ0xN?= =?utf-8?B?N055bG9tSW1kQkpUM3ZjNm9pa2RKR2JGR3A1bnJXTHN1ZnNvaHFUOTU0WXdM?= =?utf-8?B?ODJoYjVoRFBPY3ZqclJFVjg1Ri83ZVZtRXVKdWVNVEVIeHI4VjIvYkdSWkVR?= =?utf-8?B?aStiSXVsMUxRVElIdGtzbUF2a2xYaStMbTk5d3k0TWgwY1EyQURXWVpHeXpN?= =?utf-8?B?VURPOUZ2RGZPTTc3UTBEcFBPSlBkaDlxRmFwYyt5WmpHVzZya0UySFV5YTRj?= =?utf-8?B?ZzBhQjZ4VVFXVUhlYTQ3NERsSDhjTGdsWFUxeGNSUTJUNHQ5R2JNay93MmQ3?= =?utf-8?B?OWNSTDZTRk40d1Z1OHBHb05Sd25PV0FPSHUraHpyaEh3ekxXajUrZk1WQU5n?= =?utf-8?B?ZnE2OG51eTVveHlGR1JDczduOVJEbFJmSlBuODNJTkZuN04xQjRROEIvNVNm?= =?utf-8?B?NFJ4WHJVVHQvSWVKTnRNYUVWQXhybUJxWGlPdW1JaXdDUHBGdlo1a0FvMXcr?= =?utf-8?B?Ym84UnQrUldrN2ErQm9RU2hqSXB0SkRDMG9rQU1McjZqcUFKaklVaTI5Y1du?= =?utf-8?B?WVhHbnE1Y3hWTVNUNkk5eEVZZS9yNlBlcVZOYU92NUZLdTlyVmZyd0JOdUE3?= =?utf-8?B?Q0JtU1E4NXRaQUhndEF5cEFOOXhTZFFIQStaMy9YazhiMHlubHJZQlhSUVNQ?= =?utf-8?B?WUozVXpZZy9Wd283N0d2S1NrdUI1UEJBZEN4M1EweWRZa3c2Q0lET0JMclhs?= =?utf-8?B?WDZheHVBeHpCU3I4QlhYWnBVelRGSXQvcThFT2JJTFN1eVVzZ2FwK1FuRWQv?= =?utf-8?B?THZDUXNrRHU3TEZXbzhaSlI4OFpWQUo2cnhkTnk2eHpwSG1MaFJrOVBDd1F6?= =?utf-8?B?d3RTRlIyOVFzWGZURDRPVUFSVWozaEFBNjNxTDVJRkxmQWIyL1pmN2pLdUJ6?= =?utf-8?B?dmpQMG0zZ283aHhyeUNSa011ZmlRTTNGL2pQRG0vdVhQL1VweHhRVEs0ZWpy?= =?utf-8?B?b2M1ZHU0d3FVSnJ5WXE0aENhUktYNHVGSzlNR28yalVaWFIralVWcVgrdDh0?= =?utf-8?B?Sy9jejNMblRYeXhGeHI4YzdjRHR3QmQyV2xpUWF3M3czUmlLdWpvdms5R2xN?= =?utf-8?B?YkJKTTE3Und1YmZEUXBGeWNSa0dyaWVQcnFFQTV1UGtSVkltMWdMaDFLZ0Vi?= =?utf-8?B?NVJEMENaNmNRU3NPTHFBclA5Zkd4UndaMHhLUjVwNE91TTcrMk1ZbTRuMmFa?= =?utf-8?B?TnFVL2FvM3RRTlVpOE5IV082aEpTVGNTcGFLck1LeUl2K2pUdS8xVGpzYU5H?= =?utf-8?B?SWRZZDNzYkgrNitDNm80NWpuQnRhRmlGRWo0eFY4MU1YbERPWlg1MEE4YVJ4?= =?utf-8?B?UnlPN04yM3c0S0ZVTUVHZzR1bFVOVFJtT2lXdTBWOXR4WkNuVUdhOFp0WG5I?= =?utf-8?B?eFpwbklQaXBxcVpiakVjNVVobFlmaks3blQ0bGNrVHN4OWVNVkkraEcyL3JB?= =?utf-8?Q?jENqTvSN315i3Ns4iV+JsQuIxsgCv1p95Kl7g=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bXADnR1F1w3x3iQEI09um/bNveMx7yftP8Ql3qxUFKNiSo8bsSWiZr0TKE0OHzSEbvd0lwzJE1gZGuOrHpiVQNWAUbG35lvEPVNbkG7Koqlw1n5U0G5LhyQa3m34xgpeK47zqmrexEVhsxQ5ba+zmkYHlVITDMITwVTHmL3Sqwe57Sj05n90uTDYRxNbNo0S7dh3Twpswwu2cU+fdVcns34CivnzQ0pevPkkS8ggqyJVEV8REHozjIUQ2wHNxeRjFVScrk6vA6qyrEPHcnP4vZpUPVSwYl31dxqWpR0FPQQP/mh4ESV7llufPeaU+oWcz6wQ0p7Qs4Zw5CtpUuVM4A==
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=GKYmRsTR6XmvM0IRdOpNXzW+4iHlbMa7TBxETIfdwgE=; b=cdjLN2MFIP3GEjRLe62ctO09BSS2/oik6zuSyG9zbiYYLAsTZ0ox4WcYSCnESA7a97ZPeX+x+lyDYzf0L7PrH9loBrmn2BBF1IIIoRTT97mqHU9MR3g/v/SRbnLMB8cDPTQAmDpaX1G+0pLw8V88ZNRuazr+WA8Hf/miUdDR2ZRoH0NTCB0QjyQOcvLAgazJITaHi1dnsxtyu5If44wAz3Y/GU/lwLm9JnjcTAGRPrP95sWA5gfNgsf1IuJy/Bne2r4N5gnnp8EeqYCeRJ8t5EvUG0ipRISrJAgXT/I28HHdHNu1Qh7Xghph50z7tN8cNqgAwC0WxLEiaHj/S4Zefw==
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: 3258b5e6-6280-40ad-5fb7-08d8cf97c108
x-ms-exchange-crosstenant-originalarrivaltime: 12 Feb 2021 20:49:55.7178 (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: POOIidNhRAlb/0YRUECj/6FfvBGRDSb3zq+Sv5N1PjxMbURHaaDQrqix31hmQtkK1MzFDxOvmjzsSUQTi+XRgcbdcNvdL/N44uIc2nG2wTE=
x-ms-exchange-transport-crosstenantheadersstamped: BL0PR11MB3524
x-originatororg: comcast.com
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWQ
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.737 definitions=2021-02-12_09:2021-02-12, 2021-02-12 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9OTbxYTbQM3eg5R22R2Y8sljKW8>
Subject: Re: [dmarc-ietf] [EXTERNAL] Re: Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 12 Feb 2021 20:50:11 -0000

QXBvbG9naWVzLCB0aGlzIGlzIGZvciBhZ2dyZWdhdGUgcmVwb3J0cy4gIEknbSB3b3VsZCBpbWFn
aW5lIHRoZSBGYWlsdXJlIHJlcG9ydHMgZHJhZnQgd291bGQgaGF2ZSBpdHMgb3duIHNlY3Rpb24g
YXMgdGhlIHF1ZXN0aW9ucyB0aGVyZSBtYXkgYmUgZGlmZmVyZW50Lg0KDQotLQ0KQWxleCBCcm90
bWFuDQpTci4gRW5naW5lZXIsIEFudGktQWJ1c2UgJiBNZXNzYWdpbmcgUG9saWN5DQpDb21jYXN0
DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogSm9obiBMZXZpbmUgPGpv
aG5sQHRhdWdoLmNvbT4NCj4gU2VudDogRnJpZGF5LCBGZWJydWFyeSAxMiwgMjAyMSAzOjQ2IFBN
DQo+IFRvOiBkbWFyY0BpZXRmLm9yZw0KPiBDYzogQnJvdG1hbiwgQWxleCA8QWxleF9Ccm90bWFu
QGNvbWNhc3QuY29tPg0KPiBTdWJqZWN0OiBbRVhURVJOQUxdIFJlOiBbZG1hcmMtaWV0Zl0gVGlj
a2V0ICM2NCAtIENvbnRhaW5lZCBEYXRhIFBJSSBDb25jZXJucw0KPg0KPiBJbiBhcnRpY2xlDQo+
IDxNTjJQUjExTUI0MzUxODVBMTcxMDI5RUY0MjgyQTJCRjRGNzhCOUBNTjJQUjExTUI0MzUxLm5h
bXByZA0KPiAxMS5wcm9kLm91dGxvb2suY29tPiB5b3Ugd3JpdGU6DQo+ID5IZWxsbyBmb2xrcywN
Cj4gPg0KPiA+SW4gdGlja2V0ICM2NA0KPiA+KGh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19o
dHRwczovL3RyYWMuaWV0Zi5vcmcvdHJhYy9kbWFyYy90aWNrZXQvNjQNCj4gPl9fOyEhQ1FsM21j
SFgyQSFUd0RWaldPaDA4QU9HQ3hQWjBJS1I4SXhnZFViNnUzTERXMVBvMEticnpJZ1hXDQo+IHds
Vm01M05VQg0KPiA+UTZncVo4SWJJalVqRyQgKSwgaXQgd2FzIHN1Z2dlc3RlZCB0aGF0IGEgUHJp
dmFjeSBDb25zaWRlcmF0aW9ucyBzZWN0aW9uIG1heQ0KPiBhbGxldmlhdGUgc29tZSBjb25jZXJu
cyBhYm91dCB0aGUgb3duZXJzaGlwIG9mIHRoZSBkYXRhLiAgSSBjcmVhdGVkIGFuIGluaXRpYWwN
Cj4gYXR0ZW1wdCwgYW5kIHRob3VnaHQgdG8gZ2V0IHNvbWUgZmVlZGJhY2suICBJIGRpZG4ndCB0
aGluayB3ZSBzaG91bGQgZ28gdG9vIGZhcg0KPiBpbiBkZXB0aCwgb3IgcmFpc2UgY29ybmVyIGNh
c2VzLiAgRmVsdCBsaWtlIGRvaW5nIHNvIGNvdWxkIGxlYWQgZG93biBhIHJhYmJpdCBob2xlDQo+
IG9mIHRyeWluZyB0byBjb3ZlciBhbGwgY2FzZXMuIFRoaXMgd291bGQgZ28gd2l0aGluIGEgIlBy
aXZhY3kgQ29uc2lkZXJhdGlvbnMiDQo+IHNlY3Rpb24uDQo+ID4NCj4gPiogRGF0YSBDb250YWlu
ZWQgV2l0aGluIFJlcG9ydHMgKCM2NCkNCj4gPg0KPiA+V2l0aGluIHRoZSByZXBvcnRzIGlzIGNv
bnRhaW5lZCBhbiBhZ2dyZWdhdGVkIGJvZHkgb2YgYW5vbnltaXplZCBkYXRhDQo+ID5wZXJ0YWlu
aW5nIHRvIHRoZSBzZW5kaW5nIGRvbWFpbi4gIFRoZSBkYXRhIGlzIG1lYW50IHRvIGFpZCB0aGUg
cmVwb3J0DQo+ID5wcm9jZXNzb3JzIGFuZCBkb21haW4gaG9sZGVycyBpbiB2ZXJpZnlpbmcgc291
cmNlcyBvZiBtZXNzYWdlcw0KPiA+cGVydGFpbmluZyB0byB0aGUgNTMyMi5Gcm9tIERvbWFpbi4g
IFRoZSBkYXRhIHNob3VsZCBub3QgY29udGFpbiBhbnkNCj4gPmlkZW50aWZ5aW5nIGNoYXJhY3Rl
cmlzdGljcyBhYm91dCBpbmRpdmlkdWFsIHNlbmRlcnMgb3IgcmVjZWl2ZXJzLiAgQW4NCj4gPmVu
dGl0eSBzZW5kaW5nIHJlcG9ydHMgc2hvdWxkIG5vdCBiZSBjb25jZXJuZWQgd2l0aCB0aGUgZGF0
YSBjb250YWluZWQNCj4gPmFzIGl0IHNob3VsZCBub3QgY29udGFpbiBQSUkgKE5JU1QgcmVmZXJl
bmNlIGZvciBQSUkgZGVmaW5pdGlvbiksIHN1Y2gNCj4gPmFzIGVtYWlsIGFkZHJlc3NlcyBvciB1
c2VybmFtZXMuDQo+ID4NCj4gPkRvZXMgdGhpcyBzZWVtIGEgcmVhc29uYWJsZSBzdGFydD8gIFRo
YW5rcyBmb3IgeW91ciB0aW1lLg0KPg0KPiBJdCdzIG5vdCBjbGVhciB3aGljaCBraW5kIG9mIHJl
cG9ydCB0aGlzIGlzIHRhbGtpbmcgYWJvdXQuDQo+DQo+IElmIGl0J3MgYWdncmVnYXRlIHJlcG9y
dHMsIHRoZXkgY29udGFpbiBJUCBhZGRyZXNzZXMgb2YgbWFpbCBzZXJ2ZXJzIGFuZCBkb21haW4N
Cj4gbmFtZXMgb2YgU1BGIGFuZCBES0lNIGlkZW50aWZpZXJzLCBidXQgbm90aGluZyBhYm91dCB0
aGUgZS1tYWlsIGFkZHJlc3Mgb3IgSVAgb2YNCj4gdGhlIG9yaWdpbmFsIHNlbmRlcnMuDQo+DQo+
IElmIGl0J3MgZmFpbHVyZSByZXBvcnRzLCB0aGV5IGNvbnRhaW4gYXMgbXVjaCBvciBhcyBsaXR0
bGUgYXMgdGhlIHJlcG9ydGVyIGluY2x1ZGVzLA0KPiBwb3NzaWJseSBhbiBlbnRpcmUgbWVzc2Fn
ZSBzZW50IGJ5IHNvbWVvbWUgd2hvIG1heSBvciBtYXkgbm90IGJlIGNvbm5lY3RlZA0KPiB0byB0
aGUgZG9tYWluIHRoYXQgcmVjZWl2ZXMgdGhlIHJlcG9ydC4NCj4NCg0K


From nobody Fri Feb 12 13:17:09 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 380B63A0E9E for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 13:17:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 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, T_FILL_THIS_FORM_SHORT=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=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 763OoQKoQTJp for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 13:17:04 -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 9797A3A0E88 for <dmarc@ietf.org>; Fri, 12 Feb 2021 13:17:04 -0800 (PST)
Received: by mail-vs1-xe30.google.com with SMTP id x201so349495vsc.0 for <dmarc@ietf.org>; Fri, 12 Feb 2021 13:17:04 -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=ZaqGNM3DGU6oJ+P7CBP/HNkR9K9LUDEHsXaGBP/4X4Y=; b=KuGf7OLzg6UWiKbKbTryjfElXvTmF/mvINYQWcngxWwku7MmXEzXSNZXFKAnhL0ekF PO04pBLF4uH+g/x6fhXCIa/MYvh+sTBm9+cWYvTcBYEGKIexbIlxptZXC7eWxSjqSyb1 B4xD7/BEXTLGcF8cMHAgLiuooAHtGjA14J90I2qR8Melw2VXRipe3C2LXMj84+zjeeqZ vaUVSNsK2flqT9G97Qlc8B3Opp0wC4yjFZ3DgjGAoxs80wYZmGmxAwPnpeSL1vXR5ac1 hA+vej3POsqvKQoMGzPcFLIeAt92cM0OnIRlA4DjK8YTfU9ZvoWl9omypXhbHLP0+M4J ToKg==
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=ZaqGNM3DGU6oJ+P7CBP/HNkR9K9LUDEHsXaGBP/4X4Y=; b=hn5d0davfW2AkDrlp7icm7+6WMN0D5n/eysYXCakUnD0inysJJ82AErct1irS+LTob jSVL/3HIOo6dFzH/ex/p7F8GWAXhB4ivw0tVVRrVYKPo1/r5gFeK2ZBpe66Xn4YWwhPa YIgbcrsiwStjvWjRPtZAG4acm1sWcN99mJt1Uf2TeMq/vew5+QjLwjqDWd1tOpnZkuwp KNXupx/48f/JN6iUOdlDxcU9ya7FH5mVURUP8wbRYMX3h8XPNSo6b4TLPnVNUOoqJd+6 o4D/lf4pxpfxZxDEk6FvIdYLUGnN/uidOaFKWPugj1YcxWVQ0kdDVcJaarMfH8foX12D iwzA==
X-Gm-Message-State: AOAM530Rl4RsTAX3h87pKr++zEjHeHrpCS5aDWPlfb3+SudhBC//P//v JED108gASgYHxzU1rGsmO2CW2ugTkt5zXZLRpFTvQlJKVJ8=
X-Google-Smtp-Source: ABdhPJwtb0/ZYaU6VTAc64N1JqhUmFUT/B10ZvVtGtH7xSPBSNoqrHBTQMXcnC6pae+csILlrwAHKTmt/ew1DdDKwMg=
X-Received: by 2002:a67:ed84:: with SMTP id d4mr3278489vsp.52.1613164622055; Fri, 12 Feb 2021 13:17:02 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> <20210212204624.BD53A6DDB3F5@ary.qy> <MN2PR11MB435180303B5EAD3349B189F1F78B9@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB435180303B5EAD3349B189F1F78B9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Seth Blank <seth@valimail.com>
Date: Fri, 12 Feb 2021 13:16:51 -0800
Message-ID: <CAOZAAfPOW6DC3q0pusF4pZr5+OwdEBWWg284RFPfEEUv5_uQOw@mail.gmail.com>
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>
Cc: John Levine <johnl@taugh.com>, "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000431b2605bb2a28ae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/evKRiZKMsCq8WffVzegkEAFnFtc>
Subject: Re: [dmarc-ietf] [EXTERNAL] Re: Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 12 Feb 2021 21:17:07 -0000

--000000000000431b2605bb2a28ae
Content-Type: text/plain; charset="UTF-8"

As an individual, part of the reason for this ticket is that some receivers
do not send aggregate reports, as they're unclear on whose data is being
provided to whom (which then spirals into issues of legalities). While the
IETF cannot weigh in on legalities, it can make clear the intention of
whose data is being transmitted in the report. I believe clarifying this
will enable more reports to flow. My thoughts, quickly, with less precision
than I'd like, but as a starting point:

For aggregate reports, the data is intended for the domain owner to
understand what is being sent in its name, as seen by the receiver. The
intention is that this data is aggregated on behalf of the domain owner by
the receiver, and sent if the domain owner publishes a reporting record.

In the data itself, there are summaries of IP addresses and authentication
statuses of mail that fall into three categories: 1) mail that is
authenticated by the domain, 2) mail that fails to authenticate as the
domain, and 3) mail that is wholly unauthenticated. From a domain owner
perspective, this means they get reports of mail that is 1) authorized by
them, 2) not authorized by them, or 3) broken by forwarding or other
rewriting by an intermediary. In all cases, this is valuable information
for a domain owner to have, and any PII (IP addresses specifically) either
belong to the domain owner getting the report, are threat attempting to act
as the domain owner, or are intermediaries being used by the domain owner.
In all cases, there is nothing here that leaks or exposes someone else's
PII to a domain owner, just things explicitly that are theirs or attempting
to be seen as them.

Seth

On Fri, Feb 12, 2021 at 12:50 PM Brotman, Alex <Alex_Brotman=
40comcast.com@dmarc.ietf.org> wrote:

> Apologies, this is for aggregate reports.  I'm would imagine the Failure
> reports draft would have its own section as the questions there may be
> different.
>
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
>
> > -----Original Message-----
> > From: John Levine <johnl@taugh.com>
> > Sent: Friday, February 12, 2021 3:46 PM
> > To: dmarc@ietf.org
> > Cc: Brotman, Alex <Alex_Brotman@comcast.com>
> > Subject: [EXTERNAL] Re: [dmarc-ietf] Ticket #64 - Contained Data PII
> Concerns
> >
> > In article
> > <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd
> > 11.prod.outlook.com> you write:
> > >Hello folks,
> > >
> > >In ticket #64
> > >(https://urldefense.com/v3/__https://trac.ietf.org/trac/dmarc/ticket/64
> > >__;!!CQl3mcHX2A!TwDVjWOh08AOGCxPZ0IKR8IxgdUb6u3LDW1Po0KbrzIgXW
> > wlVm53NUB
> > >Q6gqZ8IbIjUjG$ ), it was suggested that a Privacy Considerations
> section may
> > alleviate some concerns about the ownership of the data.  I created an
> initial
> > attempt, and thought to get some feedback.  I didn't think we should go
> too far
> > in depth, or raise corner cases.  Felt like doing so could lead down a
> rabbit hole
> > of trying to cover all cases. This would go within a "Privacy
> Considerations"
> > section.
> > >
> > >* Data Contained Within Reports (#64)
> > >
> > >Within the reports is contained an aggregated body of anonymized data
> > >pertaining to the sending domain.  The data is meant to aid the report
> > >processors and domain holders in verifying sources of messages
> > >pertaining to the 5322.From Domain.  The data should not contain any
> > >identifying characteristics about individual senders or receivers.  An
> > >entity sending reports should not be concerned with the data contained
> > >as it should not contain PII (NIST reference for PII definition), such
> > >as email addresses or usernames.
> > >
> > >Does this seem a reasonable start?  Thanks for your time.
> >
> > It's not clear which kind of report this is talking about.
> >
> > If it's aggregate reports, they contain IP addresses of mail servers and
> domain
> > names of SPF and DKIM identifiers, but nothing about the e-mail address
> or IP of
> > the original senders.
> >
> > If it's failure reports, they contain as much or as little as the
> reporter includes,
> > possibly an entire message sent by someome who may or may not be
> connected
> > to the domain that receives the report.
> >
>
> _______________________________________________
> 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.

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

<div dir=3D"ltr"><div>As an individual, part of the reason for this ticket =
is that some receivers do not send aggregate reports, as they&#39;re unclea=
r on whose data is being provided to whom (which then spirals into issues o=
f legalities). While the IETF cannot weigh in on legalities, it can make cl=
ear the intention of whose data is being transmitted in the report. I belie=
ve clarifying this will enable more reports to flow. My thoughts, quickly, =
with less precision than I&#39;d like, but as a starting point:</div><div><=
br></div><div>For aggregate reports, the data is intended for the domain ow=
ner to understand what is being sent in its name, as seen by the receiver. =
The intention is that this data is aggregated on behalf of the domain owner=
 by the receiver, and sent if the domain owner publishes a reporting record=
.</div><div><br></div><div>In the data itself, there are summaries of IP ad=
dresses and authentication statuses of mail that fall into three categories=
: 1) mail that is authenticated by the domain, 2) mail that fails to authen=
ticate as the domain, and 3) mail that is wholly unauthenticated. From a do=
main owner perspective, this means they get reports of mail that is 1) auth=
orized by them, 2) not authorized by them, or 3) broken by forwarding or ot=
her rewriting by an intermediary. In all cases, this is valuable informatio=
n for a domain owner to have, and any PII (IP addresses specifically) eithe=
r belong to the domain owner getting the report, are threat attempting to a=
ct as the domain owner, or are intermediaries being used by the domain owne=
r. In all cases, there is nothing here that leaks or exposes someone else&#=
39;s PII to a domain owner, just things explicitly that are theirs or attem=
pting to be seen as them.</div><div><br></div><div>Seth</div></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 12=
, 2021 at 12:50 PM Brotman, Alex &lt;Alex_Brotman=3D<a href=3D"mailto:40com=
cast.com@dmarc.ietf.org">40comcast.com@dmarc.ietf.org</a>&gt; wrote:<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">Apologies, this is for=
 aggregate reports.=C2=A0 I&#39;m would imagine the Failure reports draft w=
ould have its own section as the questions there may be different.<br>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: John Levine &lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_bl=
ank">johnl@taugh.com</a>&gt;<br>
&gt; Sent: Friday, February 12, 2021 3:46 PM<br>
&gt; To: <a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org=
</a><br>
&gt; Cc: Brotman, Alex &lt;<a href=3D"mailto:Alex_Brotman@comcast.com" targ=
et=3D"_blank">Alex_Brotman@comcast.com</a>&gt;<br>
&gt; Subject: [EXTERNAL] Re: [dmarc-ietf] Ticket #64 - Contained Data PII C=
oncerns<br>
&gt;<br>
&gt; In article<br>
&gt; &lt;MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd<br>
&gt; <a href=3D"http://11.prod.outlook.com" rel=3D"noreferrer" target=3D"_b=
lank">11.prod.outlook.com</a>&gt; you write:<br>
&gt; &gt;Hello folks,<br>
&gt; &gt;<br>
&gt; &gt;In ticket #64<br>
&gt; &gt;(<a href=3D"https://urldefense.com/v3/__https://trac.ietf.org/trac=
/dmarc/ticket/64" rel=3D"noreferrer" target=3D"_blank">https://urldefense.c=
om/v3/__https://trac.ietf.org/trac/dmarc/ticket/64</a><br>
&gt; &gt;__;!!CQl3mcHX2A!TwDVjWOh08AOGCxPZ0IKR8IxgdUb6u3LDW1Po0KbrzIgXW<br>
&gt; wlVm53NUB<br>
&gt; &gt;Q6gqZ8IbIjUjG$ ), it was suggested that a Privacy Considerations s=
ection may<br>
&gt; alleviate some concerns about the ownership of the data.=C2=A0 I creat=
ed an initial<br>
&gt; attempt, and thought to get some feedback.=C2=A0 I didn&#39;t think we=
 should go too far<br>
&gt; in depth, or raise corner cases.=C2=A0 Felt like doing so could lead d=
own a rabbit hole<br>
&gt; of trying to cover all cases. This would go within a &quot;Privacy Con=
siderations&quot;<br>
&gt; section.<br>
&gt; &gt;<br>
&gt; &gt;* Data Contained Within Reports (#64)<br>
&gt; &gt;<br>
&gt; &gt;Within the reports is contained an aggregated body of anonymized d=
ata<br>
&gt; &gt;pertaining to the sending domain.=C2=A0 The data is meant to aid t=
he report<br>
&gt; &gt;processors and domain holders in verifying sources of messages<br>
&gt; &gt;pertaining to the 5322.From Domain.=C2=A0 The data should not cont=
ain any<br>
&gt; &gt;identifying characteristics about individual senders or receivers.=
=C2=A0 An<br>
&gt; &gt;entity sending reports should not be concerned with the data conta=
ined<br>
&gt; &gt;as it should not contain PII (NIST reference for PII definition), =
such<br>
&gt; &gt;as email addresses or usernames.<br>
&gt; &gt;<br>
&gt; &gt;Does this seem a reasonable start?=C2=A0 Thanks for your time.<br>
&gt;<br>
&gt; It&#39;s not clear which kind of report this is talking about.<br>
&gt;<br>
&gt; If it&#39;s aggregate reports, they contain IP addresses of mail serve=
rs and domain<br>
&gt; names of SPF and DKIM identifiers, but nothing about the e-mail addres=
s or IP of<br>
&gt; the original senders.<br>
&gt;<br>
&gt; If it&#39;s failure reports, they contain as much or as little as the =
reporter includes,<br>
&gt; possibly an entire message sent by someome who may or may not be conne=
cted<br>
&gt; to the domain that receives the report.<br>
&gt;<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><div style=3D"text=
-align:left"><span style=3D"vertical-align:baseline"><br></span></div></spa=
n><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"><img src=3D"https://valimail-logos.s3.a=
mazonaws.com/Valimail__Tag_DarkBlue_TM.png" style=3D"height: 35px; width: 1=
59px;">`</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>

--000000000000431b2605bb2a28ae--


From nobody Fri Feb 12 13:23:36 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 B4C8B3A0EC4 for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 13:23:35 -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=e7xCYcG2; dkim=pass (2048-bit key) header.d=taugh.com header.b=P3DDjGAb
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tmjor24hrTeg for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 13:23: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 338393A0EC3 for <dmarc@ietf.org>; Fri, 12 Feb 2021 13:23:33 -0800 (PST)
Received: (qmail 2877 invoked from network); 12 Feb 2021 21:23:33 -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=b3b.6026f1d5.k2102; bh=iDIduWe19PS0C81RbYsxgUfI3VccrSsxLvaWXLwidEw=; b=e7xCYcG2Pype3z71XeueUslZxroQ76viddjyQGZdocalyFsuTXLzlPowo2YBGB8yrW8N9PW56SDMPHYGKo6HnuhOCW8EwqeMKhhsHP1h2zam7K/9GrFrBkN5zCoqJVVAlIuzDvWVARGzYb5vhiDVtWTAXlkM+PWZPVwG6ObZ4x/Q09FNuD971xGtYHdqCZpSsXX4HmjFe1fiTnmIoB4zv5RUtqwVBUgWsFH78oc1P2INeGj4XPF4Vfhzd46BkRfW/1PciPBXWwsmjjwdDaH63NpL8njqWmXhtzdxPMc8Sx4DWpy2hOe94/t5xJjOtN9flpinlKhjR/RzIPeVbirMtA==
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=b3b.6026f1d5.k2102; bh=iDIduWe19PS0C81RbYsxgUfI3VccrSsxLvaWXLwidEw=; b=P3DDjGAbC6fmC0OccRZiKEhKF6KuIExZUZT/dqFqCqRPbn4GAqaRXQyOGb/tVuAaZ6RAW/fQmE5clSi9MSWa5MWzRqwlr7EkYf26wUK7fZdSeor3Enp52EecQChdquEuUOSN5q29pm8byAFl8HVmCL325ACKPji2C7d72OhHMIhEslqL0KiVrlwQYpu50+0csWI1yT0DsUpj4jxP1uaYVsp5PjuiMN+q8/tJlOdPqDdiJRC4SPxHN4y3qQHnzCTXuElMJWgqHCbQd75hrd05wFvQOP+CM1Clqoe1PUWLKDZmXNUimyqE4yjH1OJ1X9Tablm5dglD2MD7IzfVQMomMA==
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; 12 Feb 2021 21:23:32 -0000
Received: by ary.qy (Postfix, from userid 501) id 3D63C6DDBA71; Fri, 12 Feb 2021 16:23:31 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 9FD7B6DDBA53; Fri, 12 Feb 2021 16:23:31 -0500 (EST)
Date: 12 Feb 2021 16:23:31 -0500
Message-ID: <9ca2792f-d7d2-70b6-a814-a08bfc31d9ba@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Seth Blank" <seth@valimail.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
In-Reply-To: <CAOZAAfPOW6DC3q0pusF4pZr5+OwdEBWWg284RFPfEEUv5_uQOw@mail.gmail.com>
References: <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> <20210212204624.BD53A6DDB3F5@ary.qy> <MN2PR11MB435180303B5EAD3349B189F1F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAOZAAfPOW6DC3q0pusF4pZr5+OwdEBWWg284RFPfEEUv5_uQOw@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/jM1LhRNmw5Mv6NRP_n-0__PhpmU>
Subject: Re: [dmarc-ietf] [EXTERNAL] Re: Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 12 Feb 2021 21:23:36 -0000

> In the data itself, there are summaries of IP addresses and authentication
> statuses of mail that fall into three categories: 1) mail that is
> authenticated by the domain, 2) mail that fails to authenticate as the
> domain, and 3) mail that is wholly unauthenticated. From a domain owner
> perspective, this means they get reports of mail that is 1) authorized by
> them, 2) not authorized by them, or 3) broken by forwarding or other
> rewriting by an intermediary. ...

All true, but more to the point, the reports include IP addresses and 
domain names of mail servers and DKIM signers, not IP or e-mail addresses 
of individual users.  There's no PII other than in the extreme case that 
the domain has only a single user so all of the mail can be attributed to 
that user.

R's,
John

PS: updated the ticket title to say aggregate reports

PPS: that extreme case lets me tell things like how many NANOG subscribers 
get their mail at gmail.


From nobody Fri Feb 12 13:27:20 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 16A663A0EE6 for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 13:27:19 -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 6Xu_N59Of5H4 for <dmarc@ietfa.amsl.com>; Fri, 12 Feb 2021 13:27:17 -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 30D873A0EE5 for <dmarc@ietf.org>; Fri, 12 Feb 2021 13:27:17 -0800 (PST)
Received: by mail-vs1-xe30.google.com with SMTP id y123so317107vsy.13 for <dmarc@ietf.org>; Fri, 12 Feb 2021 13:27:17 -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=yGo4J8zevOuhOlNM6+fuGXsebTzN9yKOPoZRgzr64Ao=; b=LT+ilJsrIFoWD4jDPYH7AjJ4YKK5J1KAXPUvPA8g+zf18yUCNrscatFZ1WkBJQ7QTB Ei8NO/RiiWWMF2TptMzj+vq/Nvh15n8eShdNFipvJh0GmwHJdCOZ69uegM8EbWIm4FEK EWvjnD6Eu/i0oc5/RprARgiMJvegUbLFYZ4cGbdRZwMfR7NePiHjXesyF5QDl3TK8Zu+ YHamojC3MFWhahIuCvtAogdJLfwy23P3T7+XZQtAJcseIZ9WcAWPUBps/C1H///h0LlM QvkL8CXK1xsdoFm9AjezaiaIv0RuVzX7hesoKld5qYW//rXcbiiH2ciUL+cbCbLr91GO slXQ==
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=yGo4J8zevOuhOlNM6+fuGXsebTzN9yKOPoZRgzr64Ao=; b=hM7GExJfSAkJ32CSW3FNRJSFvYExKHP+ryhFBIEbU9W615/tQgXwj+1jrgcxvZSEAg fCQISoI7OW48RosTPXPoRnCr2ACGlhOF+z/JxRIJYMAFwncn79PGwTeGRt+C+Q9fK+SA HRt7W2rSGuh0fjyNy5sFAopid4caPtaJvrXNm6TgPDfXWR42B9CuJpx4RlNBPDMq9MRH YgyagPSoAt3H8wqNkzz9CyPvy5tWAXgjyffgdoJfYakGSTl+zHYsGsVk55fwsa1ENScr xeYX4UZ0P6LCY07UVJhnzhkxjA13LH8ffcJ8FtyXiMasUJZiwWeICmiHqwETPwRMCT7z l6SA==
X-Gm-Message-State: AOAM533Cam9Y/R3/8MmBd+3vtKIfBbFMmTaRvVPezzJfnnOJKpm3mmmx YgBc33FTJH5dfzvYq4gaAT8BzfUHAtVsNEeyeWz1ng==
X-Google-Smtp-Source: ABdhPJzVf3oShNpTsC2aocEACiYG+q0Zn8LnataiEAgwzLEXbz7jfz0G/O/Px3r+QOBM90gt14e+JyU2x5Bzmhmp4y8=
X-Received: by 2002:a05:6102:a1c:: with SMTP id t28mr3341416vsa.56.1613165234674;  Fri, 12 Feb 2021 13:27:14 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> <20210212204624.BD53A6DDB3F5@ary.qy> <MN2PR11MB435180303B5EAD3349B189F1F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> <CAOZAAfPOW6DC3q0pusF4pZr5+OwdEBWWg284RFPfEEUv5_uQOw@mail.gmail.com> <9ca2792f-d7d2-70b6-a814-a08bfc31d9ba@taugh.com>
In-Reply-To: <9ca2792f-d7d2-70b6-a814-a08bfc31d9ba@taugh.com>
From: Seth Blank <seth@valimail.com>
Date: Fri, 12 Feb 2021 13:27:03 -0800
Message-ID: <CAOZAAfOBE9Dt+a7i1U83tpA4hVGcfZfDcd_8wDpH2opVoi-R0g@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c6f41e05bb2a4cbc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/sdV-_Tt3TYCkV7d7ZyhbOQzjb64>
Subject: Re: [dmarc-ietf] [EXTERNAL] Re: Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 12 Feb 2021 21:27:19 -0000

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

Yes, very true. Again as an individual, I think it's worth calling out
explicitly in the draft, simply because it does seem to cause friction with
implementations.

On Fri, Feb 12, 2021 at 1:23 PM John R Levine <johnl@taugh.com> wrote:

> > In the data itself, there are summaries of IP addresses and
> authentication
> > statuses of mail that fall into three categories: 1) mail that is
> > authenticated by the domain, 2) mail that fails to authenticate as the
> > domain, and 3) mail that is wholly unauthenticated. From a domain owner
> > perspective, this means they get reports of mail that is 1) authorized by
> > them, 2) not authorized by them, or 3) broken by forwarding or other
> > rewriting by an intermediary. ...
>
> All true, but more to the point, the reports include IP addresses and
> domain names of mail servers and DKIM signers, not IP or e-mail addresses
> of individual users.  There's no PII other than in the extreme case that
> the domain has only a single user so all of the mail can be attributed to
> that user.
>
> R's,
> John
>
> PS: updated the ticket title to say aggregate reports
>
> PPS: that extreme case lets me tell things like how many NANOG subscribers
> get their mail at gmail.
>


-- 

*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.

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

<div dir=3D"ltr">Yes, very true. Again as an individual, I think it&#39;s w=
orth calling out explicitly in the draft, simply because it does seem to ca=
use friction with implementations.</div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Fri, Feb 12, 2021 at 1:23 PM John R Le=
vine &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.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">&gt; In the data=
 itself, there are summaries of IP addresses and authentication<br>
&gt; statuses of mail that fall into three categories: 1) mail that is<br>
&gt; authenticated by the domain, 2) mail that fails to authenticate as the=
<br>
&gt; domain, and 3) mail that is wholly unauthenticated. From a domain owne=
r<br>
&gt; perspective, this means they get reports of mail that is 1) authorized=
 by<br>
&gt; them, 2) not authorized by them, or 3) broken by forwarding or other<b=
r>
&gt; rewriting by an intermediary. ...<br>
<br>
All true, but more to the point, the reports include IP addresses and <br>
domain names of mail servers and DKIM signers, not IP or e-mail addresses <=
br>
of individual users.=C2=A0 There&#39;s no PII other than in the extreme cas=
e that <br>
the domain has only a single user so all of the mail can be attributed to <=
br>
that user.<br>
<br>
R&#39;s,<br>
John<br>
<br>
PS: updated the ticket title to say aggregate reports<br>
<br>
PPS: that extreme case lets me tell things like how many NANOG subscribers =
<br>
get their mail at gmail.<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><div style=3D"text=
-align:left"><span style=3D"vertical-align:baseline"><br></span></div></spa=
n><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"><img src=3D"https://valimail-logos.s3.a=
mazonaws.com/Valimail__Tag_DarkBlue_TM.png" style=3D"height: 35px; width: 1=
59px;">`</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>

--000000000000c6f41e05bb2a4cbc--


From nobody Fri Feb 12 16:38:42 2021
Return-Path: <agenda@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 998AD3A1191; Fri, 12 Feb 2021 16:33:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <alexey.melnikov@isode.com>, <dmarc-chairs@ietf.org>
Cc: dmarc@ietf.org, superuser@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161317641460.31337.6291091878244027340@ietfa.amsl.com>
Date: Fri, 12 Feb 2021 16:33:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/C86Pdto53QLOW2fRZoYn78vcr40>
Subject: [dmarc-ietf] dmarc - Requested session has been scheduled for IETF 110
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, 13 Feb 2021 00:33:44 -0000

Dear Alexey Melnikov,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    dmarc Session 1 (1:00 requested)
    Wednesday, 10 March 2021, Session II 1530-1630
    Room Name: Room 2 size: 502
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/110/sessions/dmarc.ics

Request Information:


---------------------------------------------------------
Working Group Name: Domain-based Message Authentication, Reporting &amp; Conformance
Area Name: Applications and Real-Time Area
Session Requester: Alexey Melnikov


Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 76
Conflicts to Avoid: 
 Chair Conflict: dnsop dprive cfrg kitten emailcore
 Technology Overlap: saag uta extra jmap cbor






People who must be present:
  Alexey Melnikov
  Murray Kucherawy
  Seth Blank
  Tim Wicinski

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Sun Feb 14 03:02:40 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 202293A0BE9 for <dmarc@ietfa.amsl.com>; Sun, 14 Feb 2021 03:02:39 -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 gWm60nw3v5tM for <dmarc@ietfa.amsl.com>; Sun, 14 Feb 2021 03:02:38 -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 CD8E53A0BDF for <dmarc@ietf.org>; Sun, 14 Feb 2021 03:02:37 -0800 (PST)
Received: (qmail 14204 invoked by uid 100); 14 Feb 2021 11:02:35 -0000
Date: 14 Feb 2021 11:00:57 -0000
Message-ID: <20210214110057.13630.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/HwobRDRIjyZCbliBTf1UA-VcCmA>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Feb 14 06:02:35 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, 14 Feb 2021 11:02:39 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
  5 (20.0%) |  76428 (29.0%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  5 (20.0%) |  23572 ( 9.0%) | John Levine <johnl@taugh.com>
  4 (16.0%) |  37980 (14.4%) | Scott Kitterman <sklist@kitterman.com>
  3 (12.0%) |  55523 (21.1%) | Seth Blank <seth@valimail.com>
  2 ( 8.0%) |  26578 (10.1%) | Brotman, Alex <alex_brotman@comcast.com>
  2 ( 8.0%) |  10490 ( 4.0%) | Alessandro Vesely <vesely@tana.it>
  1 ( 4.0%) |  18251 ( 6.9%) | Todd Herr <todd.herr@valimail.com>
  1 ( 4.0%) |   6212 ( 2.4%) | Kurt Andersen (b) <kboth@drkurt.com>
  1 ( 4.0%) |   5576 ( 2.1%) | Dave Crocker <dcrocker@gmail.com>
  1 ( 4.0%) |   2617 ( 1.0%) | "IETF Secretariat" <agenda@ietf.org>


From nobody Sun Feb 14 12:13:01 2021
Return-Path: <worley@alum.mit.edu>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D95343A099F for <dmarc@ietfa.amsl.com>; Sun, 14 Feb 2021 12:12:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.224
X-Spam-Level: *
X-Spam-Status: No, score=1.224 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.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 kNj0F8UXDRYu for <dmarc@ietfa.amsl.com>; Sun, 14 Feb 2021 12:12:57 -0800 (PST)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (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 31EAF3A098C for <dmarc@ietf.org>; Sun, 14 Feb 2021 12:12:56 -0800 (PST)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-01v.sys.comcast.net with ESMTP id BNhWlvsuufFsMBNlIlje54; Sun, 14 Feb 2021 20:12:56 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1613333576; bh=HioRR+VZjzJq67UHB8Ay5eBMhJPw3LlJOEF0vMsZTFo=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=Az36eIiMfUf1dQXfR/jbvk2SF9bBA4mtL3/VbIUtaFAH92lQa0DsWe3cIsPApa+3z NIaIimXjZbnETeFk+207/ky6qNN/cBFoYxCxaxN7jRljpOpK3yhRdeMr1YzZSsWt3o wU7RCOrkOgpO43pD6HnUUGmlrbk1Fz4kuQbhW1XS6R2WT6ZZkv86YdKr0hU2N4FHaQ 9WUL51QRD3USk5auf2kzHAfeFoA2tnjUZlhZr+iDJLQSDHNKaDeY9tOBwpVIP9Kq2v h5pOPIC4y45IFbXp54WUueZbAhzigzpTJMBF4KfLKRtU30etRxTSFa0dgF/hGJiyB5 +iaStRHFp3OAA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-12v.sys.comcast.net with ESMTPA id BNlFlrQB4o85jBNlFlvtgb; Sun, 14 Feb 2021 20:12:55 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id 11EKCqL2022125; Sun, 14 Feb 2021 15:12:52 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 11EKCqq3022122; Sun, 14 Feb 2021 15:12:52 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: dmarc@ietf.org
In-Reply-To: <CAL0qLwbiOrgsEjZU_V6W8e42SRNoUh7CzyngRMR5RLeQpzrxaQ@mail.gmail.com> (superuser@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 14 Feb 2021 15:12:52 -0500
Message-ID: <87o8gm4ddn.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rHOhle1JXXM64-pfIrE7l8eaXEQ>
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, 14 Feb 2021 20:12:59 -0000

My apologies for not replying to this sooner.

To give the TL;DR, I think the proposed changes adequately address my
concerns.

"Murray S. Kucherawy" <superuser@gmail.com> writes:
> 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.

Yes, I've noticed that people (even authors) forget that Gen-Art
reviewers do not have veto power, they are just additional commentators.

Dale


From nobody Mon Feb 15 05:31: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 746D13A09C9 for <dmarc@ietfa.amsl.com>; Mon, 15 Feb 2021 05:31:03 -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, 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 NkBYmA2S0she for <dmarc@ietfa.amsl.com>; Mon, 15 Feb 2021 05:31: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 14CF83A09C7 for <dmarc@ietf.org>; Mon, 15 Feb 2021 05:31:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1613395857; bh=ygYt6sleBUZRVQNugVCI0zM1CZg6TwCHQ+uSlvNUA8k=; l=1685; h=To:References:From:Date:In-Reply-To; b=Cc5aP3V95Q438h9MPPS9TaqsAH3uk4Ba/BcFTfJ0h650pNOkqNtbJE+Mg+YprfffM e9gAp66wkXo7ypWp56t7RmmxhFVc/D6Lcv2Bb7bl7lROfkoPs0K1r3GroHa0ug1if9 LsQv/USF1MquRFkhUa3LdJWShn7YZ/iBXDFO1Q9B9/skILBayTegKddj4mIj1
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 00000000005DC050.00000000602A7791.00004EDE; Mon, 15 Feb 2021 14:30:57 +0100
To: dmarc@ietf.org
References: <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <7086a5e4-2a9c-bbdc-1969-f77d0d00fa38@tana.it>
Date: Mon, 15 Feb 2021 14:30:57 +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: <MN2PR11MB435185A171029EF4282A2BF4F78B9@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/Nb8Hv538l_li9_WEsyI0JYxcbmI>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 15 Feb 2021 13:31:04 -0000

On Fri 12/Feb/2021 21:30:38 +0100 Brotman, Alex wrote:
> Hello folks,
> 
> In ticket #64 (https://trac.ietf.org/trac/dmarc/ticket/64), it was suggested that a Privacy Considerations section may alleviate some concerns about the ownership of the data.  I created an initial attempt, and thought to get some feedback.  I didn't think we should go too far in depth, or raise corner cases.  Felt like doing so could lead down a rabbit hole of trying to cover all cases. This would go within a "Privacy Considerations" section.
> 
> * Data Contained Within Reports (#64)
> 
> Within the reports is contained an aggregated body of anonymized data pertaining
> to the sending domain.  The data is meant to aid the report processors
> and domain holders in verifying sources of messages pertaining to the
> 5322.From Domain.


I'd replace all those 5322.From Domain with main DMARC identifier.


> The data should not contain any identifying
> characteristics about individual senders or receivers.


The aggregated data refers to names and IP addresses of SMTP servers.  It 
cannot be used to identify individual users.


>  An entity
> sending reports should not be concerned with the data contained as
> it should not contain PII (NIST reference for PII definition), such as email addresses or
> usernames.


I'd substitute /should not/does not/.  Even if a server has a unique user, the 
domain name and the IP address are those of a public entity, not those of a 
private citizen.

The term Personally Identifiable Information (PII) is US-national.  I think 
just personal information is of broader use.  Personal data is also a valid 
alternative.


jm2c
Ale
-- 
























From nobody Wed Feb 17 10:40: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 85D953A0D74 for <dmarc@ietfa.amsl.com>; Wed, 17 Feb 2021 10:40:55 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=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=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 WoDF9-YFrw4h for <dmarc@ietfa.amsl.com>; Wed, 17 Feb 2021 10:40:53 -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 C4FB73A0D63 for <dmarc@ietf.org>; Wed, 17 Feb 2021 10:40:53 -0800 (PST)
Received: from pps.filterd (m0184893.ppops.net [127.0.0.1]) by mx0a-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 11HIQL32024420; Wed, 17 Feb 2021 13:40:53 -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=QRnYhhmQg54MRPVp7in5nuP7ATAGjl7yesegrClucAE=; b=dpvXTG7mQmlEr0kMh3d6P6j0ouBKbOpRYtAbNfA6K9mzdWlLL6DYR52QU4KqlmiOQpl7 NOrCNX0qMkEOqKIa+e4bcZbG5xQwG7MMB1L+HtJHc53wRrEYp3UbPk/UNr32juzAefYu anWAKcUHS4nBRUD9tkPpypyzzmsPTepkpteOqApXyhmg0Aqy5QBnNzTzlYgylNNgE6ku AI2IVavz5aYy8G2p2GRSvEwEvN27moOFb7CXVrj7TMrjhSkqszMPWaAgM+8fE/4YXMm6 ioW2yNcM6hro8rQBc9DHljKUFybcaxv4L3k2vPBTR/wbqbwDULqfK6c7AvvNwj1RoEox Hg== 
Received: from pacdcex55.cable.comcast.com (dlppfpt-wc-1p.slb.comcast.com [96.99.226.136]) by mx0a-00143702.pphosted.com with ESMTP id 36patn421r-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 17 Feb 2021 13:40:52 -0500
Received: from PACDCEX49.cable.comcast.com (24.40.2.148) by PACDCEX55.cable.comcast.com (24.40.2.154) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 17 Feb 2021 13:40:50 -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; Wed, 17 Feb 2021 13:40:50 -0500
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.171) by webmail.comcast.com (76.96.78.71) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 17 Feb 2021 13:40:24 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by MN2PR11MB4632.namprd11.prod.outlook.com (2603:10b6:208:24f::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.29; Wed, 17 Feb 2021 18:40:13 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::2495:cfaf:88ca:6b2d]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::2495:cfaf:88ca:6b2d%7]) with mapi id 15.20.3868.027; Wed, 17 Feb 2021 18:40:13 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: Alessandro Vesely <vesely@tana.it>, "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
Thread-Index: AdcBfLdYcAd1ycC0TvWJKBD11cOyegCIhNKAAG9eXXA=
Date: Wed, 17 Feb 2021 18:40:13 +0000
Message-ID: <MN2PR11MB435129E4F5DA8C8EC141E9E9F7869@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> <7086a5e4-2a9c-bbdc-1969-f77d0d00fa38@tana.it>
In-Reply-To: <7086a5e4-2a9c-bbdc-1969-f77d0d00fa38@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:c4e0:d169:12f5:37d8]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0e074d3d-4361-4225-73ce-08d8d373766c
x-ms-traffictypediagnostic: MN2PR11MB4632:
x-microsoft-antispam-prvs: <MN2PR11MB463297513FFE4785C4C2AC20F7869@MN2PR11MB4632.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: cG4kjoAcacxVDJngbQLd//dkqzEkZl+WyUPNeejXb+7IRoQu77MQIM7u/b18e9KaD7Gq11pyBtiEFn32DOlXUvidSvJF6uE7eHZPaS38rDn1PLu6sGn0L2FUhfjjMmLbdDIsByTfRmu+Hm/dbw6iv/oocY1npONdmH81pVQqkHRxblHbSQwmVBgRFTRT9F0c8zcL6H0iqOenOrLWclMuMTYp2MOk+Wj7ZFmAbqpQDywAJdkyEIN+cAHbSnt0L5/OOxCD/p58zlnksolt6Zf7JjS8cW7Fw7v+Oue3PM4EyWGrHv+PLABYl1du+NPR9PCXFN0zKAJ/Pz3H0Tfs50mWMVbzel9lewKW1wRSIRmT4FDK2nlGbA6oyAMukdR6c1omOziE00YJu02oUmisgejdtZNG4Y8/I30iI00wfJzcVDt82cmil8C5pOqYLE1nbBjqxqWb/IO7jGC3N7LlNBGheOgjYKNwspAD5foUuHpje13Cq5Go1DwsTyeCLHJoB367Nsn53TnC/i/FXv4Y9DtMotVXo3dkrtpidMi9QJJ6Mxc8MG/qFzDhQ7fsAc1CBH0ho4IPaSB2xJP9O2rj8kb74q+L1VRLyV8L8FUgBiJsgIw=
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)(366004)(376002)(39860400002)(396003)(136003)(71200400001)(2906002)(52536014)(110136005)(186003)(76116006)(8676002)(6506007)(64756008)(8936002)(83380400001)(53546011)(478600001)(5660300002)(966005)(66476007)(86362001)(66446008)(316002)(7696005)(9686003)(66946007)(55016002)(66556008)(33656002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?5K/N8Pc6dtSP6sJZNXvOy4b8K/r+M/WgWQb6k7dlNyfGZfJZDliQEkmvuV83?= =?us-ascii?Q?pXhXmOQ8oNldXPy7CooFHY2m4MaJX3hAy3NSxIs8zhh6ODCO2RPuI8k1Ae2y?= =?us-ascii?Q?RS7PsKKQjm4cHzgXL9o0CqXrztkJ3x3OsD6vC0zkpYmQKVsB0tLaLbMsu/yj?= =?us-ascii?Q?YDqTObKuEHdj2FUciP2gpbhxuduE1QkyTUIK7OyqjtDGd69/1DSABB+TSLNe?= =?us-ascii?Q?9ZWDL8+HJTCW4ExXQW3l9aGDtt3PTIYrOmpupWlvzrs95moxoRJDHL8QmcAF?= =?us-ascii?Q?K9rRC9GdpzrBQvW6GDp97AJl5bVWtAKIUp+/ZZ8qHRIxKIRj13WqhFWlDHMk?= =?us-ascii?Q?YkcYChci/dVfakNbBD4Dxx9IrOphhyuMqXszZySnPgv2qpFr8ympXVIAXtFE?= =?us-ascii?Q?scmDP35ZTIslk5hgYvbCvcT38GGG5BX01b+M5BN7jEyB0XVx7o+LXJoaBQ4U?= =?us-ascii?Q?iZllg1+ErCuDIk4mczSC3tG/SUJbXROTdm251JlBKAOSVjehq75trCkAFqU6?= =?us-ascii?Q?p2uHH1JrAaqV/Unt1uu3VGfHSnuoXFT22ARwzTplzHPGlCiKQaxsDnx/nhdE?= =?us-ascii?Q?uq/ttHSE01Ekwm/3v5DLZiZiycn/fAnnvFXwqMraCZ4Z3fIGShYEoYomufGf?= =?us-ascii?Q?lkWWV+qC2m9+PfyALYhlMTefHy+peqtD3uHjLWG5+8zFOU6ifUeESFEyS7ws?= =?us-ascii?Q?2vbP9qtvQQHLrNK1Ej8NRtr9UVKh4eqlo6FM1J/nazUH4GmKRAb7LW8giKjl?= =?us-ascii?Q?qnNaOzuY+njLZSyP8X3c5DnpWnSs8xHRSoqT2vEOyTnPjaRorSGZhAg9/4aP?= =?us-ascii?Q?KKz/I5iPIM1Gi/axwlYXy/i01eyq8vVlOTiCa9Ry9qkmQ5AMMqAGtjxACp2T?= =?us-ascii?Q?lKatTFx3iyPvzNVLUOfYBJk6Qdr0wJWG3QXj3E7Ca/ueKms3zbGgd2BgeI65?= =?us-ascii?Q?hoN5NnnsDhtD+PEiCloySf9irDGJPBgyF+CgY2wgTqPryQrGXJxgOCFnonVC?= =?us-ascii?Q?CrykVz3tlJxK8i4dHsHjUyMvjYt7ZYWvTu36VjWBRoifLWRAHCcyLqsPhd15?= =?us-ascii?Q?owwXZO8hYnhGsWaj6FMRAD8vdvq1YV4viNpNiGD+9kfiKs84R8YZKrl1m3x/?= =?us-ascii?Q?AtMhFSM2R7IociPYNbZy5KuSmisDb1/xxbApd5ic9fy7vPOC6MfIRYNM6/Mb?= =?us-ascii?Q?WAHJ1bVURZZlwXN4rX1jxNDb799kASWIKyJHgCyWqDkBfV+t8zAkYn8Sn7hA?= =?us-ascii?Q?X85POR7HcOBq2RWszjGShmjO0Rshc8/8Bdj74xw/R1C3G+QHEkxgpBXlF5+J?= =?us-ascii?Q?3LZX3Y3CUWUqiOm7B5PkjfiJD3U4d3Cs4v9nSZ67L5DBUgabK9OLn/r5QD57?= =?us-ascii?Q?uUmAmUg=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LuhX4mqHlVAhFqGHxefMm3Lb0ghfpv4cw6gNo5cGxMy33fcTrR4nHp+X8PlrBsW9WKtpQjsyYwzyXijzl2ZbFkh3cUVJTuISeNvwIgs2l3Lg7VvWGKULQN3fLk6PoW9kZc6HEWwvrujh0iiUwnWFnHoUQDulnI6IKc8YmjL/uJfNgaROk2OXozcAHO6XV7IHNV+fbeo6t/7GcmrUF9Rycu6MmxEcCHko+jUuZs4sUM6yHBDpk2o+5DibsFZuBWyRRoL2aeqnNiIwYePr0tN0N0PXkp5vjzQc17nXoG+5ALrH83ni26RUAOC/+P4aR5vSNSNj/67wWI9b3gBdJ+4UUQ==
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=JnmGkHWRO9leF3V08GsVl2AJVw8yvKzDoDLpDSmH5so=; b=XtWJi2opYprom+5Baw2XR9FNDbtCov7S9rhPhVuTT0tBWysaQAXUuFsGq92yEhuVxvnTUPXKhttMQblQrVZIqBAHS3GduAUBIaDtFJL1AurZNCARQ5sznl+Ii21DMl+QM1bUl4/FLzZMuGgzvn7XX09GE46OOHhoeIibnz0xFrgsw22yJPIsVBwuhT63jPq4MaGiVECrdk92ftlPssa6jZsGP8u2iHYwDair0u8KqjntvCjR16oAlXUG6oYbzYeeVFUD9mmka0MUK7GcGO19pgHmI1PdITg19x9mfMh19VkZaENCsxWOgBmaF2w4gQXHNa5F65fvmQEXpIcyzePsQg==
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: 0e074d3d-4361-4225-73ce-08d8d373766c
x-ms-exchange-crosstenant-originalarrivaltime: 17 Feb 2021 18:40:13.2924 (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: aJDCJo5ypJDpnQFdbCW1wNA0E8dR+M679q1K5FvNCUJIIiFK5Fjqf85X5cbBMQgK02IWPAo0Z75EnsWqhlifeHnQ1e8yTpJww6Om54gSFpI=
x-ms-exchange-transport-crosstenantheadersstamped: MN2PR11MB4632
x-originatororg: comcast.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWB
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-02-17_13:2021-02-16, 2021-02-17 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/GKoqRt2HyWDh2-vL8sP1mIdgRl0>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Feb 2021 18:40:56 -0000

Incorporating some feedback:

-------------------
## Data Contained Within Reports (Tkt64)

Within the reports is contained an aggregated body of anonymized data perta=
ining
to the sending domain.  The data is meant to aid the report processors
and domain holders in verifying sources of messages pertaining to the
DMARC Identifier.  The data should not contain any identifying
characteristics about individual senders or receivers.  An entity
sending reports should not be concerned with the data contained as
it does not contain personal information, such as email addresses or
usernames. There are typically three situations where data is reported to
the aggregate receivers: messages properly authenticated, messages that fai=
l to
authenticate as the domain, or messages utilizing the DMARC Identifier that
have no authentication at all.  In each of these cases, there exists no ide=
ntifying
information for individuals, and all content within the reports should be r=
elated
to SMTP servers sending messages posing as that domain.
-------------------


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

> -----Original Message-----
> From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Alessandro Vesely
> Sent: Monday, February 15, 2021 8:31 AM
> To: dmarc@ietf.org
> Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
>
> On Fri 12/Feb/2021 21:30:38 +0100 Brotman, Alex wrote:
> > Hello folks,
> >
> > In ticket #64
> (https://urldefense.com/v3/__https://trac.ietf.org/trac/dmarc/ticket/64__=
;!
> !CQl3mcHX2A!W97hZ0-
> iwRDi8wBssmRFF6OycVE12vM3xhGd9BmLhEzi6Vycp3bgzwji21xLQQgnnMRa
> BuxGQg$ ), it was suggested that a Privacy Considerations section may
> alleviate some concerns about the ownership of the data.  I created an in=
itial
> attempt, and thought to get some feedback.  I didn't think we should go t=
oo
> far in depth, or raise corner cases.  Felt like doing so could lead down =
a rabbit
> hole of trying to cover all cases. This would go within a "Privacy
> Considerations" section.
> >
> > * Data Contained Within Reports (#64)
> >
> > Within the reports is contained an aggregated body of anonymized data
> > pertaining to the sending domain.  The data is meant to aid the report
> > processors and domain holders in verifying sources of messages
> > pertaining to the 5322.From Domain.
>
>
> I'd replace all those 5322.From Domain with main DMARC identifier.
>
>
> > The data should not contain any identifying characteristics about
> > individual senders or receivers.
>
>
> The aggregated data refers to names and IP addresses of SMTP servers.  It
> cannot be used to identify individual users.
>
>
> >  An entity
> > sending reports should not be concerned with the data contained as
> > it should not contain PII (NIST reference for PII definition), such as =
email
> addresses or
> > usernames.
>
>
> I'd substitute /should not/does not/.  Even if a server has a unique user=
, the
> domain name and the IP address are those of a public entity, not those of=
 a
> private citizen.
>
> The term Personally Identifiable Information (PII) is US-national.  I thi=
nk
> just personal information is of broader use.  Personal data is also a val=
id
> alternative.
>
>
> jm2c
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/dmarc
> __;!!CQl3mcHX2A!W97hZ0-
> iwRDi8wBssmRFF6OycVE12vM3xhGd9BmLhEzi6Vycp3bgzwji21xLQQgnnMTF6
> fzPKA$


From nobody Wed Feb 17 13:27:08 2021
Return-Path: <ken@wemonitoremail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92CEB3A1D81 for <dmarc@ietfa.amsl.com>; Wed, 17 Feb 2021 13:27:07 -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, RCVD_IN_MSPIKE_H2=-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=wemonitoremail.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 NTBuyXyPp6UH for <dmarc@ietfa.amsl.com>; Wed, 17 Feb 2021 13:27:05 -0800 (PST)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2096.outbound.protection.outlook.com [40.107.22.96]) (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 347013A1D7B for <dmarc@ietf.org>; Wed, 17 Feb 2021 13:27:04 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gTqrPC9JiYWWT3rjTIczxBAiSzzKRdOiFxct+fRTG4x3JOHzLpUCt4Sj3EpiC9EDZERLHwCmMfTaf6ygJoMargrBCmPSR/fj2HT8D44OYYODQz5l+uLmbGnzBUtctGadDfcFhWMFmCsIqSiiX33tMA1uXuU52AkHGNaYyIkSVDa7mgcqE+0FSbqfJt9H71e9Mj4O9yHlZFyvnRL8UVeZGkNM/0nJ2Nxaq0lYsFfwvjJPiPhu4Nqb+AhQ1rPxNz2gLVHjT0w+dDNuBP1JDcqUIlfQFSs5gTw6xxDsKISa0ordBVfWEm4HolzEq+zclwHXuQcnI06jedZXC/O/JXp80A==
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=aI8y/8UfryRqEqyU7ZTRGj2OQhrvhVeEeYt4MD99b10=; b=jtM17MqjUH2SgVkaczmaA+K9U8TPB/teUC5VSaKKD3pD1DaPPh7eVC3HKRFIvdW7ONqLXoX7bVopI0UZabvaS3QEF8Tkpufwro+UR5nUvQQrjKgvUdZ52q9kytXGTMZCWfOXJPdzkXFTI+9x+4rN/pvmG/RJj3vRQFa8JCRUdWfdSTMBBv2hJyL3u1V2sH2AvQPFlsuiClA+ru8tQzeowYkaIHpyfBEN/rNDOdKC6ubA/gKDtlJRU97YlEbiI2Lby1o71FOJV45KcAZ8uP19uurvLqw3RKnPazUauseeWM8+SZndEOSml9t4KI5dDcr8mlB72VP0sQu2qcnFncME3w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=wemonitoremail.com; dmarc=pass action=none header.from=wemonitoremail.com; dkim=pass header.d=wemonitoremail.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemonitoremail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aI8y/8UfryRqEqyU7ZTRGj2OQhrvhVeEeYt4MD99b10=; b=BSN4sa07yJBBFUSiqxnnFuKgOL6JOihyQiIEUdGCIFqw+K3iy9OeRYZ2FAffpKJAItXoAyjhPqHVZSKMUmfsm7OFeSBn80PPLfSvN+6VCpCWUaywnQg1k+XRLrprzVuR+9tkBndOMHux1YBDCbOS/U6i8siZyrbcCR5Ahw2v+1CV9+5rD97y1WOAJWE7/bMSTij/TDI80rXA3GyvwA/hCxWBlRvKKbOxvJePvV3bSzJsPs5gP5B0qsOuG7s+w5drCjgiwyTCVIYwuUMA8+Z9OH/f676cgUZgNh/ENrgsPReUq8nS8PzPYJoOBPRuHQAVGCGhazlcJh74J1ZrDJlcVg==
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com (2603:10a6:800:19a::9) by VI1PR01MB4270.eurprd01.prod.exchangelabs.com (2603:10a6:803:65::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25; Wed, 17 Feb 2021 21:27:01 +0000
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::9c69:59f:c073:bd9f]) by VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::9c69:59f:c073:bd9f%7]) with mapi id 15.20.3846.039; Wed, 17 Feb 2021 21:27:01 +0000
From: Ken O'Driscoll <ken@wemonitoremail.com>
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>, Alessandro Vesely <vesely@tana.it>
CC: "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
Thread-Index: AdcBfLdYcAd1ycC0TvWJKBD11cOyegCIhNKAAG9eXXAABJQJQA==
Date: Wed, 17 Feb 2021 21:27:00 +0000
Message-ID: <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
References: <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> <7086a5e4-2a9c-bbdc-1969-f77d0d00fa38@tana.it> <MN2PR11MB435129E4F5DA8C8EC141E9E9F7869@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB435129E4F5DA8C8EC141E9E9F7869@MN2PR11MB4351.namprd11.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=wemonitoremail.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 57396170-ecf5-4ba6-2e06-08d8d38ac370
x-ms-traffictypediagnostic: VI1PR01MB4270:
x-microsoft-antispam-prvs: <VI1PR01MB4270637720C7F1728AD12322C7869@VI1PR01MB4270.eurprd01.prod.exchangelabs.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: J0HJR1CVj8Rh1FRckWv9K9hearnk7dFvwaeLCGHqUPEXjsLNNjDoidf8ArSMguHWjmqcwulvcHiLdpfh4lj1swvYc6imY2vUfSrU98KzmumiKHjh4HrYVDwy0iYPdqLAqnX6HqHBkmyvZ8uwtN705jDlqGBsBDPyy+Lx47EJIYDQvDpYjgZA6JfKN5z/l8zKQ0h/+xA0M1hWSZlnHujD6O9h61WR3ej5NaXYDLZlwgK6sp61Bg2pF0r7C7vOwh4SHt1bW8N5I6zZqRSyHHwCdlZNkTIYQbEzccWnYc0RGbcjSPpl+SYJfAAj9093nYBrRptmHViu1UhZetuo8SdAeED3P4uhZVZ7uaNlHmzLPlnUuE1Cx59qyQTdmPToZreFdPqRQoc81EVTLZn38c2atuzYYx59NDYaUxO7u5nJLlYSooF9cOrzCVzovZN5QzgiLfjLq27kjItGLWSAbrXPEOln38eQyAqEM5b+a0m/wHHwgdeioTs4XpgLu0D0Ng/grFaVal4HSYWSUNWwC3FZh+WGC5wOlJmkgINvDfTGT2hYdUi8sXuIQ4VYQpUJ1IPtyCP8rkXPN9ntNh3RybGqGlb391RXwnopIjGPDt7GRqc=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR01MB7053.eurprd01.prod.exchangelabs.com; PTR:;  CAT:NONE; SFS:(376002)(346002)(366004)(136003)(396003)(39830400003)(7696005)(186003)(8676002)(9686003)(86362001)(316002)(64756008)(83380400001)(6506007)(26005)(66446008)(52536014)(66476007)(66556008)(8936002)(110136005)(53546011)(33656002)(55016002)(966005)(5660300002)(4326008)(478600001)(76116006)(2906002)(71200400001)(66946007); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?Tn3W1NQ9xIIgvp346JDRS9IPSCELDmFkTjke8dXXLfwTzjomFTzjjiNYawuB?= =?us-ascii?Q?x3ohDWgKlrcztn6EY+BsQoxizC3skOkInXqaqJdAK+t6ufrcQTSATYglKrG7?= =?us-ascii?Q?kBhUh86uZuGDr+wi4pTuuqphZnBkDjpYoISgDQkTFnse9W5yt9u2JzDZS79r?= =?us-ascii?Q?Vdi9puEzIX9UbK+n695glx7s/G/22QSrh/lmzyZx9rQYkbSogsGMf1A+ACRZ?= =?us-ascii?Q?j8QxuOToBFnudx9v8VxwQxcyhnFd9HKBLed8eB+oyQgA9sLbFX2kX8mDRVAV?= =?us-ascii?Q?TXdfPyOshfEQtucZfMD2LkaLj6iDjkgTwTrTM5w6++HnaToSm/SzSfXGXHj4?= =?us-ascii?Q?Y7D+2EtAkWu5HUaeifr6ndIHyNx93nXan8/XX3qETuFi0+Q9tNWqtlQwuKbZ?= =?us-ascii?Q?UliHlwIgfhxeKKKv2jBDnaNXrrJQeXvRYj29wHHEOo6CUE4YW77u1ScvjoJj?= =?us-ascii?Q?lQY6R3/OQ+K5B9GHHvvJ1HWrRetYMRKFavZrADDrn1PQHp/jfprv7IM4JXeK?= =?us-ascii?Q?BeExxK4Bm6wSqrbAn7UkiibAT2b3PGL/jKGjwhLoxNFFOMlSkznoij2+hITo?= =?us-ascii?Q?3/lc6fF5HdWeGZjbdk1c2oXNGH5kfbE18/6JnPJTzFN8lbGlzdz8Z4C76WM+?= =?us-ascii?Q?Ol2YiA6mWC1P0qhJUnK5XwYDo5ur619QAs7yBWLAi1OExLU5//7GTJLtNwEG?= =?us-ascii?Q?pmv/ZpLqyJ6LfQQ99qNjIoOd3O0FDgcg2GWqVcG91ZL766mOmPLUN1J61uth?= =?us-ascii?Q?g4OY3x9GqoSk0Z4ZBLC6HWx97ZI/OVIPZY3Z6lheAYRMh4OfQnCYhwVFPdRS?= =?us-ascii?Q?HugXF65IndsCzi286BzQDLNo2RrCcuyJNR7ccnUkq90T/oZ6wTLDR4Zbc2EH?= =?us-ascii?Q?W67B2aQEj8JsF6+sjrOyj23DVZKuZfMlfR6K0u0gck+Q8MIj+nvvXBP1q07+?= =?us-ascii?Q?QVF8XPxEWUzRd9dhgh74mCO+yP8pbV+WuSeqhpwaB31mBBnpw/M9L8lISDrP?= =?us-ascii?Q?/ixwUhKvHYyFfj+d8Lfd1mgoEb5/nT9SDlgaYKueiqQcjP2Gskoox9ijCae1?= =?us-ascii?Q?wGX9u0NuFakiVSvcrTH4CAM1GQNZAZnFfdVzbkICkI20UXiezB7wSVzvoN9N?= =?us-ascii?Q?MSrOJzE3XNnFlZM0zAWOIy9asoXNvWPIrb8u5IG2bCmyqAdeBWnZO/nvC+W2?= =?us-ascii?Q?NHRkUE2qXRm02lfYh+mjh5wB2eMUUbteObPLmqNcdBHlUvxK6KHMA1Tg+Iyx?= =?us-ascii?Q?lZTk97+vamhUOxrSG7ABV1Qq9YD9y2G4DITcDZMZZmDM+ptjuf8n9XsDSnTU?= =?us-ascii?Q?ecI=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: wemonitoremail.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: VI1PR01MB7053.eurprd01.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 57396170-ecf5-4ba6-2e06-08d8d38ac370
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Feb 2021 21:27:00.8999 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a2b1d6fe-fc8b-4b7c-b9f1-d7b1ab3d23b3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: w8zwbC1xqQIxAYKu6vgrKmzXyJmpzNABDKR0EvW78xXIjgdgZDH8UawqHx2rKJLNM7MJWmXVRI96tnyj4l9P+w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR01MB4270
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/zqiR5lYV8QljA4dKYRpPix0cSyM>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Feb 2021 21:27:08 -0000

I PM deployments for organisations and the concept of aggregate reports hav=
e caused problem more than once. Similar to the PII concerns of providers w=
hich originated this ticket, these organisations operate in heavily a regul=
ated industry and have extensive DPO functions. To give a flavour of what t=
hose concerns translate to - I have been asked is it possible to implement =
DMARC without using reports! I have also had con-calls about training a new=
 hire to read and classify the reports! That's just two examples. It's most=
ly driven by overzealous DPOs but I understand their concerns on some level=
. When they realise that we can distil the report data and it doesn't need =
to be on-site, they hand wave away any custodian concerns and the project m=
oves forward.

So, assuming that my DMARC clients aren't unique, I'm wondering if this sec=
tion could be split into two parts, one for Mail Receivers and one for Doma=
in Owners?

If so, for Domain Owners, I'd propose something like this:

Aggregate feedback reports are essential for the proper implementation and =
operation of DMARC. Domain Owners can choose to exclusively direct reports =
to a processor external to their organization. In such cases, the content o=
f the reports are never sent directly to the Domain Owner.

Thoughts?

Ken.

> -----Original Message-----
> From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Brotman, Alex
> Sent: Wednesday 17 February 2021 18:40
> To: Alessandro Vesely <vesely@tana.it>; dmarc@ietf.org
> Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
>=20
> Incorporating some feedback:
>=20
> -------------------
> ## Data Contained Within Reports (Tkt64)
>=20
> Within the reports is contained an aggregated body of anonymized data
> pertaining to the sending domain.  The data is meant to aid the report
> processors and domain holders in verifying sources of messages
> pertaining to the DMARC Identifier.  The data should not contain any
> identifying characteristics about individual senders or receivers.  An
> entity sending reports should not be concerned with the data contained
> as it does not contain personal information, such as email addresses or
> usernames. There are typically three situations where data is reported
> to the aggregate receivers: messages properly authenticated, messages
> that fail to authenticate as the domain, or messages utilizing the DMARC
> Identifier that have no authentication at all.  In each of these cases,
> there exists no identifying information for individuals, and all content
> within the reports should be related to SMTP servers sending messages
> posing as that domain.
> -------------------
>=20
>=20
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy Comcast
>=20
> > -----Original Message-----
> > From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Alessandro Vesely
> > Sent: Monday, February 15, 2021 8:31 AM
> > To: dmarc@ietf.org
> > Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
> >
> > On Fri 12/Feb/2021 21:30:38 +0100 Brotman, Alex wrote:
> > > Hello folks,
> > >
> > > In ticket #64
> >
> (https://urldefense.com/v3/__https://trac.ietf.org/trac/dmarc/ticket/64_
> _;!
> > !CQl3mcHX2A!W97hZ0-
> > iwRDi8wBssmRFF6OycVE12vM3xhGd9BmLhEzi6Vycp3bgzwji21xLQQgnnMRa
> > BuxGQg$ ), it was suggested that a Privacy Considerations section may
> > alleviate some concerns about the ownership of the data.  I created an
> > initial attempt, and thought to get some feedback.  I didn't think we
> > should go too far in depth, or raise corner cases.  Felt like doing so
> > could lead down a rabbit hole of trying to cover all cases. This would
> > go within a "Privacy Considerations" section.
> > >
> > > * Data Contained Within Reports (#64)
> > >
> > > Within the reports is contained an aggregated body of anonymized
> > > data pertaining to the sending domain.  The data is meant to aid the
> > > report processors and domain holders in verifying sources of
> > > messages pertaining to the 5322.From Domain.
> >
> >
> > I'd replace all those 5322.From Domain with main DMARC identifier.
> >
> >
> > > The data should not contain any identifying characteristics about
> > > individual senders or receivers.
> >
> >
> > The aggregated data refers to names and IP addresses of SMTP servers.
> > It cannot be used to identify individual users.
> >
> >
> > >  An entity
> > > sending reports should not be concerned with the data contained as
> > > it should not contain PII (NIST reference for PII definition), such
> > > as email
> > addresses or
> > > usernames.
> >
> >
> > I'd substitute /should not/does not/.  Even if a server has a unique
> > user, the domain name and the IP address are those of a public entity,
> > not those of a private citizen.
> >
> > The term Personally Identifiable Information (PII) is US-national.  I
> > think just personal information is of broader use.  Personal data is
> > also a valid alternative.
> >
> >
> > jm2c
> > Ale
> > --
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > dmarc mailing list
> > dmarc@ietf.org
> > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/dmar
> > c
> > __;!!CQl3mcHX2A!W97hZ0-
> > iwRDi8wBssmRFF6OycVE12vM3xhGd9BmLhEzi6Vycp3bgzwji21xLQQgnnMTF6
> > fzPKA$
>=20
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


From nobody Wed Feb 17 18:21:31 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 1EB263A1EF2 for <dmarc@ietfa.amsl.com>; Wed, 17 Feb 2021 18:21:30 -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 BsAiXBt7iqqG for <dmarc@ietfa.amsl.com>; Wed, 17 Feb 2021 18:21:27 -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 ADA893A1EF0 for <dmarc@ietf.org>; Wed, 17 Feb 2021 18:21:27 -0800 (PST)
Received: by mail-vs1-xe30.google.com with SMTP id a11so187380vsm.7 for <dmarc@ietf.org>; Wed, 17 Feb 2021 18:21: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;  bh=93Yr9LrWp5Tu0nCrh2WrLX027Igfk1sWQw+EEMVXo5E=; b=dItMsrrYRRaulZSiY5cpvOCxgUlvpCIX+p2j1mwnVzkbT/jxe92o7k2J6FcT+bau1W TwYF2Lq/n9MX2v/PY+Kk1QccyRQ6g+DDMAiKDAgSmt0ug+vDM8NmFEDaWNML6uKndY/V VLSBUYXxPS+pv+9zEtKZ0kGi1FpuefTTtKpg1CrvyB6dA2j8i+EE6mPvFOumjKY35hbt pnJJ7HLVwnGMoCNoOuv07SBTy9CXtcUXRaE4FkY8bbgJA+wCJbZYx/foXV5h1EQBqAwX tFEBx8yvkYOm1fuLAK2jU9tsLOCrAP2RE39wlOdM0FlaseLcV0Pxd5qZXnbNeq4HteaN 60bg==
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=93Yr9LrWp5Tu0nCrh2WrLX027Igfk1sWQw+EEMVXo5E=; b=Wnmvjbfl4YT1JXmvn2adausYR5QElTnEbafRBvGA6KrLeQvGZ5rGsflYfVwXlxhJYf dmJsX1SkHBucig0DUgYb90icE4arN7ZjfNMjP85nIPMEN/3vYiGxHUQZocgOdzDIYhE4 7/E7BKsPhbRGtU0J5bfWVmJ+jjRMWhdhmznEM0A+qQR/+FB8TMagjOTcjVx1bEiO/ivM qMmnxnACs4bo11UZw7DD5DJJaTnjyg3vibjXIiaxkNseSkM6zmLuJUG+gltvZP7L0mhm B4M9qzsrljo42e3W8ezFmyAYD52paHMOxirwDLdQGrzNjQX3fLfdzSaxoRnGtwsmfIOX eK1g==
X-Gm-Message-State: AOAM530t0cjVl5yHJ/0+EiOflmktiFQz2xj5go7DKq0tg72iSZRZDqyn 8OBITzhLCGQpRX+k0ylHtytRV8QmxJvmyI14WpFf8tyT
X-Google-Smtp-Source: ABdhPJyJ05kAuX5cmkRRVQGG9iJqfSJ+xDI++lH2cVfm+5nW45OvUfNtbimio1Ij6+UsmrUFKNWkF/LtkKDPh9IJ3gI=
X-Received: by 2002:a67:ad06:: with SMTP id t6mr1440158vsl.59.1613614886409; Wed, 17 Feb 2021 18:21:26 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> <7086a5e4-2a9c-bbdc-1969-f77d0d00fa38@tana.it> <MN2PR11MB435129E4F5DA8C8EC141E9E9F7869@MN2PR11MB4351.namprd11.prod.outlook.com> <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
In-Reply-To: <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 17 Feb 2021 21:21:11 -0500
Message-ID: <CAH48Zfy6oqHE8WfyOv2j57d-VhFXYBVqq_zvTTQtTnpCxo6V+g@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001bd8cd05bb92fe73"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rt3hQGAsKAJo3eKGlGIqQej4cDE>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 18 Feb 2021 02:21:30 -0000

--0000000000001bd8cd05bb92fe73
Content-Type: text/plain; charset="UTF-8"

It would help me if you could elaborate on the concerns that you have
encountered.

Which data is sensitive and therefore needing classification?

Which roles creates the objection?   Server owner sending reports,
recipient domain allowing the server owner to send reports from recipient
data, or only report recipient?

When the report recipient domain delegates reception to an authorized
agent, how does the organization making the delegation escape liability for
how the information is handled and used?


On Wed, Feb 17, 2021 at 4:27 PM Ken O'Driscoll <ken=
40wemonitoremail.com@dmarc.ietf.org> wrote:

>
> I PM deployments for organisations and the concept of aggregate reports
> have caused problem more than once. Similar to the PII concerns of
> providers which originated this ticket, these organisations operate in
> heavily a regulated industry and have extensive DPO functions. To give a
> flavour of what those concerns translate to - I have been asked is it
> possible to implement DMARC without using reports! I have also had
> con-calls about training a new hire to read and classify the reports!
> That's just two examples. It's mostly driven by overzealous DPOs but I
> understand their concerns on some level. When they realise that we can
> distil the report data and it doesn't need to be on-site, they hand wave
> away any custodian concerns and the project moves forward.
>
> So, assuming that my DMARC clients aren't unique, I'm wondering if this
> section could be split into two parts, one for Mail Receivers and one for
> Domain Owners?
>
> If so, for Domain Owners, I'd propose something like this:
>
> Aggregate feedback reports are essential for the proper implementation and
> operation of DMARC. Domain Owners can choose to exclusively direct reports
> to a processor external to their organization. In such cases, the content
> of the reports are never sent directly to the Domain Owner.
>
> Thoughts?
>
> Ken.
>
> > -----Original Message-----
> > From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Brotman, Alex
> > Sent: Wednesday 17 February 2021 18:40
> > To: Alessandro Vesely <vesely@tana.it>; dmarc@ietf.org
> > Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
> >
> > Incorporating some feedback:
> >
> > -------------------
> > ## Data Contained Within Reports (Tkt64)
> >
> > Within the reports is contained an aggregated body of anonymized data
> > pertaining to the sending domain.  The data is meant to aid the report
> > processors and domain holders in verifying sources of messages
> > pertaining to the DMARC Identifier.  The data should not contain any
> > identifying characteristics about individual senders or receivers.  An
> > entity sending reports should not be concerned with the data contained
> > as it does not contain personal information, such as email addresses or
> > usernames. There are typically three situations where data is reported
> > to the aggregate receivers: messages properly authenticated, messages
> > that fail to authenticate as the domain, or messages utilizing the DMARC
> > Identifier that have no authentication at all.  In each of these cases,
> > there exists no identifying information for individuals, and all content
> > within the reports should be related to SMTP servers sending messages
> > posing as that domain.
> > -------------------
> >
> >
> > --
> > Alex Brotman
> > Sr. Engineer, Anti-Abuse & Messaging Policy Comcast
> >
> > > -----Original Message-----
> > > From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Alessandro Vesely
> > > Sent: Monday, February 15, 2021 8:31 AM
> > > To: dmarc@ietf.org
> > > Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
> > >
> > > On Fri 12/Feb/2021 21:30:38 +0100 Brotman, Alex wrote:
> > > > Hello folks,
> > > >
> > > > In ticket #64
> > >
> > (https://urldefense.com/v3/__https://trac.ietf.org/trac/dmarc/ticket/64_
> > _;!
> > > !CQl3mcHX2A!W97hZ0-
> > > iwRDi8wBssmRFF6OycVE12vM3xhGd9BmLhEzi6Vycp3bgzwji21xLQQgnnMRa
> > > BuxGQg$ ), it was suggested that a Privacy Considerations section may
> > > alleviate some concerns about the ownership of the data.  I created an
> > > initial attempt, and thought to get some feedback.  I didn't think we
> > > should go too far in depth, or raise corner cases.  Felt like doing so
> > > could lead down a rabbit hole of trying to cover all cases. This would
> > > go within a "Privacy Considerations" section.
> > > >
> > > > * Data Contained Within Reports (#64)
> > > >
> > > > Within the reports is contained an aggregated body of anonymized
> > > > data pertaining to the sending domain.  The data is meant to aid the
> > > > report processors and domain holders in verifying sources of
> > > > messages pertaining to the 5322.From Domain.
> > >
> > >
> > > I'd replace all those 5322.From Domain with main DMARC identifier.
> > >
> > >
> > > > The data should not contain any identifying characteristics about
> > > > individual senders or receivers.
> > >
> > >
> > > The aggregated data refers to names and IP addresses of SMTP servers.
> > > It cannot be used to identify individual users.
> > >
> > >
> > > >  An entity
> > > > sending reports should not be concerned with the data contained as
> > > > it should not contain PII (NIST reference for PII definition), such
> > > > as email
> > > addresses or
> > > > usernames.
> > >
> > >
> > > I'd substitute /should not/does not/.  Even if a server has a unique
> > > user, the domain name and the IP address are those of a public entity,
> > > not those of a private citizen.
> > >
> > > The term Personally Identifiable Information (PII) is US-national.  I
> > > think just personal information is of broader use.  Personal data is
> > > also a valid alternative.
> > >
> > >
> > > jm2c
> > > Ale
> > > --
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > dmarc mailing list
> > > dmarc@ietf.org
> > > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/dmar
> > > c
> > > __;!!CQl3mcHX2A!W97hZ0-
> > > iwRDi8wBssmRFF6OycVE12vM3xhGd9BmLhEzi6Vycp3bgzwji21xLQQgnnMTF6
> > > fzPKA$
> >
> > _______________________________________________
> > 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
>

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

<div dir=3D"ltr">It would help me if you could elaborate on the concerns th=
at=C2=A0you have encountered.=C2=A0=C2=A0<div><br></div><div>Which data is =
sensitive and therefore needing classification?<div><br></div><div>Which ro=
les creates the objection?=C2=A0 =C2=A0Server owner sending reports, recipi=
ent domain allowing the server owner to send reports from recipient data, o=
r only report recipient?=C2=A0=C2=A0</div><div><br></div><div>When the repo=
rt recipient domain delegates reception to an authorized agent, how does th=
e organization making the delegation escape liability for how the informati=
on is handled and used?</div><div><br></div></div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Feb 17, 2021 at 4=
:27 PM Ken O&#39;Driscoll &lt;ken=3D<a href=3D"mailto:40wemonitoremail.com@=
dmarc.ietf.org">40wemonitoremail.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"><br>
I PM deployments for organisations and the concept of aggregate reports hav=
e caused problem more than once. Similar to the PII concerns of providers w=
hich originated this ticket, these organisations operate in heavily a regul=
ated industry and have extensive DPO functions. To give a flavour of what t=
hose concerns translate to - I have been asked is it possible to implement =
DMARC without using reports! I have also had con-calls about training a new=
 hire to read and classify the reports! That&#39;s just two examples. It&#3=
9;s mostly driven by overzealous DPOs but I understand their concerns on so=
me level. When they realise that we can distil the report data and it doesn=
&#39;t need to be on-site, they hand wave away any custodian concerns and t=
he project moves forward.<br>
<br>
So, assuming that my DMARC clients aren&#39;t unique, I&#39;m wondering if =
this section could be split into two parts, one for Mail Receivers and one =
for Domain Owners?<br>
<br>
If so, for Domain Owners, I&#39;d propose something like this:<br>
<br>
Aggregate feedback reports are essential for the proper implementation and =
operation of DMARC. Domain Owners can choose to exclusively direct reports =
to a processor external to their organization. In such cases, the content o=
f the reports are never sent directly to the Domain Owner.<br>
<br>
Thoughts?<br>
<br>
Ken.<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: dmarc &lt;<a href=3D"mailto:dmarc-bounces@ietf.org" target=3D"_b=
lank">dmarc-bounces@ietf.org</a>&gt; On Behalf Of Brotman, Alex<br>
&gt; Sent: Wednesday 17 February 2021 18:40<br>
&gt; To: Alessandro Vesely &lt;<a href=3D"mailto:vesely@tana.it" target=3D"=
_blank">vesely@tana.it</a>&gt;; <a href=3D"mailto:dmarc@ietf.org" target=3D=
"_blank">dmarc@ietf.org</a><br>
&gt; Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns<br>
&gt; <br>
&gt; Incorporating some feedback:<br>
&gt; <br>
&gt; -------------------<br>
&gt; ## Data Contained Within Reports (Tkt64)<br>
&gt; <br>
&gt; Within the reports is contained an aggregated body of anonymized data<=
br>
&gt; pertaining to the sending domain.=C2=A0 The data is meant to aid the r=
eport<br>
&gt; processors and domain holders in verifying sources of messages<br>
&gt; pertaining to the DMARC Identifier.=C2=A0 The data should not contain =
any<br>
&gt; identifying characteristics about individual senders or receivers.=C2=
=A0 An<br>
&gt; entity sending reports should not be concerned with the data contained=
<br>
&gt; as it does not contain personal information, such as email addresses o=
r<br>
&gt; usernames. There are typically three situations where data is reported=
<br>
&gt; to the aggregate receivers: messages properly authenticated, messages<=
br>
&gt; that fail to authenticate as the domain, or messages utilizing the DMA=
RC<br>
&gt; Identifier that have no authentication at all.=C2=A0 In each of these =
cases,<br>
&gt; there exists no identifying information for individuals, and all conte=
nt<br>
&gt; within the reports should be related to SMTP servers sending messages<=
br>
&gt; posing as that domain.<br>
&gt; -------------------<br>
&gt; <br>
&gt; <br>
&gt; --<br>
&gt; Alex Brotman<br>
&gt; Sr. Engineer, Anti-Abuse &amp; Messaging Policy Comcast<br>
&gt; <br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: dmarc &lt;<a href=3D"mailto:dmarc-bounces@ietf.org" target=
=3D"_blank">dmarc-bounces@ietf.org</a>&gt; On Behalf Of Alessandro Vesely<b=
r>
&gt; &gt; Sent: Monday, February 15, 2021 8:31 AM<br>
&gt; &gt; To: <a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@iet=
f.org</a><br>
&gt; &gt; Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concern=
s<br>
&gt; &gt;<br>
&gt; &gt; On Fri 12/Feb/2021 21:30:38 +0100 Brotman, Alex wrote:<br>
&gt; &gt; &gt; Hello folks,<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; In ticket #64<br>
&gt; &gt;<br>
&gt; (<a href=3D"https://urldefense.com/v3/__https://trac.ietf.org/trac/dma=
rc/ticket/64_" rel=3D"noreferrer" target=3D"_blank">https://urldefense.com/=
v3/__https://trac.ietf.org/trac/dmarc/ticket/64_</a><br>
&gt; _;!<br>
&gt; &gt; !CQl3mcHX2A!W97hZ0-<br>
&gt; &gt; iwRDi8wBssmRFF6OycVE12vM3xhGd9BmLhEzi6Vycp3bgzwji21xLQQgnnMRa<br>
&gt; &gt; BuxGQg$ ), it was suggested that a Privacy Considerations section=
 may<br>
&gt; &gt; alleviate some concerns about the ownership of the data.=C2=A0 I =
created an<br>
&gt; &gt; initial attempt, and thought to get some feedback.=C2=A0 I didn&#=
39;t think we<br>
&gt; &gt; should go too far in depth, or raise corner cases.=C2=A0 Felt lik=
e doing so<br>
&gt; &gt; could lead down a rabbit hole of trying to cover all cases. This =
would<br>
&gt; &gt; go within a &quot;Privacy Considerations&quot; section.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; * Data Contained Within Reports (#64)<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Within the reports is contained an aggregated body of anonym=
ized<br>
&gt; &gt; &gt; data pertaining to the sending domain.=C2=A0 The data is mea=
nt to aid the<br>
&gt; &gt; &gt; report processors and domain holders in verifying sources of=
<br>
&gt; &gt; &gt; messages pertaining to the 5322.From Domain.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; I&#39;d replace all those 5322.From Domain with main DMARC identi=
fier.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &gt; The data should not contain any identifying characteristics =
about<br>
&gt; &gt; &gt; individual senders or receivers.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The aggregated data refers to names and IP addresses of SMTP serv=
ers.<br>
&gt; &gt; It cannot be used to identify individual users.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &gt;=C2=A0 An entity<br>
&gt; &gt; &gt; sending reports should not be concerned with the data contai=
ned as<br>
&gt; &gt; &gt; it should not contain PII (NIST reference for PII definition=
), such<br>
&gt; &gt; &gt; as email<br>
&gt; &gt; addresses or<br>
&gt; &gt; &gt; usernames.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; I&#39;d substitute /should not/does not/.=C2=A0 Even if a server =
has a unique<br>
&gt; &gt; user, the domain name and the IP address are those of a public en=
tity,<br>
&gt; &gt; not those of a private citizen.<br>
&gt; &gt;<br>
&gt; &gt; The term Personally Identifiable Information (PII) is US-national=
.=C2=A0 I<br>
&gt; &gt; think just personal information is of broader use.=C2=A0 Personal=
 data is<br>
&gt; &gt; also a valid alternative.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; jm2c<br>
&gt; &gt; Ale<br>
&gt; &gt; --<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; dmarc mailing list<br>
&gt; &gt; <a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.or=
g</a><br>
&gt; &gt; <a href=3D"https://urldefense.com/v3/__https://www.ietf.org/mailm=
an/listinfo/dmar" rel=3D"noreferrer" target=3D"_blank">https://urldefense.c=
om/v3/__https://www.ietf.org/mailman/listinfo/dmar</a><br>
&gt; &gt; c<br>
&gt; &gt; __;!!CQl3mcHX2A!W97hZ0-<br>
&gt; &gt; iwRDi8wBssmRFF6OycVE12vM3xhGd9BmLhEzi6Vycp3bgzwji21xLQQgnnMTF6<br=
>
&gt; &gt; fzPKA$<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; dmarc mailing list<br>
&gt; <a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a>=
<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</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>

--0000000000001bd8cd05bb92fe73--


From nobody Wed Feb 17 18:46:13 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 26ECC3A1ED2 for <dmarc@ietfa.amsl.com>; Wed, 17 Feb 2021 18:46:12 -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=r4zhVmSK; dkim=pass (2048-bit key) header.d=taugh.com header.b=sGLOlgVm
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLW8By3v9cKs for <dmarc@ietfa.amsl.com>; Wed, 17 Feb 2021 18:46: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 7CC683A1DD1 for <dmarc@ietf.org>; Wed, 17 Feb 2021 18:46:10 -0800 (PST)
Received: (qmail 72249 invoked from network); 18 Feb 2021 02:46: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:mime-version:content-type:content-transfer-encoding:cleverness; s=11a36.602dd4ef.k2102; bh=iZV8QSA3ugCfCf38H4DVCON3npHEMr0hbZFwEppUo40=; b=r4zhVmSKROr04KQ1tkeMQGIAeJcheXgnrcVVKSeOFZ8fOBbD0oPjJpOuvTOQ7d0iDDYlv9ceM1YVK10UhjfC/KBHqEF4ke4wgsvHsLCW+knwTJgy2ZVw4S3XYzWQqzSfecWh+Diwews/1Cq4nIFQ8javrI2CCnS6/79TPx2QTWTaXDEd5u0x9HOoXOMCxi0tX6+j/g8zpkP/bSGijJKByRuZBPJow6l87VUEVn9V6nN0VZhg9CFtFfz9sLBpIP3+4Hf1ZqgYq4mIRQ8lWc/mVo+fzGRrf7+27m1jr6TZxp6Mzy54GIvH6rCI/EvzMVOF9Zkdz53dD5bbqxwllf0AmQ==
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=11a36.602dd4ef.k2102; bh=iZV8QSA3ugCfCf38H4DVCON3npHEMr0hbZFwEppUo40=; b=sGLOlgVmZNRGZgQHJYCYFqMOR38lwkY3W51sNjpHiNUUFDBtTGs31s6zl/qZcbaP6mum7AQz/KyxPwnVErIi/HqM7LbKvVRqwVBEImCLGzzwKQPvBSxeO7nfQx7n3D+H1oLxTxvBW4RnbkguuSxItWulLxOW9n6p5ximQdGJ7x37ToEQU542zvncVc2/8jvNRDK04uRLcNCPgtIFbcVWQAWa8au/fyS2bY7J8G2cgryWPoivYznAAwBGWnc+ldyYqTla6On/EdE++XApqTPR7K53FlJZtvJShx+8/w/nkUZd6nO79H+9PEAqwKu/00hH2C53AuA1eO4PL7GH2Y07ZA==
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 Feb 2021 02:46:06 -0000
Received: by ary.qy (Postfix, from userid 501) id 4727B6E23874; Wed, 17 Feb 2021 21:46:05 -0500 (EST)
Date: 17 Feb 2021 21:46:05 -0500
Message-Id: <20210218024606.4727B6E23874@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: ken@wemonitoremail.com
In-Reply-To: <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.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/IKKrhDPkUSRDTAFdhgXuLsnczmU>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 18 Feb 2021 02:46:12 -0000

In article <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> you write:
>Aggregate feedback reports are essential for the proper implementation and operation of DMARC. Domain Owners can choose to
>exclusively direct reports to a processor external to their organization. In such cases, the content of the reports are never
>sent directly to the Domain Owner.

That is OK but I would also want to point out that the data are
aggregated and contain no individual e-mail addresses of senders or
recipients, nor IP addresses of individuals nor any contents of
messages, so it is unlikely that they contain any PII.

I have to say it seems weird to me that it's OK to send whatever to external places but not to 
your own staff.

R's,
John


From nobody Thu Feb 18 07:09:25 2021
Return-Path: <ken@wemonitoremail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11A0E3A1338 for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 07:09:24 -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, RCVD_IN_MSPIKE_H2=-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=wemonitoremail.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 md4sV5Q5akjX for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 07:09:22 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60128.outbound.protection.outlook.com [40.107.6.128]) (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 1ED6C3A12A0 for <dmarc@ietf.org>; Thu, 18 Feb 2021 07:09:21 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=A6XHzz1AecUfFx58p3HU6AkoOnjIN1W3JRCmLphv9A6o+BKOrE+SVN8+BMyEVbIhij/UkZRbiCKDUqBGk2bclkprfwZo2/kNJfbLR6qBGJt/+ZFF7l2A96d50urPwUJgkrLLQh4oE8/qbOKuENm5cc7gPJ2yx9xI/iKce+oRlQUSF5qDndI0ShETuOCVgzl2/0tCAgBnt9bxK+Xxeq6JnLQHKy4FqJcpLEwsRwyLTzG+kjDSy8zAefvGqdfI6YRzwmLVQGe+y6MmZcEUQ1cDkMhvw742ty/p1SrrlLEhp7jRHo5eGDQELmiILiVQwmm7vNlSJzS4x00MYTrbv/1Zdg==
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=nkdRo7sdA6NhS0PMNPhgSmDEwHe6CgeCySQQxxTQKiA=; b=YDT9OALp/LthuJdIDHcYYHNbjMNfCOVaGNjqAzQZhxUyfZWpvI99IRDUCperzp3Kh0P1+krc6bH3aJU78bK5Tzti3+ZIkFz+YIQs5IqH/EHigg4LihRD61u/3Tid6hMKhGPDHAiDBWij8U/emBT/xPfHcABUDPghQreDurkR4IzK9isN+j6ksoSQhZmoEsVqOI1g1k6fSqk5HPwy+t0ZI1ji76U/2n8wZ5E9PG/qAvYG5ZV5sQn+oxxpyTdr0w/C4q5iP8lOH2mW3DbqBi31WLZSm0ogxAm032ytUiAoStlZhoQv41j1Zps5etRJB7MEBUIz6uI44mwkmPDCy8R83A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=wemonitoremail.com; dmarc=pass action=none header.from=wemonitoremail.com; dkim=pass header.d=wemonitoremail.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemonitoremail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=nkdRo7sdA6NhS0PMNPhgSmDEwHe6CgeCySQQxxTQKiA=; b=RSsjkOZFAd7lSdTIl0ye/EZY804UBQ7Q+RJdToJZE490caWyQh8iJ/LqjL06IRluCkPoiua67Lh3YLfve5ygfYi/KEiLrRC9+Vfm4q4UamJTqB6xLNgGfTh3UKFtAnVOSjIp6kZQ9aK4GpWmbG4no0GrrpqbrH/ds3vArHV8lIcos8Jxr2JX2vgoKV0X6SP5i39oYjaM4meYCLO2LsG0WT93/jRfulkH8df4Y4mpqHeKFGxYmYvkG4ufEXfTfvFav+8TQoUuGjz42fmoupQwthCmXiKO5LP2olMzH90xfuXZCOq2MRWKyyGCRm/QKYlBeW+avRsCvJKliFiOFy0WAw==
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com (2603:10a6:800:19a::9) by VI1PR01MB4512.eurprd01.prod.exchangelabs.com (2603:10a6:803:a4::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25; Thu, 18 Feb 2021 15:09:18 +0000
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::9c69:59f:c073:bd9f]) by VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::9c69:59f:c073:bd9f%7]) with mapi id 15.20.3846.039; Thu, 18 Feb 2021 15:09:18 +0000
From: Ken O'Driscoll <ken@wemonitoremail.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
CC: John Levine <johnl@taugh.com>
Thread-Topic: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
Thread-Index: AdcBfLdYcAd1ycC0TvWJKBD11cOyegCIhNKAAG9eXXAABJQJQAAMZ9qAABjkaCA=
Date: Thu, 18 Feb 2021 15:09:18 +0000
Message-ID: <VI1PR01MB70530199B815F3216D64E9A2C7859@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
References: <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <20210218024606.4727B6E23874@ary.qy>
In-Reply-To: <20210218024606.4727B6E23874@ary.qy>
Accept-Language: en-GB, 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=wemonitoremail.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 83dda0b9-f703-46b4-2a50-08d8d41f29f6
x-ms-traffictypediagnostic: VI1PR01MB4512:
x-microsoft-antispam-prvs: <VI1PR01MB4512462EAD376A6290ED04BDC7859@VI1PR01MB4512.eurprd01.prod.exchangelabs.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: BIOs0imf4NEXlgrSEPVoE4OkpjMXtIDhC+YSTPnAvE6vWDGUUldGGoq2N4ojs4k24Q0GbF/R1ow082iM5iR6iZD+8uNOxM+7VWo/4dRHIsbR77UmutN0tNUdpttCZaT8wSOzV328jVLaK3hJRK9sS205Sz48Hnf3hPxAxylo4TMxJCzyAgr9VZzqXEP33liHgzp5XasruSEfset+hnIYyZ5/eqLLu8vdR1TOIMfJwHtu8nElciHfVFUf5nuBNPuWUwcZiAexEHjc0wSjsfvEA6BKllbjyx6foh07b4gd2O7pIuQr1/D18PsIjYcoDLE5ibBf0SaiYFHFM/sM4WzgWXKyE5omjaM+G7IpURdKk8D7Oc1MCsCamiB+ku1JV1IiBuORptcHXsZG0xHK/orNtx/z43sR1qIUGq0cH92p1AuzcbA5kBTrz1WIe+T19vRAUr8Aq/LSvE3l8bhi7OMA24HIhnnxBmYzX5UBRzxTf9Yypvde1/fr7zON2s77179hog3nDZDdEzv4lpDlOFapUQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR01MB7053.eurprd01.prod.exchangelabs.com; PTR:;  CAT:NONE; SFS:(366004)(376002)(396003)(136003)(39830400003)(346002)(2906002)(66476007)(66446008)(8936002)(52536014)(4326008)(6506007)(6916009)(71200400001)(53546011)(5660300002)(86362001)(83380400001)(33656002)(316002)(186003)(55016002)(478600001)(64756008)(76116006)(66556008)(9686003)(7696005)(8676002)(26005)(66946007); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?NjZpcHUwc0QwbnArbkthN0NqWnhBdFlaVjIwdzRaazZ2OUxoWHp0T2RwUjVv?= =?utf-8?B?cHl4dUZ4TG8yc1BVWGw3R1Jsa2hGNFhYV1VBOTFydThqekd5UHN1YzA3YUFx?= =?utf-8?B?WUpLdEFKMnM5UmJDemphOUFFUTNsQ0lHc3FoQjhON3Z3SFdhcXc2dUk3WlZP?= =?utf-8?B?cFVtMVcyV1lvZlFpcy9IVTBDSitDdUZ1UzNDK2N2ZFR1MHU5cm9ycEtTazhh?= =?utf-8?B?cGdqdDc4MiszOXdObkZlMDgwa2tpNWxJSkxKTnlmdWNSV2Q5SXprOXU4WnBK?= =?utf-8?B?aEpRT3BNalZ6VFVNT1krQmxuZzRFbUoyc21EakhST2lXK1VoOE1tVE1SWDVr?= =?utf-8?B?d1BwN05ROHhqNFlrQk1aclRZUThJUm04NHV0ZTR5dXV2ZnhEVUVOTkhVMnIx?= =?utf-8?B?VWsveWhja2hPNFFZRUl3SlZ2MzVYT082VmNYQ0RRbktKMUZYTng0WnFadElo?= =?utf-8?B?ZEwxS1E4dXJJSnczNU5zSnV2cXRLa243ZHpWWTZXUk9EM2gvMUU0TityeW1l?= =?utf-8?B?VEExVmswZDd1R1dEWk93eW5zR0RLTmVORTM5eDUxZkN3YUtXM3hJdmV0RnpM?= =?utf-8?B?Rmc2V1FXaGZ3dXkydnVOR0VyUWxuNkFXSkZ5azArTVRwQkdvSTEvWmplVG12?= =?utf-8?B?bjdIMFIzN0kzS1kxOGluK1dwOVN5TnhWM3lMMG4ySHovV2k0S2M0QmxPZHRQ?= =?utf-8?B?bUJ1aUZ2ZlBmR2ZQU243T2RwOEZTUDlLbWRxb0NYS25MUS8vTTVCcW9heFFl?= =?utf-8?B?NzkrRkFjOENVbldkNHlDWWpQVGpiUWlvY3NJK0NiV01nZjJtRXpDYXJBU0VJ?= =?utf-8?B?SE13T2ZzZ0ptbkdaaXdmcjhRVG5na3FBOEJ0Rld2Z1lFR01BZitxY0xpWE5q?= =?utf-8?B?NWtVWEtGUUptWUlhODcwdUJrOTdPWVBialUwRWcxNWxBQitsaGJPZy9WclBq?= =?utf-8?B?NXA0aUpFaWVLU2pZQ0E2WUFrcE1YWjJHRVRPM2F0R01VcFpBZG92RS8yMzJH?= =?utf-8?B?N3A2anFXNW1ZdU44bll0OTFJbkVIUTBhMnRFMXg0VjdHQ0MvV0VPOEZuVytS?= =?utf-8?B?djJjT041M0tjZjlxQ2ZSSGh3eDZnRWhodGtpSGFDNnVRQ3lQSWJpajZKbjJt?= =?utf-8?B?blVpbXIvME8rMlRjUTI0MDhrRjJCMURlQ0VSZWtjREx4TjRUOSsxN25XRERJ?= =?utf-8?B?aDQ0RXo3Qy9YclAybWpid29aZFNEbDF0eDl0aHNDcmNUK0EwTGRLSGcxRUh3?= =?utf-8?B?WXFuNTUya2pHMzVvSzcyekVtVTZ6TXpqTlJxUUxqUHNrbXRhdU5HWTRVN0Qz?= =?utf-8?B?Y29OOUlCNXh4dU1SQnRBemF4OEJ1UWR5SWhoV2ZTQVV6Sm5iRUV2NWI3c251?= =?utf-8?B?MzFEaFRrSE5tQlVNS1B6bjZxRlBwOERBVXhCNWsxMUhPVVJtNVRHT1N3L1BL?= =?utf-8?B?SzJERW5aV0toSUF5SlBqWm11eFJVYjRORGt6eXlRdzBDUEJmUEtPTGdlRWF6?= =?utf-8?B?R2tMdENRYUxNbm1idVJXRW5YWk10azVGTDRUSkIrOTNHMlUvSFAwZzBrbGRG?= =?utf-8?B?aW91Y3pzanlhWTQ3cER1SGJqOS90RXFWZjVVRHpRWmRabFVHbnJHTS9aM29U?= =?utf-8?B?MUIrY0tDcTFueDFhTDJZN2JqRFZpUU5CWDM4SWh0N0xJaUxGdG8wajJqTjdT?= =?utf-8?B?aE5qcjQwK2xtKzRVbEFUbTROYmhJZllpajdZOHFHUHByUWpsY2xlR2lVU2oy?= =?utf-8?Q?IczVn2Gs/X7Z88a+jc=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: wemonitoremail.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: VI1PR01MB7053.eurprd01.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 83dda0b9-f703-46b4-2a50-08d8d41f29f6
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2021 15:09:18.4425 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a2b1d6fe-fc8b-4b7c-b9f1-d7b1ab3d23b3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 8iQkjjUTuQaVg8BnqYtN1cUmhAMxcH15tFeOLKcPt1q29W9hRwheuwWDwJygsARn8yYeoNSFFXtMR639A/uzQg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR01MB4512
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/e7Xfm5Z_9LCWWzDSCwUGXmMMQVU>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 18 Feb 2021 15:09:24 -0000

DQpJbiBoaW5kc2lnaHQsIGl0IGxvb2tzIGEgYml0IHN0cmFuZ2UgdG8gaGF2ZSB0aGUgZmlyc3Qg
cGFyYWdyYXBoIHNheSAiZG9uJ3Qgd29ycnkgYWJvdXQgUElJIiBhbmQgdGhlIG5leHQgcGFyYWdy
YXBoIHNheSAiaWYgeW91J3JlIHdvcnJpZWQgYWJvdXQgUElJLCBoZXJlJ3MgaG93IHRvIG1pdGln
YXRlIi4NCg0KQnV0IGl0J3MgYSBnZW51aW5lIGNvbmNlcm4gKG1pc2d1aWRlZCBvciBub3QpIGFu
ZCBJJ3ZlIGJlZW4gaW4gZW5vdWdoIG1lZXRpbmdzIHRvIGF0IGxlYXN0IHVuZGVyc3RhbmQgd2hl
cmUgaXQgY29tZXMgZnJvbSwgZXZlbiBpZiBJIGRvbid0IGFncmVlLiBTbyBJJ2QgcHJvcG9zZSBz
b21ldGhpbmcgbGlrZSB0aGUgYmVsb3csIHdoaWNoIEkgdGhpbmsgZ2V0cyBhY3Jvc3Mgd2hhdCB3
ZSBhbGwgd2FudCB0byBzYXkuDQoNCj09PT09PT0NCkFnZ3JlZ2F0ZSBmZWVkYmFjayByZXBvcnRz
IGNvbnRhaW4gYW5vbnltaXplZCBkYXRhIHJlbGF0aW5nIHRvIG1lc3NhZ2VzIHB1cnBvcnRlZGx5
IG9yaWdpbmF0aW5nIGZyb20gdGhlIERvbWFpbiBPd25lci4gVGhlIGRhdGEgZG9lcyBub3QgY29u
dGFpbiBhbnkgaWRlbnRpZnlpbmcgY2hhcmFjdGVyaXN0aWNzIGFib3V0IGluZGl2aWR1YWwgc2Vu
ZGVycyBvciByZWNlaXZlcnMuIE5vIHBlcnNvbmFsIGluZm9ybWF0aW9uIHN1Y2ggYXMgaW5kaXZp
ZHVhbCBlbWFpbCBhZGRyZXNzZXMsIElQIGFkZHJlc3NlcyBvZiBpbmRpdmlkdWFscywgb3IgdGhl
IGNvbnRlbnQgb2YgYW55IG1lc3NhZ2VzLCBpcyBpbmNsdWRlZCBpbiByZXBvcnRzLg0KDQpNYWls
IFJlY2VpdmVycyBzaG91bGQgaGF2ZSBubyBjb25jZXJucyBpbiBzZW5kaW5nIHJlcG9ydHMgYXMg
dGhleSBkbyBub3QgY29udGFpbiBwZXJzb25hbCBpbmZvcm1hdGlvbi4gSW4gYWxsIGNhc2VzLCB0
aGUgZGF0YSB3aXRoaW4gdGhlIHJlcG9ydHMgcmVsYXRlcyB0byB0aGUgYXV0aGVudGljYXRpb24g
aW5mb3JtYXRpb24gcHJvdmlkZWQgYnkgbWFpbCBzZXJ2ZXJzIHNlbmRpbmcgbWVzc2FnZXMgb24g
YmVoYWxmIG9mIHRoZSBEb21haW4gT3duZXIuIFRoaXMgaW5mb3JtYXRpb24gaXMgbmVjZXNzYXJ5
IHRvIGFzc2lzdCBEb21haW4gT3duZXJzIGluIGltcGxlbWVudGluZyBhbmQgbWFpbnRhaW5pbmcg
RE1BUkMuDQoNCkRvbWFpbiBPd25lcnMgc2hvdWxkIGhhdmUgbm8gY29uY2VybnMgaW4gcmVjZWl2
aW5nIHJlcG9ydHMgYXMgdGhleSBkbyBub3QgY29udGFpbiBwZXJzb25hbCBpbmZvcm1hdGlvbi4g
VGhlIHJlcG9ydHMgb25seSBjb250YWluIGFnZ3JlZ2F0ZWQgYW5vbnltaXplZCBkYXRhIHJlbGF0
ZWQgdG8gdGhlIGF1dGhlbnRpY2F0aW9uIGRldGFpbHMgb2YgbWVzc2FnZXMgY2xhaW1pbmcgdG8g
b3JpZ2luYXRlIGZyb20gdGhlaXIgZG9tYWluLiBUaGlzIGluZm9ybWF0aW9uIGlzIGVzc2VudGlh
bCBmb3IgdGhlIHByb3BlciBpbXBsZW1lbnRhdGlvbiBhbmQgb3BlcmF0aW9uIG9mIERNQVJDLiBE
b21haW4gT3duZXJzIHdobyBhcmUgdW5hYmxlIHRvIHJlY2VpdmUgcmVwb3J0cyBmb3Igb3JnYW5p
emF0aW9uYWwgcmVhc29ucywgY2FuIGNob29zZSB0byBleGNsdXNpdmVseSBkaXJlY3QgdGhlIHJl
cG9ydHMgdG8gYW4gZXh0ZXJuYWwgcHJvY2Vzc29yLg0KPT09PT09PQ0KDQpBbmQsIEkgYWdyZWUg
LSBpdCdzIGEgYml0IHdlaXJkIHRvIGJlIG9rYXkgd2l0aCBoYXZpbmcgYSBwb2xpY3kgdG8gbm90
IHNlZSB5b3VyIG93biByZXBvcnRzLiBCdXQgdGhlICJzZWUgbm8gZXZpbCwgaGVhciBubyBldmls
IiByaXNrIG1pdGlnYXRpb24gc3RyYXRlZ3kgaXMgdHJpZWQgYW5kIHRlc3RlZC4gVGhlIHdob2xl
IElHL0RQTyBzcGFjZSBpcyByZWFsbHkgY3JhenkgaW4gc29tZSBwbGFjZXMgdG9vLg0KDQpLZW4u
DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogSm9obiBMZXZpbmUgPGpv
aG5sQHRhdWdoLmNvbT4NCj4gU2VudDogVGh1cnNkYXkgMTggRmVicnVhcnkgMjAyMSAwMjo0Ng0K
PiBUbzogZG1hcmNAaWV0Zi5vcmcNCj4gQ2M6IEtlbiBPJ0RyaXNjb2xsIDxrZW5Ad2Vtb25pdG9y
ZW1haWwuY29tPg0KPiBTdWJqZWN0OiBSZTogW2RtYXJjLWlldGZdIFRpY2tldCAjNjQgLSBDb250
YWluZWQgRGF0YSBQSUkgQ29uY2VybnMNCj4gDQo+IEluIGFydGljbGUNCj4gPFZJMVBSMDFNQjcw
NTM4NTQxRDdBREUxOEE1NTVCMDVENkM3ODY5QFZJMVBSMDFNQjcwNTMuZXVycHJkMDEucHJvZC5l
eGNoDQo+IGFuZ2VsYWJzLmNvbT4geW91IHdyaXRlOg0KPiA+QWdncmVnYXRlIGZlZWRiYWNrIHJl
cG9ydHMgYXJlIGVzc2VudGlhbCBmb3IgdGhlIHByb3BlciBpbXBsZW1lbnRhdGlvbg0KPiA+YW5k
IG9wZXJhdGlvbiBvZiBETUFSQy4gRG9tYWluIE93bmVycyBjYW4gY2hvb3NlIHRvIGV4Y2x1c2l2
ZWx5IGRpcmVjdA0KPiA+cmVwb3J0cyB0byBhIHByb2Nlc3NvciBleHRlcm5hbCB0byB0aGVpciBv
cmdhbml6YXRpb24uIEluIHN1Y2ggY2FzZXMsDQo+IHRoZSBjb250ZW50IG9mIHRoZSByZXBvcnRz
IGFyZSBuZXZlciBzZW50IGRpcmVjdGx5IHRvIHRoZSBEb21haW4gT3duZXIuDQo+IA0KPiBUaGF0
IGlzIE9LIGJ1dCBJIHdvdWxkIGFsc28gd2FudCB0byBwb2ludCBvdXQgdGhhdCB0aGUgZGF0YSBh
cmUNCj4gYWdncmVnYXRlZCBhbmQgY29udGFpbiBubyBpbmRpdmlkdWFsIGUtbWFpbCBhZGRyZXNz
ZXMgb2Ygc2VuZGVycyBvcg0KPiByZWNpcGllbnRzLCBub3IgSVAgYWRkcmVzc2VzIG9mIGluZGl2
aWR1YWxzIG5vciBhbnkgY29udGVudHMgb2YNCj4gbWVzc2FnZXMsIHNvIGl0IGlzIHVubGlrZWx5
IHRoYXQgdGhleSBjb250YWluIGFueSBQSUkuDQo+IA0KPiBJIGhhdmUgdG8gc2F5IGl0IHNlZW1z
IHdlaXJkIHRvIG1lIHRoYXQgaXQncyBPSyB0byBzZW5kIHdoYXRldmVyIHRvDQo+IGV4dGVybmFs
IHBsYWNlcyBidXQgbm90IHRvIHlvdXIgb3duIHN0YWZmLg0KPiANCj4gUidzLA0KPiBKb2huDQo=


From nobody Thu Feb 18 07:31:07 2021
Return-Path: <ken@wemonitoremail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 700C73A1379 for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 07:31:05 -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, RCVD_IN_MSPIKE_H2=-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=wemonitoremail.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 aSWZWtguen67 for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 07:31:02 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40093.outbound.protection.outlook.com [40.107.4.93]) (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 50B433A1377 for <dmarc@ietf.org>; Thu, 18 Feb 2021 07:31:02 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GjZjMdB5AI82WIL0WlP3Cf2VQOobBXnKxGET4DGL0Yg8fGnw/QICk3dtLyEXFl/8mToKnPwyraxWK+vzC3AhqFbqRRSmCiJI6W+9FFd+ZFOs2u0q+zDKWhFxMAjYlE86RQ49mnCwFDDGfGfZPr399ApFeoIpOOf/PGH7Dw7TT1gAxUVLQo49OkSscJVrea8BD7Fpp/criVeMCvW+piPkaaK3ipMURzNZ48JWi9drKgR+DgZzvcW8b5q8mdj9vtv6Z7AGLqNXmlnSlPeDsOaRdeHmhVS/DvTCtEmGp/izDasZ9so/QkOwXeLcJpQhoUNPTLTtb31ZdDZ23EKu5sknaw==
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=FSlp0FtxyGn6o79cujBWNwo99trYQjvtgG5Lgz1lHiA=; b=aSp5vYgiXaHg8/tVcBll3+/MtIJ74dYSIdS6CS3C3NNHDxYDxCsRKNrAVMM6m7JR9AB5lVo1PkFKWQGLp5ss3U/tLK/jxojBqGpgzBNj6TT7ZoFanKVhqMvfhGASrEq1icjjMw7CGyyahzlZd+L0Q/JTZE9khuS92qaocm8cxqr+k4iyNEP0ydD0Y9bJw5q2mgIU0fa1gZhg0KDwrF3Jaghf7ai6ancp2MG1fZXCnyduLs1y50pJvdtVWKb3iyfY+P60EujZh1uKZ6nt2Y3Stn+A4BzzGaxVVUmAlNkx6YwEpeFn06emM/njSeHE3DbuDC8cp8Z6M1TkEbHs4TUKTQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=wemonitoremail.com; dmarc=pass action=none header.from=wemonitoremail.com; dkim=pass header.d=wemonitoremail.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemonitoremail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FSlp0FtxyGn6o79cujBWNwo99trYQjvtgG5Lgz1lHiA=; b=ROu6GMI0Fele+sYC+BD8KSzepXRfZDRE1k7hSh9e2CqtiNv+AN111uU1zMzBdHJUP1iQS77hw9QW5hjNHREC67uaCnwRNKKBvdAAXV1PYSdfPYErd1k/D9ayCPHTvRc33dtCiSpz5xyAicMkm7YqLNjt3+z8eEemaNPeuDxw9HqYbjBuAI+LnW+BtZNVfikrjfWzSLxFCt1yk6dOcDOxAQrH74z2UlVPSDHuPbG4QWIIcqtD5cyi6DLZ7cJU4oHZZWqInVRHCcXJ3XqSeFAky2Uf7duoiVuEm3/Dlj20aSH9TF+hh4tukZu0m6lNVZciNSBEwDBEXJ3pF1I2ShsZgA==
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com (2603:10a6:800:19a::9) by VI1PR01MB6623.eurprd01.prod.exchangelabs.com (2603:10a6:800:183::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.27; Thu, 18 Feb 2021 15:30:59 +0000
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::9c69:59f:c073:bd9f]) by VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::9c69:59f:c073:bd9f%7]) with mapi id 15.20.3846.039; Thu, 18 Feb 2021 15:30:59 +0000
From: Ken O'Driscoll <ken@wemonitoremail.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
CC: Douglas Foster <dougfoster.emailstandards@gmail.com>
Thread-Topic: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
Thread-Index: AdcBfLdYcAd1ycC0TvWJKBD11cOyegCIhNKAAG9eXXAABJQJQAALiTuAABrd4SA=
Date: Thu, 18 Feb 2021 15:30:58 +0000
Message-ID: <VI1PR01MB7053E1E0EDCE1FCA2B2B09A9C7859@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
References: <MN2PR11MB435185A171029EF4282A2BF4F78B9@MN2PR11MB4351.namprd11.prod.outlook.com> <7086a5e4-2a9c-bbdc-1969-f77d0d00fa38@tana.it> <MN2PR11MB435129E4F5DA8C8EC141E9E9F7869@MN2PR11MB4351.namprd11.prod.outlook.com> <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <CAH48Zfy6oqHE8WfyOv2j57d-VhFXYBVqq_zvTTQtTnpCxo6V+g@mail.gmail.com>
In-Reply-To: <CAH48Zfy6oqHE8WfyOv2j57d-VhFXYBVqq_zvTTQtTnpCxo6V+g@mail.gmail.com>
Accept-Language: en-GB, 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=wemonitoremail.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9fb70677-6321-4ee6-ca43-08d8d4223112
x-ms-traffictypediagnostic: VI1PR01MB6623:
x-microsoft-antispam-prvs: <VI1PR01MB6623A027D1F1C3E2D0487907C7859@VI1PR01MB6623.eurprd01.prod.exchangelabs.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: uh9UGZng5i2FdP9ayfwsq847f9pvy0audfTW38/StwN2H1WMAk/kLEdaY/pPXo80MQW/nzrR7y5ITTqA3I3GXImn2gQHPPuw6LuGeJ6x4yPGQP+WOxMWbE67hQVqyLIc1v/WMPPfdfmJRUdlIUxpP/vFw51rHTlGjWoubcS/YRjiqnFCjt1nKjYJzC4poQyZWTW4ce8SD9hm8x7uZ4GHxE3YvH8gX6E9hECGetL+upR3Gvux1iywrsdOcb/3D2Y0JplgatHxEv2JR0Xf+tArfKphqLiAE1eJntcP+dOgEJmVyBISjj26Xiy5iDZHh825h7324GCjZDppd09nPXQZXm4RRdRIDTktAst45l/V7N/doWUzAMm4vXxwMYII42yEWA66pPl8ZaHQ/5zZa+cZyzU9zpjAJJeZ0Pp2hUM6hglZKu1U7ViX3KLlhd22hFbb53O86LvO/l2BUWVHERpaySutQ4dqUSQpaXvGff6ZL7WRe7P3lcH3dYkC7k1b3u3m+Pz2WoKsMFjxZyyvRRSP4Nlhm10MCVSStL+dCbp+DZOSin/Tc6xhwLO+I+z84ncAWQBj1YNrkQwoC2ieDKkFGV8npoWrLymX8HImYGTY0kM=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR01MB7053.eurprd01.prod.exchangelabs.com; PTR:;  CAT:NONE; SFS:(376002)(366004)(346002)(136003)(39830400003)(396003)(83380400001)(66946007)(52536014)(8936002)(66556008)(66476007)(8676002)(2906002)(5660300002)(86362001)(64756008)(66446008)(6916009)(4326008)(966005)(33656002)(7696005)(55016002)(186003)(9686003)(53546011)(71200400001)(6506007)(76116006)(478600001)(316002)(26005)(166002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?SmNqM25Xazd1WFRmc1ZiZFlCcXhabTZtT2xUdG03Nlp6S0JDMTc5QjJ1VTIw?= =?utf-8?B?b3MzcHdCOTJPUkpXY1NmVm1BS2lUWUFpWlB2djRCeDBsWXd5RWhWeGMwTmtM?= =?utf-8?B?NENQc0FKN0tVTEJZSlJrL2NPaWhUc0hpdmpMS1pyREtEbmc1bzhmdGlRNFZR?= =?utf-8?B?NXhtL0w5RnVWamV3c01HWm93ZEI2UnNVREFVcUVTNHZleGs5ZE1QdDBlMWI3?= =?utf-8?B?SGo0Rk1ydnJRTGZjVCtBNUljdVk5aGNiMnlJbCtEZmdUQWFvOVdac1dHWGVE?= =?utf-8?B?MlJjSS9hUW5salZBZDFaV3d6akl1UnFHd1VlSE03aHJHUDJnelF6WjRwL2VJ?= =?utf-8?B?ZXpjNjNpcEMwMkxEeUxFTDQvSEF1SXJEUlNOajV1RUU2ZmszRWNXOW5xbXNw?= =?utf-8?B?NVFERlNPcVhtdWF0azhpL3BrM3Y5R3kvS1BudzZBZnJxcStkSlN6VnJneFdy?= =?utf-8?B?YkJKYy9MUUM2OXVKbzV4VXlIcjNRNGRLK3VYSExWSG04WUtyenB2bUsyZDBp?= =?utf-8?B?aG01Z3grSVRJL011eGlNaHJhTm5PNE1JRFRQaHJmQ2FERmk1Y0NENEFoVzBW?= =?utf-8?B?eld6TkhldTZhVHVJVi9SMTFsMlNMUk9LeDkzL0YzRkFHQlNnbjUwZ3hBcHBI?= =?utf-8?B?dGFoOG1kc2kwbmNWZjlNVk43RDhmSlhMV2JoRHFhWVlHa1BaYlFnMGN3dStM?= =?utf-8?B?NFNOSjl0a3I1cXkvQ0Z1b0lFN2cvWnk2cmRvRERDVTJINURLaDJNckpvZG1Q?= =?utf-8?B?SlRsRVlkM3Ziekkra2JTYjJPcldxNW5lTlJnTldZclNIbjFIM2FSTVh5Q2Rz?= =?utf-8?B?TVVHUmVicGZ2TTM0S2IrVXI0emZTK1lLV3dXZStvRnFJdkNMSjBZV0R5U00x?= =?utf-8?B?WVlpM1pMaEViMFNvVyt3SnpYUVFwazlCSFcydnBQODFaemIyQ2tnR0tnUW01?= =?utf-8?B?OWU2enBOUWJUWGNDZlNsczhUbVc5bkRHTjBWbnlSNHNvMmZsVnZIN2lreUFx?= =?utf-8?B?bW5KRWtEV2VtNUM3YlpRWTR4SnB4Z0puV2h3SWhScHJQTVM4THFvRXpPVms5?= =?utf-8?B?UCtzY3ByZUtkbGNRQ3ZDQWFPRlJ3c2JKYTFNV1o3UWR6a1hVMUcrNlhtcXQ5?= =?utf-8?B?MXZvZUpFREJIcXdYSnVXTGlXcDljNzVuM1cybXJ0dGErT2dSTWpkNEFmZkJs?= =?utf-8?B?YnFnV29BcnhEUnduTFhQL0lZTHhNWEhKRVFhRmRDdzRhUTlrNjM0WFNPam1P?= =?utf-8?B?b1RVdlIrQldPNGtlR0t6dTZUc0J6bHlDU0ZnMFlzQ0w1RjVaelR3cjJkVU9n?= =?utf-8?B?eVdjR21CdFpmZDlpRVdBV3JFbk8yZ3ZPSTdCaTJpM1RGVmFIbmFYVDAxOXNH?= =?utf-8?B?ZkdScmI1eTdhTFpsSktUY1dIN05HUmt4cUJLdU5rSUh6WG52Tk5OV3FjVkd3?= =?utf-8?B?dnRMRWdTaGxqWFNBZXh2WmtUV2lYeDkrSjZKNXM5bjkvaUZJbEZFNC8ybzh5?= =?utf-8?B?ZTRJU1hIcWxVTzhBbzBBdWZ0OHpEZFhrTExmNUhremhWQi83MXNua3NWNmVp?= =?utf-8?B?eXAyNnkyMk14bk5MMjJmQ2d4UDIvT2lEMHVjWE1BZzRWcWQvYm11TGFOcngw?= =?utf-8?B?NjFUczZ4MGVpK0F2NHNMQWcrYWI1Y3kxbzhLMUczUnlncTUxc242NDkyeVRs?= =?utf-8?B?elBLai9pei9MYmg4VVRDb0VsVVVBa3NJZS81Q3RyR21CeGlrSUpqZTFRbEw0?= =?utf-8?Q?f192qDsbjXe5gp7ak4=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_VI1PR01MB7053E1E0EDCE1FCA2B2B09A9C7859VI1PR01MB7053eurp_"
MIME-Version: 1.0
X-OriginatorOrg: wemonitoremail.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: VI1PR01MB7053.eurprd01.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9fb70677-6321-4ee6-ca43-08d8d4223112
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2021 15:30:58.9709 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a2b1d6fe-fc8b-4b7c-b9f1-d7b1ab3d23b3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Ofh2+Dc+ZH9Wtc0CyIwQwqhniSWPm56xxS5kB3ORuqeL5R8bQrRlFY1yFJp5suZ/xnkymCcwDLk/YnShrxp+jA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR01MB6623
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ByJn72AkxG1nOP0RJ27EFbEWGEE>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 18 Feb 2021 15:31:06 -0000

--_000_VI1PR01MB7053E1E0EDCE1FCA2B2B09A9C7859VI1PR01MB7053eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpUaGUgY29uY2VybiBpcyB0aGF0IFBJSSBpcyBjb250YWluZWQgaW4gdGhlIGFnZ3JlZ2F0ZSBy
ZXBvcnRzLg0KDQpUaGUgbWFjaGluYXRpb25zIG9mIHRoZSBpbmRpdmlkdWFsIEluZm9ybWF0aW9u
IEdvdmVybmFuY2UgZnVuY3Rpb25zIHRoYXQgZHJhdyBzdWNoIGNvbmNsdXNpb25zIG9yIHRoZSBk
ZWNpc2lvbiBtYWtpbmcgcHJvY2Vzc2VzIG9mIGluZGl2aWR1YWwgb3JnYW5pc2F0aW9ucyBhcm91
bmQgdGhvc2UgY29uY2x1c2lvbnMsIGlzIG5vdCByZWxldmFudCwgYW5kIHdvbuKAmXQgaGVscCBj
bG9zZSB0aGlzIHRpY2tldC4NCg0KS2VuLg0KDQpGcm9tOiBkbWFyYyA8ZG1hcmMtYm91bmNlc0Bp
ZXRmLm9yZz4gT24gQmVoYWxmIE9mIERvdWdsYXMgRm9zdGVyDQpTZW50OiBUaHVyc2RheSAxOCBG
ZWJydWFyeSAyMDIxIDAyOjIxDQpUbzogSUVURiBETUFSQyBXRyA8ZG1hcmNAaWV0Zi5vcmc+DQpT
dWJqZWN0OiBSZTogW2RtYXJjLWlldGZdIFRpY2tldCAjNjQgLSBDb250YWluZWQgRGF0YSBQSUkg
Q29uY2VybnMNCg0KSXQgd291bGQgaGVscCBtZSBpZiB5b3UgY291bGQgZWxhYm9yYXRlIG9uIHRo
ZSBjb25jZXJucyB0aGF0IHlvdSBoYXZlIGVuY291bnRlcmVkLg0KDQpXaGljaCBkYXRhIGlzIHNl
bnNpdGl2ZSBhbmQgdGhlcmVmb3JlIG5lZWRpbmcgY2xhc3NpZmljYXRpb24/DQoNCldoaWNoIHJv
bGVzIGNyZWF0ZXMgdGhlIG9iamVjdGlvbj8gICBTZXJ2ZXIgb3duZXIgc2VuZGluZyByZXBvcnRz
LCByZWNpcGllbnQgZG9tYWluIGFsbG93aW5nIHRoZSBzZXJ2ZXIgb3duZXIgdG8gc2VuZCByZXBv
cnRzIGZyb20gcmVjaXBpZW50IGRhdGEsIG9yIG9ubHkgcmVwb3J0IHJlY2lwaWVudD8NCg0KV2hl
biB0aGUgcmVwb3J0IHJlY2lwaWVudCBkb21haW4gZGVsZWdhdGVzIHJlY2VwdGlvbiB0byBhbiBh
dXRob3JpemVkIGFnZW50LCBob3cgZG9lcyB0aGUgb3JnYW5pemF0aW9uIG1ha2luZyB0aGUgZGVs
ZWdhdGlvbiBlc2NhcGUgbGlhYmlsaXR5IGZvciBob3cgdGhlIGluZm9ybWF0aW9uIGlzIGhhbmRs
ZWQgYW5kIHVzZWQ/DQoNCg0KT24gV2VkLCBGZWIgMTcsIDIwMjEgYXQgNDoyNyBQTSBLZW4gTydE
cmlzY29sbCA8a2VuPTQwd2Vtb25pdG9yZW1haWwuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzo0
MHdlbW9uaXRvcmVtYWlsLmNvbUBkbWFyYy5pZXRmLm9yZz4+IHdyb3RlOg0KDQpJIFBNIGRlcGxv
eW1lbnRzIGZvciBvcmdhbmlzYXRpb25zIGFuZCB0aGUgY29uY2VwdCBvZiBhZ2dyZWdhdGUgcmVw
b3J0cyBoYXZlIGNhdXNlZCBwcm9ibGVtIG1vcmUgdGhhbiBvbmNlLiBTaW1pbGFyIHRvIHRoZSBQ
SUkgY29uY2VybnMgb2YgcHJvdmlkZXJzIHdoaWNoIG9yaWdpbmF0ZWQgdGhpcyB0aWNrZXQsIHRo
ZXNlIG9yZ2FuaXNhdGlvbnMgb3BlcmF0ZSBpbiBoZWF2aWx5IGEgcmVndWxhdGVkIGluZHVzdHJ5
IGFuZCBoYXZlIGV4dGVuc2l2ZSBEUE8gZnVuY3Rpb25zLiBUbyBnaXZlIGEgZmxhdm91ciBvZiB3
aGF0IHRob3NlIGNvbmNlcm5zIHRyYW5zbGF0ZSB0byAtIEkgaGF2ZSBiZWVuIGFza2VkIGlzIGl0
IHBvc3NpYmxlIHRvIGltcGxlbWVudCBETUFSQyB3aXRob3V0IHVzaW5nIHJlcG9ydHMhIEkgaGF2
ZSBhbHNvIGhhZCBjb24tY2FsbHMgYWJvdXQgdHJhaW5pbmcgYSBuZXcgaGlyZSB0byByZWFkIGFu
ZCBjbGFzc2lmeSB0aGUgcmVwb3J0cyEgVGhhdCdzIGp1c3QgdHdvIGV4YW1wbGVzLiBJdCdzIG1v
c3RseSBkcml2ZW4gYnkgb3ZlcnplYWxvdXMgRFBPcyBidXQgSSB1bmRlcnN0YW5kIHRoZWlyIGNv
bmNlcm5zIG9uIHNvbWUgbGV2ZWwuIFdoZW4gdGhleSByZWFsaXNlIHRoYXQgd2UgY2FuIGRpc3Rp
bCB0aGUgcmVwb3J0IGRhdGEgYW5kIGl0IGRvZXNuJ3QgbmVlZCB0byBiZSBvbi1zaXRlLCB0aGV5
IGhhbmQgd2F2ZSBhd2F5IGFueSBjdXN0b2RpYW4gY29uY2VybnMgYW5kIHRoZSBwcm9qZWN0IG1v
dmVzIGZvcndhcmQuDQoNClNvLCBhc3N1bWluZyB0aGF0IG15IERNQVJDIGNsaWVudHMgYXJlbid0
IHVuaXF1ZSwgSSdtIHdvbmRlcmluZyBpZiB0aGlzIHNlY3Rpb24gY291bGQgYmUgc3BsaXQgaW50
byB0d28gcGFydHMsIG9uZSBmb3IgTWFpbCBSZWNlaXZlcnMgYW5kIG9uZSBmb3IgRG9tYWluIE93
bmVycz8NCg0KSWYgc28sIGZvciBEb21haW4gT3duZXJzLCBJJ2QgcHJvcG9zZSBzb21ldGhpbmcg
bGlrZSB0aGlzOg0KDQpBZ2dyZWdhdGUgZmVlZGJhY2sgcmVwb3J0cyBhcmUgZXNzZW50aWFsIGZv
ciB0aGUgcHJvcGVyIGltcGxlbWVudGF0aW9uIGFuZCBvcGVyYXRpb24gb2YgRE1BUkMuIERvbWFp
biBPd25lcnMgY2FuIGNob29zZSB0byBleGNsdXNpdmVseSBkaXJlY3QgcmVwb3J0cyB0byBhIHBy
b2Nlc3NvciBleHRlcm5hbCB0byB0aGVpciBvcmdhbml6YXRpb24uIEluIHN1Y2ggY2FzZXMsIHRo
ZSBjb250ZW50IG9mIHRoZSByZXBvcnRzIGFyZSBuZXZlciBzZW50IGRpcmVjdGx5IHRvIHRoZSBE
b21haW4gT3duZXIuDQoNClRob3VnaHRzPw0KDQpLZW4uDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gRnJvbTogZG1hcmMgPGRtYXJjLWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOmRt
YXJjLWJvdW5jZXNAaWV0Zi5vcmc+PiBPbiBCZWhhbGYgT2YgQnJvdG1hbiwgQWxleA0KPiBTZW50
OiBXZWRuZXNkYXkgMTcgRmVicnVhcnkgMjAyMSAxODo0MA0KPiBUbzogQWxlc3NhbmRybyBWZXNl
bHkgPHZlc2VseUB0YW5hLml0PG1haWx0bzp2ZXNlbHlAdGFuYS5pdD4+OyBkbWFyY0BpZXRmLm9y
ZzxtYWlsdG86ZG1hcmNAaWV0Zi5vcmc+DQo+IFN1YmplY3Q6IFJlOiBbZG1hcmMtaWV0Zl0gVGlj
a2V0ICM2NCAtIENvbnRhaW5lZCBEYXRhIFBJSSBDb25jZXJucw0KPg0KPiBJbmNvcnBvcmF0aW5n
IHNvbWUgZmVlZGJhY2s6DQo+DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gIyMgRGF0YSBDb250
YWluZWQgV2l0aGluIFJlcG9ydHMgKFRrdDY0KQ0KPg0KPiBXaXRoaW4gdGhlIHJlcG9ydHMgaXMg
Y29udGFpbmVkIGFuIGFnZ3JlZ2F0ZWQgYm9keSBvZiBhbm9ueW1pemVkIGRhdGENCj4gcGVydGFp
bmluZyB0byB0aGUgc2VuZGluZyBkb21haW4uICBUaGUgZGF0YSBpcyBtZWFudCB0byBhaWQgdGhl
IHJlcG9ydA0KPiBwcm9jZXNzb3JzIGFuZCBkb21haW4gaG9sZGVycyBpbiB2ZXJpZnlpbmcgc291
cmNlcyBvZiBtZXNzYWdlcw0KPiBwZXJ0YWluaW5nIHRvIHRoZSBETUFSQyBJZGVudGlmaWVyLiAg
VGhlIGRhdGEgc2hvdWxkIG5vdCBjb250YWluIGFueQ0KPiBpZGVudGlmeWluZyBjaGFyYWN0ZXJp
c3RpY3MgYWJvdXQgaW5kaXZpZHVhbCBzZW5kZXJzIG9yIHJlY2VpdmVycy4gIEFuDQo+IGVudGl0
eSBzZW5kaW5nIHJlcG9ydHMgc2hvdWxkIG5vdCBiZSBjb25jZXJuZWQgd2l0aCB0aGUgZGF0YSBj
b250YWluZWQNCj4gYXMgaXQgZG9lcyBub3QgY29udGFpbiBwZXJzb25hbCBpbmZvcm1hdGlvbiwg
c3VjaCBhcyBlbWFpbCBhZGRyZXNzZXMgb3INCj4gdXNlcm5hbWVzLiBUaGVyZSBhcmUgdHlwaWNh
bGx5IHRocmVlIHNpdHVhdGlvbnMgd2hlcmUgZGF0YSBpcyByZXBvcnRlZA0KPiB0byB0aGUgYWdn
cmVnYXRlIHJlY2VpdmVyczogbWVzc2FnZXMgcHJvcGVybHkgYXV0aGVudGljYXRlZCwgbWVzc2Fn
ZXMNCj4gdGhhdCBmYWlsIHRvIGF1dGhlbnRpY2F0ZSBhcyB0aGUgZG9tYWluLCBvciBtZXNzYWdl
cyB1dGlsaXppbmcgdGhlIERNQVJDDQo+IElkZW50aWZpZXIgdGhhdCBoYXZlIG5vIGF1dGhlbnRp
Y2F0aW9uIGF0IGFsbC4gIEluIGVhY2ggb2YgdGhlc2UgY2FzZXMsDQo+IHRoZXJlIGV4aXN0cyBu
byBpZGVudGlmeWluZyBpbmZvcm1hdGlvbiBmb3IgaW5kaXZpZHVhbHMsIGFuZCBhbGwgY29udGVu
dA0KPiB3aXRoaW4gdGhlIHJlcG9ydHMgc2hvdWxkIGJlIHJlbGF0ZWQgdG8gU01UUCBzZXJ2ZXJz
IHNlbmRpbmcgbWVzc2FnZXMNCj4gcG9zaW5nIGFzIHRoYXQgZG9tYWluLg0KPiAtLS0tLS0tLS0t
LS0tLS0tLS0tDQo+DQo+DQo+IC0tDQo+IEFsZXggQnJvdG1hbg0KPiBTci4gRW5naW5lZXIsIEFu
dGktQWJ1c2UgJiBNZXNzYWdpbmcgUG9saWN5IENvbWNhc3QNCj4NCj4gPiAtLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KPiA+IEZyb206IGRtYXJjIDxkbWFyYy1ib3VuY2VzQGlldGYub3JnPG1h
aWx0bzpkbWFyYy1ib3VuY2VzQGlldGYub3JnPj4gT24gQmVoYWxmIE9mIEFsZXNzYW5kcm8gVmVz
ZWx5DQo+ID4gU2VudDogTW9uZGF5LCBGZWJydWFyeSAxNSwgMjAyMSA4OjMxIEFNDQo+ID4gVG86
IGRtYXJjQGlldGYub3JnPG1haWx0bzpkbWFyY0BpZXRmLm9yZz4NCj4gPiBTdWJqZWN0OiBSZTog
W2RtYXJjLWlldGZdIFRpY2tldCAjNjQgLSBDb250YWluZWQgRGF0YSBQSUkgQ29uY2VybnMNCj4g
Pg0KPiA+IE9uIEZyaSAxMi9GZWIvMjAyMSAyMTozMDozOCArMDEwMCBCcm90bWFuLCBBbGV4IHdy
b3RlOg0KPiA+ID4gSGVsbG8gZm9sa3MsDQo+ID4gPg0KPiA+ID4gSW4gdGlja2V0ICM2NA0KPiA+
DQo+IChodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cHM6Ly90cmFjLmlldGYub3JnL3Ry
YWMvZG1hcmMvdGlja2V0LzY0XzxodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cHM6L3Ry
YWMuaWV0Zi5vcmcvdHJhYy9kbWFyYy90aWNrZXQvNjRfPg0KPiBfOyENCj4gPiAhQ1FsM21jSFgy
QSFXOTdoWjAtDQo+ID4gaXdSRGk4d0Jzc21SRkY2T3ljVkUxMnZNM3hoR2Q5Qm1MaEV6aTZWeWNw
M2JnendqaTIxeExRUWdubk1SYQ0KPiA+IEJ1eEdRZyQgKSwgaXQgd2FzIHN1Z2dlc3RlZCB0aGF0
IGEgUHJpdmFjeSBDb25zaWRlcmF0aW9ucyBzZWN0aW9uIG1heQ0KPiA+IGFsbGV2aWF0ZSBzb21l
IGNvbmNlcm5zIGFib3V0IHRoZSBvd25lcnNoaXAgb2YgdGhlIGRhdGEuICBJIGNyZWF0ZWQgYW4N
Cj4gPiBpbml0aWFsIGF0dGVtcHQsIGFuZCB0aG91Z2h0IHRvIGdldCBzb21lIGZlZWRiYWNrLiAg
SSBkaWRuJ3QgdGhpbmsgd2UNCj4gPiBzaG91bGQgZ28gdG9vIGZhciBpbiBkZXB0aCwgb3IgcmFp
c2UgY29ybmVyIGNhc2VzLiAgRmVsdCBsaWtlIGRvaW5nIHNvDQo+ID4gY291bGQgbGVhZCBkb3du
IGEgcmFiYml0IGhvbGUgb2YgdHJ5aW5nIHRvIGNvdmVyIGFsbCBjYXNlcy4gVGhpcyB3b3VsZA0K
PiA+IGdvIHdpdGhpbiBhICJQcml2YWN5IENvbnNpZGVyYXRpb25zIiBzZWN0aW9uLg0KPiA+ID4N
Cj4gPiA+ICogRGF0YSBDb250YWluZWQgV2l0aGluIFJlcG9ydHMgKCM2NCkNCj4gPiA+DQo+ID4g
PiBXaXRoaW4gdGhlIHJlcG9ydHMgaXMgY29udGFpbmVkIGFuIGFnZ3JlZ2F0ZWQgYm9keSBvZiBh
bm9ueW1pemVkDQo+ID4gPiBkYXRhIHBlcnRhaW5pbmcgdG8gdGhlIHNlbmRpbmcgZG9tYWluLiAg
VGhlIGRhdGEgaXMgbWVhbnQgdG8gYWlkIHRoZQ0KPiA+ID4gcmVwb3J0IHByb2Nlc3NvcnMgYW5k
IGRvbWFpbiBob2xkZXJzIGluIHZlcmlmeWluZyBzb3VyY2VzIG9mDQo+ID4gPiBtZXNzYWdlcyBw
ZXJ0YWluaW5nIHRvIHRoZSA1MzIyLkZyb20gRG9tYWluLg0KPiA+DQo+ID4NCj4gPiBJJ2QgcmVw
bGFjZSBhbGwgdGhvc2UgNTMyMi5Gcm9tIERvbWFpbiB3aXRoIG1haW4gRE1BUkMgaWRlbnRpZmll
ci4NCj4gPg0KPiA+DQo+ID4gPiBUaGUgZGF0YSBzaG91bGQgbm90IGNvbnRhaW4gYW55IGlkZW50
aWZ5aW5nIGNoYXJhY3RlcmlzdGljcyBhYm91dA0KPiA+ID4gaW5kaXZpZHVhbCBzZW5kZXJzIG9y
IHJlY2VpdmVycy4NCj4gPg0KPiA+DQo+ID4gVGhlIGFnZ3JlZ2F0ZWQgZGF0YSByZWZlcnMgdG8g
bmFtZXMgYW5kIElQIGFkZHJlc3NlcyBvZiBTTVRQIHNlcnZlcnMuDQo+ID4gSXQgY2Fubm90IGJl
IHVzZWQgdG8gaWRlbnRpZnkgaW5kaXZpZHVhbCB1c2Vycy4NCj4gPg0KPiA+DQo+ID4gPiAgQW4g
ZW50aXR5DQo+ID4gPiBzZW5kaW5nIHJlcG9ydHMgc2hvdWxkIG5vdCBiZSBjb25jZXJuZWQgd2l0
aCB0aGUgZGF0YSBjb250YWluZWQgYXMNCj4gPiA+IGl0IHNob3VsZCBub3QgY29udGFpbiBQSUkg
KE5JU1QgcmVmZXJlbmNlIGZvciBQSUkgZGVmaW5pdGlvbiksIHN1Y2gNCj4gPiA+IGFzIGVtYWls
DQo+ID4gYWRkcmVzc2VzIG9yDQo+ID4gPiB1c2VybmFtZXMuDQo+ID4NCj4gPg0KPiA+IEknZCBz
dWJzdGl0dXRlIC9zaG91bGQgbm90L2RvZXMgbm90Ly4gIEV2ZW4gaWYgYSBzZXJ2ZXIgaGFzIGEg
dW5pcXVlDQo+ID4gdXNlciwgdGhlIGRvbWFpbiBuYW1lIGFuZCB0aGUgSVAgYWRkcmVzcyBhcmUg
dGhvc2Ugb2YgYSBwdWJsaWMgZW50aXR5LA0KPiA+IG5vdCB0aG9zZSBvZiBhIHByaXZhdGUgY2l0
aXplbi4NCj4gPg0KPiA+IFRoZSB0ZXJtIFBlcnNvbmFsbHkgSWRlbnRpZmlhYmxlIEluZm9ybWF0
aW9uIChQSUkpIGlzIFVTLW5hdGlvbmFsLiAgSQ0KPiA+IHRoaW5rIGp1c3QgcGVyc29uYWwgaW5m
b3JtYXRpb24gaXMgb2YgYnJvYWRlciB1c2UuICBQZXJzb25hbCBkYXRhIGlzDQo+ID4gYWxzbyBh
IHZhbGlkIGFsdGVybmF0aXZlLg0KPiA+DQo+ID4NCj4gPiBqbTJjDQo+ID4gQWxlDQo+ID4gLS0N
Cj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+
ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+
DQo+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4g
PiBkbWFyYyBtYWlsaW5nIGxpc3QNCj4gPiBkbWFyY0BpZXRmLm9yZzxtYWlsdG86ZG1hcmNAaWV0
Zi5vcmc+DQo+ID4gaHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vZG1hcjxodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0
cHM6L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RtYXI+DQo+ID4gYw0KPiA+IF9fOyEh
Q1FsM21jSFgyQSFXOTdoWjAtDQo+ID4gaXdSRGk4d0Jzc21SRkY2T3ljVkUxMnZNM3hoR2Q5Qm1M
aEV6aTZWeWNwM2JnendqaTIxeExRUWdubk1URjYNCj4gPiBmelBLQSQNCj4NCj4gX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gZG1hcmMgbWFpbGluZyBs
aXN0DQo+IGRtYXJjQGlldGYub3JnPG1haWx0bzpkbWFyY0BpZXRmLm9yZz4NCj4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbWFyYw0KDQpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KZG1hcmMgbWFpbGluZyBsaXN0DQpkbWFyY0Bp
ZXRmLm9yZzxtYWlsdG86ZG1hcmNAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2RtYXJjDQo=

--_000_VI1PR01MB7053E1E0EDCE1FCA2B2B09A9C7859VI1PR01MB7053eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1yZXBseTsNCglmb250LWZhbWlseToiQXJpYWwiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93
dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpF
Ti1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFy
Z2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8
bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFb
ZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0i
ZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91
dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLUlFIiBsaW5rPSJi
bHVlIiB2bGluaz0icHVycGxlIiBzdHlsZT0id29yZC13cmFwOmJyZWFrLXdvcmQiPg0KPGRpdiBj
bGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxmb250IHNpemU9IjIi
IGZhY2U9IkFyaWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQXJpYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPlRoZSBjb25jZXJuIGlzIHRoYXQgUElJIGlzIGNvbnRhaW5lZCBpbiB0aGUg
YWdncmVnYXRlIHJlcG9ydHMuPG86cD48L286cD48L3NwYW4+PC9mb250PjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxmb250IHNpemU9IjIiIGZhY2U9IkFyaWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2ZvbnQ+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQXJpYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlRoZSBtYWNoaW5hdGlvbnMg
b2YgdGhlIGluZGl2aWR1YWwgSW5mb3JtYXRpb24gR292ZXJuYW5jZSBmdW5jdGlvbnMgdGhhdCBk
cmF3IHN1Y2ggY29uY2x1c2lvbnMgb3IgdGhlIGRlY2lzaW9uIG1ha2luZyBwcm9jZXNzZXMNCiBv
ZiBpbmRpdmlkdWFsIG9yZ2FuaXNhdGlvbnMgYXJvdW5kIHRob3NlIGNvbmNsdXNpb25zLCBpcyBu
b3QgcmVsZXZhbnQsIGFuZCB3b27igJl0IGhlbHAgY2xvc2UgdGhpcyB0aWNrZXQuPG86cD48L286
cD48L3NwYW4+PC9mb250PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxmb250IHNpemU9IjIi
IGZhY2U9IkFyaWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQXJpYWwiPjxzcGFuIGxhbmc9IkVOLUdCIiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5L
ZW4uPG86cD48L286cD48L3NwYW4+PC9mb250PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxm
b250IHNpemU9IjIiIGZhY2U9IkFyaWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wPg0KPGRpdiBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAw
Y20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9w
OnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48Yj48Zm9udCBzaXplPSIyIiBmYWNlPSJDYWxpYnJpIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC13ZWlnaHQ6Ym9sZCI+RnJvbTo8
L3NwYW4+PC9mb250PjwvYj48c3BhbiBsYW5nPSJFTi1VUyI+IGRtYXJjICZsdDtkbWFyYy1ib3Vu
Y2VzQGlldGYub3JnJmd0Ow0KPGI+PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPk9uIEJl
aGFsZiBPZiA8L3NwYW4+PC9iPkRvdWdsYXMgRm9zdGVyPGJyPg0KPGI+PHNwYW4gc3R5bGU9ImZv
bnQtd2VpZ2h0OmJvbGQiPlNlbnQ6PC9zcGFuPjwvYj4gVGh1cnNkYXkgMTggRmVicnVhcnkgMjAy
MSAwMjoyMTxicj4NCjxiPjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5Ubzo8L3NwYW4+
PC9iPiBJRVRGIERNQVJDIFdHICZsdDtkbWFyY0BpZXRmLm9yZyZndDs8YnI+DQo8Yj48c3BhbiBz
dHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDo8L3NwYW4+PC9iPiBSZTogW2RtYXJjLWll
dGZdIFRpY2tldCAjNjQgLSBDb250YWluZWQgRGF0YSBQSUkgQ29uY2VybnM8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6
ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvZm9udD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQiPkl0IHdvdWxkIGhlbHAgbWUgaWYgeW91IGNvdWxkIGVsYWJvcmF0ZSBvbiB0aGUgY29u
Y2VybnMgdGhhdCZuYnNwO3lvdSBoYXZlIGVuY291bnRlcmVkLiZuYnNwOyZuYnNwOzxvOnA+PC9v
OnA+PC9zcGFuPjwvZm9udD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQg
c2l6ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvZm9udD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48Zm9udCBzaXplPSIyIiBmYWNlPSJDYWxpYnJpIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdCI+V2hpY2ggZGF0YSBpcyBzZW5zaXRpdmUgYW5kIHRoZXJlZm9yZSBu
ZWVkaW5nIGNsYXNzaWZpY2F0aW9uPzxvOnA+PC9vOnA+PC9zcGFuPjwvZm9udD48L3A+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvZm9u
dD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Zm9udCBzaXplPSIy
IiBmYWNlPSJDYWxpYnJpIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+V2hpY2ggcm9s
ZXMgY3JlYXRlcyB0aGUgb2JqZWN0aW9uPyZuYnNwOyAmbmJzcDtTZXJ2ZXIgb3duZXIgc2VuZGlu
ZyByZXBvcnRzLCByZWNpcGllbnQgZG9tYWluIGFsbG93aW5nIHRoZSBzZXJ2ZXIgb3duZXIgdG8g
c2VuZCByZXBvcnRzIGZyb20gcmVjaXBpZW50IGRhdGEsIG9yIG9ubHkgcmVwb3J0IHJlY2lwaWVu
dD8mbmJzcDsmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvZm9u
dD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Zm9udCBzaXplPSIy
IiBmYWNlPSJDYWxpYnJpIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+V2hlbiB0aGUg
cmVwb3J0IHJlY2lwaWVudCBkb21haW4gZGVsZWdhdGVzIHJlY2VwdGlvbiB0byBhbiBhdXRob3Jp
emVkIGFnZW50LCBob3cgZG9lcyB0aGUgb3JnYW5pemF0aW9uIG1ha2luZyB0aGUgZGVsZWdhdGlv
biBlc2NhcGUgbGlhYmlsaXR5IGZvciBob3cgdGhlIGluZm9ybWF0aW9uIGlzIGhhbmRsZWQNCiBh
bmQgdXNlZD88bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvZm9udD48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Zm9udCBzaXpl
PSIyIiBmYWNlPSJDYWxpYnJpIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9mb250PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQiPk9uIFdlZCwgRmViIDE3LCAyMDIxIGF0IDQ6MjcgUE0gS2VuIE8nRHJpc2Nv
bGwgJmx0O2tlbj08YSBocmVmPSJtYWlsdG86NDB3ZW1vbml0b3JlbWFpbC5jb21AZG1hcmMuaWV0
Zi5vcmciPjQwd2Vtb25pdG9yZW1haWwuY29tQGRtYXJjLmlldGYub3JnPC9hPiZndDsgd3JvdGU6
PG86cD48L286cD48L3NwYW4+PC9mb250PjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9
ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20g
MGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxmb250IHNpemU9IjIiIGZhY2U9IkNhbGlicmkiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0Ij48YnI+DQpJIFBNIGRlcGxveW1lbnRzIGZvciBvcmdhbmlzYXRp
b25zIGFuZCB0aGUgY29uY2VwdCBvZiBhZ2dyZWdhdGUgcmVwb3J0cyBoYXZlIGNhdXNlZCBwcm9i
bGVtIG1vcmUgdGhhbiBvbmNlLiBTaW1pbGFyIHRvIHRoZSBQSUkgY29uY2VybnMgb2YgcHJvdmlk
ZXJzIHdoaWNoIG9yaWdpbmF0ZWQgdGhpcyB0aWNrZXQsIHRoZXNlIG9yZ2FuaXNhdGlvbnMgb3Bl
cmF0ZSBpbiBoZWF2aWx5IGEgcmVndWxhdGVkIGluZHVzdHJ5IGFuZCBoYXZlIGV4dGVuc2l2ZQ0K
IERQTyBmdW5jdGlvbnMuIFRvIGdpdmUgYSBmbGF2b3VyIG9mIHdoYXQgdGhvc2UgY29uY2VybnMg
dHJhbnNsYXRlIHRvIC0gSSBoYXZlIGJlZW4gYXNrZWQgaXMgaXQgcG9zc2libGUgdG8gaW1wbGVt
ZW50IERNQVJDIHdpdGhvdXQgdXNpbmcgcmVwb3J0cyEgSSBoYXZlIGFsc28gaGFkIGNvbi1jYWxs
cyBhYm91dCB0cmFpbmluZyBhIG5ldyBoaXJlIHRvIHJlYWQgYW5kIGNsYXNzaWZ5IHRoZSByZXBv
cnRzISBUaGF0J3MganVzdCB0d28gZXhhbXBsZXMuDQogSXQncyBtb3N0bHkgZHJpdmVuIGJ5IG92
ZXJ6ZWFsb3VzIERQT3MgYnV0IEkgdW5kZXJzdGFuZCB0aGVpciBjb25jZXJucyBvbiBzb21lIGxl
dmVsLiBXaGVuIHRoZXkgcmVhbGlzZSB0aGF0IHdlIGNhbiBkaXN0aWwgdGhlIHJlcG9ydCBkYXRh
IGFuZCBpdCBkb2Vzbid0IG5lZWQgdG8gYmUgb24tc2l0ZSwgdGhleSBoYW5kIHdhdmUgYXdheSBh
bnkgY3VzdG9kaWFuIGNvbmNlcm5zIGFuZCB0aGUgcHJvamVjdCBtb3ZlcyBmb3J3YXJkLjxicj4N
Cjxicj4NClNvLCBhc3N1bWluZyB0aGF0IG15IERNQVJDIGNsaWVudHMgYXJlbid0IHVuaXF1ZSwg
SSdtIHdvbmRlcmluZyBpZiB0aGlzIHNlY3Rpb24gY291bGQgYmUgc3BsaXQgaW50byB0d28gcGFy
dHMsIG9uZSBmb3IgTWFpbCBSZWNlaXZlcnMgYW5kIG9uZSBmb3IgRG9tYWluIE93bmVycz88YnI+
DQo8YnI+DQpJZiBzbywgZm9yIERvbWFpbiBPd25lcnMsIEknZCBwcm9wb3NlIHNvbWV0aGluZyBs
aWtlIHRoaXM6PGJyPg0KPGJyPg0KQWdncmVnYXRlIGZlZWRiYWNrIHJlcG9ydHMgYXJlIGVzc2Vu
dGlhbCBmb3IgdGhlIHByb3BlciBpbXBsZW1lbnRhdGlvbiBhbmQgb3BlcmF0aW9uIG9mIERNQVJD
LiBEb21haW4gT3duZXJzIGNhbiBjaG9vc2UgdG8gZXhjbHVzaXZlbHkgZGlyZWN0IHJlcG9ydHMg
dG8gYSBwcm9jZXNzb3IgZXh0ZXJuYWwgdG8gdGhlaXIgb3JnYW5pemF0aW9uLiBJbiBzdWNoIGNh
c2VzLCB0aGUgY29udGVudCBvZiB0aGUgcmVwb3J0cyBhcmUgbmV2ZXIgc2VudCBkaXJlY3RseQ0K
IHRvIHRoZSBEb21haW4gT3duZXIuPGJyPg0KPGJyPg0KVGhvdWdodHM/PGJyPg0KPGJyPg0KS2Vu
Ljxicj4NCjxicj4NCiZndDsgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+DQomZ3Q7IEZy
b206IGRtYXJjICZsdDs8YSBocmVmPSJtYWlsdG86ZG1hcmMtYm91bmNlc0BpZXRmLm9yZyIgdGFy
Z2V0PSJfYmxhbmsiPmRtYXJjLWJvdW5jZXNAaWV0Zi5vcmc8L2E+Jmd0OyBPbiBCZWhhbGYgT2Yg
QnJvdG1hbiwgQWxleDxicj4NCiZndDsgU2VudDogV2VkbmVzZGF5IDE3IEZlYnJ1YXJ5IDIwMjEg
MTg6NDA8YnI+DQomZ3Q7IFRvOiBBbGVzc2FuZHJvIFZlc2VseSAmbHQ7PGEgaHJlZj0ibWFpbHRv
OnZlc2VseUB0YW5hLml0IiB0YXJnZXQ9Il9ibGFuayI+dmVzZWx5QHRhbmEuaXQ8L2E+Jmd0OzsN
CjxhIGhyZWY9Im1haWx0bzpkbWFyY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmRtYXJjQGll
dGYub3JnPC9hPjxicj4NCiZndDsgU3ViamVjdDogUmU6IFtkbWFyYy1pZXRmXSBUaWNrZXQgIzY0
IC0gQ29udGFpbmVkIERhdGEgUElJIENvbmNlcm5zPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEluY29y
cG9yYXRpbmcgc29tZSBmZWVkYmFjazo8YnI+DQomZ3Q7IDxicj4NCiZndDsgLS0tLS0tLS0tLS0t
LS0tLS0tLTxicj4NCiZndDsgIyMgRGF0YSBDb250YWluZWQgV2l0aGluIFJlcG9ydHMgKFRrdDY0
KTxicj4NCiZndDsgPGJyPg0KJmd0OyBXaXRoaW4gdGhlIHJlcG9ydHMgaXMgY29udGFpbmVkIGFu
IGFnZ3JlZ2F0ZWQgYm9keSBvZiBhbm9ueW1pemVkIGRhdGE8YnI+DQomZ3Q7IHBlcnRhaW5pbmcg
dG8gdGhlIHNlbmRpbmcgZG9tYWluLiZuYnNwOyBUaGUgZGF0YSBpcyBtZWFudCB0byBhaWQgdGhl
IHJlcG9ydDxicj4NCiZndDsgcHJvY2Vzc29ycyBhbmQgZG9tYWluIGhvbGRlcnMgaW4gdmVyaWZ5
aW5nIHNvdXJjZXMgb2YgbWVzc2FnZXM8YnI+DQomZ3Q7IHBlcnRhaW5pbmcgdG8gdGhlIERNQVJD
IElkZW50aWZpZXIuJm5ic3A7IFRoZSBkYXRhIHNob3VsZCBub3QgY29udGFpbiBhbnk8YnI+DQom
Z3Q7IGlkZW50aWZ5aW5nIGNoYXJhY3RlcmlzdGljcyBhYm91dCBpbmRpdmlkdWFsIHNlbmRlcnMg
b3IgcmVjZWl2ZXJzLiZuYnNwOyBBbjxicj4NCiZndDsgZW50aXR5IHNlbmRpbmcgcmVwb3J0cyBz
aG91bGQgbm90IGJlIGNvbmNlcm5lZCB3aXRoIHRoZSBkYXRhIGNvbnRhaW5lZDxicj4NCiZndDsg
YXMgaXQgZG9lcyBub3QgY29udGFpbiBwZXJzb25hbCBpbmZvcm1hdGlvbiwgc3VjaCBhcyBlbWFp
bCBhZGRyZXNzZXMgb3I8YnI+DQomZ3Q7IHVzZXJuYW1lcy4gVGhlcmUgYXJlIHR5cGljYWxseSB0
aHJlZSBzaXR1YXRpb25zIHdoZXJlIGRhdGEgaXMgcmVwb3J0ZWQ8YnI+DQomZ3Q7IHRvIHRoZSBh
Z2dyZWdhdGUgcmVjZWl2ZXJzOiBtZXNzYWdlcyBwcm9wZXJseSBhdXRoZW50aWNhdGVkLCBtZXNz
YWdlczxicj4NCiZndDsgdGhhdCBmYWlsIHRvIGF1dGhlbnRpY2F0ZSBhcyB0aGUgZG9tYWluLCBv
ciBtZXNzYWdlcyB1dGlsaXppbmcgdGhlIERNQVJDPGJyPg0KJmd0OyBJZGVudGlmaWVyIHRoYXQg
aGF2ZSBubyBhdXRoZW50aWNhdGlvbiBhdCBhbGwuJm5ic3A7IEluIGVhY2ggb2YgdGhlc2UgY2Fz
ZXMsPGJyPg0KJmd0OyB0aGVyZSBleGlzdHMgbm8gaWRlbnRpZnlpbmcgaW5mb3JtYXRpb24gZm9y
IGluZGl2aWR1YWxzLCBhbmQgYWxsIGNvbnRlbnQ8YnI+DQomZ3Q7IHdpdGhpbiB0aGUgcmVwb3J0
cyBzaG91bGQgYmUgcmVsYXRlZCB0byBTTVRQIHNlcnZlcnMgc2VuZGluZyBtZXNzYWdlczxicj4N
CiZndDsgcG9zaW5nIGFzIHRoYXQgZG9tYWluLjxicj4NCiZndDsgLS0tLS0tLS0tLS0tLS0tLS0t
LTxicj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IC0tPGJyPg0KJmd0OyBBbGV4IEJyb3Rt
YW48YnI+DQomZ3Q7IFNyLiBFbmdpbmVlciwgQW50aS1BYnVzZSAmYW1wOyBNZXNzYWdpbmcgUG9s
aWN5IENvbWNhc3Q8YnI+DQomZ3Q7IDxicj4NCiZndDsgJmd0OyAtLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLTxicj4NCiZndDsgJmd0OyBGcm9tOiBkbWFyYyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRt
YXJjLWJvdW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5kbWFyYy1ib3VuY2VzQGlldGYu
b3JnPC9hPiZndDsgT24gQmVoYWxmIE9mIEFsZXNzYW5kcm8gVmVzZWx5PGJyPg0KJmd0OyAmZ3Q7
IFNlbnQ6IE1vbmRheSwgRmVicnVhcnkgMTUsIDIwMjEgODozMSBBTTxicj4NCiZndDsgJmd0OyBU
bzogPGEgaHJlZj0ibWFpbHRvOmRtYXJjQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+ZG1hcmNA
aWV0Zi5vcmc8L2E+PGJyPg0KJmd0OyAmZ3Q7IFN1YmplY3Q6IFJlOiBbZG1hcmMtaWV0Zl0gVGlj
a2V0ICM2NCAtIENvbnRhaW5lZCBEYXRhIFBJSSBDb25jZXJuczxicj4NCiZndDsgJmd0Ozxicj4N
CiZndDsgJmd0OyBPbiBGcmkgMTIvRmViLzIwMjEgMjE6MzA6MzggKzAxMDAgQnJvdG1hbiwgQWxl
eCB3cm90ZTo8YnI+DQomZ3Q7ICZndDsgJmd0OyBIZWxsbyBmb2xrcyw8YnI+DQomZ3Q7ICZndDsg
Jmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7IEluIHRpY2tldCAjNjQ8YnI+DQomZ3Q7ICZndDs8YnI+
DQomZ3Q7ICg8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cHM6L3RyYWMu
aWV0Zi5vcmcvdHJhYy9kbWFyYy90aWNrZXQvNjRfIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly91
cmxkZWZlbnNlLmNvbS92My9fX2h0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2RtYXJjL3RpY2tl
dC82NF88L2E+PGJyPg0KJmd0OyBfOyE8YnI+DQomZ3Q7ICZndDsgIUNRbDNtY0hYMkEhVzk3aFow
LTxicj4NCiZndDsgJmd0OyBpd1JEaTh3QnNzbVJGRjZPeWNWRTEydk0zeGhHZDlCbUxoRXppNlZ5
Y3AzYmd6d2ppMjF4TFFRZ25uTVJhPGJyPg0KJmd0OyAmZ3Q7IEJ1eEdRZyQgKSwgaXQgd2FzIHN1
Z2dlc3RlZCB0aGF0IGEgUHJpdmFjeSBDb25zaWRlcmF0aW9ucyBzZWN0aW9uIG1heTxicj4NCiZn
dDsgJmd0OyBhbGxldmlhdGUgc29tZSBjb25jZXJucyBhYm91dCB0aGUgb3duZXJzaGlwIG9mIHRo
ZSBkYXRhLiZuYnNwOyBJIGNyZWF0ZWQgYW48YnI+DQomZ3Q7ICZndDsgaW5pdGlhbCBhdHRlbXB0
LCBhbmQgdGhvdWdodCB0byBnZXQgc29tZSBmZWVkYmFjay4mbmJzcDsgSSBkaWRuJ3QgdGhpbmsg
d2U8YnI+DQomZ3Q7ICZndDsgc2hvdWxkIGdvIHRvbyBmYXIgaW4gZGVwdGgsIG9yIHJhaXNlIGNv
cm5lciBjYXNlcy4mbmJzcDsgRmVsdCBsaWtlIGRvaW5nIHNvPGJyPg0KJmd0OyAmZ3Q7IGNvdWxk
IGxlYWQgZG93biBhIHJhYmJpdCBob2xlIG9mIHRyeWluZyB0byBjb3ZlciBhbGwgY2FzZXMuIFRo
aXMgd291bGQ8YnI+DQomZ3Q7ICZndDsgZ28gd2l0aGluIGEgJnF1b3Q7UHJpdmFjeSBDb25zaWRl
cmF0aW9ucyZxdW90OyBzZWN0aW9uLjxicj4NCiZndDsgJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7
ICZndDsgKiBEYXRhIENvbnRhaW5lZCBXaXRoaW4gUmVwb3J0cyAoIzY0KTxicj4NCiZndDsgJmd0
OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7ICZndDsgV2l0aGluIHRoZSByZXBvcnRzIGlzIGNvbnRhaW5l
ZCBhbiBhZ2dyZWdhdGVkIGJvZHkgb2YgYW5vbnltaXplZDxicj4NCiZndDsgJmd0OyAmZ3Q7IGRh
dGEgcGVydGFpbmluZyB0byB0aGUgc2VuZGluZyBkb21haW4uJm5ic3A7IFRoZSBkYXRhIGlzIG1l
YW50IHRvIGFpZCB0aGU8YnI+DQomZ3Q7ICZndDsgJmd0OyByZXBvcnQgcHJvY2Vzc29ycyBhbmQg
ZG9tYWluIGhvbGRlcnMgaW4gdmVyaWZ5aW5nIHNvdXJjZXMgb2Y8YnI+DQomZ3Q7ICZndDsgJmd0
OyBtZXNzYWdlcyBwZXJ0YWluaW5nIHRvIHRoZSA1MzIyLkZyb20gRG9tYWluLjxicj4NCiZndDsg
Jmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBJJ2QgcmVwbGFjZSBhbGwgdGhvc2Ug
NTMyMi5Gcm9tIERvbWFpbiB3aXRoIG1haW4gRE1BUkMgaWRlbnRpZmllci48YnI+DQomZ3Q7ICZn
dDs8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgJmd0OyBUaGUgZGF0YSBzaG91bGQgbm90
IGNvbnRhaW4gYW55IGlkZW50aWZ5aW5nIGNoYXJhY3RlcmlzdGljcyBhYm91dDxicj4NCiZndDsg
Jmd0OyAmZ3Q7IGluZGl2aWR1YWwgc2VuZGVycyBvciByZWNlaXZlcnMuPGJyPg0KJmd0OyAmZ3Q7
PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IFRoZSBhZ2dyZWdhdGVkIGRhdGEgcmVmZXJz
IHRvIG5hbWVzIGFuZCBJUCBhZGRyZXNzZXMgb2YgU01UUCBzZXJ2ZXJzLjxicj4NCiZndDsgJmd0
OyBJdCBjYW5ub3QgYmUgdXNlZCB0byBpZGVudGlmeSBpbmRpdmlkdWFsIHVzZXJzLjxicj4NCiZn
dDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyAmZ3Q7Jm5ic3A7IEFuIGVudGl0
eTxicj4NCiZndDsgJmd0OyAmZ3Q7IHNlbmRpbmcgcmVwb3J0cyBzaG91bGQgbm90IGJlIGNvbmNl
cm5lZCB3aXRoIHRoZSBkYXRhIGNvbnRhaW5lZCBhczxicj4NCiZndDsgJmd0OyAmZ3Q7IGl0IHNo
b3VsZCBub3QgY29udGFpbiBQSUkgKE5JU1QgcmVmZXJlbmNlIGZvciBQSUkgZGVmaW5pdGlvbiks
IHN1Y2g8YnI+DQomZ3Q7ICZndDsgJmd0OyBhcyBlbWFpbDxicj4NCiZndDsgJmd0OyBhZGRyZXNz
ZXMgb3I8YnI+DQomZ3Q7ICZndDsgJmd0OyB1c2VybmFtZXMuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0K
Jmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IEknZCBzdWJzdGl0dXRlIC9zaG91bGQgbm90L2RvZXMg
bm90Ly4mbmJzcDsgRXZlbiBpZiBhIHNlcnZlciBoYXMgYSB1bmlxdWU8YnI+DQomZ3Q7ICZndDsg
dXNlciwgdGhlIGRvbWFpbiBuYW1lIGFuZCB0aGUgSVAgYWRkcmVzcyBhcmUgdGhvc2Ugb2YgYSBw
dWJsaWMgZW50aXR5LDxicj4NCiZndDsgJmd0OyBub3QgdGhvc2Ugb2YgYSBwcml2YXRlIGNpdGl6
ZW4uPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IFRoZSB0ZXJtIFBlcnNvbmFsbHkgSWRl
bnRpZmlhYmxlIEluZm9ybWF0aW9uIChQSUkpIGlzIFVTLW5hdGlvbmFsLiZuYnNwOyBJPGJyPg0K
Jmd0OyAmZ3Q7IHRoaW5rIGp1c3QgcGVyc29uYWwgaW5mb3JtYXRpb24gaXMgb2YgYnJvYWRlciB1
c2UuJm5ic3A7IFBlcnNvbmFsIGRhdGEgaXM8YnI+DQomZ3Q7ICZndDsgYWxzbyBhIHZhbGlkIGFs
dGVybmF0aXZlLjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0OyBq
bTJjPGJyPg0KJmd0OyAmZ3Q7IEFsZTxicj4NCiZndDsgJmd0OyAtLTxicj4NCiZndDsgJmd0Ozxi
cj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0
Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsg
Jmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZn
dDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4N
CiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxi
cj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0
OyBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZn
dDsgJmd0OyBkbWFyYyBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7ICZndDsgPGEgaHJlZj0ibWFpbHRv
OmRtYXJjQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+ZG1hcmNAaWV0Zi5vcmc8L2E+PGJyPg0K
Jmd0OyAmZ3Q7IDxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZG1hciIgdGFyZ2V0PSJfYmxhbmsiPg0KaHR0cHM6
Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vZG1hcjwvYT48YnI+DQomZ3Q7ICZndDsgYzxicj4NCiZndDsgJmd0OyBfXzshIUNRbDNtY0hY
MkEhVzk3aFowLTxicj4NCiZndDsgJmd0OyBpd1JEaTh3QnNzbVJGRjZPeWNWRTEydk0zeGhHZDlC
bUxoRXppNlZ5Y3AzYmd6d2ppMjF4TFFRZ25uTVRGNjxicj4NCiZndDsgJmd0OyBmelBLQSQ8YnI+
DQomZ3Q7IDxicj4NCiZndDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX188YnI+DQomZ3Q7IGRtYXJjIG1haWxpbmcgbGlzdDxicj4NCiZndDsgPGEgaHJlZj0i
bWFpbHRvOmRtYXJjQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+ZG1hcmNAaWV0Zi5vcmc8L2E+
PGJyPg0KJmd0OyA8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L2RtYXJjIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9kbWFyYzwvYT48YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXzxicj4NCmRtYXJjIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1h
aWx0bzpkbWFyY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmRtYXJjQGlldGYub3JnPC9hPjxi
cj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZG1hcmMi
IHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2Rt
YXJjPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvZm9udD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_VI1PR01MB7053E1E0EDCE1FCA2B2B09A9C7859VI1PR01MB7053eurp_--


From nobody Thu Feb 18 08:53:25 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 F19143A144B for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 08:53: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 (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 klgyfGgng6WF for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 08:53:22 -0800 (PST)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 3090F3A144A for <dmarc@ietf.org>; Thu, 18 Feb 2021 08:53:22 -0800 (PST)
Received: by mail-io1-xd2d.google.com with SMTP id y202so2709551iof.1 for <dmarc@ietf.org>; Thu, 18 Feb 2021 08:53:21 -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=pGKg70k+mjY0sco96COcIMoje0G065EcTjtCGbEPOtk=; b=G7hS0ooltYjW03fDqYSe+ozyvaTlrW6jax5sqd4fVt2OAtlwh8guaOAN/f8qokBtfF rxWr/KL/z871CQYnNCeD+WdZW2zaCKj8wyJSamM7qsE05WFO6XjZ3ihQJawi5MlqCxrC uLktl1c9s2dZb2uNhe+Bu4MApR9MFJbUiegO0=
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=pGKg70k+mjY0sco96COcIMoje0G065EcTjtCGbEPOtk=; b=F/SFENg53MTEE3BRiDa9/FiZreqv8zDtkxlQNkTm7ACX3NeVya+p840RRtqoU2f0pg JKdDYcXY3Z/E8F06cvYDqIrGThRyZVG4iY0qZGxicrRNDiH2dpu91JAOWqViTxGkNKBY W+tjPDoyaSl/wIv7KYDp1LvT+mVjGJsGNSxZnepRfpUYurOTtjO/wcLckelRbs++Hso7 eF1yqdjtwl3RzpOijrc5P/3Fqzr1rWu30BRmCvhJOUC/6oyRczmE8uDl5p1RyUYCnqOL UMX0JPVtEUQg1NhZ8cqQZgThMXNQRvigbdLYJhmfFwP8NRYQGRFDKxWhY03dcOEnQiU2 ryow==
X-Gm-Message-State: AOAM531jEvpraFzYYeqfamQG2Hu8TxURFeFG5+0vxg/Df8QhgNbn3fks j6vdDcZH3KZiROhYHOrzgMlIfiJYdfGcqTJe2f3Z9cu3Y9U=
X-Google-Smtp-Source: ABdhPJxW1YYdh+wWaJftWjEKagPfwLIJtlvLhGvNKx99KWNJBtq+Bq4IuiJhvS17GcmvXA5wMBQiZQNVcAt1rIOSS4s=
X-Received: by 2002:a6b:f406:: with SMTP id i6mr6327iog.121.1613667201124; Thu, 18 Feb 2021 08:53:21 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <20210218024606.4727B6E23874@ary.qy> <VI1PR01MB70530199B815F3216D64E9A2C7859@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
In-Reply-To: <VI1PR01MB70530199B815F3216D64E9A2C7859@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Thu, 18 Feb 2021 08:52:55 -0800
Message-ID: <CABuGu1pC_rh2vDUuNsHF0dLgKGiR3nve8YE1P9trPM-wUi+EfA@mail.gmail.com>
To: "Ken O'Driscoll" <ken=40wemonitoremail.com@dmarc.ietf.org>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary="0000000000004f222105bb9f2c3b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/cmS1Wlyr8OzF2noG8UBee-8Wvqk>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 18 Feb 2021 16:53:24 -0000

--0000000000004f222105bb9f2c3b
Content-Type: text/plain; charset="UTF-8"

On Thu, Feb 18, 2021 at 7:09 AM Ken O'Driscoll <ken=
40wemonitoremail.com@dmarc.ietf.org> wrote:

>
> . . . I'd propose something like the below, which I think gets across what
> we all want to say.
>
> =======
> Aggregate feedback reports contain anonymized data relating to messages
> purportedly originating from the Domain Owner. The data does not contain
> any identifying characteristics about individual senders or receivers. No
> personal information such as individual email addresses, IP addresses of
> individuals, or the content of any messages, is included in reports.
>
> Mail Receivers should have no concerns in sending reports as they do not
> contain personal information. In all cases, the data within the reports
> relates to the authentication information provided by mail servers sending
> messages on behalf of the Domain Owner. This information is necessary to
> assist Domain Owners in implementing and maintaining DMARC.
>
> Domain Owners should have no concerns in receiving reports as they do not
> contain personal information. The reports only contain aggregated
> anonymized data related to the authentication details of messages claiming
> to originate from their domain. This information is essential for the
> proper implementation and operation of DMARC. Domain Owners who are unable
> to receive reports for organizational reasons, can choose to exclusively
> direct the reports to an external processor.
> =======
>

With a s/anonymized/aggregated/g change, this seems like reasonable
language. In technical terms, there is no anonymization involved. The only
other issue might be some ambiguity in the intepretation of the term
"individual senders or receivers" because the IP addresses of the MTAs
involved in the email interchange are definitely in the report. As someone
has pointed out earlier in the thread, a compromised home computer which is
able to send out on port 25 would indeed be exposed in such a scenario,
though it is a rare case.

--Kurt

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

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Feb 18, 2021 at 7:09 AM Ken O&#39=
;Driscoll &lt;ken=3D<a href=3D"mailto:40wemonitoremail.com@dmarc.ietf.org">=
40wemonitoremail.com@dmarc.ietf.org</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"><br>. . . I&#=
39;d propose something like the below, which I think gets across what we al=
l want to say.<br>
<br>
=3D=3D=3D=3D=3D=3D=3D<br>
Aggregate feedback reports contain anonymized data relating to messages pur=
portedly originating from the Domain Owner. The data does not contain any i=
dentifying characteristics about individual senders or receivers. No person=
al information such as individual email addresses, IP addresses of individu=
als, or the content of any messages, is included in reports.<br>
<br>
Mail Receivers should have no concerns in sending reports as they do not co=
ntain personal information. In all cases, the data within the reports relat=
es to the authentication information provided by mail servers sending messa=
ges on behalf of the Domain Owner. This information is necessary to assist =
Domain Owners in implementing and maintaining DMARC.<br>
<br>
Domain Owners should have no concerns in receiving reports as they do not c=
ontain personal information. The reports only contain aggregated anonymized=
 data related to the authentication details of messages claiming to origina=
te from their domain. This information is essential for the proper implemen=
tation and operation of DMARC. Domain Owners who are unable to receive repo=
rts for organizational reasons, can choose to exclusively direct the report=
s to an external processor.<br>
=3D=3D=3D=3D=3D=3D=3D<br></blockquote><div><br></div><div>With a s/anonymiz=
ed/aggregated/g change, this seems like reasonable language. In technical t=
erms, there is no anonymization involved. The only other issue might be som=
e ambiguity in the intepretation of the term &quot;individual senders or re=
ceivers&quot;=C2=A0because the IP addresses of the MTAs involved in the ema=
il interchange are definitely in the report. As someone has pointed out ear=
lier in the thread, a compromised home computer which is able to send out o=
n port 25 would indeed be exposed in such a scenario, though it is a rare c=
ase.</div><div><br></div><div>--Kurt</div></div></div>

--0000000000004f222105bb9f2c3b--


From nobody Thu Feb 18 09:09:13 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 D03ED3A1471 for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 09:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level: 
X-Spam-Status: No, score=-4.399 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.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 Y72EI9jpM0pt for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 09:09: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 3577B3A1460 for <dmarc@ietf.org>; Thu, 18 Feb 2021 09:09:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1613668146; bh=Vfyt9bu3WxrloMDTbbI71+YnGl2AVOjYDMl6zgPQ/RE=; l=2268; h=To:Cc:References:From:Date:In-Reply-To; b=AEqA9zChWZ+hsqY3R5sTh5w6fofueyWvg/4m1E81HZx9AFos1+uZNCyLR+Zkg+Fy1 GgnpaFbiug7dARqi8K29+0q3S0ts5MAC+7bbb+wOjShwaA2gpvD/aDWoYDN3mS+D/d QdrGkdjAx0RajGQOitgtIlFC92Q0KYD1D2J5i2uIcqvcl8yT1AYaQedPf/Qj8
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Original-Cc: "dmarc@ietf.org" <dmarc@ietf.org>, John Levine <johnl@taugh.com>
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 00000000005DC042.00000000602E9F32.00003CD7; Thu, 18 Feb 2021 18:09:06 +0100
To: "Kurt Andersen (b)" <kboth@drkurt.com>, Ken O'Driscoll <ken=40wemonitoremail.com@dmarc.ietf.org>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, John Levine <johnl@taugh.com>
References: <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <20210218024606.4727B6E23874@ary.qy> <VI1PR01MB70530199B815F3216D64E9A2C7859@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <CABuGu1pC_rh2vDUuNsHF0dLgKGiR3nve8YE1P9trPM-wUi+EfA@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <d72d002a-be58-5f66-eddd-4e0bf6806dcf@tana.it>
Date: Thu, 18 Feb 2021 18:09:06 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <CABuGu1pC_rh2vDUuNsHF0dLgKGiR3nve8YE1P9trPM-wUi+EfA@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/AfDftiUKYdU4O21HIan_ifzb48k>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 18 Feb 2021 17:09:12 -0000

On Thu 18/Feb/2021 17:52:55 +0100 Kurt Andersen (b) wrote:
> On Thu, Feb 18, 2021 at 7:09 AM Ken O'Driscoll <ken=
> 40wemonitoremail.com@dmarc.ietf.org> wrote:
> 
>>
>> . . . I'd propose something like the below, which I think gets across what
>> we all want to say.
>>
>> =======
>> Aggregate feedback reports contain anonymized data relating to messages
>> purportedly originating from the Domain Owner. The data does not contain
>> any identifying characteristics about individual senders or receivers. No
>> personal information such as individual email addresses, IP addresses of
>> individuals, or the content of any messages, is included in reports.
>>
>> Mail Receivers should have no concerns in sending reports as they do not
>> contain personal information. In all cases, the data within the reports
>> relates to the authentication information provided by mail servers sending
>> messages on behalf of the Domain Owner. This information is necessary to
>> assist Domain Owners in implementing and maintaining DMARC.
>>
>> Domain Owners should have no concerns in receiving reports as they do not
>> contain personal information. The reports only contain aggregated
>> anonymized data related to the authentication details of messages claiming
>> to originate from their domain. This information is essential for the
>> proper implementation and operation of DMARC. Domain Owners who are unable
>> to receive reports for organizational reasons, can choose to exclusively
>> direct the reports to an external processor.
>> =======
>>
> 
> With a s/anonymized/aggregated/g change, this seems like reasonable
> language. In technical terms, there is no anonymization involved. The only
> other issue might be some ambiguity in the intepretation of the term
> "individual senders or receivers" because the IP addresses of the MTAs
> involved in the email interchange are definitely in the report. As someone
> has pointed out earlier in the thread, a compromised home computer which is
> able to send out on port 25 would indeed be exposed in such a scenario,
> though it is a rare case.


I'd s/individual senders or receivers/individual users/.

Also s/authentication/domain-level authentication/.


Best
Ale
-- 

















From nobody Thu Feb 18 09: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 DC82A3A1486 for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 09: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, 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 q3BfSnfK-aaX for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 09:10:50 -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 10ECF3A146D for <dmarc@ietf.org>; Thu, 18 Feb 2021 09:10:50 -0800 (PST)
Received: by mail-vs1-xe2e.google.com with SMTP id y123so1253975vsy.13 for <dmarc@ietf.org>; Thu, 18 Feb 2021 09: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=M21nSrq/TEqLOPvfbXXLlnOLUiYtngB+tYfW95UqrqQ=; b=f8iliBTSCNG2fuGL/TFyMNuBdHA9JLalYEDub/VpaU7tUW1ypHge3x5yg4Lv13/NO/ wiJQckBFcwsOjz5du/EP4QZY7YThxp2sltDT/wDIz9UrOt4dOC9zPtXsPlvKT3t5R+fe snd6vPcEObzKatM0rZ265gv9lpyBwZSTeaG5UYgMWO/sdJk1jQNglf0gBuO6BxfVIkBQ DV2aGglVYOKP+hZsx2pextDdYfw/b5Db4tRgC6Sc74fxInyDeUevrJUB0o4kPJ+2jidH 62KpNrZNBGoWoc/7LLzzJkpw11g1L+BVdT/HG7l9B0AXN6+ukxLEkYTFo0hHNo5xJz1I 5VDw==
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=M21nSrq/TEqLOPvfbXXLlnOLUiYtngB+tYfW95UqrqQ=; b=aLPTM6B6MJY9+nOafua1NX35TKAipNsL0aTZFALCnp1BUwGS6fP2zgPytxQbPeYke8 c9FrILNdeYjPl3+n7rSUzVQk7F1Of7m/5EvGkX9pWQ0aj81XtG4w6utFy38cxhKoFvKw m+Ww2mj+5gy0QgfQopvudjT1YP1KkjuFPc9O4YQJnB5SIKbHVua9IEjS+LjQU6JkLuiY Oa0TSyNK1bUnJsp56ZlkTD9x1BvCoJZLZA88Q7vZBbZGhRq9HVBGAIf8JhNQGAKNZpkf DebdfKE2chdPMzeJSu43gjKPfY5x4RvFi1c6OqDQxx2zWlTMJpTGjuQvTsFsVCKFQiFA r3sQ==
X-Gm-Message-State: AOAM531gkw9tslk4yypVOK3y/p6JwoRLlsQzYg4lvboySsNwFyL1ZLT4 s514fVZJxUDzz7GwH3sGnhWTQt+tyQWmOM/Qq2c=
X-Google-Smtp-Source: ABdhPJy5+bYO/zXBr4y1pD9WWeR72PkNMj5mbH24vYoM8ZAvMKJhAA7s/0TsyV2Hd5sYK5m1qTiNDO3pit8FBeBIYfg=
X-Received: by 2002:a67:441:: with SMTP id 62mr1243129vse.0.1613668248811; Thu, 18 Feb 2021 09:10:48 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com>
In-Reply-To: <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 18 Feb 2021 09:10:37 -0800
Message-ID: <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c1811905bb9f6a89"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/vcRsV5yICIBafxIVuSkIv0FKeZg>
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: Thu, 18 Feb 2021 17:10:52 -0000

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

Circling back to this:

On Fri, Jan 29, 2021 at 12:56 PM Dave Crocker <dcrocker@gmail.com> wrote:

> 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> 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.
>
I'm struggling to understand the concern here.  I think we all know what it
means to register a domain, and that the namespace is arranged as a tree,
and that trees are made up of nodes, and that some nodes are above the cut
where registrations take place while the rest are below.  What other
meaning might someone in this space infer from this text?

Maybe this is better, just for the sake of having something else to look at?

   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 nodes in the DNS tree that are either
   reserved as points below which new domain name registrations are made, or are
   the results of those registrations; it does not permit a node 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.

Apart from that, I'm at a loss to understand what's confusing.  I'm not
convinced that "registrations" in the context of domain names is unclear to
a reader familiar with this space.

-MSK

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

<div dir=3D"ltr"><div dir=3D"ltr">Circling back to this:<br></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 29,=
 2021 at 12:56 PM Dave Crocker &lt;<a href=3D"mailto:dcrocker@gmail.com">dc=
rocker@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);pa=
dding-left:1ex">
 =20
   =20
 =20
  <div>
    <div>On 1/29/2021 12:15 PM, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr">On Fri, Jan 29, 2021 at 7:51 AM Dave Crocker &lt;<=
a href=3D"mailto:dcrocker@gmail.com" target=3D"_blank">dcrocker@gmail.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> </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
            registrations.</div>
          <div> <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>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>
          </blockquote>
          <div>&quot;exist&quot;?</div>
          <div>&quot;take place&quot;?</div>
          <div>&quot;are made&quot;?</div>
          <div>&quot;are done&quot;?<br>
          </div>
        </div>
      </div>
    </blockquote>
    <p>The issue wasn&#39;t synonyms but semantics.=C2=A0 &#39;registration=
s
      occurred&#39; has no obvious DMARC meaning.</p>
    <p>unless, perhaps, the meaning is &#39;domain names exist&#39;, but th=
at
      still doesn&#39;t explain the contrast being drawn.</p></div></blockq=
uote><div>I&#39;m struggling to understand the concern here.=C2=A0 I think =
we all know what it means to register a domain, and that the namespace is a=
rranged as a tree, and that trees are made up of nodes, and that some nodes=
 are above the cut where registrations take place while the rest are below.=
=C2=A0 What other meaning might someone in this space infer from this text?=
</div><div><br></div><div>Maybe this is better, just for the sake of having=
 something else to look at?</div><div><br></div><div><pre>   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 nodes in the DNS tree that are eith=
er<br>   reserved as points below which new domain name registrations are m=
ade, or are<br>   the results of those registrations; it does not permit a =
node 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.
</pre></div><div> Apart from that, I&#39;m at a loss to understand what&#39=
;s confusing.=C2=A0 I&#39;m not convinced that &quot;registrations&quot; in=
 the context of domain names is unclear to a reader familiar with this spac=
e.</div><div><br></div><div>-MSK<br></div></div></div>

--000000000000c1811905bb9f6a89--


From nobody Thu Feb 18 09:55:42 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 753203A14F5; Thu, 18 Feb 2021 09:55:40 -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.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dmarc@ietf.org
Message-ID: <161367094042.3548.7948696086356652539@ietfa.amsl.com>
Date: Thu, 18 Feb 2021 09:55:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/-opRfBRNqDs0r0nCX5UuvOuqn1Q>
Subject: [dmarc-ietf] I-D Action: draft-ietf-dmarc-failure-reporting-01.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: Thu, 18 Feb 2021 17:55:41 -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           : Domain-based Message Authentication, Reporting, and Conformance (DMARC) Failure Reporting
        Authors         : Steven M Jones
                          Alessandro Vesely
	Filename        : draft-ietf-dmarc-failure-reporting-01.txt
	Pages           : 11
	Date            : 2021-02-18

Abstract:
   Domain-based Message Authentication, Reporting, and Conformance
   (DMARC) is a scalable mechanism by which a domain owner can request
   feedback about email messages using their domain in the From: address
   field.  This document describes "failure reports," or "failed message
   reports," which provide details about individual messages that failed
   to authenticate according to the DMARC mechanism.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmarc-failure-reporting/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-dmarc-failure-reporting-01.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmarc-failure-reporting-01


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 Thu Feb 18 12:39: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 AE2C73A1833 for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 12:39:52 -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 hV_4n_4USq-o for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 12:39: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 C8BBD3A1835 for <dmarc@ietf.org>; Thu, 18 Feb 2021 12:39:50 -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 11IKZoIS002082; Thu, 18 Feb 2021 15:39:49 -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 : content-transfer-encoding : mime-version; s=20190412; bh=1TKaO/x5vDSA6bEj9//i7Q44rfdWX2Q8z7j6zatHF6U=; b=SVPSl2UGNtuVIHCo8atfDU5dUMvepd7iHPVLUvXb8U9kiD7+lHvSGSz8nl3hTO3Uvdot x/AE6nbvSGKZD9lM5P3IXp/cFwfRsk3HmCSe604fSbDDKp3D3aWd5MxXAv9b2A1yW+7c 23WswVbSu4n7mElU2DP1pMmercvUJtaiWEUGY2dOhcN0EEHwSGAcKcLVGVrjYlzvxcui 1vx27Z17Cz5HFx7iGt+cVWOFwmxAKk1vpjCjoJGApqDIR6TrTP6fHInXiF7Ydqum2d8s NQ3stBuicAn2d9WGY7s4O7J9fkeMRcRWuhkKU8Ve3zdRrLD74i47BymBAPNxkLgQPEVy Kw== 
Received: from pacdcex50.cable.comcast.com (dlppfpt-wc-1p.slb.comcast.com [96.99.226.136]) by mx0a-00143702.pphosted.com with ESMTP id 36payq4wtq-9 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 18 Feb 2021 15:39:49 -0500
Received: from PACDCEX56.cable.comcast.com (24.40.2.155) by PACDCEX50.cable.comcast.com (24.40.2.149) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 18 Feb 2021 15:39:46 -0500
Received: from PACDCEXEDGE01.cable.comcast.com (76.96.78.71) by PACDCEX56.cable.comcast.com (24.40.2.155) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 18 Feb 2021 15:39:46 -0500
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (104.47.59.169) by webmail.comcast.com (76.96.78.71) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 18 Feb 2021 15:39:33 -0500
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by MN2PR11MB4255.namprd11.prod.outlook.com (2603:10b6:208:18a::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.25; Thu, 18 Feb 2021 20:39:20 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::2495:cfaf:88ca:6b2d]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::2495:cfaf:88ca:6b2d%7]) with mapi id 15.20.3868.027; Thu, 18 Feb 2021 20:39:20 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: Alessandro Vesely <vesely@tana.it>, "Kurt Andersen (b)" <kboth@drkurt.com>, Ken O'Driscoll <ken=40wemonitoremail.com@dmarc.ietf.org>
CC: "dmarc@ietf.org" <dmarc@ietf.org>, John Levine <johnl@taugh.com>
Thread-Topic: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
Thread-Index: AdcBfLdYcAd1ycC0TvWJKBD11cOyegCIhNKAAG9eXXAABJQJQAAMZ9qAABjkaCAABK7ggAAAkLEAAAdCehA=
Date: Thu, 18 Feb 2021 20:39:19 +0000
Message-ID: <MN2PR11MB4351A46D0D40ED33AA0FB911F7859@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <20210218024606.4727B6E23874@ary.qy> <VI1PR01MB70530199B815F3216D64E9A2C7859@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <CABuGu1pC_rh2vDUuNsHF0dLgKGiR3nve8YE1P9trPM-wUi+EfA@mail.gmail.com> <d72d002a-be58-5f66-eddd-4e0bf6806dcf@tana.it>
In-Reply-To: <d72d002a-be58-5f66-eddd-4e0bf6806dcf@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:3ce7:7bea:77c3:5c17]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a0c5240c-8c9b-4635-ace0-08d8d44d4487
x-ms-traffictypediagnostic: MN2PR11MB4255:
x-microsoft-antispam-prvs: <MN2PR11MB4255445B330C32DA06960C15F7859@MN2PR11MB4255.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:3631;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: MUd3Sd6GlnLtnBP0EUXSLWaqwp5qUX5ZXGoW04ESUf3BQBJ1Ecb/lVUxE6ekpq6CJ7l1RXXR45MSTnbFBnAFIRkUh4qP5UJQ1DC+oSa+YA8LDtgSks4GAx7IENt825R1ack2GzfyHBYsOYeveTOzCV8ivnhz53SyYL1mNGrO+fHUZHjDtCXIwdDxcxuLy3BoXv70r//6FDVBLjZRgUO71zjoAgjC7JILV/SGXM+6nCZPn1bkvxLIrPHzcrj6YBBuiD/amqNLkPATimJpeh/jjVhOaaQqhBlI70cXTtzVhEBzG3HsQO0fiIJfzkGJ9ACeYNNEig/I9MY9krW+5tUq5mohEoSXSFUKjAMzTNgl/yEyIK0CrNDSzNPK/IinJ1ytAcDxkK0sL0vzrEdQbv7BIK06kBo7lQ0uFIG7P/WKnK2amK6fjD95EvpqMykarj5KyQgSZXYmy4NURJq8WYd+HVJzmYvqETTVtd4PMYgrXyMOYWhk4FUtwkfLq0IJ/+umTbsPIvAYRsckDmoWXlgztRlVSwpfz5/84i+S2+M1Sicff/mdwwX/H4fknn/HiT4ognW+rCjlVDvYPR0oVbpYSG8GHXwfmdHhjBlx97maDCU=
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)(136003)(346002)(396003)(39860400002)(33656002)(8936002)(966005)(5660300002)(66446008)(54906003)(110136005)(7696005)(186003)(8676002)(66556008)(76116006)(66946007)(55016002)(83380400001)(52536014)(2906002)(9686003)(66476007)(64756008)(316002)(6506007)(86362001)(71200400001)(4326008)(53546011)(478600001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?AmnGQv9pk1dPWAXvU5KOq2uVMoh0+cSa83FE5aWXIrejwRIW7dPl5YUUm6l2?= =?us-ascii?Q?A66nkF0MZyNH8agzOnko5wIrPu/0vvUUfIAcqmZEXiy/CTyD3nwxKwxhD/DI?= =?us-ascii?Q?qTDZ+147sfEltbWAvockTpcACZAIRehaJVEdIJxptKQU+Jjq3NtBNMJqYt3E?= =?us-ascii?Q?YwZIFkRj7JRox03YZjBa8oUB9yZ3SsYoYLZLMeWmyM0W4qI2UDeJO2pZ6yDD?= =?us-ascii?Q?00Uc/D5MOSDyCIdtonQ4oDxBM3YbWVDZM41eIej6WuedI4wqMCiSByuI6bMY?= =?us-ascii?Q?AOgzJuihm7J7lbulHAsKeFCBjJd3fFJ22dCWaUUJ+zGO6c4hMyHQ6DwIByQ/?= =?us-ascii?Q?/dXBNlXKRhmbEWAGpAiVZFMRbEqSti54gDsn4PAM/NqRQxxN5ZWjVcn164w0?= =?us-ascii?Q?pBxHnEwcZBg1RBILU+CwvTAzDw9RkKfOvWGAMP/j++hZP9IOzJusZUvjCxPF?= =?us-ascii?Q?WXnkBkumUS40tfYIxm/NjNYIE6lSKsfAhABL+9Y2A1pEJWbYjeH8fVftHYsl?= =?us-ascii?Q?6rGRIYUxmVvav6Sw8+sw5SsjwUiUuIO0gxUc+XjrFpBcK9TndN863nc9469L?= =?us-ascii?Q?518arsnnyUP5cl5G3xcgl7zyNAFItOxAs0J+I+5WDoBxApygC3zWlwLqDPcU?= =?us-ascii?Q?8hSUWthgVvIhgxZEY1rGrNLxe8p04dRHcV+pkFDfhXzvB/GmoOHKPWONgCqT?= =?us-ascii?Q?9K4BBMm/ywH861Ka1g7ag6XhEmEHh1bOekC0F5VTo7IntNAMf04os67Safxl?= =?us-ascii?Q?EsHyd2WMvZABjV8IL37xFeLGD+jn2A7EwD2kNyRtgipRm1tTOeSaNPbVZOVM?= =?us-ascii?Q?UZxJdNbHhK4y+oqNpPfRStCNz5Jb4XAO3rsYono/o9nmiPnASxbytJL8+UPD?= =?us-ascii?Q?4zZvzXSxjqSLFAtThnutMczGIJTCAwTrFoW2BNMHef03JBzFphHVxqgv04+7?= =?us-ascii?Q?5AhzwDrYUm9nJLL6vUis1eN7VGObEpwQ6bLcjmbKfaKvHz3RjffHIeBu9fnc?= =?us-ascii?Q?8bBS+MeHLRsv6ong05kRgLCx8Jd0EEEYMIdpuLXhynAKWG7M7gi6xKnGBr6c?= =?us-ascii?Q?5Fyu0L7Um6q2yY2HLn9NzrLAQC0qMhuaFkEKIYjspQ9XGHM6ub0oM4R53cda?= =?us-ascii?Q?tRPaQR1bKNtbwyDO02DlojIxP5IGvZwhmto5Ps1/KeKx+IfIIhTsh+bypo1F?= =?us-ascii?Q?wa8PEO4TtNSOGQjrxCJCThpv2LMi/nTD0lckpacqwxtKWjWBN8KG7tLnU/0S?= =?us-ascii?Q?PV43bYryIb4oyfCHWSnKQbBttZ9vL+joTa0K2as6/1OFgotEq4AvZ3mPxJdu?= =?us-ascii?Q?y6vPqWXw9U+HcIJggJDa1IlXGiMUJwdVmwNwwTO3Op0rSt4W2E22xJtQ6ZFO?= =?us-ascii?Q?GZ7zZnI=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kXz2R7OWle1WxPyWnRWHv+SLlSEbxlxbFy1JvQmElpQot2bZuHBHANNEGpCFJcGNzBefpH7aFQBLlgrSdzjBuDTsU3ahyTpsQQHlU+M9GER+uOnQPEZqLhQuftpBMMekrYnMbYxBFvADdogcYMmryDdmszEqtHRho8gvixjAZysrfIohalXnw1Hlgo7Jrdk5csyUGKKatZ2ojYG73D1SJ5cVbUBAAf9sd6A/+GPHCe70LZERRXFtHY/4p8iUe9cevEH4RyEYTxe+snUzPMV+u+laCKMJqGwSzmwO9jtRl0t7rAz3VgmEFe2eB3hk30Vbmbx/W9s2GtuEdVCYIp957Q==
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=z01ragKalKm6uZZJrFxbuPGsXSVmZOeBill1+wXRIvU=; b=mfo1Oznq4iWEeatwncKdH/3zJip6A6cMkQxDvbB59y+cMTkZWxpbQZswlcLL2WvLg19FAhsqG+ILc4ESEQB7iXUC9b2KkC6OtaCi7cWXMVU5EzKMGtXstFWa+YbqD9gvIATEKCAxdhMaibjjwbRl3sJoe5E2h3LLbOfa7t+15vmQ9V4pmg3IoO4uudjHlPK5pHW8BGc0pEFQBO31Zn7unvCzUM3sky20m5Iak9WlyLtfqxmezZGerGxf7tgVeMdfwdEdeb/mXns4P46tTpU36NcWZynF7Wx7E9qcmr5sP8qoUCGirBs0jR4JimXmUzdpcVkXm5Ky6wUiN1mByeEakw==
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: a0c5240c-8c9b-4635-ace0-08d8d44d4487
x-ms-exchange-crosstenant-originalarrivaltime: 18 Feb 2021 20:39:19.8588 (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: FI2dgmxBPESIa4RhJdSZ4cDBdr8QEkSU+6SbpWb33isD5keu1FlHm1J/ZJnD5N5bzZmGXp8ZiSt6D7q6spo0H0R6Ch4ILnjfLQXeWLP/810=
x-ms-exchange-transport-crosstenantheadersstamped: MN2PR11MB4255
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.369, 18.0.761 definitions=2021-02-18_09:2021-02-18, 2021-02-18 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/jsC7wAoV0ssUNqpyb8IxZWpWdGY>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 18 Feb 2021 20:39:53 -0000

Aggregated comments:

--------------------------
Aggregate feedback reports contain aggregated data relating to messages pur=
portedly originating from the Domain Owner. The data does not contain any i=
dentifying characteristics about individual users. No personal information =
such as individual email addresses, IP addresses of individuals, or the con=
tent of any messages, is included in reports.

Mail Receivers should have no concerns in sending reports as they do not co=
ntain personal information. In all cases, the data within the reports relat=
es to the domain-level authentication information provided by mail servers =
sending messages on behalf of the Domain Owner. This information is necessa=
ry to assist Domain Owners in implementing and maintaining DMARC.

Domain Owners should have no concerns in receiving reports as they do not c=
ontain personal information. The reports only contain aggregated data relat=
ed to the domain-level authentication details of messages claiming to origi=
nate from their domain. This information is essential for the proper implem=
entation and operation of DMARC. Domain Owners who are unable to receive re=
ports for organizational reasons, can choose to exclusively direct the repo=
rts to an external processor.
--------------------------

Agreeable?

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

> -----Original Message-----
> From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Alessandro Vesely
> Sent: Thursday, February 18, 2021 12:09 PM
> To: Kurt Andersen (b) <kboth@drkurt.com>; Ken O'Driscoll
> <ken=3D40wemonitoremail.com@dmarc.ietf.org>
> Cc: dmarc@ietf.org; John Levine <johnl@taugh.com>
> Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
>
> On Thu 18/Feb/2021 17:52:55 +0100 Kurt Andersen (b) wrote:
> > On Thu, Feb 18, 2021 at 7:09 AM Ken O'Driscoll <ken=3D
> > 40wemonitoremail.com@dmarc.ietf.org> wrote:
> >
> >>
> >> . . . I'd propose something like the below, which I think gets across
> >> what we all want to say.
> >>
> >> =3D=3D=3D=3D=3D=3D=3D
> >> Aggregate feedback reports contain anonymized data relating to
> >> messages purportedly originating from the Domain Owner. The data does
> >> not contain any identifying characteristics about individual senders
> >> or receivers. No personal information such as individual email
> >> addresses, IP addresses of individuals, or the content of any messages=
, is
> included in reports.
> >>
> >> Mail Receivers should have no concerns in sending reports as they do
> >> not contain personal information. In all cases, the data within the
> >> reports relates to the authentication information provided by mail
> >> servers sending messages on behalf of the Domain Owner. This
> >> information is necessary to assist Domain Owners in implementing and
> maintaining DMARC.
> >>
> >> Domain Owners should have no concerns in receiving reports as they do
> >> not contain personal information. The reports only contain aggregated
> >> anonymized data related to the authentication details of messages
> >> claiming to originate from their domain. This information is
> >> essential for the proper implementation and operation of DMARC.
> >> Domain Owners who are unable to receive reports for organizational
> >> reasons, can choose to exclusively direct the reports to an external
> processor.
> >> =3D=3D=3D=3D=3D=3D=3D
> >>
> >
> > With a s/anonymized/aggregated/g change, this seems like reasonable
> > language. In technical terms, there is no anonymization involved. The
> > only other issue might be some ambiguity in the intepretation of the
> > term "individual senders or receivers" because the IP addresses of the
> > MTAs involved in the email interchange are definitely in the report.
> > As someone has pointed out earlier in the thread, a compromised home
> > computer which is able to send out on port 25 would indeed be exposed
> > in such a scenario, though it is a rare case.
>
>
> I'd s/individual senders or receivers/individual users/.
>
> Also s/authentication/domain-level authentication/.
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/dmarc__=
;!
> !CQl3mcHX2A!QnQcMsS_KTWtqiiZuaapRUWc3xT1P55tS453rXWzE_lJElYm2DKE3
> yW2lwFWuJZIJs-sye0H4w$


From nobody Thu Feb 18 13:07:49 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 A3C563A187B for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 13:07: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 jJVg2OKKAPLe for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 13:07:45 -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 074E43A18DA for <dmarc@ietf.org>; Thu, 18 Feb 2021 13:07:06 -0800 (PST)
Received: by mail-qt1-x832.google.com with SMTP id z32so2468327qtd.8 for <dmarc@ietf.org>; Thu, 18 Feb 2021 13:07: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=0TSt+c8IYTrfT3XJWLKQcPStOhj7wX+kO2EgQs/sV7k=; b=CL73q43i/+v9lOa7y2B3cSj8yuNneHYGqk86TdMOW63gzJ+J+wvnTWp8uDBNoBZqVJ v9Sl6Dkl/azTMlen2GEP9J4aPDIBpB0LBYufEytVif5eRBYagF/5piJz4vGsRFldyMGu NS0b+wETOjtgX9Io3cHY99TmVQEpbSj9wvI5tO0g/+WSUTXULohdxgn9GBAyAK5yPwXl VzUfCv5NSKNrydF1w9CFfm25kZDarGniE1J17w+gTR0m0JWvN4XV7YFHRwyZRAkcafTm j0vpI3wy5Y+J5+aw2cNoUig5vePb6ykL/e6ZMCRWbYe70jeR7qKN+xzuZGvVZl/kSEwk c41Q==
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=0TSt+c8IYTrfT3XJWLKQcPStOhj7wX+kO2EgQs/sV7k=; b=o1QV8X6ohbscoMIPeBUtiQcsYAwED5IQ74d4GxlifUeTzKYLbNDuB4IRLm7PbWjJ/F 2wPWt0Vk8RA+q+sVmwxMPgMAdpxJOqmYRWBy3Itx+Y13hiOPps1b9wGpb7dj59srGtKI zQG2pscEWfq/3QGdsrgmFpm97t6xArammAf2KNeli4uIjD7TEYuAuDzxQr+Q4+GyWYZD 1NNvUrtHA323x7/DKbsGVsJZdjL+dIzEjkIihOeI1lmC8EZXcBVs3WK7iWpqjuEaM7qw zEdcaoIs9y7lpJy4T3hksmFjn9DPSEHdVsKIyAz8+vwUNHqTajNiuIVsikDeKC0cUx7i ECFQ==
X-Gm-Message-State: AOAM5313anrEDUhV1chkPnwKfVu16YKrbQAhfoNLwVg2YepL/cQmpOrG vO4wB5RcWElffCUVzcFqXWV7zjwRnPqBlt04wKy7FXaP
X-Google-Smtp-Source: ABdhPJw/YBc21k3MKmSU3sUafUVOlBRmeFQLGysYOV3y7nFCJz8KRSkJyLVuZRnkwGUdC69IUHH0xiKWdTa5llQzzec=
X-Received: by 2002:ac8:70d5:: with SMTP id g21mr6110805qtp.267.1613682426001;  Thu, 18 Feb 2021 13:07:06 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR01MB70538541D7ADE18A555B05D6C7869@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <20210218024606.4727B6E23874@ary.qy> <VI1PR01MB70530199B815F3216D64E9A2C7859@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <CABuGu1pC_rh2vDUuNsHF0dLgKGiR3nve8YE1P9trPM-wUi+EfA@mail.gmail.com> <d72d002a-be58-5f66-eddd-4e0bf6806dcf@tana.it> <MN2PR11MB4351A46D0D40ED33AA0FB911F7859@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB4351A46D0D40ED33AA0FB911F7859@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Dotzero <dotzero@gmail.com>
Date: Thu, 18 Feb 2021 16:06:53 -0500
Message-ID: <CAJ4XoYe0AhvH3-srRYw1g3aipmR7da46M4ye20cD9JGf3oQ1+A@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="000000000000c83d0c05bba2b77d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/t9us-96TZTB7RuhlqRsy2wVYvq8>
Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 18 Feb 2021 21:07:48 -0000

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

I'm comfortable with the language.

Michael Hammer

On Thu, Feb 18, 2021 at 3:40 PM Brotman, Alex <Alex_Brotman=
40comcast.com@dmarc.ietf.org> wrote:

> Aggregated comments:
>
> --------------------------
> Aggregate feedback reports contain aggregated data relating to messages
> purportedly originating from the Domain Owner. The data does not contain
> any identifying characteristics about individual users. No personal
> information such as individual email addresses, IP addresses of
> individuals, or the content of any messages, is included in reports.
>
> Mail Receivers should have no concerns in sending reports as they do not
> contain personal information. In all cases, the data within the reports
> relates to the domain-level authentication information provided by mail
> servers sending messages on behalf of the Domain Owner. This information is
> necessary to assist Domain Owners in implementing and maintaining DMARC.
>
> Domain Owners should have no concerns in receiving reports as they do not
> contain personal information. The reports only contain aggregated data
> related to the domain-level authentication details of messages claiming to
> originate from their domain. This information is essential for the proper
> implementation and operation of DMARC. Domain Owners who are unable to
> receive reports for organizational reasons, can choose to exclusively
> direct the reports to an external processor.
> --------------------------
>
> Agreeable?
>
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
>
> > -----Original Message-----
> > From: dmarc <dmarc-bounces@ietf.org> On Behalf Of Alessandro Vesely
> > Sent: Thursday, February 18, 2021 12:09 PM
> > To: Kurt Andersen (b) <kboth@drkurt.com>; Ken O'Driscoll
> > <ken=40wemonitoremail.com@dmarc.ietf.org>
> > Cc: dmarc@ietf.org; John Levine <johnl@taugh.com>
> > Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns
> >
> > On Thu 18/Feb/2021 17:52:55 +0100 Kurt Andersen (b) wrote:
> > > On Thu, Feb 18, 2021 at 7:09 AM Ken O'Driscoll <ken=
> > > 40wemonitoremail.com@dmarc.ietf.org> wrote:
> > >
> > >>
> > >> . . . I'd propose something like the below, which I think gets across
> > >> what we all want to say.
> > >>
> > >> =======
> > >> Aggregate feedback reports contain anonymized data relating to
> > >> messages purportedly originating from the Domain Owner. The data does
> > >> not contain any identifying characteristics about individual senders
> > >> or receivers. No personal information such as individual email
> > >> addresses, IP addresses of individuals, or the content of any
> messages, is
> > included in reports.
> > >>
> > >> Mail Receivers should have no concerns in sending reports as they do
> > >> not contain personal information. In all cases, the data within the
> > >> reports relates to the authentication information provided by mail
> > >> servers sending messages on behalf of the Domain Owner. This
> > >> information is necessary to assist Domain Owners in implementing and
> > maintaining DMARC.
> > >>
> > >> Domain Owners should have no concerns in receiving reports as they do
> > >> not contain personal information. The reports only contain aggregated
> > >> anonymized data related to the authentication details of messages
> > >> claiming to originate from their domain. This information is
> > >> essential for the proper implementation and operation of DMARC.
> > >> Domain Owners who are unable to receive reports for organizational
> > >> reasons, can choose to exclusively direct the reports to an external
> > processor.
> > >> =======
> > >>
> > >
> > > With a s/anonymized/aggregated/g change, this seems like reasonable
> > > language. In technical terms, there is no anonymization involved. The
> > > only other issue might be some ambiguity in the intepretation of the
> > > term "individual senders or receivers" because the IP addresses of the
> > > MTAs involved in the email interchange are definitely in the report.
> > > As someone has pointed out earlier in the thread, a compromised home
> > > computer which is able to send out on port 25 would indeed be exposed
> > > in such a scenario, though it is a rare case.
> >
> >
> > I'd s/individual senders or receivers/individual users/.
> >
> > Also s/authentication/domain-level authentication/.
> >
> >
> > Best
> > Ale
> > --
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > dmarc mailing list
> > dmarc@ietf.org
> >
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/dmarc__
> ;!
> > !CQl3mcHX2A!QnQcMsS_KTWtqiiZuaapRUWc3xT1P55tS453rXWzE_lJElYm2DKE3
> > yW2lwFWuJZIJs-sye0H4w$
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr"><div>I&#39;m comfortable with the language.</div><div><br>=
</div><div>Michael Hammer<br></div></div><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Thu, Feb 18, 2021 at 3:40 PM Brotman,=
 Alex &lt;Alex_Brotman=3D<a href=3D"mailto:40comcast.com@dmarc.ietf.org">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">Aggregated comments:<br>
<br>
--------------------------<br>
Aggregate feedback reports contain aggregated data relating to messages pur=
portedly originating from the Domain Owner. The data does not contain any i=
dentifying characteristics about individual users. No personal information =
such as individual email addresses, IP addresses of individuals, or the con=
tent of any messages, is included in reports.<br>
<br>
Mail Receivers should have no concerns in sending reports as they do not co=
ntain personal information. In all cases, the data within the reports relat=
es to the domain-level authentication information provided by mail servers =
sending messages on behalf of the Domain Owner. This information is necessa=
ry to assist Domain Owners in implementing and maintaining DMARC.<br>
<br>
Domain Owners should have no concerns in receiving reports as they do not c=
ontain personal information. The reports only contain aggregated data relat=
ed to the domain-level authentication details of messages claiming to origi=
nate from their domain. This information is essential for the proper implem=
entation and operation of DMARC. Domain Owners who are unable to receive re=
ports for organizational reasons, can choose to exclusively direct the repo=
rts to an external processor.<br>
--------------------------<br>
<br>
Agreeable?<br>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: dmarc &lt;<a href=3D"mailto:dmarc-bounces@ietf.org" target=3D"_b=
lank">dmarc-bounces@ietf.org</a>&gt; On Behalf Of Alessandro Vesely<br>
&gt; Sent: Thursday, February 18, 2021 12:09 PM<br>
&gt; To: Kurt Andersen (b) &lt;<a href=3D"mailto:kboth@drkurt.com" target=
=3D"_blank">kboth@drkurt.com</a>&gt;; Ken O&#39;Driscoll<br>
&gt; &lt;ken=3D<a href=3D"mailto:40wemonitoremail.com@dmarc.ietf.org" targe=
t=3D"_blank">40wemonitoremail.com@dmarc.ietf.org</a>&gt;<br>
&gt; Cc: <a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org=
</a>; John Levine &lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_blank">=
johnl@taugh.com</a>&gt;<br>
&gt; Subject: Re: [dmarc-ietf] Ticket #64 - Contained Data PII Concerns<br>
&gt;<br>
&gt; On Thu 18/Feb/2021 17:52:55 +0100 Kurt Andersen (b) wrote:<br>
&gt; &gt; On Thu, Feb 18, 2021 at 7:09 AM Ken O&#39;Driscoll &lt;ken=3D<br>
&gt; &gt; <a href=3D"mailto:40wemonitoremail.com@dmarc.ietf.org" target=3D"=
_blank">40wemonitoremail.com@dmarc.ietf.org</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; . . . I&#39;d propose something like the below, which I think=
 gets across<br>
&gt; &gt;&gt; what we all want to say.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =3D=3D=3D=3D=3D=3D=3D<br>
&gt; &gt;&gt; Aggregate feedback reports contain anonymized data relating t=
o<br>
&gt; &gt;&gt; messages purportedly originating from the Domain Owner. The d=
ata does<br>
&gt; &gt;&gt; not contain any identifying characteristics about individual =
senders<br>
&gt; &gt;&gt; or receivers. No personal information such as individual emai=
l<br>
&gt; &gt;&gt; addresses, IP addresses of individuals, or the content of any=
 messages, is<br>
&gt; included in reports.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Mail Receivers should have no concerns in sending reports as =
they do<br>
&gt; &gt;&gt; not contain personal information. In all cases, the data with=
in the<br>
&gt; &gt;&gt; reports relates to the authentication information provided by=
 mail<br>
&gt; &gt;&gt; servers sending messages on behalf of the Domain Owner. This<=
br>
&gt; &gt;&gt; information is necessary to assist Domain Owners in implement=
ing and<br>
&gt; maintaining DMARC.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Domain Owners should have no concerns in receiving reports as=
 they do<br>
&gt; &gt;&gt; not contain personal information. The reports only contain ag=
gregated<br>
&gt; &gt;&gt; anonymized data related to the authentication details of mess=
ages<br>
&gt; &gt;&gt; claiming to originate from their domain. This information is<=
br>
&gt; &gt;&gt; essential for the proper implementation and operation of DMAR=
C.<br>
&gt; &gt;&gt; Domain Owners who are unable to receive reports for organizat=
ional<br>
&gt; &gt;&gt; reasons, can choose to exclusively direct the reports to an e=
xternal<br>
&gt; processor.<br>
&gt; &gt;&gt; =3D=3D=3D=3D=3D=3D=3D<br>
&gt; &gt;&gt;<br>
&gt; &gt;<br>
&gt; &gt; With a s/anonymized/aggregated/g change, this seems like reasonab=
le<br>
&gt; &gt; language. In technical terms, there is no anonymization involved.=
 The<br>
&gt; &gt; only other issue might be some ambiguity in the intepretation of =
the<br>
&gt; &gt; term &quot;individual senders or receivers&quot; because the IP a=
ddresses of the<br>
&gt; &gt; MTAs involved in the email interchange are definitely in the repo=
rt.<br>
&gt; &gt; As someone has pointed out earlier in the thread, a compromised h=
ome<br>
&gt; &gt; computer which is able to send out on port 25 would indeed be exp=
osed<br>
&gt; &gt; in such a scenario, though it is a rare case.<br>
&gt;<br>
&gt;<br>
&gt; I&#39;d s/individual senders or receivers/individual users/.<br>
&gt;<br>
&gt; Also s/authentication/domain-level authentication/.<br>
&gt;<br>
&gt;<br>
&gt; Best<br>
&gt; Ale<br>
&gt; --<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; dmarc mailing list<br>
&gt; <a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a>=
<br>
&gt; <a href=3D"https://urldefense.com/v3/__https://www.ietf.org/mailman/li=
stinfo/dmarc__" rel=3D"noreferrer" target=3D"_blank">https://urldefense.com=
/v3/__https://www.ietf.org/mailman/listinfo/dmarc__</a>;!<br>
&gt; !CQl3mcHX2A!QnQcMsS_KTWtqiiZuaapRUWc3xT1P55tS453rXWzE_lJElYm2DKE3<br>
&gt; yW2lwFWuJZIJs-sye0H4w$<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>

--000000000000c83d0c05bba2b77d--


From nobody Fri Feb 19 15:02:08 2021
Return-Path: <barryleiba.mailing.lists@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 A529F3A0CEE for <dmarc@ietfa.amsl.com>; Fri, 19 Feb 2021 15:02:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level: 
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ehnwgxrQfc3o for <dmarc@ietfa.amsl.com>; Fri, 19 Feb 2021 15:02:05 -0800 (PST)
Received: from mail-ej1-f51.google.com (mail-ej1-f51.google.com [209.85.218.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 3DD5F3A0CEB for <dmarc@ietf.org>; Fri, 19 Feb 2021 15:02:05 -0800 (PST)
Received: by mail-ej1-f51.google.com with SMTP id gg8so5249135ejb.13 for <dmarc@ietf.org>; Fri, 19 Feb 2021 15:02:05 -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=7ehtNC3R9CqzK+JZ1K6z1DfII1s6X4ihVwUc+nnO/qM=; b=LwTNO40BEOV3jLCm8AYg++DTNwF525XC9ovnZUimsrM93D0i8yPomML+3QVQpoXKMt eHY6aBjC3FX4bMHwnh7o3QRSTGohKteq8MmcfkkDwHY+13VzjLKulCWcAKSlEqSIx5bM LLNa15TH6I7Dt7MqgrEoXQrvWmtL7wzRMnA1p7qtlCSEpQ/w8Mq/IGqD/3Mjt0v3vwGi AXX6UHdcuCwfyWqp3G3Mc33htKV3KwiE+aek17b+ypx8cYehK4M6xplmVOI+wj5sVta+ TP9nkVDRHMJjzlBXbdfZG2OjV1zo+Bsjujlv3QfqRYNlwJdBG5qW92goLDG3A8ij2/lj Pv9A==
X-Gm-Message-State: AOAM533ax+4U/EvN9BC2AlN8lD36zhvZmRTbq7qBHdZGhju9OwzU5MBm E51O+tk1SvzJgxCHer6xAmR7R8tXWQ0L83bnHlI=
X-Google-Smtp-Source: ABdhPJybFyBHgjYaJUXxuCWSX4y5QNE0EpT0KyCK9atGIPFRFmyXCHN77vjJqtsWyGOZ1T4/7k3BoJ8glHVwQi8CPKc=
X-Received: by 2002:a17:906:2dd8:: with SMTP id h24mr10482103eji.96.1613775723665;  Fri, 19 Feb 2021 15:02:03 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com>
In-Reply-To: <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 19 Feb 2021 18:01:52 -0500
Message-ID: <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/vvmqENx2N_vpIYE4By9J4SrxZ00>
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, 19 Feb 2021 23:02:07 -0000

I agree that the abstract is unclear.  This makes no sense to me:

   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.

I don't understand the distinction that it's trying to make between
the two possibilities.
I also don't see the antecedent to "these domains" in the final
sentence of that paragraph.

Beyond that:
> I'm at a loss to understand what's confusing.  I'm not convinced that "registrations" in the
> context of domain names is unclear to a reader familiar with this space.

I am absolutely convinced that it is.  Think of people in M3AAWG, for
whom this is very relevant.  Many of them don't know much about
registries, registrars, and such, and in general, the average reader
won't understand the difference, from a "registration" standpoint,
between facebook.com (which is registered) and "www.facebook.com"
(which is not).  To the average reader, "facebook.com" is registered
under com, and "www.facebook.com" is registered under facebook.  And
the ones who don't think that will likely not understand why we can't
just talk about second-level domains and be done with it.

All that needs to be explained in the Introduction, not the Abstract.
But the Abstract has to explain enough for a reader to understand why
she might or might not be interested in getting the document and
reading it.  So it's going to be tough to word it carefully and to
keep it concise.  But we have to.

Stressing a point:
We very clearly do NOT want to explain this stuff in the Abstract.  In
fact, we don't have to explain much at all in the Abstract.  What we
have to do is make sure that the Abstract doesn't say stuff that's
*wrong* or confusing.  So let's try to find some fifth-grade language
that can suffice, and then make sure the Introduction has the right
words to make it clear to people who know how to do email, but who
don't already understand the issues involved here.

Barry


From nobody Fri Feb 19 20:12:28 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 CEC1D3A111A for <dmarc@ietfa.amsl.com>; Fri, 19 Feb 2021 20:12: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, 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 oY4gWxFrwEPp for <dmarc@ietfa.amsl.com>; Fri, 19 Feb 2021 20:12:25 -0800 (PST)
Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (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 DEC293A1117 for <dmarc@ietf.org>; Fri, 19 Feb 2021 20:12:24 -0800 (PST)
Received: by mail-oi1-x22d.google.com with SMTP id v193so8138601oie.8 for <dmarc@ietf.org>; Fri, 19 Feb 2021 20:12:24 -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=4X0v5oxL/GzS74yoqiNLpND1RqCwBCu5Foq+nipLNyg=; b=fbJhRWvZTi1OUFoOXi/fnZC2QK3a6G7L6/2+EnlW34h5NBcFB8+6oC9ESYlsOLn16B hVeh2wta5YcuWZYuZ5QSJ4/cEO0ig6NC4p0DDwKA/Z3mfSkK/4HmyoIvxz2b1YGzU3+9 bFtDTq6ULmiMcxsXjimCNFgOwdqj0b9DptWUvVKKfrEAkk2HtTN3DJjqiR9t6ksDfgp0 W3nBtOk+i2GhtY3QtyOdhq3R0DyhfwLZJLAtvCIKo4JLnii90qre9jC60ZE56gvM9q6R MK7X5kmuKoh3JN2iIkypR9XUu69Yiy59T8+QDp5zTE5RAiq2Si1Z7QsPmE/2FEuI0QEY 8bdA==
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=4X0v5oxL/GzS74yoqiNLpND1RqCwBCu5Foq+nipLNyg=; b=MqmtRzeCvwExi9TerTTe1QY+faaQa5oVO0xwCQAreXl9lugnWSM6KGdLmLGMspGTAt tSpGDiRur1jH/UhlsLWwxEekq79nKZNMhurUa9yYY6PMCnx1T3gJF7Tuxmb5W23GVziJ np0TRx/7s00FlPtnz1NXIaR/SyrIIsssC5pW/a4b5eWXzjllTQnvHDrEgaFreEOsBcBA 4lgKj/Q0ZkjuMsFtpkRsTacMiKT5WsJpdnLIQkpXNi7VWj8DSPOPOcQIVehxdWI37DZn 8fmwLlI1Z7SRAaJ1ipcNoRvIEHNtSk4K8LX8mx5cd7kZvA/PPPFxOkoDmd8GZsdIniP4 mCDA==
X-Gm-Message-State: AOAM5306weaiLPvoZ9h2GOmyISnjTqhmAs24+e0QTbUO5uGwrb2HXrqb Stq3pRzdVYqjEwcX2+9jj6Ks6UpV4lT6VQ==
X-Google-Smtp-Source: ABdhPJyeLMxQ6UEltO6mg6nurgOuDg8xfVe0Fh+EqV6cvEyPQnpQoF7INnkA6sRmAY9EU4xd/5dmJQ==
X-Received: by 2002:a54:4710:: with SMTP id k16mr4957917oik.67.1613794344109;  Fri, 19 Feb 2021 20:12:24 -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 r205sm2299262oib.15.2021.02.19.20.12.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 19 Feb 2021 20:12:23 -0800 (PST)
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: 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> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <e0a4c5eb-b047-67fe-8d76-e5beb921e5ae@gmail.com>
Date: Fri, 19 Feb 2021 20:12:22 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------698E0BE8366B8791B8C4BF25"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/cTqBIQnVJrRPgbGkrVtztSGcPDI>
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: Sat, 20 Feb 2021 04:12:27 -0000

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

On 2/18/2021 9:10 AM, Murray S. Kucherawy wrote:
> Circling back to this:
>
> On Fri, Jan 29, 2021 at 12:56 PM Dave Crocker <dcrocker@gmail.com 
> <mailto:dcrocker@gmail.com>> wrote:
>
>     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:
>>
>>>             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'.
>>
>>
>>     ...
>
> I'm struggling to understand the concern here.  I think we all know 
> what it means to register a domain, and that the namespace is arranged 
> as a tree,


With the intent of building upon Barry's note:

<pedanty> Specification writing requires clarity of who the reader is 
and empathy with the experience they will have reading the document.  
</pedantry>

In that context "we all know" is automatically a red flag for requiring 
overly insider expertise.

However in this case, I think the problem is worse.

Simply put, I believe the text does not say what it means to 
distinguish, even for an expert reader.  So, yes, we all know what you 
say we know.

But in fact that's not the point of the text.  It's trying to make some 
other point,  I assume it's about a type of boundary status, but it 
doesn't say that, nevermind saying it clearly and with enough technical 
and semantic detail to distinguish it.

The text you offer:

> Maybe this is better, just for the sake of having something else to 
> look at?
>
>     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 nodes in the DNS tree that are either
>     reserved as points below which new domain name registrations are made, or are
>     the results of those registrations; it does not permit a node 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.
moves closer to the mark, I think, but still doesn't get there.

EVERY node can have sub-nodes registered.  So it isn't clear what 
'reserved' means.

Worse is that:

    reserved as points below which new domain name registrations are made, or are
    the results of those registrations; it does not permit a node to have both of these
    properties simultaneously.

doesn't make sense to me.  I suspect an average technical reader will be 
at least as confused as I am.

d/


-- 

Dave Crocker
dcrocker@gmail.com
408.329.0791

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


--------------698E0BE8366B8791B8C4BF25
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 2/18/2021 9:10 AM, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">Circling back to this:<br>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Fri, Jan 29, 2021 at
            12:56 PM Dave Crocker &lt;<a
              href="mailto:dcrocker@gmail.com" moz-do-not-send="true">dcrocker@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>
              <div>On 1/29/2021 12:15 PM, Murray S. Kucherawy wrote:<br>
              </div>
              <blockquote type="cite">
                <div dir="ltr">
                  <div dir="ltr">On Fri, Jan 29, 2021 at 7:51 AM Dave
                    Crocker &lt;<a href="mailto:dcrocker@gmail.com"
                      target="_blank" 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>
                        <p> </p>
                        <blockquote type="cite">
                          <div>
                            <pre>   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>
                </div>
              </blockquote>
              <br>
            </div>
          </blockquote>
          <div>I'm struggling to understand the concern here.  I think
            we all know what it means to register a domain, and that the
            namespace is arranged as a tree, <br>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>With the intent of building upon Barry's note:</p>
    <p>&lt;pedanty&gt; Specification writing requires clarity of who the
      reader is and empathy with the experience they will have reading
      the document.  &lt;/pedantry&gt;</p>
    <p>In that context "we all know" is automatically a red flag for
      requiring overly insider expertise.<br>
    </p>
    <p> However in this case, I think the problem is worse. <br>
    </p>
    <p>Simply put, I believe the text does not say what it means to
      distinguish, even for an expert reader.  So, yes, we all know what
      you say we know.  <br>
    </p>
    <p>But in fact that's not the point of the text.  It's trying to
      make some other point,  I assume it's about a type of boundary
      status, but it doesn't say that, nevermind saying it clearly and
      with enough technical and semantic detail to distinguish it.</p>
    <p>The text you offer:</p>
    <p>
      <blockquote type="cite">
        <div>Maybe this is better, just for the sake of having something
          else to look at?</div>
        <div><br>
        </div>
        <div>
          <pre>   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 nodes in the DNS tree that are either
   reserved as points below which new domain name registrations are made, or are
   the results of those registrations; it does not permit a node 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.
</pre>
        </div>
      </blockquote>
      moves closer to the mark, I think, but still doesn't get there.</p>
    <p>EVERY node can have sub-nodes registered.  So it isn't clear what
      'reserved' means.</p>
    <p>Worse is that:</p>
    <pre>   reserved as points below which new domain name registrations are made, or are
   the results of those registrations; it does not permit a node to have both of these
   properties simultaneously.</pre>
    <div>doesn't make sense to me.  I suspect an average technical
      reader will be at least as confused as I am.</div>
    <br>
    <p>d/</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>

--------------698E0BE8366B8791B8C4BF25--


From nobody Sat Feb 20 06:01:36 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 37CD13A13EE for <dmarc@ietfa.amsl.com>; Sat, 20 Feb 2021 06:01:34 -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 kVZeVW2UjTY3 for <dmarc@ietfa.amsl.com>; Sat, 20 Feb 2021 06:01:32 -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 0342B3A13ED for <dmarc@ietf.org>; Sat, 20 Feb 2021 06:01:31 -0800 (PST)
Received: by mail-ua1-x931.google.com with SMTP id 62so2815240uar.13 for <dmarc@ietf.org>; Sat, 20 Feb 2021 06:01: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=oWvCzfvEOpfUDnZ2SYmkWpqDiimzZZ5vOZTYXu/9znQ=; b=l+ShgNW/Bau+0mzx6SN/DFZyBJbZnYPStQ//9z1RIZ392c9C3fWFO7S6cxz0XnoLH6 juPHReVlbndwLXEri5ygFUCaZiInglf/ZDRucNGciR3G1bvmExHOz2d8ztmmIR09DnW4 J0nkd2ksw3XSVbxKfvvaQub9U/J+S5ZlssY+iuusQxb+BuMp9hvFQZbMJnko3cRfcEXB XHGWDBMf/76E3ZonckG4jL93KGUtu0AGKp14G/AL3T8u+Rv3sPQUlvi1tAkX2m8yjhYy idaN/hvlAjkYt544lwu5L8A5ddixjbvja3vhTX3B9FmTAdhqp4HzYmvFn+Jo9K7wthE1 WReg==
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=oWvCzfvEOpfUDnZ2SYmkWpqDiimzZZ5vOZTYXu/9znQ=; b=g1qnbpoiCAFUYELArJAbG/fFL7eQogWiNZL69sjsl/B7ZrCm6peJh9pD5cyDCJeZF8 MpfBZOTsLxPSvVQErdoyLuBQPCyBDXKJ5/jvhJryvD29QryUAr/JRQ1U3CcFTBend4T7 GI0GIkf2aiIcU++T4uCOmhLAM5DX3OLCHjF0b31T6N3zF8NpBaoV6gvdNBGlZ/H9fR7h m3u7tehUnp2iMlk2o6NlfmqFmAN7htjEUU1Xr1N3R525zh6RAQmNUwzHc+G7UugDg6VD lfRfdFvfE4j4rgq1bDl9eFmBNOBfLe7jM5m7e9FDDAs4gx0MDWjDnGECH3GmDG6RFZhx UyhQ==
X-Gm-Message-State: AOAM53002YRjorKC8BhXUNbqgy1BwvJfw2CG1muq9cUNHsfIF/rRApPm wOl0kVfI0AB8Dw3rRzJUVI5hUSVXshBsqI8xnhI=
X-Google-Smtp-Source: ABdhPJyHHj46BgT/CqOYGHVKJaaY6U1kWf6D3kGw37JJ97PIzNkHVCgGIQidYxu49h3ylXwx0GTShgVl5A6B+Kmsvic=
X-Received: by 2002:ab0:3142:: with SMTP id e2mr10688852uam.110.1613829690459;  Sat, 20 Feb 2021 06:01:30 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <e0a4c5eb-b047-67fe-8d76-e5beb921e5ae@gmail.com>
In-Reply-To: <e0a4c5eb-b047-67fe-8d76-e5beb921e5ae@gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 20 Feb 2021 09:01:20 -0500
Message-ID: <CAH48ZfyZmBp91WjfnNb0W35m+5wFGBonG+hoe2RCK_3N3xd6Xw@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006d877a05bbc50165"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/lEGAP9PnWpTkwHkXifXJJBl__08>
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: Sat, 20 Feb 2021 14:01:34 -0000

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

This wording attempts to address the objections by giving
"registration" a specific context.    I also rewrote some of it for
readability.

- -

DMARC (Domain-based Message Authentication, Reporting, and
Conformance) is a scalable mechanism by which a mail-originating
organization can policies and preferences for validation and
disposition of messages which purport to come from owned domains,
as well as requesting feedback reporting about those message
validation and disposition actions.  These features allow the domain
owner to detect and inhibit domain name abuse.

DMARC is designed for use by domain owners.  Consequently it has no
applicability for domains that have no owner because the domain has
never been registered with an Internet Naming Authority.  Those
authorities have an interest in detecting and inhibiting abuse of the
name registration process, and message recipients have an interest
in preventing deception by entities using unregistered organization
domain names.

Domains at which Internet Naming Authorities perform registration 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.

On Fri, Feb 19, 2021 at 11:12 PM Dave Crocker <dcrocker@gmail.com> wrote:

> On 2/18/2021 9:10 AM, Murray S. Kucherawy wrote:
>
> Circling back to this:
>
> On Fri, Jan 29, 2021 at 12:56 PM Dave Crocker <dcrocker@gmail.com> wrote:
>
>> 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> wrote:
>>
>>>    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'.
>>>
>>
>> ...
>>
>>
>> I'm struggling to understand the concern here.  I think we all know what
> it means to register a domain, and that the namespace is arranged as a
> tree,
>
>
> With the intent of building upon Barry's note:
>
> <pedanty> Specification writing requires clarity of who the reader is and
> empathy with the experience they will have reading the document.
> </pedantry>
>
> In that context "we all know" is automatically a red flag for requiring
> overly insider expertise.
>
> However in this case, I think the problem is worse.
>
> Simply put, I believe the text does not say what it means to distinguish,
> even for an expert reader.  So, yes, we all know what you say we know.
>
> But in fact that's not the point of the text.  It's trying to make some
> other point,  I assume it's about a type of boundary status, but it doesn't
> say that, nevermind saying it clearly and with enough technical and
> semantic detail to distinguish it.
>
> The text you offer:
>
> Maybe this is better, just for the sake of having something else to look
> at?
>
>    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 nodes in the DNS tree that are either
>    reserved as points below which new domain name registrations are made, or are
>    the results of those registrations; it does not permit a node 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.
>
> moves closer to the mark, I think, but still doesn't get there.
>
> EVERY node can have sub-nodes registered.  So it isn't clear what
> 'reserved' means.
>
> Worse is that:
>
>    reserved as points below which new domain name registrations are made, or are
>    the results of those registrations; it does not permit a node to have both of these
>    properties simultaneously.
>
> doesn't make sense to me.  I suspect an average technical reader will be
> at least as confused as I am.
>
> d/
>
>
> --
>
> Dave Crockerdcrocker@gmail.com
> 408.329.0791
>
> Volunteer, Silicon Valley Chapter
> American Red Crossdave.crocker2@redcross.org
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr"><div>This wording attempts to address the objections by gi=
ving</div><div>&quot;registration&quot; a specific context.=C2=A0 =C2=A0 I =
also rewrote some of it for readability.</div><div><br></div><div>- -</div>=
<div><br></div>DMARC (Domain-based Message Authentication, Reporting, and<b=
r>Conformance) is a scalable mechanism by which a mail-originating<br>organ=
ization can policies and preferences for validation and <br>disposition of =
messages which purport to come from owned domains, <br>as well as requestin=
g feedback reporting about those message <br>validation and disposition act=
ions.=C2=A0 These features allow the domain <br>owner to detect and inhibit=
 domain name abuse.<br><br>DMARC is designed for use by domain owners.=C2=
=A0 Consequently it has no <br>applicability for domains that have no owner=
 because the domain has <br>never been registered with an Internet Naming A=
uthority.=C2=A0 Those <br>authorities have an interest in detecting and inh=
ibiting abuse of the <br>name registration process, and message recipients =
have an interest<br>in preventing deception by entities using unregistered =
organization <br>domain names.<br><br>Domains at which Internet Naming=C2=
=A0Authorities perform registration are=C2=A0<div>referred to as Public =C2=
=A0Suffix Domains (PSDs).=C2=A0 This document describes=C2=A0</div><div>an =
extension to DMARC to enable DMARC functionality for PSDs.<br><br>=C2=A0Thi=
s document also seeks to address implementations that consider a<br>=C2=A0d=
omain on a public Suffix list to be ineligible for DMARC<br>=C2=A0enforceme=
nt.<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D=
"gmail_attr">On Fri, Feb 19, 2021 at 11:12 PM Dave Crocker &lt;<a href=3D"m=
ailto:dcrocker@gmail.com">dcrocker@gmail.com</a>&gt; wrote:<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">
 =20
   =20
 =20
  <div>
    <div>On 2/18/2021 9:10 AM, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div dir=3D"ltr">Circling back to this:<br>
        </div>
        <br>
        <div class=3D"gmail_quote">
          <div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 29, 2021 at
            12:56 PM Dave Crocker &lt;<a href=3D"mailto:dcrocker@gmail.com"=
 target=3D"_blank">dcrocker@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>
              <div>On 1/29/2021 12:15 PM, Murray S. Kucherawy wrote:<br>
              </div>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">
                  <div dir=3D"ltr">On Fri, Jan 29, 2021 at 7:51 AM Dave
                    Crocker &lt;<a href=3D"mailto:dcrocker@gmail.com" targe=
t=3D"_blank">dcrocker@gmail.com</a>&gt;
                    wrote:<br>
                  </div>
                  <div class=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">
                      <div>
                        <p> </p>
                        <blockquote type=3D"cite">
                          <div>
                            <pre>   organization can use to improve mail ha=
ndling.  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>
                </div>
              </blockquote>
              <br>
            </div>
          </blockquote>
          <div>I&#39;m struggling to understand the concern here.=C2=A0 I t=
hink
            we all know what it means to register a domain, and that the
            namespace is arranged as a tree, <br>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>With the intent of building upon Barry&#39;s note:</p>
    <p>&lt;pedanty&gt; Specification writing requires clarity of who the
      reader is and empathy with the experience they will have reading
      the document.=C2=A0 &lt;/pedantry&gt;</p>
    <p>In that context &quot;we all know&quot; is automatically a red flag =
for
      requiring overly insider expertise.<br>
    </p>
    <p> However in this case, I think the problem is worse. <br>
    </p>
    <p>Simply put, I believe the text does not say what it means to
      distinguish, even for an expert reader.=C2=A0 So, yes, we all know wh=
at
      you say we know.=C2=A0 <br>
    </p>
    <p>But in fact that&#39;s not the point of the text.=C2=A0 It&#39;s try=
ing to
      make some other point,=C2=A0 I assume it&#39;s about a type of bounda=
ry
      status, but it doesn&#39;t say that, nevermind saying it clearly and
      with enough technical and semantic detail to distinguish it.</p>
    <p>The text you offer:</p>
    <p>
      </p><blockquote type=3D"cite">
        <div>Maybe this is better, just for the sake of having something
          else to look at?</div>
        <div><br>
        </div>
        <div>
          <pre>   DMARC (Domain-based Message Authentication, Reporting, an=
d
   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 nodes in the DNS tree that are eith=
er
   reserved as points below which new domain name registrations are made, o=
r are
   the results of those registrations; it does not permit a node to have bo=
th 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.
</pre>
        </div>
      </blockquote>
      moves closer to the mark, I think, but still doesn&#39;t get there.<p=
></p>
    <p>EVERY node can have sub-nodes registered.=C2=A0 So it isn&#39;t clea=
r what
      &#39;reserved&#39; means.</p>
    <p>Worse is that:</p>
    <pre>   reserved as points below which new domain name registrations ar=
e made, or are
   the results of those registrations; it does not permit a node to have bo=
th of these
   properties simultaneously.</pre>
    <div>doesn&#39;t make sense to me.=C2=A0 I suspect an average technical
      reader will be at least as confused as I am.</div>
    <br>
    <p>d/</p>
    <p><br>
    </p>
    <p>-- </p>
    <pre cols=3D"72">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>

_______________________________________________<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>

--0000000000006d877a05bbc50165--


From nobody Sun Feb 21 03:02:40 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 71A533A1992 for <dmarc@ietfa.amsl.com>; Sun, 21 Feb 2021 03:02:38 -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 H5Jj6_PvNcBA for <dmarc@ietfa.amsl.com>; Sun, 21 Feb 2021 03:02:36 -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 8D8DB3A1991 for <dmarc@ietf.org>; Sun, 21 Feb 2021 03:02:36 -0800 (PST)
Received: (qmail 6378 invoked by uid 100); 21 Feb 2021 11:02:35 -0000
Date: 21 Feb 2021 11:00:56 -0000
Message-ID: <20210221110056.5337.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/rYdjJMD1LsFl2VUSVKfythZzrX8>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Feb 21 06:02:35 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, 21 Feb 2021 11:02:38 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
  3 (16.7%) |  69293 (31.0%) | Ken O'Driscoll <ken@wemonitoremail.com>
  2 (11.1%) |  38298 (17.1%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  2 (11.1%) |  30251 (13.5%) | Brotman, Alex <alex_brotman@comcast.com>
  2 (11.1%) |  11388 ( 5.1%) | Alessandro Vesely <vesely@tana.it>
  2 (11.1%) |   7975 ( 3.6%) | John Levine <johnl@taugh.com>
  1 ( 5.6%) |  16802 ( 7.5%) | Dotzero <dotzero@gmail.com>
  1 ( 5.6%) |  14282 ( 6.4%) | Dave Crocker <dcrocker@gmail.com>
  1 ( 5.6%) |  11935 ( 5.3%) | Murray S. Kucherawy <superuser@gmail.com>
  1 ( 5.6%) |   9068 ( 4.1%) | Kurt Andersen (b) <kboth@drkurt.com>
  1 ( 5.6%) |   6093 ( 2.7%) | Barry Leiba <barryleiba@computer.org>
  1 ( 5.6%) |   4888 ( 2.2%) | Dale R. Worley <worley@ariadne.com>
  1 ( 5.6%) |   3052 ( 1.4%) |  <internet-drafts@ietf.org>


From nobody Sun Feb 21 04:48:18 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 29E9D3A1ADB; Sun, 21 Feb 2021 04:48:13 -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.26.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dmarc@ietf.org
Message-ID: <161391169312.21967.16763111766288461406@ietfa.amsl.com>
Date: Sun, 21 Feb 2021 04:48:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QIixjus-uLqGpwxirquB7Sog7Eo>
Subject: [dmarc-ietf] I-D Action: draft-ietf-dmarc-aggregate-reporting-01.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: Sun, 21 Feb 2021 12:48:13 -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           : DMARC Aggregate Reporting
        Author          : Alex Brotman
	Filename        : draft-ietf-dmarc-aggregate-reporting-01.txt
	Pages           : 20
	Date            : 2021-02-21

Abstract:
   DMARC allows for domain holders to request aggregate reports from
   receivers.  This report is an XML document, and contains extensible
   elements that allow for other types of data to be specified later.
   The aggregate reports can be submitted to the domain holder's
   specified destination as supported by the receiver.

   This document (along with others) obsoletes RFC7489.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmarc-aggregate-reporting/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dmarc-aggregate-reporting-01
https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-aggregate-reporting-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmarc-aggregate-reporting-01


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 Sun Feb 21 08:49:49 2021
Return-Path: <eric.b.chudow.civ@mail.mil>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF993A0C70 for <dmarc@ietfa.amsl.com>; Sun, 21 Feb 2021 08:49:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.667
X-Spam-Level: 
X-Spam-Status: No, score=-2.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.57, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=mail.mil
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HNam87nrdVPV for <dmarc@ietfa.amsl.com>; Sun, 21 Feb 2021 08:49:45 -0800 (PST)
Received: from UPDC19PA20.eemsg.mail.mil (UPDC19PA20.eemsg.mail.mil [214.24.27.195]) (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 14BB33A0C6F for <dmarc@ietf.org>; Sun, 21 Feb 2021 08:49:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mail.mil; i=@mail.mil; q=dns/txt; s=EEMSG2018v1a; t=1613926185; x=1645462185; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=r7qjRHv+2MfozIeS6ucmLV6An249kmKrVUnNk87O9Hc=; b=jpRGXX1leHNA+Bspp0dwDdoSoqwEhlJW9gYTZadGKeeKHpg5iO6WxA3v 5EaJ8/lxwJaaSre5uEA0RgrQAHWTga12sPzuhJFRAJJpJ08MmXUpl1DkC BT9Jf/HOnASjHgbQdxOJTK5dU41k5G3ak4OG6uv8NfDYqF+OpkglQxR3D BsJzwtPH2uqC690C6d6ba84Li3roTbERPwa73kLisc/lQJxFpfvr0A8MH lUNURRerGj1y/r8ssx450AtadxqxS8DaUsq9NCHTc0/YstoDsbu+kruI2 6SkytquWJPUDBwufA0EQA4zrfJY22fDoQDFG3PjPIgi1BvWuq0d4GAmBV Q==;
X-EEMSG-check-017: 181979386|UPDC19PA20_ESA_OUT02.csd.disa.mil
X-IronPort-AV: E=Sophos;i="5.81,195,1610409600"; d="scan'208";a="181979386"
Received: from edge-mech02.mail.mil ([214.21.130.231]) by UPDC19PA20.eemsg.mail.mil with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Feb 2021 16:49:41 +0000
Received: from UMECHPAOS.easf.csd.disa.mil (214.21.130.162) by edge-mech02.mail.mil (214.21.130.231) with Microsoft SMTP Server (TLS) id 14.3.498.0; Sun, 21 Feb 2021 16:49:26 +0000
Received: from UMECHPA7D.easf.csd.disa.mil ([169.254.6.57]) by umechpaos.easf.csd.disa.mil ([214.21.130.162]) with mapi id 14.03.0509.000; Sun, 21 Feb 2021 16:49:24 +0000
From: "Chudow, Eric B CIV NSA DSAW (USA)" <eric.b.chudow.civ@mail.mil>
To: 'Douglas Foster' <dougfoster.emailstandards@gmail.com>
CC: "'Murray S. Kucherawy'" <superuser@gmail.com>, 'IETF DMARC WG' <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Fwd: I-D Action: draft-ietf-dmarc-psd-10.txt
Thread-Index: AQHXB5ET6UmKpEsHj0KnyPYuL27pUKpizr6Q
Date: Sun, 21 Feb 2021 16:49:24 +0000
Message-ID: <553D43C8D961C14BB27C614AC48FC03128186461@UMECHPA7D.easf.csd.disa.mil>
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> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <e0a4c5eb-b047-67fe-8d76-e5beb921e5ae@gmail.com> <CAH48ZfyZmBp91WjfnNb0W35m+5wFGBonG+hoe2RCK_3N3xd6Xw@mail.gmail.com>
In-Reply-To: <CAH48ZfyZmBp91WjfnNb0W35m+5wFGBonG+hoe2RCK_3N3xd6Xw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [214.21.44.12]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/CHd9A_0LWsW_N6sSLXUbjxhI-H0>
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: Sun, 21 Feb 2021 16:49:47 -0000

SSB0aGluayBpdCdzIGdldHRpbmcgYmV0dGVyLCBidXQgSSB3b3VsZG4ndCBjYWxsIHRoZW0gSW50
ZXJuZXQgTmFtaW5nIEF1dGhvcml0aWVzLiBTaG91bGQgd2UganVzdCBjYWxsIHRoZW0gaGlnaGVy
LWxldmVsIGVudGl0aWVzPyBBbHNvLCB3aGlsZSB0aGUgYmlnZ2VzdCBoZWxwIHRoYXQgUFNEIERN
QVJDIHdvdWxkIG1ha2UgaXMgZm9yIG5vbi1leGlzdGVudCBvcmdhbml6YXRpb25hbCBkb21haW5z
LCBpdCBjYW4gYWxzbyBoZWxwIHdpdGggb3RoZXIgZG9tYWlucyB0aGF0IGhhdmVuJ3QgZXhwcmVz
c2VkIGEgRE1BUkMgcG9saWN5LCBzbyB0aGUgYWJzdHJhY3Qgc2hvdWxkbid0IG9ubHkgZGlzY3Vz
cyB1bnJlZ2lzdGVyZWQgZG9tYWlucy4NCg0KSG93IGFib3V0IHRoaXM6DQotLQ0KRE1BUkMgKERv
bWFpbi1iYXNlZCBNZXNzYWdlIEF1dGhlbnRpY2F0aW9uLCBSZXBvcnRpbmcsIGFuZCBDb25mb3Jt
YW5jZSkgaXMgYSBzY2FsYWJsZSBtZWNoYW5pc20gYnkgd2hpY2ggYSBtYWlsLW9yaWdpbmF0aW5n
IG9yZ2FuaXphdGlvbiBjYW4gZXhwcmVzcyBwb2xpY3kgcHJlZmVyZW5jZXMgZm9yIHZhbGlkYXRp
b24gYW5kIGRpc3Bvc2l0aW9uIG9mIG1lc3NhZ2VzIHdoaWNoIHB1cnBvcnQgdG8gY29tZSBmcm9t
IG93bmVkIGRvbWFpbnMsIGFzIHdlbGwgYXMgcmVxdWVzdGluZyBmZWVkYmFjayByZXBvcnRpbmcg
YWJvdXQgdGhvc2UgbWVzc2FnZSB2YWxpZGF0aW9uIGFuZCBkaXNwb3NpdGlvbiBhY3Rpb25zLiBU
aGVzZSBmZWF0dXJlcyBhbGxvdyB0aGUgRG9tYWluIE93bmVyIHRvIGRldGVjdCBhbmQgaW5oaWJp
dCBkb21haW4gbmFtZSBhYnVzZS4NCg0KRE1BUkMgaXMgZGVzaWduZWQgZm9yIHVzZSBieSBpbmRp
dmlkdWFsIERvbWFpbiBPd25lcnMgb3Igb3JnYW5pemF0aW9uYWwgRG9tYWluIE93bmVycyBmb3Ig
dGhlaXIgZG9tYWlucyBhbmQgc3ViLWRvbWFpbnMuIENvbnNlcXVlbnRseSwgRE1BUkMgcHJlZmVy
ZW5jZXMgYnkgaGlnaGVyLWxldmVsIGVudGl0aWVzIHRoYXQgaGF2ZSBPcmdhbml6YXRpb25hbCBE
b21haW5zIGJlbG93IHRoZW0gaW4gdGhlIEROUyBoaWVyYXJjaHkgY2Fubm90IGJlIHNwZWNpZmll
ZCBmb3Igc3ViLWRvbWFpbnMgaW4gdGhlaXIgcHVydmlldy4gVGhvc2UgaGlnaGVyLWxldmVsIGVu
dGl0aWVzIGhhdmUgYW4gaW50ZXJlc3QgaW4gZGV0ZWN0aW5nIGFuZCBpbmhpYml0aW5nIGRvbWFp
biBuYW1lIGFidXNlIGZvciBkb21haW4gbmFtZXMgd2l0aGluIHRoZWlyIHNlY3Rpb24gb2YgdGhl
IEROUyB0cmVlLCBhbmQgbWVzc2FnZSByZWNpcGllbnRzIGhhdmUgYW4gaW50ZXJlc3QgaW4gcHJl
dmVudGluZyBkZWNlcHRpb24gYnkgZW50aXRpZXMgdXNpbmcgdGhvc2UgZG9tYWluIG5hbWVzIGFz
IHdlbGwuIFNpbmNlIGl0cyBkZXBsb3ltZW50IGluIDIwMTUsIHVzZSBvZiBETUFSQyBoYXMgc2hv
d24gYSBjbGVhciBuZWVkIGZvciB0aGUgYWJpbGl0eSB0byBleHByZXNzIHBvbGljeSBwcmVmZXJl
bmNlcyBmb3IgdGhlc2UgZG9tYWlucy4NCg0KRG9tYWlucyBhdCB3aGljaCBoaWdoZXItbGV2ZWwg
ZW50aXRpZXMgYWNjZXB0IHJlZ2lzdHJhdGlvbnMgYnkgbXVsdGlwbGUgb3JnYW5pemF0aW9ucyBv
ciBvdGhlciBzZXBhcmF0ZSBlbnRpdGllcyBhcmUgcmVmZXJyZWQgdG8gYXMgUHVibGljIFN1ZmZp
eCBEb21haW5zIChQU0RzKS4gIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGFuIGV4dGVuc2lvbiB0
byBETUFSQyB0byBlbmFibGUgRE1BUkMgZnVuY3Rpb25hbGl0eSBmb3IgUFNEcy4gSXQgYWxzbyBh
ZGRyZXNzZXMgaW1wbGVtZW50YXRpb25zIHRoYXQgY29uc2lkZXIgYSBkb21haW4gb24gYSBQdWJs
aWMgU3VmZml4IExpc3QgdG8gYmUgaW5lbGlnaWJsZSBmb3IgRE1BUkMgZW5mb3JjZW1lbnQuDQoN
ClRoaXMgZG9jdW1lbnQgYWxzbyBkZXNjcmliZXMgYW4gZXh0ZW5zaW9uIHRvIERNQVJDIHRvIHNw
ZWNpZnkgc2VwYXJhdGUsIG9mdGVuIHN0cmljdGVyLCBwb2xpY3kgcHJlZmVyZW5jZXMgZm9yIG5v
bi1leGlzdGVudCBzdWItZG9tYWlucy4NCi0tDQoNClRoYW5rcywNCi1FcmljDQoNCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQpFcmljIENodWRvdw0KRG9EIEN5YmVyc2VjdXJp
dHkgTWl0aWdhdGlvbnMNCjQxMC04NTQtNTczNSwgZXJpYy5iLmNodWRvdy5jaXZAbWFpbC5taWwN
Cg0KRnJvbTogRG91Z2xhcyBGb3N0ZXIgPGRvdWdmb3N0ZXIuZW1haWxzdGFuZGFyZHNAZ21haWwu
Y29tPiANClNlbnQ6IFNhdHVyZGF5LCBGZWJydWFyeSAyMCwgMjAyMSA5OjAxIEFNDQpUbzogRGF2
ZSBDcm9ja2VyIDxkY3JvY2tlckBnbWFpbC5jb20+DQpDYzogTXVycmF5IFMuIEt1Y2hlcmF3eSA8
c3VwZXJ1c2VyQGdtYWlsLmNvbT47IElFVEYgRE1BUkMgV0cgPGRtYXJjQGlldGYub3JnPg0KU3Vi
amVjdDogUmU6IFtkbWFyYy1pZXRmXSBGd2Q6IEktRCBBY3Rpb246IGRyYWZ0LWlldGYtZG1hcmMt
cHNkLTEwLnR4dA0KDQpUaGlzIHdvcmRpbmcgYXR0ZW1wdHMgdG8gYWRkcmVzcyB0aGUgb2JqZWN0
aW9ucyBieSBnaXZpbmcNCiJyZWdpc3RyYXRpb24iIGEgc3BlY2lmaWMgY29udGV4dC7CoCDCoCBJ
IGFsc28gcmV3cm90ZSBzb21lIG9mIGl0IGZvciByZWFkYWJpbGl0eS4NCg0KLSAtDQoNCkRNQVJD
IChEb21haW4tYmFzZWQgTWVzc2FnZSBBdXRoZW50aWNhdGlvbiwgUmVwb3J0aW5nLCBhbmQNCkNv
bmZvcm1hbmNlKSBpcyBhIHNjYWxhYmxlIG1lY2hhbmlzbSBieSB3aGljaCBhIG1haWwtb3JpZ2lu
YXRpbmcNCm9yZ2FuaXphdGlvbiBjYW4gcG9saWNpZXMgYW5kIHByZWZlcmVuY2VzIGZvciB2YWxp
ZGF0aW9uIGFuZCANCmRpc3Bvc2l0aW9uIG9mIG1lc3NhZ2VzIHdoaWNoIHB1cnBvcnQgdG8gY29t
ZSBmcm9tIG93bmVkIGRvbWFpbnMsIA0KYXMgd2VsbCBhcyByZXF1ZXN0aW5nIGZlZWRiYWNrIHJl
cG9ydGluZyBhYm91dCB0aG9zZSBtZXNzYWdlIA0KdmFsaWRhdGlvbiBhbmQgZGlzcG9zaXRpb24g
YWN0aW9ucy7CoCBUaGVzZSBmZWF0dXJlcyBhbGxvdyB0aGUgZG9tYWluIA0Kb3duZXIgdG8gZGV0
ZWN0IGFuZCBpbmhpYml0IGRvbWFpbiBuYW1lIGFidXNlLg0KDQpETUFSQyBpcyBkZXNpZ25lZCBm
b3IgdXNlIGJ5IGRvbWFpbiBvd25lcnMuwqAgQ29uc2VxdWVudGx5IGl0IGhhcyBubyANCmFwcGxp
Y2FiaWxpdHkgZm9yIGRvbWFpbnMgdGhhdCBoYXZlIG5vIG93bmVyIGJlY2F1c2UgdGhlIGRvbWFp
biBoYXMgDQpuZXZlciBiZWVuIHJlZ2lzdGVyZWQgd2l0aCBhbiBJbnRlcm5ldCBOYW1pbmcgQXV0
aG9yaXR5LsKgIFRob3NlIA0KYXV0aG9yaXRpZXMgaGF2ZSBhbiBpbnRlcmVzdCBpbiBkZXRlY3Rp
bmcgYW5kIGluaGliaXRpbmcgYWJ1c2Ugb2YgdGhlIA0KbmFtZSByZWdpc3RyYXRpb24gcHJvY2Vz
cywgYW5kIG1lc3NhZ2UgcmVjaXBpZW50cyBoYXZlIGFuIGludGVyZXN0DQppbiBwcmV2ZW50aW5n
IGRlY2VwdGlvbiBieSBlbnRpdGllcyB1c2luZyB1bnJlZ2lzdGVyZWQgb3JnYW5pemF0aW9uIA0K
ZG9tYWluIG5hbWVzLg0KDQpEb21haW5zIGF0IHdoaWNoIEludGVybmV0IE5hbWluZ8KgQXV0aG9y
aXRpZXMgcGVyZm9ybSByZWdpc3RyYXRpb24gYXJlwqANCnJlZmVycmVkIHRvIGFzIFB1YmxpYyDC
oFN1ZmZpeCBEb21haW5zIChQU0RzKS7CoCBUaGlzIGRvY3VtZW50IGRlc2NyaWJlc8KgDQphbiBl
eHRlbnNpb24gdG8gRE1BUkMgdG8gZW5hYmxlIERNQVJDIGZ1bmN0aW9uYWxpdHkgZm9yIFBTRHMu
DQoNCsKgVGhpcyBkb2N1bWVudCBhbHNvIHNlZWtzIHRvIGFkZHJlc3MgaW1wbGVtZW50YXRpb25z
IHRoYXQgY29uc2lkZXIgYQ0KwqBkb21haW4gb24gYSBwdWJsaWMgU3VmZml4IGxpc3QgdG8gYmUg
aW5lbGlnaWJsZSBmb3IgRE1BUkMNCsKgZW5mb3JjZW1lbnQuDQoNCg==


From nobody Sun Feb 21 15:05:48 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 85E263A12D8 for <dmarc@ietfa.amsl.com>; Sun, 21 Feb 2021 15:05:47 -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 oLZcCpTMQjRm for <dmarc@ietfa.amsl.com>; Sun, 21 Feb 2021 15:05:45 -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 9EE973A12D4 for <dmarc@ietf.org>; Sun, 21 Feb 2021 15:05:45 -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 11LN5Y9C005011 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dmarc@ietf.org>; Sun, 21 Feb 2021 23:05:42 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 11LN5Y9C005011
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1613948743; bh=zAahz7BzuAvT7feBHZNxsjvZbScG7XvkHJY0/QtRdJs=; h=Subject:To:References:From:Date:In-Reply-To; b=Acn7EQY65YKLyL07VE9Br6TE2HwTsdQcF5qolKLD0o8t4CiUN4u7EM7KX3M7BDYa/ LbGLMA7TsTtGmjrg/S/TIPr2/qj8OBCxbm6jUzpHxYFlwdQ9kPg5qI0Ja9O5F8uBrk /N+5aUh8MiRfPGFcB0oSscrzZLvGoZELr40lICIpI00FpEout+nHOttOdvrBuvLOzt Bmj+rAF42RO28vOgPL5bPwdnXOOdtPNY3xkfiLuMhdAUT63by3V4X07d2dUT3RauAj vS0ooymLsE6IKFeWZKoVau+imor2vZ+rNqjiUTVBhNMNhuRmZjt0V7wRqzCNlrvMHv GumyqzOG+SMpg==
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: <161144436332.13490.10651420808048876097@ietfa.amsl.com> <CADyWQ+EhD0nz71dLtUFwb9V_6uuen-k6E5fpvrCg3ZYzfr2JSw@mail.gmail.com> <ba38a9e4-7f43-c747-2d90-f35de22a8399@gmail.com> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <e0a4c5eb-b047-67fe-8d76-e5beb921e5ae@gmail.com> <CAH48ZfyZmBp91WjfnNb0W35m+5wFGBonG+hoe2RCK_3N3xd6Xw@mail.gmail.com> <553D43C8D961C14BB27C614AC48FC03128186461@UMECHPA7D.easf.csd.disa.mil>
From: Steven M Jones <smj@crash.com>
Message-ID: <798be0bb-7044-0b72-b91c-5d3ecb8f430e@crash.com>
Date: Sun, 21 Feb 2021 15:05:30 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <553D43C8D961C14BB27C614AC48FC03128186461@UMECHPA7D.easf.csd.disa.mil>
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]); Sun, 21 Feb 2021 23:05:42 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/vj9A4-EC2RsvQH1MbjxNtU_b_Eg>
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: Sun, 21 Feb 2021 23:05:48 -0000

On 2/21/21 08:49, Chudow, Eric B CIV NSA DSAW (USA) wrote:
> I think it's getting better, but I wouldn't call them Internet Naming Authorities. Should we just call them higher-level entities?

There are proper names for these actors - there's no need to be even
more vague ...


> Also, while the biggest help that PSD DMARC would make is for non-existent organizational domains, it can also help with other domains that haven't expressed a DMARC policy, so the abstract shouldn't only discuss unregistered domains.

Except for the few cases where the registrar for a given TLD mandates
DMARC participation and/or certain policies, there should be no language
that sounds like /imposing/ DMARC on domains where the domain
owner/operator has not elected to do so. Loose language here will not be
received well.


--S.


From nobody Sun Feb 21 23:08:55 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 8B86E3A0C9A for <dmarc@ietfa.amsl.com>; Sun, 21 Feb 2021 23:08:53 -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 QN0lnTkvIrFy for <dmarc@ietfa.amsl.com>; Sun, 21 Feb 2021 23:08:51 -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 8DAE03A0C98 for <dmarc@ietf.org>; Sun, 21 Feb 2021 23:08:51 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id t23so6011112vsk.2 for <dmarc@ietf.org>; Sun, 21 Feb 2021 23:08: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=DOf2GNKQsNKKuLkh1T/EF3vMGwm+bnfvD5ht9mYx/ls=; b=jRI+83eUP074R+6uajLvC+C/qfsz83mVfAOM5Mw2lnOiB7JRPh14aB0HzjkNDXBwHH wQJThqARBU8pUtLKMpijgmImXAIyDRPvqSGhmCfD9JTMgJB6SbH6bRSZLN/OkcKjE/7L xyzGtlySrXmlq3EKH7eyZhQYeqXjfiCpi95V9ovq9lEgGHJUhpLPefQaergsFA3hIf/U /XT7/s5qu2sc62bxB7X5jZzCxBhAPvpmLYRs1f1rRpZzsEeSeitxV0OWelnpg8zGDrkw gIp4u8dottCIbAjRsenMgTlm/e9qDkbwWOgCtBxXf8FHOn+eoI/NIfTyer224zgaSrE8 YTVg==
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=DOf2GNKQsNKKuLkh1T/EF3vMGwm+bnfvD5ht9mYx/ls=; b=fx13fzveAT7ijiE/MBeOIScmjoIGdT11GDnkUKGNBHPIVUk7LFzrc5MHIfoXJBUYTK y9085quZXasEGB4I8KYmkJpaYTga1jqzRB5UEUe1YezUJWdgXeNXnjy1m2id9w6WgDc0 /4P9ilZetyjI1wLLaLpdghhlLTLoGkj52s1pDIvVnVg0P52DHh0YTZJXPpo+wwrVui/i XWsLKcshsnj+JE+a9uVmBP2tFqGJXzIR6m7aJg21h36/sGiokR5cp8LTRdcYahmKs9Jo MbjnuAZUsP3285tl7jQ0n76Ba0qojW3W7P0GlOj0GBHFRjfMhwmkBPW5LBcSWuoC7p/o fGEQ==
X-Gm-Message-State: AOAM53023z7h+OSanRgjVdFpSgikKJ1mleLseMmWDGyF1S2bGnIrfzrK O7RDGnT2crqX2TYsH/7WgnPKhN+praEZ/aBf5nI=
X-Google-Smtp-Source: ABdhPJwYqq+Aw494KM23BH9lO9HlATKm6oycb2CEF80oCyqC5wabkVtqZ8nqXAsOFy5ESLDm9ui6xBqx5FYT3CCFnJY=
X-Received: by 2002:a67:f7d0:: with SMTP id a16mr6633395vsp.15.1613977730460;  Sun, 21 Feb 2021 23:08:50 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com>
In-Reply-To: <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sun, 21 Feb 2021 23:08:37 -0800
Message-ID: <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004cb10405bbe7791f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/1uTcVeUWEFLNFERcWuYtFv4qpEQ>
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: Mon, 22 Feb 2021 07:08:54 -0000

--0000000000004cb10405bbe7791f
Content-Type: text/plain; charset="UTF-8"

On Fri, Feb 19, 2021 at 3:02 PM Barry Leiba <barryleiba@computer.org> wrote:

> I agree that the abstract is unclear.  This makes no sense to me:
>
>    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.
>
> I don't understand the distinction that it's trying to make between
> the two possibilities.
> I also don't see the antecedent to "these domains" in the final
> sentence of that paragraph.
>
> Beyond that:
> > I'm at a loss to understand what's confusing.  I'm not convinced that
> "registrations" in the
> > context of domain names is unclear to a reader familiar with this space.
>
> I am absolutely convinced that it is.  Think of people in M3AAWG, for
> whom this is very relevant.  Many of them don't know much about
> registries, registrars, and such, and in general, the average reader
> won't understand the difference, from a "registration" standpoint,
> between facebook.com (which is registered) and "www.facebook.com"
> (which is not).  To the average reader, "facebook.com" is registered
> under com, and "www.facebook.com" is registered under facebook.  And
> the ones who don't think that will likely not understand why we can't
> just talk about second-level domains and be done with it.
>

Actually that's a community that I would expect to know exactly what all
those terms mean and how they are all related.

I think the use of "registered" seems to be the source of some of this
confusion.  To work with the example you gave here, I agree that "
facebook.com" is registered (under "com"), but disagree that "
www.facebook.com" is registered at all; "facebook.com" was delegated to
some company that now "owns" that piece of the namespace tree and can
create whatever it wants under there without any external arrangement.  To
my mind, "register" involves a specific transaction, sometimes involving
money, with whoever gates access to make those delegations.

All that needs to be explained in the Introduction, not the Abstract.
> But the Abstract has to explain enough for a reader to understand why
> she might or might not be interested in getting the document and
> reading it.  So it's going to be tough to word it carefully and to
> keep it concise.  But we have to.
>
> Stressing a point:
> We very clearly do NOT want to explain this stuff in the Abstract.  In
> fact, we don't have to explain much at all in the Abstract.  What we
> have to do is make sure that the Abstract doesn't say stuff that's
> *wrong* or confusing.  So let's try to find some fifth-grade language
> that can suffice, and then make sure the Introduction has the right
> words to make it clear to people who know how to do email, but who
> don't already understand the issues involved here.
>

How's this?:

   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.

   Within the Domain Name System (DNS) on the public Internet, which is

   organized as a tree, some nodes of that tree are reserved for use by

   registrars, who delegate sub-trees to other operators on request.
DMARC currently
   permits expression of policy only for such sub-trees.  There is a
marked desire to

   be able to express policy for the reserved nodes as well.  This document

   describes an experimental extension to DMARC to add that capability.

If we like that as a replacement Abstract, I'll carry on and propose a
revision to the Introduction.

-MSK

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

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Feb 19, 2021 at 3:02 PM Barry Lei=
ba &lt;<a href=3D"mailto:barryleiba@computer.org">barryleiba@computer.org</=
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">I agree that the abstract is unclear.=C2=A0 This m=
akes no sense to me:<br>
<br>
=C2=A0 =C2=A0domain 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.<br>
<br>
I don&#39;t understand the distinction that it&#39;s trying to make between=
<br>
the two possibilities.<br>
I also don&#39;t see the antecedent to &quot;these domains&quot; in the fin=
al<br>
sentence of that paragraph.<br>
<br>
Beyond that:<br>
&gt; I&#39;m at a loss to understand what&#39;s confusing.=C2=A0 I&#39;m no=
t convinced that &quot;registrations&quot; in the<br>
&gt; context of domain names is unclear to a reader familiar with this spac=
e.<br>
<br>
I am absolutely convinced that it is.=C2=A0 Think of people in M3AAWG, for<=
br>
whom this is very relevant.=C2=A0 Many of them don&#39;t know much about<br=
>
registries, registrars, and such, and in general, the average reader<br>
won&#39;t understand the difference, from a &quot;registration&quot; standp=
oint,<br>
between <a href=3D"http://facebook.com" rel=3D"noreferrer" target=3D"_blank=
">facebook.com</a> (which is registered) and &quot;<a href=3D"http://www.fa=
cebook.com" rel=3D"noreferrer" target=3D"_blank">www.facebook.com</a>&quot;=
<br>
(which is not).=C2=A0 To the average reader, &quot;<a href=3D"http://facebo=
ok.com" rel=3D"noreferrer" target=3D"_blank">facebook.com</a>&quot; is regi=
stered<br>
under com, and &quot;<a href=3D"http://www.facebook.com" rel=3D"noreferrer"=
 target=3D"_blank">www.facebook.com</a>&quot; is registered under facebook.=
=C2=A0 And<br>
the ones who don&#39;t think that will likely not understand why we can&#39=
;t<br>
just talk about second-level domains and be done with it.<br></blockquote><=
div><br></div><div>Actually that&#39;s a community that I would expect to k=
now exactly what all those terms mean and how they are all related.</div><d=
iv><br></div><div>I think the use of &quot;registered&quot; seems to be the=
 source of some of this confusion.=C2=A0 To work with the example you gave =
here, I agree that &quot;<a href=3D"http://facebook.com">facebook.com</a>&q=
uot; is registered (under &quot;com&quot;), but disagree that &quot;<a href=
=3D"http://www.facebook.com">www.facebook.com</a>&quot; is registered at al=
l; &quot;<a href=3D"http://facebook.com">facebook.com</a>&quot; was delegat=
ed to some company that now &quot;owns&quot; that piece of the namespace tr=
ee and can create whatever it wants under there without any external arrang=
ement.=C2=A0 To my mind, &quot;register&quot; involves a specific transacti=
on, sometimes involving money, with whoever gates access to make those dele=
gations.</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">
All that needs to be explained in the Introduction, not the Abstract.<br>
But the Abstract has to explain enough for a reader to understand why<br>
she might or might not be interested in getting the document and<br>
reading it.=C2=A0 So it&#39;s going to be tough to word it carefully and to=
<br>
keep it concise.=C2=A0 But we have to.<br>
<br>
Stressing a point:<br>
We very clearly do NOT want to explain this stuff in the Abstract.=C2=A0 In=
<br>
fact, we don&#39;t have to explain much at all in the Abstract.=C2=A0 What =
we<br>
have to do is make sure that the Abstract doesn&#39;t say stuff that&#39;s<=
br>
*wrong* or confusing.=C2=A0 So let&#39;s try to find some fifth-grade langu=
age<br>
that can suffice, and then make sure the Introduction has the right<br>
words to make it clear to people who know how to do email, but who<br>
don&#39;t already understand the issues involved here.<br></blockquote><div=
><br></div><div>How&#39;s this?: <br></div><div><br></div><div>
<pre>   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.<br><br></pre><pre>   With=
in the Domain Name System (DNS) on the public Internet, which is<br></pre><=
pre>   organized as a tree, some nodes of that tree are reserved for use by=
<br></pre><pre>   registrars, who delegate sub-trees to other operators on =
request.  DMARC currently<br>   permits expression of policy only for such =
sub-trees.  There is a marked desire to<br></pre><pre>   be able to express=
 policy for the reserved nodes as well.  This document<br></pre><pre>   des=
cribes an experimental extension to DMARC to add that capability.
<br></pre>If we like that as a replacement Abstract, I&#39;ll carry on and =
propose a revision to the Introduction.<br><br>-MSK =C2=A0</div></div></div=
>

--0000000000004cb10405bbe7791f--


From nobody Mon Feb 22 06:32:41 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 CA6093A08C0 for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 06:32:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 NpFjg-VQfDhB for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 06:32:33 -0800 (PST)
Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) (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 44E2F3A086E for <dmarc@ietf.org>; Mon, 22 Feb 2021 06:32:33 -0800 (PST)
Received: by mail-lj1-f175.google.com with SMTP id u4so13008602lja.3 for <dmarc@ietf.org>; Mon, 22 Feb 2021 06:32:33 -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=GcSBWfL1SI4A/ijTdBKcEkuYB1yvyHvo9tQKL5UxNbM=; b=A5hJViNVJOZSo35uLqr+nhO6J13f6QwsNP4n/OisNT2/psz8JWhpnQRZPqlpPEVs95 CKnZAquRtsjwWcMf1RykZeapx5gmkDbZ7FxLXN1x16TjBMVQJDMs1m5svgAFj1EkzqRi daZCBByO9HVsCr3IY6F1N8PhmVE3qlfbQ81ILpoCKCxGTxkso6Ymut84SCzGoV44gHy1 u+KC6V+92RD6KKKr6QF/LFsdH8Bkl+zbYpPmUJq7lBjr/KZD/SmwO0A8d6w2iRQ/KnZv hjEAhCAA8gWMTXXeu/i+AcJrGXTkzP1abP9FOcayxCYJ6CTwLuSNYP6xXFvm2ieW1Llm vCsw==
X-Gm-Message-State: AOAM531mgvrnV/vspN6Etqv3rrTM6qCamDRtvGM2NOC67St8LhUz3MCQ wO2t3GWfuajUvbh7KOIyMIf6P6TH3JJd+UEkMvk=
X-Google-Smtp-Source: ABdhPJzjjiXcFnaFsDTscOQXgxT3eepLO2fRZVLG4LhSt//1bEiUl27Jj9zfkuX6FFDIyxtqGC+3qOdYVsD6x1GYwlU=
X-Received: by 2002:a2e:5841:: with SMTP id x1mr13746711ljd.473.1614004351045;  Mon, 22 Feb 2021 06:32:31 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com>
In-Reply-To: <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 22 Feb 2021 09:32:19 -0500
Message-ID: <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/jlVi2CO9ceI4jAR7tC-bGwMyrXs>
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: Mon, 22 Feb 2021 14:32:40 -0000

>> > I'm at a loss to understand what's confusing.  I'm not convinced that "registrations" in the
>> > context of domain names is unclear to a reader familiar with this space.
>>
>> I am absolutely convinced that it is.  Think of people in M3AAWG, for
>> whom this is very relevant.  Many of them don't know much about
>> registries, registrars, and such, and in general, the average reader
>> won't understand the difference, from a "registration" standpoint,
>> between facebook.com (which is registered) and "www.facebook.com"
>> (which is not).  To the average reader, "facebook.com" is registered
>> under com, and "www.facebook.com" is registered under facebook.  And
>> the ones who don't think that will likely not understand why we can't
>> just talk about second-level domains and be done with it.
>
> Actually that's a community that I would expect to know exactly what all those terms mean and
> how they are all related.

There clearly are some in that community who do.  But there are many
there who don't.  This stuff is more esoteric than those of us who are
in the middle of it often realize.

> I think the use of "registered" seems to be the source of some of this confusion.

Yes, exactly.

> To work with the example you gave here, I agree that "facebook.com" is registered (under "com"), but
> disagree that "www.facebook.com" is registered at all;

Right, of course it's not.  I didn't say that it is: I said that
people who don't fully understand this stuff *think* it is, and that's
the part that the text isn't making clear.

> To my mind, "register" involves a specific transaction, sometimes involving money, with whoever gates
> access to make those delegations.

And that's what we need to explain better in the Introduction.

> How's this?:
>
>    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.
>
>    Within the Domain Name System (DNS) on the public Internet, which is
>    organized as a tree, some nodes of that tree are reserved for use by
>    registrars, who delegate sub-trees to other operators on request.  DMARC currently
>    permits expression of policy only for such sub-trees.  There is a marked desire to
>    be able to express policy for the reserved nodes as well.  This document
>    describes an experimental extension to DMARC to add that capability.
>
> If we like that as a replacement Abstract, I'll carry on and propose a revision to the Introduction.

I don't think that really explains it properly either -- I think with
the above text, it's less confusing, but also not correct, or at least
not really indicative of what the document is proposing.

I don't have time today, but give me a couple of days to work on the
Abstract and the Introduction/Example, and I'll propose some specific
text that we can try out.

Barry


From nobody Mon Feb 22 06:36:11 2021
Return-Path: <ken@wemonitoremail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7DDF3A07DA for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 06:36: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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=wemonitoremail.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 d5q1sa66OVQ7 for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 06:36:06 -0800 (PST)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10095.outbound.protection.outlook.com [40.107.1.95]) (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 9DD633A0657 for <dmarc@ietf.org>; Mon, 22 Feb 2021 06:36:05 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eTPbq8u08WXOzYwttp44qwfsYXzL/6F67B51nd+gXLqaKMjC43H9tfPUEHQXvnlQXve/lOp7vTKgjrcToDbeWN+XpGl+J8kczUZAMynfOwpxBIHcpCFg4xDGSV0Txp7UHT8PMkgF2Xj/n4rWUjGjOrCZXC5Nxf9TM11dfxaASPAXWFz2Mn9/yMMCgsOSsSyL1umtcjSvq4vnnGtgeqOr9IE9SeWEzb6sN84Lekt2Edf9VdZg2OVjKIntRxT9AS/tFme7I8pzeZm5i//SC0/cuIXfVuir7EAYf0DWqmnUo/5sOkp1Ltss+IykQUXYzEGfbwt/XHKGubH70TVEnvJlqA==
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=428zxZpRe5H6sfw8HySo7elnFULY2knggwEt8/CcsPs=; b=aRsMnH0VOYRg3e6Op1qXr63Ue7HbeLVB8uJF5kz0IjgludiGDwmyIMrFsrkgs8DddDmHQeB+BL+CY6yi02gJZJ2LKdMKYW+nraMfC9otbZO2YyhYsLBoqOQuxM2N6UFSwPBVxKr69YLGdmfHifT7M5OmGlhvAgrCkJbINn8tBT1AXHJb6Yps4TOdk/31V9GPJdevuL8Mm/2u194qb4OqBtaOj9askxQ0IWuwUQpYoCw+cINRAkzm0EFvlrCi+a/LQjb25Xm9Y1OtARSU7biRcHOTzsQ3ORvuE6CPM2iVG/cd+Jw/vPljgfVaA/3GTHpnS0mrSHSKfQZARj7nzVT9hQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=wemonitoremail.com; dmarc=pass action=none header.from=wemonitoremail.com; dkim=pass header.d=wemonitoremail.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemonitoremail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=428zxZpRe5H6sfw8HySo7elnFULY2knggwEt8/CcsPs=; b=TMdBOC87iGD79D5VQPYiqQ+R6n6hQB9uUb1cW2qM+3Rg88iPJdWmdJgAq59IyX08O4QaQNIKI6H196VKvCWH4BCvNi3ryYnwVb2297gbOPVxcYtYMbb6dtX/BHRh733eescpPGzlYU2xTQFjQvnMKx/ehkiSoZOxvdHJtR/3X452LqZZgA4DJefPRnFQJ3UQzlBUUzw+rkd0lIryNha8F/l+bn5M62lxX//pT2PEI5/nR66OxPuPRN942TYrODN0woqt+P72bamZZK/nMVvSqA6CthqtlQg32Frz/r9WAtK5dyGTw+OuwSba59MsC0Q3KQjrLiD4ZbXrouoh3ZlXpw==
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com (2603:10a6:800:19a::9) by VI1PR0102MB2847.eurprd01.prod.exchangelabs.com (2603:10a6:802:6::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.29; Mon, 22 Feb 2021 14:36:00 +0000
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::9c69:59f:c073:bd9f]) by VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::9c69:59f:c073:bd9f%7]) with mapi id 15.20.3846.045; Mon, 22 Feb 2021 14:36:00 +0000
From: Ken O'Driscoll <ken@wemonitoremail.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
CC: Dave Crocker <dcrocker@gmail.com>, "Murray S. Kucherawy" <superuser@gmail.com>, Barry Leiba <barryleiba@computer.org>
Thread-Topic: [dmarc-ietf] Fwd: I-D Action: draft-ietf-dmarc-psd-10.txt
Thread-Index: AQHW9lab2k+8FMVZi0mnpCcspdofhKo/CiwAgAALfYCAHy+dgIAB9HgAgAOsqYCAAHRfoA==
Date: Mon, 22 Feb 2021 14:36:00 +0000
Message-ID: <VI1PR01MB705365834B737AF46A2DF099C7819@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
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> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com>
In-Reply-To: <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com>
Accept-Language: en-GB, 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=wemonitoremail.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 24dfa346-e454-402e-8223-08d8d73f2c9e
x-ms-traffictypediagnostic: VI1PR0102MB2847:
x-microsoft-antispam-prvs: <VI1PR0102MB28470BCA31ED5B3D160832B0C7819@VI1PR0102MB2847.eurprd01.prod.exchangelabs.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 5xFZgbD5pic/JiyQrWYrCXFLm5UqS0P/GaqWTNZAZHfNUnhMK0E6ae7jBkz65rmAzK2h+Toxl+nFGems1Zf3txWA3ftuLacUREjHxNrdCBZliiWn1VUC2R78v6hRwOIxv6eo+BlIjp8x/QA4SX1yfvk6BnhYb4u3bfNycDD50Z+1RFqb5yOkhjQdECou1lezrz4g3LKmH2i1Qpg4IFgBEnxZTyL2V4rU70cSErZ2VQQ0afllnwu/fFJCl9We5Ek7y0zRtezAVzmZlIPvq56RlgyQ9+EnrDSr1aNQQefEESyn+uhu+PIBMb3CK6KWUQytHNjaMJWA6NDoD7DlHnCDbFtI9hvQfYi4iwkPTKZEYdvv4aWbXXzPi8/NfoslL/jP58WXjZKTrF1vjbGUcsb61LsWLCyZPTUtSsf+HqL/EzeeRWzdjVt2n1oPW0YlQrar1TDmKBGh05Usb92HdbVESc6MpZTMgQ7LdELcdq6hVsK8hXtiwvwGhiBbSkEO2OPms2cPaXmP7fvSEOULwt7vXpeC6ckpVdH7Mx58rlI7MD7IRSSWrc8i/UuX3OumoHXGlQPZo5irVCKjDzLzFBhLQVbo2DGbK2nSEI8PTOtI8H8=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR01MB7053.eurprd01.prod.exchangelabs.com; PTR:;  CAT:NONE; SFS:(136003)(376002)(346002)(396003)(39830400003)(366004)(52536014)(316002)(66574015)(166002)(66476007)(66556008)(66446008)(64756008)(478600001)(26005)(83380400001)(5660300002)(86362001)(66946007)(54906003)(6506007)(53546011)(8676002)(71200400001)(55016002)(4326008)(8936002)(9686003)(6916009)(33656002)(76116006)(7696005)(186003)(2906002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?NFFWTnZ1alU4YldIcERBVnJJZjlVcnJpS3VYZUk1TkdTTVNZbnA2NVo5L0lj?= =?utf-8?B?TkJVdXFreDZWWXVUWDFIU1JMMDgwVGR5T0ttVjBJZnVpeFJaTVQvWEpwMSsw?= =?utf-8?B?djhoUm55Mjl6dHVpdDZBR2E4cWpzYVR5WHE0MVpyUTMxY0dxN1hTVTdkM1lP?= =?utf-8?B?ZHpBNFc0Nno3ODlGaVFSSFljU3g3d1BVOHRwcFdaTzBwUXJEd2JpT25qN0sv?= =?utf-8?B?ZVQxZGZmYUw4OElDSkVUc0VyYXZCbVZ0RElTczFKaWQyeW1ad29qeFdFK3Jz?= =?utf-8?B?RXZNNmo5blZDZDRHQWdoMTVzK0pEUGZydS9aUjBxTFpLa3ZhOXg3R05xL2tz?= =?utf-8?B?Y0hxVVJiQTZMTjdmZWNIQmJyeEcwazhwc004OHNvOVFaMXRJQzVLanlaN3Fv?= =?utf-8?B?Q0VJbU9SOW1yMVVnSThlNzN6Ti8yaUxCSStSNWpvenVrYVBVMi8yaTNOdTBl?= =?utf-8?B?MngremNPRDZKek5IdUFIcVlqNEFITU45L25Gbldmell5eUdicFVDZE1zR1N5?= =?utf-8?B?eTNrT2FITXNwVGMvb01UMXlGbFBJYno3aUdzMndGUG5Sd3d3YUNUOTluckRT?= =?utf-8?B?MVJFUm9rWFRsQzlBekE4ZkY1ZkZ5V2pDd2ppRFFZa0MvNW9SSHZ5SXlRMXFO?= =?utf-8?B?dkwyV0hNL1p3aTNQKzF0cnNKa1JzKy9ZNzZoaUNCeXFYelgycmRlMHdpTlN2?= =?utf-8?B?Q1Uwb0tjeFcrN2tTSFBXYUpyWjJ5V0l4ckNPcnBDUUV1R3U4Y0gyUE1PeTlj?= =?utf-8?B?cmhDVXBQQTl2SEwwVWloZUhQVERTV08xa2lRekJpS2kwbzl1NlVtTUdVZGNQ?= =?utf-8?B?QTdaakhmNzJvR1RmY0h2ZVUrMSs0MzB4WHk1c1cyTWljN3RyTFBBWGc3Si8r?= =?utf-8?B?WTdJVDFpd3laaDdIZzhlWllyWmJNR1piR2U5b09UWUNzM293OUdaZ2xXUlJE?= =?utf-8?B?L3Y0T1grZDVRZDA0NWJLaXN3N1V6T2RvRnJKUWxwNjQ5bHRhU09hbDA3VDMy?= =?utf-8?B?bTZzKys0ZHVVQy9iaFRtQmVMZjBOY0RTc3dVRHcwTXd2S00rSWFsUm5WYkRy?= =?utf-8?B?eEIwSElXKzhjRTZadXFFclV6MlIzNllpdyszY0ZNSmk5ZGVnekk2ZHppTzRP?= =?utf-8?B?VWRMZjVwWUFIUGNpTGc3NkEraXB4Y1dia0lQREZsdkRHZzlmVkpqRW5ncnZV?= =?utf-8?B?Z2cwcnpmak45Qk91bGR0djZHTEZVOXhRTDdDMTNtcWtvZEtNVHpFb3pQOVhT?= =?utf-8?B?QndTMnJ4QjdrazRQUTlyUm9jZWx5eGU0R3NnUEVCOFZwT1BBcWFVb0xWTkdz?= =?utf-8?B?UWNrd2RmU1RWd0xYaXZGZlBxR3dxRC9icy9EZWd4ZnZFbzR2Sk04QitJY0lt?= =?utf-8?B?NzdBN2R5WXRRcFhOQ0RyaWNlU1RETXBoVVRDM0QxOExUa1JUQnJ0Ky9BRmtB?= =?utf-8?B?cnJHWVZ0SXJOTlhJZUVOSkVHT0NFM1pLQldHYWFLTFkxdWZkbzVJOXFoRVoz?= =?utf-8?B?T3g3bFZCN09uZWY3U2pkTGlzMXZEaS84SEhCenQ3Nit4VWFsZk43SGZkd0Q1?= =?utf-8?B?VUNqMXlBUVVYMFA3cW1yYU0rQzdueXpRUS9sNGw0cyt3dmFpcTNNayt4TTdt?= =?utf-8?B?SDlQa0E2QkplTnlEVkgyYzBkQkpQRHFmejR2cGlINVlwOWJCTXBwWHR3QjJy?= =?utf-8?B?U00yZ0NOUkpDV2hYNFFxempmL05Ka3JKREtOdC9iVXZ5cXBsK3JxT0pJbGFO?= =?utf-8?Q?b31jb+Od0/yzjkezAE=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_VI1PR01MB705365834B737AF46A2DF099C7819VI1PR01MB7053eurp_"
MIME-Version: 1.0
X-OriginatorOrg: wemonitoremail.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: VI1PR01MB7053.eurprd01.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 24dfa346-e454-402e-8223-08d8d73f2c9e
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Feb 2021 14:36:00.2430 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a2b1d6fe-fc8b-4b7c-b9f1-d7b1ab3d23b3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vSIrolIY5K+Udt/AgkqyZRxZ6wNg2xxnQHeviY7FhKy7vfcrMIIjvJOpnvB7QIctajl9nRl+RO4UlvRpy7DbHA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0102MB2847
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/-yaAy8osae1RnKgDw2olFdEkjAQ>
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: Mon, 22 Feb 2021 14:36:10 -0000

--_000_VI1PR01MB705365834B737AF46A2DF099C7819VI1PR01MB7053eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpJIHdvdWxkIGdvIGV2ZW4gZnVydGhlciBhbmQgbm90IGV2ZW4gdGFsayBhYm91dCB0aGUgdHJl
ZXMgYW5kIG5vZGVzLiBBbHNvLCBlY2hvaW5nIGVsc2V3aGVyZSBpbiB0aGlzIHRocmVhZCwgbWFr
aW5nIGl0IHJlYWxseSBjbGVhciB0aGF0IHRoaXMgaXMgbm90IGEgY2FzZSBvZiBETUFSQyBpcyBj
b21pbmcgZm9yIHlvdXIgVExELiBTbywgSeKAmWQgcHJvcG9zZSBzb21ldGhpbmcgc3VwZXIgYmFz
aWMgbGlrZSB0aGlzIGZvciB0aGUgc2Vjb25kIHBhcmFncmFwaDoNCg0KRG9tYWluIG5hbWUgc3Vm
Zml4ZXMgKGZvciBleGFtcGxlIC5jb20sIC5ldSwgYW5kIC5jby51aykgYXJlIGNvbnRyb2xsZWQg
YnkgcmVnaXN0cmllcywgd2hvIGVpdGhlciBkaXJlY3RseSBvciB0aHJvdWdoIGFjY3JlZGl0ZWQg
cmVnaXN0cmFycywgZmFjaWxpdGF0ZSB0aGUgcmVnaXN0cmF0aW9uIGFuZCBtYW5hZ2VtZW50IG9m
IGRvbWFpbiBuYW1lcyBiZWxvdyB0aGVzZSBzdWZmaXhlcy4gRE1BUkMgY3VycmVudGx5IHBlcm1p
dHMgZXhwcmVzc2lvbiBvZiBwb2xpY3kgb25seSBmb3IgZG9tYWluIG5hbWVzIGFuZCBub3QgZm9y
IGRvbWFpbiBzdWZmaXhlcy4gU2luY2UgaXRzIGRlcGxveW1lbnQgaW4gMjAxNSwgc3BlY2lhbGlz
dCB1c2UgY2FzZXMgaGF2ZSBiZWVuIGlkZW50aWZpZWQgd2hlcmUgaXQgbWF5IGJlIGRlc2lyYWJs
ZSBmb3IgYSBzdWZmaXggdG8gZXhwcmVzcyBhIERNQVJDIHBvbGljeS4gVGhpcyBkb2N1bWVudCBk
ZXNjcmliZXMgYW4gZXhwZXJpbWVudGFsIGV4dGVuc2lvbiB0byBETUFSQyB0byBhZGQgdGhhdCBj
YXBhYmlsaXR5Lg0KDQpLZW4uDQoNCkZyb206IGRtYXJjIDxkbWFyYy1ib3VuY2VzQGlldGYub3Jn
PiBPbiBCZWhhbGYgT2YgTXVycmF5IFMuIEt1Y2hlcmF3eQ0KU2VudDogTW9uZGF5IDIyIEZlYnJ1
YXJ5IDIwMjEgMDc6MDkNClRvOiBCYXJyeSBMZWliYSA8YmFycnlsZWliYUBjb21wdXRlci5vcmc+
DQpDYzogRGF2ZSBDcm9ja2VyIDxkY3JvY2tlckBnbWFpbC5jb20+OyBJRVRGIERNQVJDIFdHIDxk
bWFyY0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBbZG1hcmMtaWV0Zl0gRndkOiBJLUQgQWN0aW9u
OiBkcmFmdC1pZXRmLWRtYXJjLXBzZC0xMC50eHQNCg0KT24gRnJpLCBGZWIgMTksIDIwMjEgYXQg
MzowMiBQTSBCYXJyeSBMZWliYSA8YmFycnlsZWliYUBjb21wdXRlci5vcmc8bWFpbHRvOmJhcnJ5
bGVpYmFAY29tcHV0ZXIub3JnPj4gd3JvdGU6DQpJIGFncmVlIHRoYXQgdGhlIGFic3RyYWN0IGlz
IHVuY2xlYXIuICBUaGlzIG1ha2VzIG5vIHNlbnNlIHRvIG1lOg0KDQogICBkb21haW4gbmFtZXMg
cmVwcmVzZW50IGVpdGhlciBub2RlcyBpbiB0aGUgdHJlZSBiZWxvdw0KICAgd2hpY2ggcmVnaXN0
cmF0aW9ucyBvY2N1ciwgb3Igbm9kZXMgd2hlcmUgcmVnaXN0cmF0aW9ucyBoYXZlDQogICBvY2N1
cnJlZDsgaXQgZG9lcyBub3QgcGVybWl0IGEgZG9tYWluIG5hbWUgdG8gaGF2ZSBib3RoIG9mIHRo
ZXNlDQogICBwcm9wZXJ0aWVzIHNpbXVsdGFuZW91c2x5Lg0KDQpJIGRvbid0IHVuZGVyc3RhbmQg
dGhlIGRpc3RpbmN0aW9uIHRoYXQgaXQncyB0cnlpbmcgdG8gbWFrZSBiZXR3ZWVuDQp0aGUgdHdv
IHBvc3NpYmlsaXRpZXMuDQpJIGFsc28gZG9uJ3Qgc2VlIHRoZSBhbnRlY2VkZW50IHRvICJ0aGVz
ZSBkb21haW5zIiBpbiB0aGUgZmluYWwNCnNlbnRlbmNlIG9mIHRoYXQgcGFyYWdyYXBoLg0KDQpC
ZXlvbmQgdGhhdDoNCj4gSSdtIGF0IGEgbG9zcyB0byB1bmRlcnN0YW5kIHdoYXQncyBjb25mdXNp
bmcuICBJJ20gbm90IGNvbnZpbmNlZCB0aGF0ICJyZWdpc3RyYXRpb25zIiBpbiB0aGUNCj4gY29u
dGV4dCBvZiBkb21haW4gbmFtZXMgaXMgdW5jbGVhciB0byBhIHJlYWRlciBmYW1pbGlhciB3aXRo
IHRoaXMgc3BhY2UuDQoNCkkgYW0gYWJzb2x1dGVseSBjb252aW5jZWQgdGhhdCBpdCBpcy4gIFRo
aW5rIG9mIHBlb3BsZSBpbiBNM0FBV0csIGZvcg0Kd2hvbSB0aGlzIGlzIHZlcnkgcmVsZXZhbnQu
ICBNYW55IG9mIHRoZW0gZG9uJ3Qga25vdyBtdWNoIGFib3V0DQpyZWdpc3RyaWVzLCByZWdpc3Ry
YXJzLCBhbmQgc3VjaCwgYW5kIGluIGdlbmVyYWwsIHRoZSBhdmVyYWdlIHJlYWRlcg0Kd29uJ3Qg
dW5kZXJzdGFuZCB0aGUgZGlmZmVyZW5jZSwgZnJvbSBhICJyZWdpc3RyYXRpb24iIHN0YW5kcG9p
bnQsDQpiZXR3ZWVuIGZhY2Vib29rLmNvbTxodHRwOi8vZmFjZWJvb2suY29tPiAod2hpY2ggaXMg
cmVnaXN0ZXJlZCkgYW5kICJ3d3cuZmFjZWJvb2suY29tPGh0dHA6Ly93d3cuZmFjZWJvb2suY29t
PiINCih3aGljaCBpcyBub3QpLiAgVG8gdGhlIGF2ZXJhZ2UgcmVhZGVyLCAiZmFjZWJvb2suY29t
PGh0dHA6Ly9mYWNlYm9vay5jb20+IiBpcyByZWdpc3RlcmVkDQp1bmRlciBjb20sIGFuZCAid3d3
LmZhY2Vib29rLmNvbTxodHRwOi8vd3d3LmZhY2Vib29rLmNvbT4iIGlzIHJlZ2lzdGVyZWQgdW5k
ZXIgZmFjZWJvb2suICBBbmQNCnRoZSBvbmVzIHdobyBkb24ndCB0aGluayB0aGF0IHdpbGwgbGlr
ZWx5IG5vdCB1bmRlcnN0YW5kIHdoeSB3ZSBjYW4ndA0KanVzdCB0YWxrIGFib3V0IHNlY29uZC1s
ZXZlbCBkb21haW5zIGFuZCBiZSBkb25lIHdpdGggaXQuDQoNCkFjdHVhbGx5IHRoYXQncyBhIGNv
bW11bml0eSB0aGF0IEkgd291bGQgZXhwZWN0IHRvIGtub3cgZXhhY3RseSB3aGF0IGFsbCB0aG9z
ZSB0ZXJtcyBtZWFuIGFuZCBob3cgdGhleSBhcmUgYWxsIHJlbGF0ZWQuDQoNCkkgdGhpbmsgdGhl
IHVzZSBvZiAicmVnaXN0ZXJlZCIgc2VlbXMgdG8gYmUgdGhlIHNvdXJjZSBvZiBzb21lIG9mIHRo
aXMgY29uZnVzaW9uLiAgVG8gd29yayB3aXRoIHRoZSBleGFtcGxlIHlvdSBnYXZlIGhlcmUsIEkg
YWdyZWUgdGhhdCAiZmFjZWJvb2suY29tPGh0dHA6Ly9mYWNlYm9vay5jb20+IiBpcyByZWdpc3Rl
cmVkICh1bmRlciAiY29tIiksIGJ1dCBkaXNhZ3JlZSB0aGF0ICJ3d3cuZmFjZWJvb2suY29tPGh0
dHA6Ly93d3cuZmFjZWJvb2suY29tPiIgaXMgcmVnaXN0ZXJlZCBhdCBhbGw7ICJmYWNlYm9vay5j
b208aHR0cDovL2ZhY2Vib29rLmNvbT4iIHdhcyBkZWxlZ2F0ZWQgdG8gc29tZSBjb21wYW55IHRo
YXQgbm93ICJvd25zIiB0aGF0IHBpZWNlIG9mIHRoZSBuYW1lc3BhY2UgdHJlZSBhbmQgY2FuIGNy
ZWF0ZSB3aGF0ZXZlciBpdCB3YW50cyB1bmRlciB0aGVyZSB3aXRob3V0IGFueSBleHRlcm5hbCBh
cnJhbmdlbWVudC4gIFRvIG15IG1pbmQsICJyZWdpc3RlciIgaW52b2x2ZXMgYSBzcGVjaWZpYyB0
cmFuc2FjdGlvbiwgc29tZXRpbWVzIGludm9sdmluZyBtb25leSwgd2l0aCB3aG9ldmVyIGdhdGVz
IGFjY2VzcyB0byBtYWtlIHRob3NlIGRlbGVnYXRpb25zLg0KDQpBbGwgdGhhdCBuZWVkcyB0byBi
ZSBleHBsYWluZWQgaW4gdGhlIEludHJvZHVjdGlvbiwgbm90IHRoZSBBYnN0cmFjdC4NCkJ1dCB0
aGUgQWJzdHJhY3QgaGFzIHRvIGV4cGxhaW4gZW5vdWdoIGZvciBhIHJlYWRlciB0byB1bmRlcnN0
YW5kIHdoeQ0Kc2hlIG1pZ2h0IG9yIG1pZ2h0IG5vdCBiZSBpbnRlcmVzdGVkIGluIGdldHRpbmcg
dGhlIGRvY3VtZW50IGFuZA0KcmVhZGluZyBpdC4gIFNvIGl0J3MgZ29pbmcgdG8gYmUgdG91Z2gg
dG8gd29yZCBpdCBjYXJlZnVsbHkgYW5kIHRvDQprZWVwIGl0IGNvbmNpc2UuICBCdXQgd2UgaGF2
ZSB0by4NCg0KU3RyZXNzaW5nIGEgcG9pbnQ6DQpXZSB2ZXJ5IGNsZWFybHkgZG8gTk9UIHdhbnQg
dG8gZXhwbGFpbiB0aGlzIHN0dWZmIGluIHRoZSBBYnN0cmFjdC4gIEluDQpmYWN0LCB3ZSBkb24n
dCBoYXZlIHRvIGV4cGxhaW4gbXVjaCBhdCBhbGwgaW4gdGhlIEFic3RyYWN0LiAgV2hhdCB3ZQ0K
aGF2ZSB0byBkbyBpcyBtYWtlIHN1cmUgdGhhdCB0aGUgQWJzdHJhY3QgZG9lc24ndCBzYXkgc3R1
ZmYgdGhhdCdzDQoqd3JvbmcqIG9yIGNvbmZ1c2luZy4gIFNvIGxldCdzIHRyeSB0byBmaW5kIHNv
bWUgZmlmdGgtZ3JhZGUgbGFuZ3VhZ2UNCnRoYXQgY2FuIHN1ZmZpY2UsIGFuZCB0aGVuIG1ha2Ug
c3VyZSB0aGUgSW50cm9kdWN0aW9uIGhhcyB0aGUgcmlnaHQNCndvcmRzIHRvIG1ha2UgaXQgY2xl
YXIgdG8gcGVvcGxlIHdobyBrbm93IGhvdyB0byBkbyBlbWFpbCwgYnV0IHdobw0KZG9uJ3QgYWxy
ZWFkeSB1bmRlcnN0YW5kIHRoZSBpc3N1ZXMgaW52b2x2ZWQgaGVyZS4NCg0KSG93J3MgdGhpcz86
DQoNCg0KICAgRE1BUkMgKERvbWFpbi1iYXNlZCBNZXNzYWdlIEF1dGhlbnRpY2F0aW9uLCBSZXBv
cnRpbmcsIGFuZA0KDQogICBDb25mb3JtYW5jZSkgaXMgYSBzY2FsYWJsZSBtZWNoYW5pc20gYnkg
d2hpY2ggYSBtYWlsLW9yaWdpbmF0aW5nDQoNCiAgIG9yZ2FuaXphdGlvbiBjYW4gZXhwcmVzcyBk
b21haW4tbGV2ZWwgcG9saWNpZXMgYW5kIHByZWZlcmVuY2VzIGZvcg0KDQogICBtZXNzYWdlIHZh
bGlkYXRpb24sIGRpc3Bvc2l0aW9uLCBhbmQgcmVwb3J0aW5nLCB0aGF0IGEgbWFpbC1yZWNlaXZp
bmcNCg0KICAgb3JnYW5pemF0aW9uIGNhbiB1c2UgdG8gaW1wcm92ZSBtYWlsIGhhbmRsaW5nLg0K
DQogICBXaXRoaW4gdGhlIERvbWFpbiBOYW1lIFN5c3RlbSAoRE5TKSBvbiB0aGUgcHVibGljIElu
dGVybmV0LCB3aGljaCBpcw0KDQogICBvcmdhbml6ZWQgYXMgYSB0cmVlLCBzb21lIG5vZGVzIG9m
IHRoYXQgdHJlZSBhcmUgcmVzZXJ2ZWQgZm9yIHVzZSBieQ0KDQogICByZWdpc3RyYXJzLCB3aG8g
ZGVsZWdhdGUgc3ViLXRyZWVzIHRvIG90aGVyIG9wZXJhdG9ycyBvbiByZXF1ZXN0LiAgRE1BUkMg
Y3VycmVudGx5DQogICBwZXJtaXRzIGV4cHJlc3Npb24gb2YgcG9saWN5IG9ubHkgZm9yIHN1Y2gg
c3ViLXRyZWVzLiAgVGhlcmUgaXMgYSBtYXJrZWQgZGVzaXJlIHRvDQoNCiAgIGJlIGFibGUgdG8g
ZXhwcmVzcyBwb2xpY3kgZm9yIHRoZSByZXNlcnZlZCBub2RlcyBhcyB3ZWxsLiAgVGhpcyBkb2N1
bWVudA0KDQogICBkZXNjcmliZXMgYW4gZXhwZXJpbWVudGFsIGV4dGVuc2lvbiB0byBETUFSQyB0
byBhZGQgdGhhdCBjYXBhYmlsaXR5Lg0KDQoNCklmIHdlIGxpa2UgdGhhdCBhcyBhIHJlcGxhY2Vt
ZW50IEFic3RyYWN0LCBJJ2xsIGNhcnJ5IG9uIGFuZCBwcm9wb3NlIGEgcmV2aXNpb24gdG8gdGhl
IEludHJvZHVjdGlvbi4NCg0KLU1TSw0K

--_000_VI1PR01MB705365834B737AF46A2DF099C7819VI1PR01MB7053eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCWZvbnQtc2l6ZTox
MS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFu
Lk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0
ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowY207
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1p
bHk6IkNvdXJpZXIgTmV3Ijt9DQpzcGFuLkhUTUxQcmVmb3JtYXR0ZWRDaGFyDQoJe21zby1zdHls
ZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCglmb250LWZhbWlseTpDb25z
b2xhczsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1JRTt9DQpzcGFuLkVtYWlsU3R5bGUyMA0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQXJpYWwiLHNh
bnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5
bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsN
Cgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6
ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9
DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlk
bWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0
YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxi
b2R5IGxhbmc9IkVOLUlFIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBzdHlsZT0id29yZC13
cmFwOmJyZWFrLXdvcmQiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxmb250IHNpemU9IjIiIGZhY2U9IkFyaWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO21zby1m
YXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQXJpYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNh
bnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkkgd291bGQgZ28gZXZlbiBmdXJ0
aGVyIGFuZCBub3QgZXZlbiB0YWxrIGFib3V0IHRoZSB0cmVlcyBhbmQgbm9kZXMuIEFsc28sIGVj
aG9pbmcgZWxzZXdoZXJlIGluIHRoaXMgdGhyZWFkLCBtYWtpbmcgaXQNCiByZWFsbHkgY2xlYXIg
dGhhdCB0aGlzIGlzIG5vdCBhIGNhc2Ugb2YgPGk+PHNwYW4gc3R5bGU9ImZvbnQtc3R5bGU6aXRh
bGljIj5ETUFSQyBpcyBjb21pbmcgZm9yIHlvdXIgVExEPC9zcGFuPjwvaT4uIFNvLCBJ4oCZZCBw
cm9wb3NlIHNvbWV0aGluZyBzdXBlciBiYXNpYyBsaWtlIHRoaXMgZm9yIHRoZSBzZWNvbmQgcGFy
YWdyYXBoOjxvOnA+PC9vOnA+PC9zcGFuPjwvZm9udD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48Zm9udCBzaXplPSIyIiBmYWNlPSJBcmlhbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1s
YW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9mb250PjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxmb250IHNpemU9IjIi
IGZhY2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Ozttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+
RG9tYWluIG5hbWUgc3VmZml4ZXMgKGZvciBleGFtcGxlIC5jb20sIC5ldSwgYW5kIC5jby51aykg
YXJlIGNvbnRyb2xsZWQgYnkgcmVnaXN0cmllcywgd2hvDQogZWl0aGVyIGRpcmVjdGx5IG9yIHRo
cm91Z2ggYWNjcmVkaXRlZCByZWdpc3RyYXJzLCBmYWNpbGl0YXRlIHRoZSByZWdpc3RyYXRpb24g
YW5kIG1hbmFnZW1lbnQgb2YgZG9tYWluIG5hbWVzIGJlbG93IHRoZXNlIHN1ZmZpeGVzLiBETUFS
QyBjdXJyZW50bHkgcGVybWl0cyBleHByZXNzaW9uIG9mIHBvbGljeSBvbmx5IGZvciBkb21haW4g
bmFtZXMgYW5kIG5vdCBmb3IgZG9tYWluIHN1ZmZpeGVzLiBTaW5jZSBpdHMgZGVwbG95bWVudCBp
biAyMDE1LA0KIHNwZWNpYWxpc3QgdXNlIGNhc2VzIGhhdmUgYmVlbiBpZGVudGlmaWVkIHdoZXJl
IGl0IG1heSBiZSBkZXNpcmFibGUgZm9yIGEgc3VmZml4IHRvIGV4cHJlc3MgYSBETUFSQyBwb2xp
Y3kuIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGFuIGV4cGVyaW1lbnRhbCBleHRlbnNpb24gdG8g
RE1BUkMgdG8gYWRkIHRoYXQgY2FwYWJpbGl0eS48bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQXJpYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNh
bnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvZm9udD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Zm9udCBzaXplPSIyIiBmYWNl
PSJBcmlhbCI+PHNwYW4gbGFuZz0iRU4tR0IiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPktlbi48bzpwPjwvbzpwPjwvc3Bh
bj48L2ZvbnQ+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0i
QXJpYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvZm9udD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRp
dj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBw
dDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxm
b250IHNpemU9IjIiIGZhY2U9IkNhbGlicmkiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LXdlaWdodDpib2xkIj5Gcm9tOjwvc3Bhbj48L2ZvbnQ+PC9iPjxz
cGFuIGxhbmc9IkVOLVVTIj4gZG1hcmMgJmx0O2RtYXJjLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7DQo8
Yj48c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+T24gQmVoYWxmIE9mIDwvc3Bhbj48L2I+
TXVycmF5IFMuIEt1Y2hlcmF3eTxicj4NCjxiPjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xk
Ij5TZW50Ojwvc3Bhbj48L2I+IE1vbmRheSAyMiBGZWJydWFyeSAyMDIxIDA3OjA5PGJyPg0KPGI+
PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPlRvOjwvc3Bhbj48L2I+IEJhcnJ5IExlaWJh
ICZsdDtiYXJyeWxlaWJhQGNvbXB1dGVyLm9yZyZndDs8YnI+DQo8Yj48c3BhbiBzdHlsZT0iZm9u
dC13ZWlnaHQ6Ym9sZCI+Q2M6PC9zcGFuPjwvYj4gRGF2ZSBDcm9ja2VyICZsdDtkY3JvY2tlckBn
bWFpbC5jb20mZ3Q7OyBJRVRGIERNQVJDIFdHICZsdDtkbWFyY0BpZXRmLm9yZyZndDs8YnI+DQo8
Yj48c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDo8L3NwYW4+PC9iPiBSZTog
W2RtYXJjLWlldGZdIEZ3ZDogSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1kbWFyYy1wc2QtMTAudHh0
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxmb250IHNpemU9IjIiIGZhY2U9IkNhbGlicmkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wPg0KPGRpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Zm9udCBzaXplPSIyIiBmYWNlPSJDYWxpYnJpIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+T24gRnJpLCBGZWIgMTksIDIwMjEgYXQgMzowMiBQ
TSBCYXJyeSBMZWliYSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmJhcnJ5bGVpYmFAY29tcHV0ZXIub3Jn
Ij5iYXJyeWxlaWJhQGNvbXB1dGVyLm9yZzwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9zcGFu
PjwvZm9udD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYu
MHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQiPkkgYWdyZWUgdGhhdCB0aGUgYWJzdHJhY3QgaXMgdW5jbGVhci4mbmJzcDsgVGhp
cyBtYWtlcyBubyBzZW5zZSB0byBtZTo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ZG9tYWluIG5h
bWVzIHJlcHJlc2VudCBlaXRoZXIgbm9kZXMgaW4gdGhlIHRyZWUgYmVsb3c8YnI+DQombmJzcDsg
Jm5ic3A7d2hpY2ggcmVnaXN0cmF0aW9ucyBvY2N1ciwgb3Igbm9kZXMgd2hlcmUgcmVnaXN0cmF0
aW9ucyBoYXZlPGJyPg0KJm5ic3A7ICZuYnNwO29jY3VycmVkOyBpdCBkb2VzIG5vdCBwZXJtaXQg
YSBkb21haW4gbmFtZSB0byBoYXZlIGJvdGggb2YgdGhlc2U8YnI+DQombmJzcDsgJm5ic3A7cHJv
cGVydGllcyBzaW11bHRhbmVvdXNseS48YnI+DQo8YnI+DQpJIGRvbid0IHVuZGVyc3RhbmQgdGhl
IGRpc3RpbmN0aW9uIHRoYXQgaXQncyB0cnlpbmcgdG8gbWFrZSBiZXR3ZWVuPGJyPg0KdGhlIHR3
byBwb3NzaWJpbGl0aWVzLjxicj4NCkkgYWxzbyBkb24ndCBzZWUgdGhlIGFudGVjZWRlbnQgdG8g
JnF1b3Q7dGhlc2UgZG9tYWlucyZxdW90OyBpbiB0aGUgZmluYWw8YnI+DQpzZW50ZW5jZSBvZiB0
aGF0IHBhcmFncmFwaC48YnI+DQo8YnI+DQpCZXlvbmQgdGhhdDo8YnI+DQomZ3Q7IEknbSBhdCBh
IGxvc3MgdG8gdW5kZXJzdGFuZCB3aGF0J3MgY29uZnVzaW5nLiZuYnNwOyBJJ20gbm90IGNvbnZp
bmNlZCB0aGF0ICZxdW90O3JlZ2lzdHJhdGlvbnMmcXVvdDsgaW4gdGhlPGJyPg0KJmd0OyBjb250
ZXh0IG9mIGRvbWFpbiBuYW1lcyBpcyB1bmNsZWFyIHRvIGEgcmVhZGVyIGZhbWlsaWFyIHdpdGgg
dGhpcyBzcGFjZS48YnI+DQo8YnI+DQpJIGFtIGFic29sdXRlbHkgY29udmluY2VkIHRoYXQgaXQg
aXMuJm5ic3A7IFRoaW5rIG9mIHBlb3BsZSBpbiBNM0FBV0csIGZvcjxicj4NCndob20gdGhpcyBp
cyB2ZXJ5IHJlbGV2YW50LiZuYnNwOyBNYW55IG9mIHRoZW0gZG9uJ3Qga25vdyBtdWNoIGFib3V0
PGJyPg0KcmVnaXN0cmllcywgcmVnaXN0cmFycywgYW5kIHN1Y2gsIGFuZCBpbiBnZW5lcmFsLCB0
aGUgYXZlcmFnZSByZWFkZXI8YnI+DQp3b24ndCB1bmRlcnN0YW5kIHRoZSBkaWZmZXJlbmNlLCBm
cm9tIGEgJnF1b3Q7cmVnaXN0cmF0aW9uJnF1b3Q7IHN0YW5kcG9pbnQsPGJyPg0KYmV0d2VlbiA8
YSBocmVmPSJodHRwOi8vZmFjZWJvb2suY29tIiB0YXJnZXQ9Il9ibGFuayI+ZmFjZWJvb2suY29t
PC9hPiAod2hpY2ggaXMgcmVnaXN0ZXJlZCkgYW5kICZxdW90OzxhIGhyZWY9Imh0dHA6Ly93d3cu
ZmFjZWJvb2suY29tIiB0YXJnZXQ9Il9ibGFuayI+d3d3LmZhY2Vib29rLmNvbTwvYT4mcXVvdDs8
YnI+DQood2hpY2ggaXMgbm90KS4mbmJzcDsgVG8gdGhlIGF2ZXJhZ2UgcmVhZGVyLCAmcXVvdDs8
YSBocmVmPSJodHRwOi8vZmFjZWJvb2suY29tIiB0YXJnZXQ9Il9ibGFuayI+ZmFjZWJvb2suY29t
PC9hPiZxdW90OyBpcyByZWdpc3RlcmVkPGJyPg0KdW5kZXIgY29tLCBhbmQgJnF1b3Q7PGEgaHJl
Zj0iaHR0cDovL3d3dy5mYWNlYm9vay5jb20iIHRhcmdldD0iX2JsYW5rIj53d3cuZmFjZWJvb2su
Y29tPC9hPiZxdW90OyBpcyByZWdpc3RlcmVkIHVuZGVyIGZhY2Vib29rLiZuYnNwOyBBbmQ8YnI+
DQp0aGUgb25lcyB3aG8gZG9uJ3QgdGhpbmsgdGhhdCB3aWxsIGxpa2VseSBub3QgdW5kZXJzdGFu
ZCB3aHkgd2UgY2FuJ3Q8YnI+DQpqdXN0IHRhbGsgYWJvdXQgc2Vjb25kLWxldmVsIGRvbWFpbnMg
YW5kIGJlIGRvbmUgd2l0aCBpdC48bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wPg0KPC9ibG9j
a3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxmb250IHNpemU9IjIiIGZhY2U9
IkNhbGlicmkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L2ZvbnQ+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQiPkFjdHVhbGx5IHRoYXQncyBhIGNvbW11bml0eSB0aGF0IEkgd291bGQgZXhwZWN0IHRvIGtu
b3cgZXhhY3RseSB3aGF0IGFsbCB0aG9zZSB0ZXJtcyBtZWFuIGFuZCBob3cgdGhleSBhcmUgYWxs
IHJlbGF0ZWQuPG86cD48L286cD48L3NwYW4+PC9mb250PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxmb250IHNpemU9IjIiIGZhY2U9IkNhbGlicmkiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFj
ZT0iQ2FsaWJyaSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPkkgdGhpbmsgdGhlIHVz
ZSBvZiAmcXVvdDtyZWdpc3RlcmVkJnF1b3Q7IHNlZW1zIHRvIGJlIHRoZSBzb3VyY2Ugb2Ygc29t
ZSBvZiB0aGlzIGNvbmZ1c2lvbi4mbmJzcDsgVG8gd29yayB3aXRoIHRoZSBleGFtcGxlIHlvdSBn
YXZlIGhlcmUsIEkgYWdyZWUgdGhhdCAmcXVvdDs8YSBocmVmPSJodHRwOi8vZmFjZWJvb2suY29t
Ij5mYWNlYm9vay5jb208L2E+JnF1b3Q7DQogaXMgcmVnaXN0ZXJlZCAodW5kZXIgJnF1b3Q7Y29t
JnF1b3Q7KSwgYnV0IGRpc2FncmVlIHRoYXQgJnF1b3Q7PGEgaHJlZj0iaHR0cDovL3d3dy5mYWNl
Ym9vay5jb20iPnd3dy5mYWNlYm9vay5jb208L2E+JnF1b3Q7IGlzIHJlZ2lzdGVyZWQgYXQgYWxs
OyAmcXVvdDs8YSBocmVmPSJodHRwOi8vZmFjZWJvb2suY29tIj5mYWNlYm9vay5jb208L2E+JnF1
b3Q7IHdhcyBkZWxlZ2F0ZWQgdG8gc29tZSBjb21wYW55IHRoYXQgbm93ICZxdW90O293bnMmcXVv
dDsgdGhhdCBwaWVjZSBvZiB0aGUgbmFtZXNwYWNlIHRyZWUgYW5kDQogY2FuIGNyZWF0ZSB3aGF0
ZXZlciBpdCB3YW50cyB1bmRlciB0aGVyZSB3aXRob3V0IGFueSBleHRlcm5hbCBhcnJhbmdlbWVu
dC4mbmJzcDsgVG8gbXkgbWluZCwgJnF1b3Q7cmVnaXN0ZXImcXVvdDsgaW52b2x2ZXMgYSBzcGVj
aWZpYyB0cmFuc2FjdGlvbiwgc29tZXRpbWVzIGludm9sdmluZyBtb25leSwgd2l0aCB3aG9ldmVy
IGdhdGVzIGFjY2VzcyB0byBtYWtlIHRob3NlIGRlbGVnYXRpb25zLjxvOnA+PC9vOnA+PC9zcGFu
PjwvZm9udD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Zm9udCBz
aXplPSIyIiBmYWNlPSJDYWxpYnJpIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9mb250PjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzow
Y20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxmb250IHNpemU9IjIiIGZhY2U9IkNhbGlicmkiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0Ij5BbGwgdGhhdCBuZWVkcyB0byBiZSBleHBsYWluZWQgaW4g
dGhlIEludHJvZHVjdGlvbiwgbm90IHRoZSBBYnN0cmFjdC48YnI+DQpCdXQgdGhlIEFic3RyYWN0
IGhhcyB0byBleHBsYWluIGVub3VnaCBmb3IgYSByZWFkZXIgdG8gdW5kZXJzdGFuZCB3aHk8YnI+
DQpzaGUgbWlnaHQgb3IgbWlnaHQgbm90IGJlIGludGVyZXN0ZWQgaW4gZ2V0dGluZyB0aGUgZG9j
dW1lbnQgYW5kPGJyPg0KcmVhZGluZyBpdC4mbmJzcDsgU28gaXQncyBnb2luZyB0byBiZSB0b3Vn
aCB0byB3b3JkIGl0IGNhcmVmdWxseSBhbmQgdG88YnI+DQprZWVwIGl0IGNvbmNpc2UuJm5ic3A7
IEJ1dCB3ZSBoYXZlIHRvLjxicj4NCjxicj4NClN0cmVzc2luZyBhIHBvaW50Ojxicj4NCldlIHZl
cnkgY2xlYXJseSBkbyBOT1Qgd2FudCB0byBleHBsYWluIHRoaXMgc3R1ZmYgaW4gdGhlIEFic3Ry
YWN0LiZuYnNwOyBJbjxicj4NCmZhY3QsIHdlIGRvbid0IGhhdmUgdG8gZXhwbGFpbiBtdWNoIGF0
IGFsbCBpbiB0aGUgQWJzdHJhY3QuJm5ic3A7IFdoYXQgd2U8YnI+DQpoYXZlIHRvIGRvIGlzIG1h
a2Ugc3VyZSB0aGF0IHRoZSBBYnN0cmFjdCBkb2Vzbid0IHNheSBzdHVmZiB0aGF0J3M8YnI+DQoq
d3JvbmcqIG9yIGNvbmZ1c2luZy4mbmJzcDsgU28gbGV0J3MgdHJ5IHRvIGZpbmQgc29tZSBmaWZ0
aC1ncmFkZSBsYW5ndWFnZTxicj4NCnRoYXQgY2FuIHN1ZmZpY2UsIGFuZCB0aGVuIG1ha2Ugc3Vy
ZSB0aGUgSW50cm9kdWN0aW9uIGhhcyB0aGUgcmlnaHQ8YnI+DQp3b3JkcyB0byBtYWtlIGl0IGNs
ZWFyIHRvIHBlb3BsZSB3aG8ga25vdyBob3cgdG8gZG8gZW1haWwsIGJ1dCB3aG88YnI+DQpkb24n
dCBhbHJlYWR5IHVuZGVyc3RhbmQgdGhlIGlzc3VlcyBpbnZvbHZlZCBoZXJlLjxvOnA+PC9vOnA+
PC9zcGFuPjwvZm9udD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvZm9udD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Zm9udCBzaXplPSIyIiBmYWNlPSJDYWxpYnJpIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+SG93J3MgdGhpcz86DQo8bzpwPjwvbzpwPjwv
c3Bhbj48L2ZvbnQ+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGZv
bnQgc2l6ZT0iMiIgZmFjZT0iQ2FsaWJyaSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvZm9udD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cHJl
Pjxmb250IHNpemU9IjIiIGZhY2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdCI+Jm5ic3A7Jm5ic3A7IERNQVJDIChEb21haW4tYmFzZWQgTWVzc2FnZSBBdXRoZW50
aWNhdGlvbiwgUmVwb3J0aW5nLCBhbmQ8bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wcmU+DQo8
cHJlPjxmb250IHNpemU9IjIiIGZhY2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdCI+Jm5ic3A7Jm5ic3A7IENvbmZvcm1hbmNlKSBpcyBhIHNjYWxhYmxlIG1lY2hh
bmlzbSBieSB3aGljaCBhIG1haWwtb3JpZ2luYXRpbmc8bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+
PC9wcmU+DQo8cHJlPjxmb250IHNpemU9IjIiIGZhY2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdCI+Jm5ic3A7Jm5ic3A7IG9yZ2FuaXphdGlvbiBjYW4gZXhwcmVz
cyBkb21haW4tbGV2ZWwgcG9saWNpZXMgYW5kIHByZWZlcmVuY2VzIGZvcjxvOnA+PC9vOnA+PC9z
cGFuPjwvZm9udD48L3ByZT4NCjxwcmU+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ291cmllciBOZXci
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4mbmJzcDsmbmJzcDsgbWVzc2FnZSB2YWxp
ZGF0aW9uLCBkaXNwb3NpdGlvbiwgYW5kIHJlcG9ydGluZywgdGhhdCBhIG1haWwtcmVjZWl2aW5n
PG86cD48L286cD48L3NwYW4+PC9mb250PjwvcHJlPg0KPHByZSBzdHlsZT0ibWFyZ2luLWJvdHRv
bToxMi4wcHQiPjxmb250IHNpemU9IjIiIGZhY2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdCI+Jm5ic3A7Jm5ic3A7IG9yZ2FuaXphdGlvbiBjYW4gdXNlIHRvIGlt
cHJvdmUgbWFpbCBoYW5kbGluZy48bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wcmU+DQo8cHJl
Pjxmb250IHNpemU9IjIiIGZhY2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdCI+Jm5ic3A7Jm5ic3A7IFdpdGhpbiB0aGUgRG9tYWluIE5hbWUgU3lzdGVtIChETlMp
IG9uIHRoZSBwdWJsaWMgSW50ZXJuZXQsIHdoaWNoIGlzPG86cD48L286cD48L3NwYW4+PC9mb250
PjwvcHJlPg0KPHByZT48Zm9udCBzaXplPSIyIiBmYWNlPSJDb3VyaWVyIE5ldyI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiZuYnNwOyZuYnNwOyBvcmdhbml6ZWQgYXMgYSB0cmVlLCBz
b21lIG5vZGVzIG9mIHRoYXQgdHJlZSBhcmUgcmVzZXJ2ZWQgZm9yIHVzZSBieTxvOnA+PC9vOnA+
PC9zcGFuPjwvZm9udD48L3ByZT4NCjxwcmU+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ291cmllciBO
ZXciPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4mbmJzcDsmbmJzcDsgcmVnaXN0cmFy
cywgd2hvIGRlbGVnYXRlIHN1Yi10cmVlcyB0byBvdGhlciBvcGVyYXRvcnMgb24gcmVxdWVzdC4m
bmJzcDsgRE1BUkMgY3VycmVudGx5PGJyPiZuYnNwOyZuYnNwOyBwZXJtaXRzIGV4cHJlc3Npb24g
b2YgcG9saWN5IG9ubHkgZm9yIHN1Y2ggc3ViLXRyZWVzLiZuYnNwOyBUaGVyZSBpcyBhIG1hcmtl
ZCBkZXNpcmUgdG88bzpwPjwvbzpwPjwvc3Bhbj48L2ZvbnQ+PC9wcmU+DQo8cHJlPjxmb250IHNp
emU9IjIiIGZhY2U9IkNvdXJpZXIgTmV3Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+
Jm5ic3A7Jm5ic3A7IGJlIGFibGUgdG8gZXhwcmVzcyBwb2xpY3kgZm9yIHRoZSByZXNlcnZlZCBu
b2RlcyBhcyB3ZWxsLiZuYnNwOyBUaGlzIGRvY3VtZW50PG86cD48L286cD48L3NwYW4+PC9mb250
PjwvcHJlPg0KPHByZT48Zm9udCBzaXplPSIyIiBmYWNlPSJDb3VyaWVyIE5ldyI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiZuYnNwOyZuYnNwOyBkZXNjcmliZXMgYW4gZXhwZXJpbWVu
dGFsIGV4dGVuc2lvbiB0byBETUFSQyB0byBhZGQgdGhhdCBjYXBhYmlsaXR5LjxvOnA+PC9vOnA+
PC9zcGFuPjwvZm9udD48L3ByZT4NCjxwcmU+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQ291cmllciBO
ZXciPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L2ZvbnQ+PC9wcmU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Zm9udCBzaXplPSIyIiBmYWNl
PSJDYWxpYnJpIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+SWYgd2UgbGlrZSB0aGF0
IGFzIGEgcmVwbGFjZW1lbnQgQWJzdHJhY3QsIEknbGwgY2Fycnkgb24gYW5kIHByb3Bvc2UgYSBy
ZXZpc2lvbiB0byB0aGUgSW50cm9kdWN0aW9uLjxicj4NCjxicj4NCi1NU0s8bzpwPjwvbzpwPjwv
c3Bhbj48L2ZvbnQ+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_VI1PR01MB705365834B737AF46A2DF099C7819VI1PR01MB7053eurp_--


From nobody Mon Feb 22 07:22: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 BEB483A198E for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 07:22:42 -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, FREEMAIL_FROM=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 xC6bC70rRvfc for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 07:22:41 -0800 (PST)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (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 695FF3A0BBC for <dmarc@ietf.org>; Mon, 22 Feb 2021 07:21:10 -0800 (PST)
Received: by mail-oi1-x22c.google.com with SMTP id x20so2263216oie.11 for <dmarc@ietf.org>; Mon, 22 Feb 2021 07:21:10 -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=eQWUOTr2iBlEYRExBbKyJKgHbVNVEngBlLQSUc8i004=; b=XthClWvD5b6GW0Jr91nDErhA3kaIJH7pJ4zd+85cHd7mElDELkAQ/hILnF4oKljlg4 myUE8mDe8rEOcxBN+zQM1PmpjOB1Mg7ZTnt2aVIZ+1kpVtzU2280Y0rrTQPP/UULKYKi TWmHKoIyd5TJNC/bv1qHLNm7Y1zDSie6eD5FnkdEZeS2VpKobSskqkmk/DOU208ByTCj DFDewe8jT64lVZ/nD1m8R340ZvBSMNkx3g2eOeeXJEQUYhqJlphw8BRCy/ZAuqtd2FGu 4msP0Hk7CLiDfhJwgeOY54fEHmQ+GENS/zLUyax9yBym5BOaLpnpQHfV4JwGOUoYgehk vuZw==
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=eQWUOTr2iBlEYRExBbKyJKgHbVNVEngBlLQSUc8i004=; b=h0TtzuTWI+SfrXyV1FfUNKLMZjLvKFqGnQ0l65LWz60dhdvdI/oURmQ8CgkKxmVxdk KqBJCInaDSuJTbeWhOWfpCVCXDD1yZ2jjYCiScUPAL59ruWaWEF02DRTLF2sfWClm9ak cJJTy5YV0UxdCI4Z0wBsHVIbig72BWRQZo+bIL3Ihvs9VLQh2xgG13KXavoRZnPREMZK Zqx64DjtAQ+WewyTcdnjH7/lVKdUX9l7GbCiBQrVva66aPZS/Tw+ij0U/iM6z0Ye4G+p YXlkM2RiwJDIFmcGRXSpcE/Q6OnPS++bM2jG8yxFwIywFAcg6ylYzQrHcpHH2A6d0eOW XWEw==
X-Gm-Message-State: AOAM533y5NGZ7al1eBeU2hl+BtzqQUsxJaG99fbVPX/QQbuOFPSGGnwb /E/Kh29I4trHz88FzmdPoqRxmeS92A5JxA==
X-Google-Smtp-Source: ABdhPJzjHhZ9inHG/GYY2bGJCEsvoYc+N1Y6m8EOUNBBdhhBTMDoOmKDARkSz0nazE+2gi/dWjBAdw==
X-Received: by 2002:aca:1708:: with SMTP id j8mr15809809oii.29.1614007269533;  Mon, 22 Feb 2021 07:21:09 -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 u81sm2567007oie.46.2021.02.22.07.21.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 22 Feb 2021 07:21:09 -0800 (PST)
To: Barry Leiba <barryleiba@computer.org>, "Murray S. Kucherawy" <superuser@gmail.com>
Cc: 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> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <2e2b6204-244d-dd6f-dced-e4318562710c@gmail.com>
Date: Mon, 22 Feb 2021 07:21:06 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@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/3_eXEEN0KmQZB9Ufq5EoEe6r-2U>
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: Mon, 22 Feb 2021 15:22:49 -0000

>>> Actually that's a community that I would expect to know exactly what all those terms mean and
>>> how they are all related.

yes. But it's worse than that.  The current language is not 
automatically clear even for folk with good knowledge about DNS 
administration.

As is being noted, I too think a great deal of the problem is 
over-reliance on the word register.

It is being used as if it explains a basic difference in administrative 
roles.  It doesn't.  Not even close.


>> To work with the example you gave here, I agree that "facebook.com" is registered (under "com"), but
>> disagree that "www.facebook.com" is registered at all;
> Right, of course it's not.

I disagree.  Strongly.  The fact that one registration is internal and 
another is through a third-party, semi-regulated service does not make a 
difference, for the use of that word.

I work with an organization that has an IT department that is just as 
formal typical ICANN-authorized registries.  To get a sub-domain is a 
Very Big Deal.  Don't think for a moment that it is fundamentally 
different than interacting with the TLD registeries.


> I didn't say that it is: I said that
> people who don't fully understand this stuff *think* it is, and that's
> the part that the text isn't making clear.
>
>> To my mind, "register" involves a specific transaction, sometimes involving money, with whoever gates
>> access to make those delegations.

How much do you pay to register to vote?

However the rest of the above statement is correct.  A transaction to 
record gain access to a resource or to reserve access to it.

Registration is a process of signing up.  That's all.  And it says 
nothing about the role or relationship of the entity the registration is 
with.



d/


-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Mon Feb 22 07:49: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 0FA033A1C98 for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 07:49:29 -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 an7M_L-MtuvX for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 07:49:27 -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 677463A1D2F for <dmarc@ietf.org>; Mon, 22 Feb 2021 07:49:27 -0800 (PST)
Received: by mail-ua1-x92f.google.com with SMTP id o31so4482737uae.2 for <dmarc@ietf.org>; Mon, 22 Feb 2021 07:49: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;  bh=/Zgdx0iBbaHN7B1b2DUiLDmc5dJQH6Xuill16MGA1Tg=; b=qYX2vWj1Na3pLISgOZKA2NrePYxP4VjERke05j6OSMAapgNBX8nvIqCkA3N3WIQpcJ W9ZjKFmbb5V8C4mxoVDrxs1R56YLwkoJAItHE/tUAh9qmCI6TQ59QlSu3InMyieJn0mO SPTsTnDxOCBoSGqCg+eBJM558KIrog1F4iEuC4A8HDp58AQOOxpRsDUIPIYeMJGvj2K2 9xRY+pWoBZclnPtyHHGMwbjLt+SphS24tMWVMw7pIG3THym7zAo57+t6vrK99eFxSTEr Rl5dz3dbjJGUyH/eVX/fSL5qkIRkFYpS6AGdJTg3kLKeM6O2qs4CrWzpKpAsiHzOHMw2 ooog==
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=/Zgdx0iBbaHN7B1b2DUiLDmc5dJQH6Xuill16MGA1Tg=; b=WXMoFZcyFqBPPwsKTs/vrsN1znf7hMekiKiyt4M4LjiRKUhlaFw9iD+hmnF/S6936E z3o1z544gp28XEzUB0ffnwAu9V255qHENKLJfoKHCpYbu7teeUeyaoUsi5ESOc7wskhO 5iQg5n2UdCEimaQsNOnJ3mcmBB7P/Jx6dg5AB8/hxxTkAa2DqaQpZ18bMFuibB75KNYi Af4j7NbOV/m3iOKUHFlMoXAk1bvjTJTIEmHvG0P1x9EbtmbozAH6FKKei3bgVUVEgiWe k3LQ3nXAM19dy9TPHpbck7+lgMI4yuD7aweGqQQc4sfHAlevoy4OMzhK68Fj9wsl5MFL t2YQ==
X-Gm-Message-State: AOAM533AtzH5NgdzdMUYwm/FE4wE8iTs/3YnlZYY2b4WA+OOJW+b/647 oGI97vchjUOJhdfoq8csbKbTABXJQ7rOoyfIaipO4C1N
X-Google-Smtp-Source: ABdhPJwCcHFI8WmiJynL2nMsydplK8caSwcuLxyaYKmjz538sxa7BCbhE/pCG/mncxyc01Mddtijah+0/A6kwp9M/aY=
X-Received: by 2002:ab0:5e6:: with SMTP id e93mr13868835uae.109.1614008966162;  Mon, 22 Feb 2021 07:49:26 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <2e2b6204-244d-dd6f-dced-e4318562710c@gmail.com>
In-Reply-To: <2e2b6204-244d-dd6f-dced-e4318562710c@gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 22 Feb 2021 10:49:13 -0500
Message-ID: <CAH48ZfwzBHQz7x95nFOnr69gXXAUjKhxkgC+1WN97=i535_s0w@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000017ad8205bbeebf65"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/sqJBOItOcRmV-YQ39eFGRGbWw-g>
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: Mon, 22 Feb 2021 15:49:29 -0000

--00000000000017ad8205bbeebf65
Content-Type: text/plain; charset="UTF-8"

So what is the best nomenclature for referring to the "ICANN-authorized
registries"?   Dave's phrase or something else?

On Mon, Feb 22, 2021, 10:26 AM Dave Crocker <dcrocker@gmail.com> wrote:

>
> >>> Actually that's a community that I would expect to know exactly what
> all those terms mean and
> >>> how they are all related.
>
> yes. But it's worse than that.  The current language is not
> automatically clear even for folk with good knowledge about DNS
> administration.
>
> As is being noted, I too think a great deal of the problem is
> over-reliance on the word register.
>
> It is being used as if it explains a basic difference in administrative
> roles.  It doesn't.  Not even close.
>
>
> >> To work with the example you gave here, I agree that "facebook.com" is
> registered (under "com"), but
> >> disagree that "www.facebook.com" is registered at all;
> > Right, of course it's not.
>
> I disagree.  Strongly.  The fact that one registration is internal and
> another is through a third-party, semi-regulated service does not make a
> difference, for the use of that word.
>
> I work with an organization that has an IT department that is just as
> formal typical ICANN-authorized registries.  To get a sub-domain is a
> Very Big Deal.  Don't think for a moment that it is fundamentally
> different than interacting with the TLD registeries.
>
>
> > I didn't say that it is: I said that
> > people who don't fully understand this stuff *think* it is, and that's
> > the part that the text isn't making clear.
> >
> >> To my mind, "register" involves a specific transaction, sometimes
> involving money, with whoever gates
> >> access to make those delegations.
>
> How much do you pay to register to vote?
>
> However the rest of the above statement is correct.  A transaction to
> record gain access to a resource or to reserve access to it.
>
> Registration is a process of signing up.  That's all.  And it says
> nothing about the role or relationship of the entity the registration is
> with.
>
>
>
> 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
>

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

<div dir=3D"auto">So what is the best nomenclature for referring to the &qu=
ot;ICANN-authorized registries&quot;?=C2=A0 =C2=A0Dave&#39;s phrase or some=
thing else?</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Mon, Feb 22, 2021, 10:26 AM Dave Crocker &lt;<a href=3D"mailt=
o:dcrocker@gmail.com">dcrocker@gmail.com</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><br>
&gt;&gt;&gt; Actually that&#39;s a community that I would expect to know ex=
actly what all those terms mean and<br>
&gt;&gt;&gt; how they are all related.<br>
<br>
yes. But it&#39;s worse than that.=C2=A0 The current language is not <br>
automatically clear even for folk with good knowledge about DNS <br>
administration.<br>
<br>
As is being noted, I too think a great deal of the problem is <br>
over-reliance on the word register.<br>
<br>
It is being used as if it explains a basic difference in administrative <br=
>
roles.=C2=A0 It doesn&#39;t.=C2=A0 Not even close.<br>
<br>
<br>
&gt;&gt; To work with the example you gave here, I agree that &quot;<a href=
=3D"http://facebook.com" rel=3D"noreferrer noreferrer" target=3D"_blank">fa=
cebook.com</a>&quot; is registered (under &quot;com&quot;), but<br>
&gt;&gt; disagree that &quot;<a href=3D"http://www.facebook.com" rel=3D"nor=
eferrer noreferrer" target=3D"_blank">www.facebook.com</a>&quot; is registe=
red at all;<br>
&gt; Right, of course it&#39;s not.<br>
<br>
I disagree.=C2=A0 Strongly.=C2=A0 The fact that one registration is interna=
l and <br>
another is through a third-party, semi-regulated service does not make a <b=
r>
difference, for the use of that word.<br>
<br>
I work with an organization that has an IT department that is just as <br>
formal typical ICANN-authorized registries.=C2=A0 To get a sub-domain is a =
<br>
Very Big Deal.=C2=A0 Don&#39;t think for a moment that it is fundamentally =
<br>
different than interacting with the TLD registeries.<br>
<br>
<br>
&gt; I didn&#39;t say that it is: I said that<br>
&gt; people who don&#39;t fully understand this stuff *think* it is, and th=
at&#39;s<br>
&gt; the part that the text isn&#39;t making clear.<br>
&gt;<br>
&gt;&gt; To my mind, &quot;register&quot; involves a specific transaction, =
sometimes involving money, with whoever gates<br>
&gt;&gt; access to make those delegations.<br>
<br>
How much do you pay to register to vote?<br>
<br>
However the rest of the above statement is correct.=C2=A0 A transaction to =
<br>
record gain access to a resource or to reserve access to it.<br>
<br>
Registration is a process of signing up.=C2=A0 That&#39;s all.=C2=A0 And it=
 says <br>
nothing about the role or relationship of the entity the registration is <b=
r>
with.<br>
<br>
<br>
<br>
d/<br>
<br>
<br>
-- <br>
Dave Crocker<br>
<a href=3D"mailto:dcrocker@gmail.com" target=3D"_blank" rel=3D"noreferrer">=
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" rel=3D"nore=
ferrer">dave.crocker2@redcross.org</a><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>

--00000000000017ad8205bbeebf65--


From nobody Mon Feb 22 08:14:31 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 2D5763A1D7E for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 08:14:30 -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, FREEMAIL_FROM=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 tSI9rdDkXSMV for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 08:14:29 -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 0EFF53A1D7F for <dmarc@ietf.org>; Mon, 22 Feb 2021 08:14:29 -0800 (PST)
Received: by mail-oo1-xc2f.google.com with SMTP id x10so3093279oor.3 for <dmarc@ietf.org>; Mon, 22 Feb 2021 08:14:29 -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=SFF483MNNRTqjBZDyODQ7ZdcgYOhLrwIxAIfCICyQoI=; b=kQ8Tm/J70fSqbaMI8Z/wvDLUf6wz5ISA0n9k9PWNi9HqnMBXqg8gY9EtvPGyQWvd3W acv9TsPpdYmGXkxvVCa2DncKQAgWIdqqEf3MaoN6DyQjI+TSsW+SH9eKohjdSwHBbJXM C058EGQ5ubLibD0XvUexECLOPWyvl7xgl1qKa1SEd81HxTZKl9R5fIk0SOXG17o3gqD8 a4UIfEg82tck0Sv9lyn5cCOXu0KcCOTrWtcPSZlZJ/HL0s2bdG3zd14XbLuCyukjaHRF nuW8MxrVpZqOaJoug1vMvCJnRg6PYR0Msh6zb6uxbs1ed+A4pZuHkpEwv535oou7XeDb ozuw==
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=SFF483MNNRTqjBZDyODQ7ZdcgYOhLrwIxAIfCICyQoI=; b=lirfXV+9GkxY2KR2o2wy6PrBgZ9XOm0m7VRXiffS4AXAmYpEiU2BFahEGnsHY4BDcY iT96Pf200lEnzjTtFedage3cqyaz5Xh3gkLJhFeXWjLQsypfGMMuQDhJl2ncLidQJ21R rC3YoacOc6u1Tb/O9ZHKE6hKL/Ln3V6Jpv+9br/n/4oXqfWv/bXH+sL/7RH8i+l06PmE x4xOssYLMEiE082hTmEInZytKT5/f3SqV8Ja2W5xQhYgs2Ex+5U4FyGLfLwuSd2cp2iK SLqT8EqzivTbVOlK9Oi2GRWrvx/T5BiuaPd1YBHzDGhU9lmG39kna3W7Oe4xGQcp4feW 00mA==
X-Gm-Message-State: AOAM532AmxU7j1cavXw/AKzoWAUxRH+svNkr0d+FhJY+wHUTTbMy3B/8 tCA9BVnmGXYJIr245wGVh4ZtBF58HyjhiA==
X-Google-Smtp-Source: ABdhPJyYa4WoE6R0NgU/uLRhBLR1owmPCikiRxAag89lPINZCMfF7xuNC3zsIsSjAZ+obhHYS+3AYA==
X-Received: by 2002:a4a:9251:: with SMTP id g17mr17066727ooh.87.1614010468216;  Mon, 22 Feb 2021 08:14:28 -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 a7sm1187826oon.8.2021.02.22.08.14.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 22 Feb 2021 08:14:27 -0800 (PST)
To: Douglas Foster <dougfoster.emailstandards@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> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <2e2b6204-244d-dd6f-dced-e4318562710c@gmail.com> <CAH48ZfwzBHQz7x95nFOnr69gXXAUjKhxkgC+1WN97=i535_s0w@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <404eeea5-edbd-b795-57f4-801bb662ceac@gmail.com>
Date: Mon, 22 Feb 2021 08:14:25 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <CAH48ZfwzBHQz7x95nFOnr69gXXAUjKhxkgC+1WN97=i535_s0w@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/GGWO-8_Im_QlUS2mrjnIkSMpxnk>
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: Mon, 22 Feb 2021 16:14:30 -0000

On 2/22/2021 7:49 AM, Douglas Foster wrote:
> So what is the best nomenclature for referring to the 
> "ICANN-authorized registries"?   Dave's phrase or something else?

Strictly speaking co.uk is not ICAN-authorized.  It's authorized by 
mechanisms internal to the UK.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Mon Feb 22 08:24:49 2021
Return-Path: <ned+dmarc@mrochek.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02C633A1D98 for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 08:24:48 -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=mrochek.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 lVhe7aN7Sbzh for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 08:24:46 -0800 (PST)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (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 ADFD53A1DFF for <dmarc@ietf.org>; Mon, 22 Feb 2021 08:24:34 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RVVIYNZBR400FDM8@mauve.mrochek.com> for dmarc@ietf.org; Mon, 22 Feb 2021 08:19:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1614010770; bh=Jrau8+BFj56mNtdmUyEg3JvaKGxisjn0Q4LCs2GvRI0=;  h=From:Cc:Date:Subject:In-reply-to:References:To:From; b=rxbjT3q8VctzXBed9+Q8nL9eY8lxZRxylKT51nBjvpffFIEyO/lTqI+8sme4ts2DC gGKwn4PZrL7ZwHexwXi8JxtC93HsiIhOj9nWDGW3dp5zyFWlziSGeoGZO3bcMXAdio vM9+A5oGP/R3zumHGE1S+x3bxei5rbIHhH8ply6A=
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: TEXT/PLAIN; charset=utf-8; Format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RVQNM60R7K005PTU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for dmarc@ietf.org; Mon, 22 Feb 2021 08:19:28 -0800 (PST)
From: ned+dmarc@mrochek.com
Cc: Barry Leiba <barryleiba@computer.org>, "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Message-id: <01RVVIYLSMP6005PTU@mauve.mrochek.com>
Date: Mon, 22 Feb 2021 08:13:18 -0800 (PST)
In-reply-to: "Your message dated Mon, 22 Feb 2021 07:21:06 -0800" <2e2b6204-244d-dd6f-dced-e4318562710c@gmail.com>
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> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <2e2b6204-244d-dd6f-dced-e4318562710c@gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/_sr4VXBpV7w80IxiwLh36XBsRmE>
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: Mon, 22 Feb 2021 16:24:48 -0000

> >>> Actually that's a community that I would expect to know exactly what all those terms mean and
> >>> how they are all related.

> yes. But it's worse than that.  The current language is not
> automatically clear even for folk with good knowledge about DNS
> administration.

> As is being noted, I too think a great deal of the problem is
> over-reliance on the word register.

> It is being used as if it explains a basic difference in administrative
> roles.  It doesn't.  Not even close.


> >> To work with the example you gave here, I agree that "facebook.com" is registered (under "com"), but
> >> disagree that "www.facebook.com" is registered at all;

> > Right, of course it's not.

> I disagree.  Strongly.  The fact that one registration is internal and
> another is through a third-party, semi-regulated service does not make a
> difference, for the use of that word.

> I work with an organization that has an IT department that is just as
> formal typical ICANN-authorized registries.  To get a sub-domain is a
> Very Big Deal.  Don't think for a moment that it is fundamentally
> different than interacting with the TLD registeries.

Wow, I didn't know you had started working for Oracle! Welcome aboard! ;-)

Seriously, this is the rule, not the exception, with large organizations,
especially those that assign significant value to their domain reputations.
There are all kinds of hoops you have to jump through before you'll be able to
get a sub-domain, or for that matter a different name with the company name
embedded in it. And after it's registered, there are ongoing maintenance
requirements.

Registering a domain with, say, GoDaddy is a triviality by comparison.

The SSL certificate situation adds even more complexity, but fortunately
that's not relevant here.

> > I didn't say that it is: I said that
> > people who don't fully understand this stuff *think* it is, and that's
> > the part that the text isn't making clear.

> >> To my mind, "register" involves a specific transaction, sometimes involving money, with whoever gates
> >> access to make those delegations.

> How much do you pay to register to vote?

> However the rest of the above statement is correct.  A transaction to
> record gain access to a resource or to reserve access to it.

> Registration is a process of signing up.  That's all.  And it says
> nothing about the role or relationship of the entity the registration is
> with.

Yep.

				Ned


From nobody Mon Feb 22 08:54:31 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 BF83D3A1DBB for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 08:54:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.097
X-Spam-Level: 
X-Spam-Status: No, score=-6.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_HI=-5, 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 zEJtGhUBVWNl for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 08:54:28 -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 4051D3A1A1D for <dmarc@ietf.org>; Mon, 22 Feb 2021 08:54:28 -0800 (PST)
Received: by mail-ua1-x930.google.com with SMTP id d3so4539803uap.4 for <dmarc@ietf.org>; Mon, 22 Feb 2021 08:54: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=JNUkPvJCeVJkQ6ehZQeNcsHF0uyzs4uYz79edgRyRcU=; b=MsK3UYpQmpp3Z0YlYCy6j+fgheXIccNFVnX6EqFZNdv6FZUT9svhNgTH3oGanD7SKW vDWTLJNMb+ocLkyNw7RFsUhS9vqbtSRgs72elYppl6OBXZiHiWbyYNCeljjIxyp6Imkl puEhiF2gSPyc/lnccTrRLhafAhihz0dNCi3FnCaoJ3qIxtTGFZ8LtZO2FW6MBXSyC39m i+oXFIifM0NBH0zU98s0f1P1T7BYzOw5FU6U2LVjiaKX/vf3RWho1imF/31Uxm0Ft93i X/o52OvCjlUVsknqAKNQGoDLIXVNP+m4pMbi/4mhHlMgm7haZwPGvDJBx4TCTOGdStG4 25rg==
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=JNUkPvJCeVJkQ6ehZQeNcsHF0uyzs4uYz79edgRyRcU=; b=HJNgRdmdD/gaO+dfO1Yvuujsl9zYw0hYaBJKFlDG+TpOcA03C32Zk4owatGKdiswx+ BowKPm3Y43IgMrMnzS7XGuSUs1JTjfs0CxmMmafdqhL2aPtPovqnosBk8hCgKhUIvnPG CPv2D3vElXedZJRuIfu4haevU1Tm1K4dfV/M7JscPYgOsFGhrxGHgRsZxxMyYhrJzXPh 937Qm9f7K1jbYSCItcLzO9KYbs4vwHanuMDYo7cQnjXU3b4AF6CorB65zb2K+OH48kFt mb6q1guWS/vwoVlSEZM6u7U/44ZpYiC5NLgf3ooQBV7w1cLUSgGqmoJ6tIGx8/UvaPd4 nqQA==
X-Gm-Message-State: AOAM533TT0VJhzoUYgb6AGyyn+234jmLb+1idCnh3ZtpVBrz76T/SkQg XfKB8M0KSOYsjhzm7S2Osj7py7231BUBA5z/D8Byam6S
X-Google-Smtp-Source: ABdhPJze5Y7ZJ5IcNHi6iAkYIxDYdKvpk8nySy948Q6sUKVWcilQjvvFCkNeNHvPzZdCe4Zk+R+iuyJx975NDXzi1No=
X-Received: by 2002:ab0:5e6:: with SMTP id e93mr14145889uae.109.1614012867088;  Mon, 22 Feb 2021 08:54:27 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <2e2b6204-244d-dd6f-dced-e4318562710c@gmail.com> <CAH48ZfwzBHQz7x95nFOnr69gXXAUjKhxkgC+1WN97=i535_s0w@mail.gmail.com> <404eeea5-edbd-b795-57f4-801bb662ceac@gmail.com>
In-Reply-To: <404eeea5-edbd-b795-57f4-801bb662ceac@gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 22 Feb 2021 11:54:14 -0500
Message-ID: <CAH48ZfzZkHMuw4r=cs=ApcRY-PquFBMVKDrVDRLmZbAyLGA_Eg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009b166405bbefa765"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/-LVKBb_-IejvvTwk67zmBLKDvp4>
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: Mon, 22 Feb 2021 16:54:30 -0000

--0000000000009b166405bbefa765
Content-Type: text/plain; charset="UTF-8"

That does not answer the question.  We can only clarify the registration
question by clarifying what entity's registration mechanism is in scope.

Do we simply say that this document applies to registrations occurring
immediately below an entry on the PSL?

On Mon, Feb 22, 2021, 11:14 AM Dave Crocker <dcrocker@gmail.com> wrote:

> On 2/22/2021 7:49 AM, Douglas Foster wrote:
> > So what is the best nomenclature for referring to the
> > "ICANN-authorized registries"?   Dave's phrase or something else?
>
> Strictly speaking co.uk is not ICAN-authorized.  It's authorized by
> mechanisms internal to the UK.
>
> d/
>
> --
> Dave Crocker
> dcrocker@gmail.com
> 408.329.0791
>
> Volunteer, Silicon Valley Chapter
> American Red Cross
> dave.crocker2@redcross.org
>
>

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

<div dir=3D"auto">That does not answer the question.=C2=A0 We can only clar=
ify the registration question by clarifying what entity&#39;s registration =
mechanism is in scope.<div dir=3D"auto"><br></div><div dir=3D"auto">Do we s=
imply say that this document applies to registrations occurring immediately=
 below an entry on the PSL?</div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Mon, Feb 22, 2021, 11:14 AM Dave Crocke=
r &lt;<a href=3D"mailto:dcrocker@gmail.com" target=3D"_blank" rel=3D"norefe=
rrer">dcrocker@gmail.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 2/22/2021 7:49 AM, Douglas Foster wrote:<br>
&gt; So what is the best nomenclature for referring to the <br>
&gt; &quot;ICANN-authorized registries&quot;?=C2=A0 =C2=A0Dave&#39;s phrase=
 or something else?<br>
<br>
Strictly speaking <a href=3D"http://co.uk" rel=3D"noreferrer noreferrer nor=
eferrer" target=3D"_blank">co.uk</a> is not ICAN-authorized.=C2=A0 It&#39;s=
 authorized by <br>
mechanisms internal to the UK.<br>
<br>
d/<br>
<br>
-- <br>
Dave Crocker<br>
<a href=3D"mailto:dcrocker@gmail.com" rel=3D"noreferrer noreferrer" 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" rel=3D"noreferrer noreferrer"=
 target=3D"_blank">dave.crocker2@redcross.org</a><br>
<br>
</blockquote></div>

--0000000000009b166405bbefa765--


From nobody Mon Feb 22 09:00:24 2021
Return-Path: <ken@wemonitoremail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A12663A1E09 for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 09:00:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.801
X-Spam-Level: 
X-Spam-Status: No, score=-2.801 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_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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=wemonitoremail.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 M5dCqQZsWPGb for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 09:00:16 -0800 (PST)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on2099.outbound.protection.outlook.com [40.107.21.99]) (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 72BEF3A1DF6 for <dmarc@ietf.org>; Mon, 22 Feb 2021 09:00:16 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=odOWHeFbKiXKLKxlOU1rvNnW+6n3tAHRgpzn9mz0tumms0bEGKy99o8syfxwqHJyc+sUdoslGOWW5LyLEzQm9gj3biJOiqKCQDqSXwwixBdHoJUeSgLOyZ+32090Bje0zSrY8eyUIjpVl0zZGb8PJyok16cYwPkdbKztOsiLwuBev5ks5eSnn8YzOnhNTYKjCN7+gIfo7MIIrJi2JJqUDggHd7izjoLm7oR/S1q+1c/o1iEQIlEemxuX4nO7ENA8KaNSlKi8g1QT7DwzX8zul5DwH7hztc5f/5o0loZ3RD75ze0M1eHo57I2T58CxVMyHb107dk2+lE7ObR8+g2HLA==
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=4D1KbpN2vvOPA9bGcjI17gWEv/jIAij+lV29MyVxE6E=; b=LkQw8Lv4fPZpt/8kfyvgP+TD01q5BKHpUgjuddxXMT5m0ti6I4lWJWWH/DKlfGlpChaeK1M15Btph6Yj6Rq8EpNNfvRC55EBhDuEoKp+7aNYQIcnuztwQxv63Ipmj3lqirCfqMxjE8XawgHxvuNDNGfy1qw2ZGDsn3sa5hAsTBDo7+dWjEcU6iXR4U1Qh/xzjhw1y1Z78df6XqV8xgP17+wY5kuVatfM97DPjIaHb37Diau8AZ0sEupYF2SlxGZG4GR7499+e3oHZwP70+KDwxAcfZYg46ggcHaMPzVONdR5fjdvWzB3VdkYy6OrjIhE7q2E3abupcXCzot3U4s8+Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=wemonitoremail.com; dmarc=pass action=none header.from=wemonitoremail.com; dkim=pass header.d=wemonitoremail.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemonitoremail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4D1KbpN2vvOPA9bGcjI17gWEv/jIAij+lV29MyVxE6E=; b=bw/W1ZUHI3OhZUUxNjtO2jwZ1Rlv00F2a6+WYP+x8sj7SnLXygQyuQNnrOoZriUjV9xf780DdbBVmn/lOB/KGlaCpDmvlKKmr6pX23dDO9kMoqYByLLVXet8Qmi2NyQj24h/TH9SHTFYMKnudRgIrSkhc9N8xdp0IzgJMdhD2er4lDKku/JGWPfBrvptDVQ2WCBCxcNzxUW86cVZgMZhLDRUzWiaQ6ILurN3918zhv1NDqPaNrThQE3moJ5LQTMhbD/GbKgDLuS3UpmKUFLe+xMsrasPO79t3uttYMBduaY1n0i8R1xx3k7Qt9nxNgzbaBxhDhr9rolD1Evj79s3wQ==
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com (2603:10a6:800:19a::9) by VI1PR01MB6845.eurprd01.prod.exchangelabs.com (2603:10a6:800:19e::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3868.27; Mon, 22 Feb 2021 17:00:13 +0000
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::9c69:59f:c073:bd9f]) by VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::9c69:59f:c073:bd9f%7]) with mapi id 15.20.3846.045; Mon, 22 Feb 2021 17:00:13 +0000
From: Ken O'Driscoll <ken@wemonitoremail.com>
To: IETF DMARC WG <dmarc@ietf.org>
CC: Dave Crocker <dcrocker@gmail.com>, Douglas Foster <dougfoster.emailstandards@gmail.com>
Thread-Topic: [dmarc-ietf] Fwd: I-D Action: draft-ietf-dmarc-psd-10.txt
Thread-Index: AQHW9lab2k+8FMVZi0mnpCcspdofhKo/CiwAgAALfYCAHy+dgIAB9HgAgAOsqYCAAHv4gIAADaEAgAAH24CAAAcKgIAAAW8g
Date: Mon, 22 Feb 2021 17:00:13 +0000
Message-ID: <VI1PR01MB7053E7DAD4C8706D65850E88C7819@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
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> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <2e2b6204-244d-dd6f-dced-e4318562710c@gmail.com> <CAH48ZfwzBHQz7x95nFOnr69gXXAUjKhxkgC+1WN97=i535_s0w@mail.gmail.com> <404eeea5-edbd-b795-57f4-801bb662ceac@gmail.com>
In-Reply-To: <404eeea5-edbd-b795-57f4-801bb662ceac@gmail.com>
Accept-Language: en-GB, 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=wemonitoremail.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 951a11f1-e259-4bbd-7758-08d8d7535205
x-ms-traffictypediagnostic: VI1PR01MB6845:
x-microsoft-antispam-prvs: <VI1PR01MB6845ECB7FCC736A3F42E5B84C7819@VI1PR01MB6845.eurprd01.prod.exchangelabs.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: oGQR/Eg0ULUv+Oc2Oguw1IJSyB0JdI+EFD2YLW4Q+zVVPeAnbCKrdcg0s2i1HvSYDXgXCrYAMY1KwkyH6pqkh7YuGe6Jv0Xa7oOuItIg2llzx003SOJTUyEJNc6T3eKD/eFI+dtrrbYwNy0CnLopQP8owgQqnnV0uhzHtyFudYYoeAIkpEXoyXSwnPy1hA8RPHoMKUW9rTypB96QA1cWqQQRuah2Ma7INC9XzqztANJ5uhgrUOoD1sByKlOpxTm7UP6bqJDktfrWCtiFOake3WdOiQAT7dPQlEFdMyjbw/TiblFTjfM60OfUaEaWYZjStMljLMA7+EvV/cZA52G6a9zCO797bQT2xv/9jfAoJgIlqkDvUV3If0VV1fxBUog7pU+mVzQWV8hofx6lDrUlxX6iIS6DtSBBCVV2vxocXte7EDNQjyv6iXFgk1E1j2X0Y6o3klEVTNg8xNJXLmFgrMjSX0IWldMJL+z3Jblr7Nfe9jTwHRl0+mx8ioqVsB1fxpfdzGBPL0FxcOT11bDdLQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:VI1PR01MB7053.eurprd01.prod.exchangelabs.com; PTR:;  CAT:NONE; SFS:(346002)(396003)(376002)(39830400003)(136003)(366004)(186003)(33656002)(6506007)(71200400001)(6916009)(26005)(5660300002)(478600001)(54906003)(7696005)(316002)(9686003)(66946007)(66556008)(64756008)(55016002)(66476007)(8936002)(4326008)(52536014)(4744005)(66446008)(76116006)(8676002)(86362001)(66574015)(2906002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?TlZkMmRtZUtXSmllRVNudm8vUHh2WWJsUzhGL0JLV1BGMzhoZ3NlaXNZQm1q?= =?utf-8?B?K1JmNzlZS1NSLzRtSngxaDNwVGdIK0Q5TUlOOWVkOGFXSmNaakFobTlKOFh4?= =?utf-8?B?YTFsSnBUUzNONFNlR3FnVlNlbHpoNUxDZUY5YWhaVTRLK0szbFlqdDVtVlR2?= =?utf-8?B?TVNOY3dreU9BK2Rlc0pLK1plZ0kvdmEraU5YWndsNC9iOGdZQWFWOXByT2tt?= =?utf-8?B?SE91ZDRJV3BSaFVhc3dob1UyYk5kditHeUlyb1dFZzRudVkzV0NYTzc1d3gx?= =?utf-8?B?UjdUb0NTOHZzdmFsMlhFU1hLUzFneUFDZ044WVI4QUJFZ2VncE9TT1EyTEYv?= =?utf-8?B?NWVRZWg5MVFCbldTK1IxUkM1QS9MQTQ4RU9sN01Oc0JxN0pmTHJ0ck9RMjlO?= =?utf-8?B?ZnQ1ajJBL2ZlZVBLWnJFUjZMSmp5WEFKMDBkSmNzeEwwUmMwSHJaSVhSdE1l?= =?utf-8?B?dFlHOXUxWWhuMmx4UU1aVktuZm9BU2o3aFZuOFBraDJyMjYySENHNzR6R2Vz?= =?utf-8?B?UGNOdVhHNFhBTHhSdWRxaTJVaFI3eDc5RTlPN2tCajhkaCtPcGJzb0FES2Ix?= =?utf-8?B?SEpJeUZUTGprRTV1MjR6RnFkRUJEcXlOeWJ6T2RHYitaa2cvd3c0WVVOSkQx?= =?utf-8?B?cDBqTGhMZHRRR0dnOWNpWXgrVnI1QzB2TDRRKzI0R1BFLzZIVlFVSFBBaFBY?= =?utf-8?B?a2NqamgwdUFjWW95YzByeXhjMS82RXpQMTF5Q3I4OUxOYStZL2tHekwrT1Vl?= =?utf-8?B?Z040eTlsREs3YjZjK0NndnFpMjNFWkRpZ0ZFRFlTbXRyNmU1SzZjVE1ERWU0?= =?utf-8?B?REhhVHZBN0IrUTc5bFVTOHpSckt0QnVXL0NIbFcwM2V1bW9nRm5Ia21SOGJM?= =?utf-8?B?WXgyZGZDZ0FZbUtGS1ljaXE5MWdjazVyaFVBbGhoZ1o4cU9Qd2toYTB0ZnJh?= =?utf-8?B?ZmNWNU82SUJodWU1dUd1ZFZVV3lDWHZ0cXhKc0FZNCt6aFZEZEVmYnA1N0lt?= =?utf-8?B?bUl5cTVFRVkwdjBZSFNiNjRkMmg0N0ZLMEZSVmp4K1pCM2tlL2RxRk1rSmVa?= =?utf-8?B?ZGp5cmEwMnVWR3RUOTNtSEVhWUtjYlJjbVk2YTQ3L29Bb3JaaTFOY1pyRWJp?= =?utf-8?B?WDVkTFBmaXFYMjJUTzNSc3UrRmliMFZHMFRBeW9wcGdXZ1BETkpVQ1BDakx4?= =?utf-8?B?dXFrZ0hIcEJIYVFveTZ4aGpUWCttZGpHa2JXQ0VYekp2UXlCamtQVThmV1pE?= =?utf-8?B?bmNsT0QxMncrdGQwWU1mdVFCSk5BZU5BTjhtYjM1MW5sbVNMZmZtOVpWeFZw?= =?utf-8?B?SjhUVThQaHJCVFVtYXlRNDMxTWRxZHB6K2g5VmR5MmtGV05DY2ZFWnBNcVNP?= =?utf-8?B?MERaTUFZK1V6ZVg0aFMzd2JEdy9mVWFrTVlFcjlyK1NjWXJ0SW52MjdsQmgz?= =?utf-8?B?dTg4TGpxQUdJM0I2VFRjMnVESlN6bnFmSWxqd0VwYWJ6VkVROGd3L0RMZTdC?= =?utf-8?B?VG4reWI3VS9RYzdHdUNzUG9XVGtBZmlEalVlcEM5Yys2RHc4ZTdjbFVEbklk?= =?utf-8?B?cTBhSm5rdGF4R1o5Q1hCc0w1c2VYRytjZWNnUWVtaWV3VE5GTUREMERCMkNQ?= =?utf-8?B?NVNEUVY1YWMvSitHdUgxTEZ4aEkxZ3c2UUNnT2p0aVhDbjAvYkdoNFQwcmdM?= =?utf-8?B?ckZobXpPWUh4U2tpMzhDcUFtU2hRV0RFR21nOEFZcDZlRjEvLzBKdVg2eSty?= =?utf-8?Q?NIFnzeebKM+kgPKvUA=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: wemonitoremail.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: VI1PR01MB7053.eurprd01.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 951a11f1-e259-4bbd-7758-08d8d7535205
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Feb 2021 17:00:13.0625 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a2b1d6fe-fc8b-4b7c-b9f1-d7b1ab3d23b3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 0ITWSSTx67XF1eyRaiN3inPO1+lsffwMA1w0WE3h/zspeMIfj+DafJYO3TcZj3MWxa9+gY7Oq9itWT852b4KWw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR01MB6845
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/fQnJWCUNxUKzaiRkG7s0yjUmwXk>
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: Mon, 22 Feb 2021 17:00:24 -0000

T24gTW9uZGF5IDIyIEZlYnJ1YXJ5IDIwMjEgMTY6MTQsIERhdmUgQ3JvY2tlciB3cm90ZToNCj4g
U3RyaWN0bHkgc3BlYWtpbmcgY28udWsgaXMgbm90IElDQU4tYXV0aG9yaXplZC7CoCBJdCdzIGF1
dGhvcml6ZWQgYnkNCj4gbWVjaGFuaXNtcyBpbnRlcm5hbCB0byB0aGUgVUsuDQo+IA0KDQpOb25l
IG9mIHRoZSBjY1RMRHMgcmVnaXN0cnkgb3BlcmF0b3JzIHdvdWxkIGNhbGwgb3IgY29uc2lkZXIg
dGhlbXNlbHZlcyAiSUNBTk4tYXV0aG9yaXplZCIuIFRoZSBvcmlnaW5hbCBhdXRob3Jpc2F0aW9u
IHRvIHVzZSB0aGUgbmFtZXNwYWNlIGlzIHZlcnkgc2VwYXJhdGUgdG8gSUNBTk4gaGF2aW5nIGFu
eSBnZW5lcmFsIGF1dGhvcml0eSBvdmVyIHRoZW0uIEZ1cnRoZXIsIGl04oCZcyBsaWtlbHkgdG8g
YmUgY29uZnVzZWQgd2l0aCB0aGUgbW9yZSBjb21tb24gdGVybSAiSUNBTk4tYWNjcmVkaXRlZCIs
IHdoaWNoIHJlZmVycyB0byBhIHN1Yi1zZXQgb2YgZG9tYWluIHJlZ2lzdHJhcnMsIG5vdCByZWdp
c3RyaWVzLg0KDQpJIHRoaW5rIGEgYmV0dGVyIGFuZCBtb3JlIGluY2x1c2l2ZSB0ZXJtIHdvdWxk
IGJlICJJbnRlcm5ldCBEb21haW4gUmVnaXN0cnkiLg0KDQpLZW4uDQo=


From nobody Mon Feb 22 09:59:10 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 BFDDD3A1E8E for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 09:59:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 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, T_KAM_HTML_FONT_INVALID=0.01, 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 SQUkbsA3pblN for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 09:59:06 -0800 (PST)
Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com [IPv6:2607:f8b0:4864:20::a32]) (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 5D65C3A1E86 for <dmarc@ietf.org>; Mon, 22 Feb 2021 09:59:06 -0800 (PST)
Received: by mail-vk1-xa32.google.com with SMTP id f145so3033172vka.8 for <dmarc@ietf.org>; Mon, 22 Feb 2021 09:59:06 -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=cgWepUZaH0Dmlunk5H5QIgGFSJ0lLd89i0l0tktFdUQ=; b=gHADIp0pIguHJPLCavJIFlVNm+HOmOI6YWURrUmZPm5UlY5g3o8qvS2QurOi2XOkGX fBYRsq0mA2sWnvP9lxvcYtxsJxcG5eac5Oc1WguMkohxfhDZwlPWeZZwnTpA3a8KtEn1 VqQmRUyVgBHDJvgrXN+qmDUhhkVP+ctqUXgX/EXE3AJfsl+n9A8IWgYwscUWbPD409ac IzfyTLvdIk9fZLw3hsMH9DG4eDuhULydZKioRPoFWdE0LVdHd8ds8aYbscceNp1Dzk0g oWlNTk6+zrg8dGzj05fn/MZVeovvN2G9SjMusEL4aCoTs4ZsuJar9CR2y9yyFXdL3OqM LHTA==
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=cgWepUZaH0Dmlunk5H5QIgGFSJ0lLd89i0l0tktFdUQ=; b=RHNgcke6kZ2PfnbPaPWhfLaz08jM7Kv/pA4pIhsHjxN9CeOZ7i5W7wk+ocnk6kJhyC lbptVD+ZYMW3Bipl1QG5tcp35kNw8RUY6ZcCzpyuhBCOI087t9j+Z7uFzQAmmmjKrnvo Ywv481/aO72rvb2yMrHwkVDiw2zZhjmbEFuovUFTQyOVIlh+xIqDFST+tIG1TWzo6ygV 1FTvJIK50APsejAEZZL6xQ9GODjyRYQrop2vl92RE1G/Bhu9n3DOM8kdIvzgDE9vUrdt oZjpiztyaV76KE0JKdJMApvob0fD4qAY+F0e3te0iDfRtIozVMIbn9N+9i2y438r9+Sr EB+Q==
X-Gm-Message-State: AOAM532bN8gHI37DraP/0yiKfOPJ14CbK+vfGTS+XjbnyAR8RpOpXOYg N7XkGwzYTDTuuW6lYpsLkrW2iEk/CUg7MmXjM0zlqVw2sDq3LA==
X-Google-Smtp-Source: ABdhPJyVmodk4Zjs2+LvSy42WYULE9QkxDBn8+JzfMhWWy7QXVCqXsKGCG79+1xmNU06pbWdYtFPA09S72/PoB2d8Ok=
X-Received: by 2002:a1f:4c45:: with SMTP id z66mr13718654vka.4.1614016744885;  Mon, 22 Feb 2021 09:59:04 -0800 (PST)
MIME-Version: 1.0
From: Seth Blank <seth@valimail.com>
Date: Mon, 22 Feb 2021 09:58:53 -0800
Message-ID: <CAOZAAfPbzfJvn5XQ=4d_jHcv8cSLR-R3pxCREKzT4U3pUzzNCg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Cc: dmarc-chairs@ietf.org, ART ADs <art-ads@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bda70105bbf08e0e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/K9j4TxYEg3D7oSlsbltYEnEEd3A>
Subject: [dmarc-ietf] Announcement - DMARC bis Design Team
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 22 Feb 2021 17:59:09 -0000

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

On 27 October 2020, in post
https://mailarchive.ietf.org/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/
the chairs announced a split of RFC7489 into three documents, to be scoped
as follows:


   - The DMARC Base Spec (editors - Emil Gustafsson, Todd Herr, and John
   Levine)
   - Aggregate Reporting (editor - Alex Brotman)
   - Forensic Reporting (editors - Steve Jones and Alessandro Vesely)


The chairs are of the opinion that discussion of topics related to the
DMARC bis documents on the mailing list has reached a point where it would
be unreasonable to expect any timely progress toward completion of the
refinement of the DMARC bis at this point.

Our charter (https://datatracker.ietf.org/wg/dmarc/about/) is clear on what
this working group=E2=80=99s priority should be when reviewing and improvin=
g the
DMARC specification: =E2=80=9CIssues based on operational experience and/or=
 data
aggregated from multiple sources will be given priority.=E2=80=9D

We are spending too much time on items that are at best incidental to
DMARC, and rarely are informed by operational practice or data from
multiple sources. Efforts by the chairs to weigh in and declare discussions
unproductive work for that particular thread, but the involved parties just
move on to another thread, and consensus remains well over the horizon.

We have therefore decided that the best approach to achieve progress for
the DMARC bis documents is to form a design team, per RFC 2418, Section
6.5. The team will be composed of the editors, focused on their designated
documents, as defined above. The team will be charged with working through
all existing tickets and producing an updated version of each DMARC bis
document to present to the working group, at which point discussion would
resume on-list with respect to the updated documents.

The design team will operate as follows:


   1.

   A moratorium is hereby imposed on creating tickets for this working
   group, effective at 5pm PT, Friday, February 26th.
   2.

   The design team will have until 5pm PT, Friday, April 23rd, to work
   through all applicable tickets, and come to agreement on each to either
   modify DMARC bis documents (and make such modification) or reject the
   ticket, with the reason for rejection added to the ticket's comments. No
   tickets will be closed during this process, everything will be transpare=
nt
   for working group review after the design period.
   3.

   Changes made to the DMARC bis documents will be tracked in the following
   manner:
   1.

      By comments added to the ticket driving the change
      2.

      By comments in the markdown (.md) and/or XML version of the documents
      3.

      Through an Appendix section added temporarily to the documents, so
      that changes can be easily summarized for the next step in the proces=
s.
      4.

      All changes throughout the process will be publicly visible within
      GitHub (https://github.com/ietf-wg-dmarc).
      4.

   At the end of the time period, in roughly sixty days (or earlier if
   their work is finished before then), the design team will deliver update=
d
   versions of the DMARC bis documents to the working group, and the workin=
g
   group will have a chance to review that version and make
   comments/recommending edits, etc., using
   https://trac.ietf.org/trac/dmarc/report/1 to create tickets as needed.
   Initial discussion will be limited to what=E2=80=99s in the documents.
   5.

   The design team will consult with each other and the chairs during their
   work as needed.


The chairs spent a great deal of time discussing this, and we don=E2=80=99t=
 take
this action lightly or without hesitation, but in the end we feel it=E2=80=
=99s the
best way to not only make progress on the working group's efforts, but also
to allow for working group participants to reset and perhaps gain a fresh
perspective on this important work.

After the updated documents have been presented to the working group, we
will hold an interim to discuss them and hear all feedback.

Seth, Tim, and Alexey, as Co-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.

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

<div dir=3D"ltr">On 27 October 2020, in post <a href=3D"https://mailarchive=
.ietf.org/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/">https://mailarchive.=
ietf.org/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/</a> the chairs announc=
ed a split of RFC7489 into three documents, to be scoped as follows:<br><br=
><ul><li>The DMARC Base Spec (editors - Emil Gustafsson, Todd Herr, and Joh=
n Levine)</li><li>Aggregate Reporting (editor - Alex Brotman)</li><li>Foren=
sic Reporting (editors - Steve Jones and Alessandro Vesely)</li></ul><br>Th=
e chairs are of the opinion that discussion of topics related to the DMARC =
bis documents on the mailing list has reached a point where it would be unr=
easonable to expect any timely progress toward completion of the refinement=
 of the DMARC bis at this point.<br><br>Our charter (<a href=3D"https://dat=
atracker.ietf.org/wg/dmarc/about/">https://datatracker.ietf.org/wg/dmarc/ab=
out/</a>) is clear on what this working group=E2=80=99s priority should be =
when reviewing and improving the DMARC specification: =E2=80=9CIssues based=
 on operational experience and/or data aggregated from multiple sources wil=
l be given priority.=E2=80=9D<br><br>We are spending too much time on items=
 that are at best incidental to DMARC, and rarely are informed by operation=
al practice or data from multiple sources. Efforts by the chairs to weigh i=
n and declare discussions unproductive work for that particular thread, but=
 the involved parties just move on to another thread, and consensus remains=
 well over the horizon.<br><br>We have therefore decided that the best appr=
oach to achieve progress for the DMARC bis documents is to form a design te=
am, per RFC 2418, Section 6.5. The team will be composed of the editors, fo=
cused on their designated documents, as defined above. The team will be cha=
rged with working through all existing tickets and producing an updated ver=
sion of each DMARC bis document to present to the working group, at which p=
oint discussion would resume on-list with respect to the updated documents.=
<br><br><font face=3D"arial, sans-serif">The design team will operate as fo=
llows:<br></font><div><div><font face=3D"arial, sans-serif"><br></font></di=
v><div><span id=3D"gmail-docs-internal-guid-a6c9442d-7fff-4a08-1ee6-09197df=
4af94"><ol style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial, =
sans-serif"><li dir=3D"ltr" style=3D"list-style-type:decimal;background-col=
or:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;v=
ertical-align:baseline;white-space:pre;margin-left:11pt"><p dir=3D"ltr" sty=
le=3D"line-height:1.38;margin-top:10pt;margin-bottom:0pt"><span style=3D"ba=
ckground-color:transparent;font-variant-numeric:normal;font-variant-east-as=
ian:normal;vertical-align:baseline;white-space:pre-wrap">A moratorium is he=
reby imposed on creating tickets for this working group, effective at 5pm P=
T, Friday, February 26th.</span></p></li><li dir=3D"ltr" style=3D"list-styl=
e-type:decimal;background-color:transparent;font-variant-numeric:normal;fon=
t-variant-east-asian:normal;vertical-align:baseline;white-space:pre;margin-=
left:11pt"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-b=
ottom:0pt"><span style=3D"background-color:transparent;font-variant-numeric=
:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:=
pre-wrap">The design team will have until 5pm PT, Friday, April 23rd, to wo=
rk through all applicable tickets, and come to agreement on each to either =
modify DMARC bis documents (and make such modification) or reject the ticke=
t, with the reason for rejection added to the ticket&#39;s comments. No tic=
kets will be closed during this process, everything will be transparent for=
 working group review after the design period.</span></p></li><li dir=3D"lt=
r" style=3D"list-style-type:decimal;background-color:transparent;font-varia=
nt-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;wh=
ite-space:pre;margin-left:11pt"><p dir=3D"ltr" style=3D"line-height:1.38;ma=
rgin-top:0pt;margin-bottom:0pt"><span style=3D"background-color:transparent=
;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:=
baseline;white-space:pre-wrap">Changes made to the DMARC bis documents will=
 be tracked in the following manner:</span></p></li><ol style=3D"margin-top=
:0px;margin-bottom:0px"><li dir=3D"ltr" style=3D"list-style-type:lower-alph=
a;background-color:transparent;font-variant-numeric:normal;font-variant-eas=
t-asian:normal;vertical-align:baseline;white-space:pre"><p dir=3D"ltr" styl=
e=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"back=
ground-color:transparent;font-variant-numeric:normal;font-variant-east-asia=
n:normal;vertical-align:baseline;white-space:pre-wrap">By comments added to=
 the ticket driving the change</span></p></li><li dir=3D"ltr" style=3D"list=
-style-type:lower-alpha;background-color:transparent;font-variant-numeric:n=
ormal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pr=
e"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0p=
t"><span style=3D"background-color:transparent;font-variant-numeric:normal;=
font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap=
">By comments in the markdown (.md) and/or XML version of the documents</sp=
an></p></li><li dir=3D"ltr" style=3D"list-style-type:lower-alpha;background=
-color:transparent;font-variant-numeric:normal;font-variant-east-asian:norm=
al;vertical-align:baseline;white-space:pre"><p dir=3D"ltr" style=3D"line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"background-color=
:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;ver=
tical-align:baseline;white-space:pre-wrap">Through an Appendix section adde=
d temporarily to the documents, so that changes can be easily summarized fo=
r the next step in the process.</span></p></li><li dir=3D"ltr" style=3D"lis=
t-style-type:lower-alpha;background-color:transparent;font-variant-numeric:=
normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:p=
re"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0=
pt"><span style=3D"background-color:transparent;font-variant-numeric:normal=
;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wra=
p">All changes throughout the process will be publicly visible within GitHu=
b (<a href=3D"https://github.com/ietf-wg-dmarc">https://github.com/ietf-wg-=
dmarc</a>).</span></p></li></ol><li dir=3D"ltr" style=3D"list-style-type:de=
cimal;background-color:transparent;font-variant-numeric:normal;font-variant=
-east-asian:normal;vertical-align:baseline;white-space:pre;margin-left:11pt=
"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt=
;padding:0pt 0pt 10pt"><span style=3D"background-color:transparent;font-var=
iant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;=
white-space:pre-wrap">At the end of the time period, in roughly sixty days =
(or earlier if their work is finished before then), the design team will de=
liver updated versions of the DMARC bis documents to the working group, and=
 the working group will have a chance to review that version and make comme=
nts/recommending edits, etc., using <a href=3D"https://trac.ietf.org/trac/d=
marc/report/1">https://trac.ietf.org/trac/dmarc/report/1</a> to create tick=
ets as needed. Initial discussion will be limited to what=E2=80=99s in the =
documents.</span></p></li><li dir=3D"ltr" style=3D"list-style-type:decimal;=
background-color:transparent;font-variant-numeric:normal;font-variant-east-=
asian:normal;vertical-align:baseline;white-space:pre;margin-left:11pt"><p d=
ir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><spa=
n style=3D"color:rgb(0,0,0);background-color:transparent;font-variant-numer=
ic:normal;font-variant-east-asian:normal;vertical-align:baseline;white-spac=
e:pre-wrap">The design team will consult with each other and the chairs dur=
ing their work as needed.</span></p></li></font></ol></span></div><div><br>=
</div><div>The chairs spent a great deal of time discussing this, and we do=
n=E2=80=99t take this action lightly or without hesitation, but in the end =
we feel it=E2=80=99s the best way to not only make progress on the working =
group&#39;s efforts, but also to allow for working group participants to re=
set and perhaps gain a fresh perspective on this important work.<br><br></d=
iv><div>After the updated documents have been presented to the working grou=
p, we will hold an interim to discuss them and hear all feedback.<br></div>=
<div><br></div><div>Seth, Tim, and Alexey, as Co-Chairs</div><div><br></div=
>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_=
signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;m=
argin-bottom:0pt"></p><div style=3D"text-align:left"><span style=3D"vertica=
l-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b=
>Seth Blank</b></span><span style=3D"vertical-align:baseline;white-space:pr=
e-wrap;font-size:small;font-family:Arial"> | VP, Standards and New Technolo=
gies</span></div><span style=3D"vertical-align:baseline;white-space:pre-wra=
p;font-size:small;font-family:Arial"><div style=3D"text-align:left"><span s=
tyle=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-al=
ign: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><div style=3D"text-align:left"><spa=
n style=3D"vertical-align:baseline"><br></span></div></span><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"><img src=3D"https://valimail-logos.s3.amazonaws.com/Vali=
mail__Tag_DarkBlue_TM.png" style=3D"height:35px;width:159px">`</p><p dir=3D=
"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.38;margin-to=
p: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 trans=
mitted with it contains confidential and/or proprietary information intende=
d 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 t=
ransmission is prohibited and may be unlawful. Please immediately notify th=
e sender by replying to this email and then delete it from your system.</sp=
an></font></p></span></div></div></div>

--000000000000bda70105bbf08e0e--


From nobody Mon Feb 22 10:04: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 97D8E3A1E88; Mon, 22 Feb 2021 10:04:13 -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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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 P1bwPlKM9QA1; Mon, 22 Feb 2021 10:04:11 -0800 (PST)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 552793A1E9D; Mon, 22 Feb 2021 10:04:11 -0800 (PST)
Received: by mail-ot1-x32e.google.com with SMTP id s107so12854218otb.8; Mon, 22 Feb 2021 10:04: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=lqsRwrwmo23a2ACjR7OJD/UUyh2iTB6FiExNAAW20VY=; b=GgGk67hG+IvNNjTD4XElz+2UJrSbtQbtfquZg6DkCabZOegJbZlz926ME96TtB7Of5 FHaKZvt7mahM7a5dsj8JgEgYPRa7Ye6Zmrp3R3/37LtZ1R6ICKLK+04aM2Cii4exBsjX Uup4tsW2wDR15VX2juvl30I/A6eaMH3grdlBUZcwhqrKLRpyQgNODhoMXZHqhbn2fS2D DC8OidGX+sUosCRAFoymm+c99OIdCaOZ1pvpqiftKlMhkb3FTZNK8kAmVdWhvXtnpXbc Y96AXGY0n9ucKkG9sDVjMGWjGJvU9I4Nrt1jlC4TgL5BAU/SSsrGlSRIo4LoU6HTowsT kshg==
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=lqsRwrwmo23a2ACjR7OJD/UUyh2iTB6FiExNAAW20VY=; b=riA64cY5CENqVBXXdbS9tqIB5TIF0JCPIi0WqiidGBAe0X84XT1NDD4qVxPp2x607J tWAz8UwrHa+FnUajo6zTaHzk4+wyR82QtOVleg4tuqLi40CXJmX3kioTVrICWAnwU+mn WTWTQQePJng3ytocn4RV38XlV/6QuYmIUZo58DSpJfAOSTV281RmfyGiOqqkaJ9XgVlh w2koThOPR9vJl+89LVKGD/ceK0prdEBX+6X9fQ+Garhw5kIv08oChGT6F7FV1rZckNgK RY4tVZ9imckKCmcMdiCiv8vHg+sEy3VNW+33kWTufEFkCNgz04zYLjZ/sS/O/cv55YMI n5Eg==
X-Gm-Message-State: AOAM531eET1jQDQiPUeZ/Ilo7kqZTNVEinB65xpo0km3Ls/S1yoUDpYv j1IDJjyXQWSDVAxUs4h7VhFqs9zOxgJihpKJJaI=
X-Google-Smtp-Source: ABdhPJy7UVzSmFWcb6YiRjrEgG9jeHGWkQzZaIUvo2Fj3umZA8rVIzWl2zKMk0NyRuyw3Dt5MXf1z0G5BoK8sSD5oNU=
X-Received: by 2002:a05:6830:2248:: with SMTP id t8mr18025391otd.155.1614017050520;  Mon, 22 Feb 2021 10:04:10 -0800 (PST)
MIME-Version: 1.0
References: <CAOZAAfPbzfJvn5XQ=4d_jHcv8cSLR-R3pxCREKzT4U3pUzzNCg@mail.gmail.com>
In-Reply-To: <CAOZAAfPbzfJvn5XQ=4d_jHcv8cSLR-R3pxCREKzT4U3pUzzNCg@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Mon, 22 Feb 2021 13:03:58 -0500
Message-ID: <CADyWQ+EVT3ZwketTy0BRj6rY4RCWEFo6q4+yG4C6=uJxF-b-sg@mail.gmail.com>
To: Seth Blank <seth@valimail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, dmarc-chairs@ietf.org, ART ADs <art-ads@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f52f0b05bbf0a054"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/3Ci-3M12JA906N8D1L_W0BX-uME>
Subject: Re: [dmarc-ietf] Announcement - DMARC bis Design Team
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 22 Feb 2021 18:04:14 -0000

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

Thanks for sending this out Seth.   folks are free to contact the chairs
and our AD if they have questions, concerns.

tim


On Mon, Feb 22, 2021 at 12:59 PM Seth Blank <seth@valimail.com> wrote:

> On 27 October 2020, in post
> https://mailarchive.ietf.org/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/
> the chairs announced a split of RFC7489 into three documents, to be scope=
d
> as follows:
>
>
>    - The DMARC Base Spec (editors - Emil Gustafsson, Todd Herr, and John
>    Levine)
>    - Aggregate Reporting (editor - Alex Brotman)
>    - Forensic Reporting (editors - Steve Jones and Alessandro Vesely)
>
>
> The chairs are of the opinion that discussion of topics related to the
> DMARC bis documents on the mailing list has reached a point where it woul=
d
> be unreasonable to expect any timely progress toward completion of the
> refinement of the DMARC bis at this point.
>
> Our charter (https://datatracker.ietf.org/wg/dmarc/about/) is clear on
> what this working group=E2=80=99s priority should be when reviewing and i=
mproving
> the DMARC specification: =E2=80=9CIssues based on operational experience =
and/or
> data aggregated from multiple sources will be given priority.=E2=80=9D
>
> We are spending too much time on items that are at best incidental to
> DMARC, and rarely are informed by operational practice or data from
> multiple sources. Efforts by the chairs to weigh in and declare discussio=
ns
> unproductive work for that particular thread, but the involved parties ju=
st
> move on to another thread, and consensus remains well over the horizon.
>
> We have therefore decided that the best approach to achieve progress for
> the DMARC bis documents is to form a design team, per RFC 2418, Section
> 6.5. The team will be composed of the editors, focused on their designate=
d
> documents, as defined above. The team will be charged with working throug=
h
> all existing tickets and producing an updated version of each DMARC bis
> document to present to the working group, at which point discussion would
> resume on-list with respect to the updated documents.
>
> The design team will operate as follows:
>
>
>    1.
>
>    A moratorium is hereby imposed on creating tickets for this working
>    group, effective at 5pm PT, Friday, February 26th.
>    2.
>
>    The design team will have until 5pm PT, Friday, April 23rd, to work
>    through all applicable tickets, and come to agreement on each to eithe=
r
>    modify DMARC bis documents (and make such modification) or reject the
>    ticket, with the reason for rejection added to the ticket's comments. =
No
>    tickets will be closed during this process, everything will be transpa=
rent
>    for working group review after the design period.
>    3.
>
>    Changes made to the DMARC bis documents will be tracked in the
>    following manner:
>    1.
>
>       By comments added to the ticket driving the change
>       2.
>
>       By comments in the markdown (.md) and/or XML version of the
>       documents
>       3.
>
>       Through an Appendix section added temporarily to the documents, so
>       that changes can be easily summarized for the next step in the proc=
ess.
>       4.
>
>       All changes throughout the process will be publicly visible within
>       GitHub (https://github.com/ietf-wg-dmarc).
>       4.
>
>    At the end of the time period, in roughly sixty days (or earlier if
>    their work is finished before then), the design team will deliver upda=
ted
>    versions of the DMARC bis documents to the working group, and the work=
ing
>    group will have a chance to review that version and make
>    comments/recommending edits, etc., using
>    https://trac.ietf.org/trac/dmarc/report/1 to create tickets as needed.
>    Initial discussion will be limited to what=E2=80=99s in the documents.
>    5.
>
>    The design team will consult with each other and the chairs during
>    their work as needed.
>
>
> The chairs spent a great deal of time discussing this, and we don=E2=80=
=99t take
> this action lightly or without hesitation, but in the end we feel it=E2=
=80=99s the
> best way to not only make progress on the working group's efforts, but al=
so
> to allow for working group participants to reset and perhaps gain a fresh
> perspective on this important work.
>
> After the updated documents have been presented to the working group, we
> will hold an interim to discuss them and hear all feedback.
>
> Seth, Tim, and Alexey, as Co-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.
>

--000000000000f52f0b05bbf0a054
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">Thanks for sending this out Seth.=C2=A0 =C2=A0folks are free to contact =
the chairs and our AD if they have questions, concerns.</div><div class=3D"=
gmail_default" style=3D"font-family:monospace"><br></div><div class=3D"gmai=
l_default" style=3D"font-family:monospace">tim</div><div class=3D"gmail_def=
ault" style=3D"font-family:monospace"><br></div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Feb 22, 2021 at 12:=
59 PM Seth Blank &lt;<a href=3D"mailto:seth@valimail.com">seth@valimail.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">On 27 October 2020, in post <a href=3D"https://mailarchive=
.ietf.org/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/" target=3D"_blank">ht=
tps://mailarchive.ietf.org/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/</a> =
the chairs announced a split of RFC7489 into three documents, to be scoped =
as follows:<br><br><ul><li>The DMARC Base Spec (editors - Emil Gustafsson, =
Todd Herr, and John Levine)</li><li>Aggregate Reporting (editor - Alex Brot=
man)</li><li>Forensic Reporting (editors - Steve Jones and Alessandro Vesel=
y)</li></ul><br>The chairs are of the opinion that discussion of topics rel=
ated to the DMARC bis documents on the mailing list has reached a point whe=
re it would be unreasonable to expect any timely progress toward completion=
 of the refinement of the DMARC bis at this point.<br><br>Our charter (<a h=
ref=3D"https://datatracker.ietf.org/wg/dmarc/about/" target=3D"_blank">http=
s://datatracker.ietf.org/wg/dmarc/about/</a>) is clear on what this working=
 group=E2=80=99s priority should be when reviewing and improving the DMARC =
specification: =E2=80=9CIssues based on operational experience and/or data =
aggregated from multiple sources will be given priority.=E2=80=9D<br><br>We=
 are spending too much time on items that are at best incidental to DMARC, =
and rarely are informed by operational practice or data from multiple sourc=
es. Efforts by the chairs to weigh in and declare discussions unproductive =
work for that particular thread, but the involved parties just move on to a=
nother thread, and consensus remains well over the horizon.<br><br>We have =
therefore decided that the best approach to achieve progress for the DMARC =
bis documents is to form a design team, per RFC 2418, Section 6.5. The team=
 will be composed of the editors, focused on their designated documents, as=
 defined above. The team will be charged with working through all existing =
tickets and producing an updated version of each DMARC bis document to pres=
ent to the working group, at which point discussion would resume on-list wi=
th respect to the updated documents.<br><br><font face=3D"arial, sans-serif=
">The design team will operate as follows:<br></font><div><div><font face=
=3D"arial, sans-serif"><br></font></div><div><span id=3D"gmail-m_-529252148=
908362627gmail-docs-internal-guid-a6c9442d-7fff-4a08-1ee6-09197df4af94"><ol=
 style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial, sans-serif=
"><li dir=3D"ltr" style=3D"list-style-type:decimal;background-color:transpa=
rent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-al=
ign:baseline;white-space:pre-wrap;margin-left:11pt"><p dir=3D"ltr" style=3D=
"line-height:1.38;margin-top:10pt;margin-bottom:0pt"><span style=3D"backgro=
und-color:transparent;font-variant-numeric:normal;font-variant-east-asian:n=
ormal;vertical-align:baseline;white-space:pre-wrap">A moratorium is hereby =
imposed on creating tickets for this working group, effective at 5pm PT, Fr=
iday, February 26th.</span></p></li><li dir=3D"ltr" style=3D"list-style-typ=
e:decimal;background-color:transparent;font-variant-numeric:normal;font-var=
iant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap;margin-=
left:11pt"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-b=
ottom:0pt"><span style=3D"background-color:transparent;font-variant-numeric=
:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:=
pre-wrap">The design team will have until 5pm PT, Friday, April 23rd, to wo=
rk through all applicable tickets, and come to agreement on each to either =
modify DMARC bis documents (and make such modification) or reject the ticke=
t, with the reason for rejection added to the ticket&#39;s comments. No tic=
kets will be closed during this process, everything will be transparent for=
 working group review after the design period.</span></p></li><li dir=3D"lt=
r" style=3D"list-style-type:decimal;background-color:transparent;font-varia=
nt-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;wh=
ite-space:pre-wrap;margin-left:11pt"><p dir=3D"ltr" style=3D"line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><span style=3D"background-color:transp=
arent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-a=
lign:baseline;white-space:pre-wrap">Changes made to the DMARC bis documents=
 will be tracked in the following manner:</span></p></li><ol style=3D"margi=
n-top:0px;margin-bottom:0px"><li dir=3D"ltr" style=3D"list-style-type:lower=
-alpha;background-color:transparent;font-variant-numeric:normal;font-varian=
t-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><p dir=3D=
"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"background-color:transparent;font-variant-numeric:normal;font-variant=
-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">By comment=
s added to the ticket driving the change</span></p></li><li dir=3D"ltr" sty=
le=3D"list-style-type:lower-alpha;background-color:transparent;font-variant=
-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;whit=
e-space:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;m=
argin-bottom:0pt"><span style=3D"background-color:transparent;font-variant-=
numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white=
-space:pre-wrap">By comments in the markdown (.md) and/or XML version of th=
e documents</span></p></li><li dir=3D"ltr" style=3D"list-style-type:lower-a=
lpha;background-color:transparent;font-variant-numeric:normal;font-variant-=
east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><p dir=3D"l=
tr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=
=3D"background-color:transparent;font-variant-numeric:normal;font-variant-e=
ast-asian:normal;vertical-align:baseline;white-space:pre-wrap">Through an A=
ppendix section added temporarily to the documents, so that changes can be =
easily summarized for the next step in the process.</span></p></li><li dir=
=3D"ltr" style=3D"list-style-type:lower-alpha;background-color:transparent;=
font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:b=
aseline;white-space:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;marg=
in-top:0pt;margin-bottom:0pt"><span style=3D"background-color:transparent;f=
ont-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:ba=
seline;white-space:pre-wrap">All changes throughout the process will be pub=
licly visible within GitHub (<a href=3D"https://github.com/ietf-wg-dmarc" t=
arget=3D"_blank">https://github.com/ietf-wg-dmarc</a>).</span></p></li></ol=
><li dir=3D"ltr" style=3D"list-style-type:decimal;background-color:transpar=
ent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-ali=
gn:baseline;white-space:pre-wrap;margin-left:11pt"><p dir=3D"ltr" style=3D"=
line-height:1.38;margin-top:0pt;margin-bottom:0pt;padding:0pt 0pt 10pt"><sp=
an style=3D"background-color:transparent;font-variant-numeric:normal;font-v=
ariant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">At t=
he end of the time period, in roughly sixty days (or earlier if their work =
is finished before then), the design team will deliver updated versions of =
the DMARC bis documents to the working group, and the working group will ha=
ve a chance to review that version and make comments/recommending edits, et=
c., using <a href=3D"https://trac.ietf.org/trac/dmarc/report/1" target=3D"_=
blank">https://trac.ietf.org/trac/dmarc/report/1</a> to create tickets as n=
eeded. Initial discussion will be limited to what=E2=80=99s in the document=
s.</span></p></li><li dir=3D"ltr" style=3D"list-style-type:decimal;backgrou=
nd-color:transparent;font-variant-numeric:normal;font-variant-east-asian:no=
rmal;vertical-align:baseline;white-space:pre-wrap;margin-left:11pt"><p dir=
=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span =
style=3D"color:rgb(0,0,0);background-color:transparent;font-variant-numeric=
:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:=
pre-wrap">The design team will consult with each other and the chairs durin=
g their work as needed.</span></p></li></font></ol></span></div><div><br></=
div><div>The chairs spent a great deal of time discussing this, and we don=
=E2=80=99t take this action lightly or without hesitation, but in the end w=
e feel it=E2=80=99s the best way to not only make progress on the working g=
roup&#39;s efforts, but also to allow for working group participants to res=
et and perhaps gain a fresh perspective on this important work.<br><br></di=
v><div>After the updated documents have been presented to the working group=
, we will hold an interim to discuss them and hear all feedback.<br></div><=
div><br></div><div>Seth, Tim, and Alexey, as Co-Chairs</div><div><br></div>=
-- <br><div dir=3D"ltr"><span><p dir=3D"ltr" style=3D"line-height:1.656;mar=
gin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-fam=
ily:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baseline;w=
hite-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@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><div style=3D"text=
-align:left"><span style=3D"vertical-align:baseline"><br></span></div></spa=
n><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"><img src=3D"https://valimail-logos.s3.a=
mazonaws.com/Valimail__Tag_DarkBlue_TM.png" style=3D"height: 35px; width: 1=
59px;">`</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></div>
</blockquote></div>

--000000000000f52f0b05bbf0a054--


From nobody Mon Feb 22 13:59:29 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 465F03A20CA; Mon, 22 Feb 2021 13:59:27 -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_KAM_HTML_FONT_INVALID=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 4Yi88APEcU7m; Mon, 22 Feb 2021 13:59:25 -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 75FD13A20CB; Mon, 22 Feb 2021 13:59:24 -0800 (PST)
Received: by mail-qk1-x730.google.com with SMTP id m144so14255967qke.10; Mon, 22 Feb 2021 13:59: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=FZFdbjSGx9rFXRlfL1lbA1LcCnmBZFioJSlsQiDqm/8=; b=qGf0CCo4mjlCt4p6OsVASsim+YibAPSxX0NM7azZmiNiWfs7llmWaOt6Wy0wQSJDZz DSfzCFkHxJH7Bw+sfnw6kNiRKWurwNGP2mLwHnCbnYeds42QhVCujFbjWwjryzzqhG8c J05TJOs1trhSyWTLHp9GvIc3kgEsvqsvvN9lDf9SeDSReGqVJzhJpN/0zI65ueB4mPkh 4rZsXHKjD1w74gQ4c72NN26lWovoqP20T25qlWfP83NF455DtHZ9wvb1q9bWBQrLwCnI eDG3qAaaT/04sT2LkONUWlqCsA1Al38kT59y/ynzRirhTNC8h6mG6vdDBYFh9OAXfNu/ yrbA==
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=FZFdbjSGx9rFXRlfL1lbA1LcCnmBZFioJSlsQiDqm/8=; b=mYqYnBwEG9jm+9rTIOpKK7ZvR4B5UvSJybMp9354okUpjHMclO30N/shKKOLx4MVT1 C4WfWlZ33xXHApmbYfBUigWWVVj3HZrScqmh9hsqSa3ckjSm/HYGiZSp8b+YhU+cwPAX lHs5YsiKf15GQwzT2q+OWD5zuTy0F7fIPfGvQ41RKiqMP8vDx4aGQYW5h5Is06+dtGv/ PkTADBI0xHW3j8QcAQScGy5x/oKCBAR2JTAI/0Bt6jY5Lr1dnoupuMpZFvnm61KKKnIt xdkYVa84kDXyiBohSVXfMlzKfB4TR8dGGZQoOesVLkgRAIkcW+si5Gl8EAu4DgP5i37y bRkQ==
X-Gm-Message-State: AOAM532V3uCx6maRgZepxGUzaTXvRF5IDsh4ontC9CPaB+ImJX439Z/W /B47zFDONOiKkQcdn0Qjmi3vlKeFMN5JKKcWMw1sT5Ie
X-Google-Smtp-Source: ABdhPJyOppWJqvlu2QKGqSdlLozWEAEIeg3XBWQXn3BjpB5G3H+QRgIklCr0zfljjQxUkm+I2AdIEdm6DXDQv4GjxIk=
X-Received: by 2002:a37:27c8:: with SMTP id n191mr22796690qkn.146.1614031163407;  Mon, 22 Feb 2021 13:59:23 -0800 (PST)
MIME-Version: 1.0
References: <CAOZAAfPbzfJvn5XQ=4d_jHcv8cSLR-R3pxCREKzT4U3pUzzNCg@mail.gmail.com>
In-Reply-To: <CAOZAAfPbzfJvn5XQ=4d_jHcv8cSLR-R3pxCREKzT4U3pUzzNCg@mail.gmail.com>
From: Dotzero <dotzero@gmail.com>
Date: Mon, 22 Feb 2021 16:59:11 -0500
Message-ID: <CAJ4XoYfNYHb0psvRhF1H0avNx-dauGPQuaSmPUk50Tf=0_vfFQ@mail.gmail.com>
To: Seth Blank <seth=40valimail.com@dmarc.ietf.org>
Cc: IETF DMARC WG <dmarc@ietf.org>, ART ADs <art-ads@ietf.org>, dmarc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000026c34a05bbf3ea2a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/JORMbeoxHLQqMFZR5_k5EGaImUw>
Subject: Re: [dmarc-ietf] Announcement - DMARC bis Design Team
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 22 Feb 2021 21:59:27 -0000

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

So I'm assuming there won't be anything to talk about at the next IETF
meeting.

Michael Hammer

On Mon, Feb 22, 2021 at 12:59 PM Seth Blank <seth=3D
40valimail.com@dmarc.ietf.org> wrote:

> On 27 October 2020, in post
> https://mailarchive.ietf.org/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/
> the chairs announced a split of RFC7489 into three documents, to be scope=
d
> as follows:
>
>
>    - The DMARC Base Spec (editors - Emil Gustafsson, Todd Herr, and John
>    Levine)
>    - Aggregate Reporting (editor - Alex Brotman)
>    - Forensic Reporting (editors - Steve Jones and Alessandro Vesely)
>
>
> The chairs are of the opinion that discussion of topics related to the
> DMARC bis documents on the mailing list has reached a point where it woul=
d
> be unreasonable to expect any timely progress toward completion of the
> refinement of the DMARC bis at this point.
>
> Our charter (https://datatracker.ietf.org/wg/dmarc/about/) is clear on
> what this working group=E2=80=99s priority should be when reviewing and i=
mproving
> the DMARC specification: =E2=80=9CIssues based on operational experience =
and/or
> data aggregated from multiple sources will be given priority.=E2=80=9D
>
> We are spending too much time on items that are at best incidental to
> DMARC, and rarely are informed by operational practice or data from
> multiple sources. Efforts by the chairs to weigh in and declare discussio=
ns
> unproductive work for that particular thread, but the involved parties ju=
st
> move on to another thread, and consensus remains well over the horizon.
>
> We have therefore decided that the best approach to achieve progress for
> the DMARC bis documents is to form a design team, per RFC 2418, Section
> 6.5. The team will be composed of the editors, focused on their designate=
d
> documents, as defined above. The team will be charged with working throug=
h
> all existing tickets and producing an updated version of each DMARC bis
> document to present to the working group, at which point discussion would
> resume on-list with respect to the updated documents.
>
> The design team will operate as follows:
>
>
>    1.
>
>    A moratorium is hereby imposed on creating tickets for this working
>    group, effective at 5pm PT, Friday, February 26th.
>    2.
>
>    The design team will have until 5pm PT, Friday, April 23rd, to work
>    through all applicable tickets, and come to agreement on each to eithe=
r
>    modify DMARC bis documents (and make such modification) or reject the
>    ticket, with the reason for rejection added to the ticket's comments. =
No
>    tickets will be closed during this process, everything will be transpa=
rent
>    for working group review after the design period.
>    3.
>
>    Changes made to the DMARC bis documents will be tracked in the
>    following manner:
>    1.
>
>       By comments added to the ticket driving the change
>       2.
>
>       By comments in the markdown (.md) and/or XML version of the
>       documents
>       3.
>
>       Through an Appendix section added temporarily to the documents, so
>       that changes can be easily summarized for the next step in the proc=
ess.
>       4.
>
>       All changes throughout the process will be publicly visible within
>       GitHub (https://github.com/ietf-wg-dmarc).
>       4.
>
>    At the end of the time period, in roughly sixty days (or earlier if
>    their work is finished before then), the design team will deliver upda=
ted
>    versions of the DMARC bis documents to the working group, and the work=
ing
>    group will have a chance to review that version and make
>    comments/recommending edits, etc., using
>    https://trac.ietf.org/trac/dmarc/report/1 to create tickets as needed.
>    Initial discussion will be limited to what=E2=80=99s in the documents.
>    5.
>
>    The design team will consult with each other and the chairs during
>    their work as needed.
>
>
> The chairs spent a great deal of time discussing this, and we don=E2=80=
=99t take
> this action lightly or without hesitation, but in the end we feel it=E2=
=80=99s the
> best way to not only make progress on the working group's efforts, but al=
so
> to allow for working group participants to reset and perhaps gain a fresh
> perspective on this important work.
>
> After the updated documents have been presented to the working group, we
> will hold an interim to discuss them and hear all feedback.
>
> Seth, Tim, and Alexey, as Co-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.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr"><div>So I&#39;m assuming there won&#39;t be anything to ta=
lk about at the next IETF meeting.</div><div><br></div><div>Michael Hammer<=
br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gma=
il_attr">On Mon, Feb 22, 2021 at 12:59 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 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">On 27 October 2020, in post <a href=3D"https://mailarchive.ietf.or=
g/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/" target=3D"_blank">https://ma=
ilarchive.ietf.org/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/</a> the chai=
rs announced a split of RFC7489 into three documents, to be scoped as follo=
ws:<br><br><ul><li>The DMARC Base Spec (editors - Emil Gustafsson, Todd Her=
r, and John Levine)</li><li>Aggregate Reporting (editor - Alex Brotman)</li=
><li>Forensic Reporting (editors - Steve Jones and Alessandro Vesely)</li><=
/ul><br>The chairs are of the opinion that discussion of topics related to =
the DMARC bis documents on the mailing list has reached a point where it wo=
uld be unreasonable to expect any timely progress toward completion of the =
refinement of the DMARC bis at this point.<br><br>Our charter (<a href=3D"h=
ttps://datatracker.ietf.org/wg/dmarc/about/" target=3D"_blank">https://data=
tracker.ietf.org/wg/dmarc/about/</a>) is clear on what this working group=
=E2=80=99s priority should be when reviewing and improving the DMARC specif=
ication: =E2=80=9CIssues based on operational experience and/or data aggreg=
ated from multiple sources will be given priority.=E2=80=9D<br><br>We are s=
pending too much time on items that are at best incidental to DMARC, and ra=
rely are informed by operational practice or data from multiple sources. Ef=
forts by the chairs to weigh in and declare discussions unproductive work f=
or that particular thread, but the involved parties just move on to another=
 thread, and consensus remains well over the horizon.<br><br>We have theref=
ore decided that the best approach to achieve progress for the DMARC bis do=
cuments is to form a design team, per RFC 2418, Section 6.5. The team will =
be composed of the editors, focused on their designated documents, as defin=
ed above. The team will be charged with working through all existing ticket=
s and producing an updated version of each DMARC bis document to present to=
 the working group, at which point discussion would resume on-list with res=
pect to the updated documents.<br><br><font face=3D"arial, sans-serif">The =
design team will operate as follows:<br></font><div><div><font face=3D"aria=
l, sans-serif"><br></font></div><div><span id=3D"gmail-m_879882410662823048=
3gmail-docs-internal-guid-a6c9442d-7fff-4a08-1ee6-09197df4af94"><ol style=
=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial, sans-serif"><li =
dir=3D"ltr" style=3D"list-style-type:decimal;background-color:transparent;f=
ont-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:ba=
seline;white-space:pre-wrap;margin-left:11pt"><p dir=3D"ltr" style=3D"line-=
height:1.38;margin-top:10pt;margin-bottom:0pt"><span style=3D"background-co=
lor:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;=
vertical-align:baseline;white-space:pre-wrap">A moratorium is hereby impose=
d on creating tickets for this working group, effective at 5pm PT, Friday, =
February 26th.</span></p></li><li dir=3D"ltr" style=3D"list-style-type:deci=
mal;background-color:transparent;font-variant-numeric:normal;font-variant-e=
ast-asian:normal;vertical-align:baseline;white-space:pre-wrap;margin-left:1=
1pt"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:=
0pt"><span style=3D"background-color:transparent;font-variant-numeric:norma=
l;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wr=
ap">The design team will have until 5pm PT, Friday, April 23rd, to work thr=
ough all applicable tickets, and come to agreement on each to either modify=
 DMARC bis documents (and make such modification) or reject the ticket, wit=
h the reason for rejection added to the ticket&#39;s comments. No tickets w=
ill be closed during this process, everything will be transparent for worki=
ng group review after the design period.</span></p></li><li dir=3D"ltr" sty=
le=3D"list-style-type:decimal;background-color:transparent;font-variant-num=
eric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-sp=
ace:pre-wrap;margin-left:11pt"><p dir=3D"ltr" style=3D"line-height:1.38;mar=
gin-top:0pt;margin-bottom:0pt"><span style=3D"background-color:transparent;=
font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:b=
aseline;white-space:pre-wrap">Changes made to the DMARC bis documents will =
be tracked in the following manner:</span></p></li><ol style=3D"margin-top:=
0px;margin-bottom:0px"><li dir=3D"ltr" style=3D"list-style-type:lower-alpha=
;background-color:transparent;font-variant-numeric:normal;font-variant-east=
-asian:normal;vertical-align:baseline;white-space:pre-wrap"><p dir=3D"ltr" =
style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"=
background-color:transparent;font-variant-numeric:normal;font-variant-east-=
asian:normal;vertical-align:baseline;white-space:pre-wrap">By comments adde=
d to the ticket driving the change</span></p></li><li dir=3D"ltr" style=3D"=
list-style-type:lower-alpha;background-color:transparent;font-variant-numer=
ic:normal;font-variant-east-asian:normal;vertical-align:baseline;white-spac=
e:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-=
bottom:0pt"><span style=3D"background-color:transparent;font-variant-numeri=
c:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space=
:pre-wrap">By comments in the markdown (.md) and/or XML version of the docu=
ments</span></p></li><li dir=3D"ltr" style=3D"list-style-type:lower-alpha;b=
ackground-color:transparent;font-variant-numeric:normal;font-variant-east-a=
sian:normal;vertical-align:baseline;white-space:pre-wrap"><p dir=3D"ltr" st=
yle=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"ba=
ckground-color:transparent;font-variant-numeric:normal;font-variant-east-as=
ian:normal;vertical-align:baseline;white-space:pre-wrap">Through an Appendi=
x section added temporarily to the documents, so that changes can be easily=
 summarized for the next step in the process.</span></p></li><li dir=3D"ltr=
" style=3D"list-style-type:lower-alpha;background-color:transparent;font-va=
riant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline=
;white-space:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"background-color:transparent;font-var=
iant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;=
white-space:pre-wrap">All changes throughout the process will be publicly v=
isible within GitHub (<a href=3D"https://github.com/ietf-wg-dmarc" target=
=3D"_blank">https://github.com/ietf-wg-dmarc</a>).</span></p></li></ol><li =
dir=3D"ltr" style=3D"list-style-type:decimal;background-color:transparent;f=
ont-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:ba=
seline;white-space:pre-wrap;margin-left:11pt"><p dir=3D"ltr" style=3D"line-=
height:1.38;margin-top:0pt;margin-bottom:0pt;padding:0pt 0pt 10pt"><span st=
yle=3D"background-color:transparent;font-variant-numeric:normal;font-varian=
t-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">At the en=
d of the time period, in roughly sixty days (or earlier if their work is fi=
nished before then), the design team will deliver updated versions of the D=
MARC bis documents to the working group, and the working group will have a =
chance to review that version and make comments/recommending edits, etc., u=
sing <a href=3D"https://trac.ietf.org/trac/dmarc/report/1" target=3D"_blank=
">https://trac.ietf.org/trac/dmarc/report/1</a> to create tickets as needed=
. Initial discussion will be limited to what=E2=80=99s in the documents.</s=
pan></p></li><li dir=3D"ltr" style=3D"list-style-type:decimal;background-co=
lor:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;=
vertical-align:baseline;white-space:pre-wrap;margin-left:11pt"><p dir=3D"lt=
r" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=
=3D"color:rgb(0,0,0);background-color:transparent;font-variant-numeric:norm=
al;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-w=
rap">The design team will consult with each other and the chairs during the=
ir work as needed.</span></p></li></font></ol></span></div><div><br></div><=
div>The chairs spent a great deal of time discussing this, and we don=E2=80=
=99t take this action lightly or without hesitation, but in the end we feel=
 it=E2=80=99s the best way to not only make progress on the working group&#=
39;s efforts, but also to allow for working group participants to reset and=
 perhaps gain a fresh perspective on this important work.<br><br></div><div=
>After the updated documents have been presented to the working group, we w=
ill hold an interim to discuss them and hear all feedback.<br></div><div><b=
r></div><div>Seth, Tim, and Alexey, as Co-Chairs</div><div><br></div>-- <br=
><div dir=3D"ltr"><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-to=
p: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:Ar=
ial"><b>Seth Blank</b></span><span style=3D"vertical-align:baseline;white-s=
pace:pre-wrap;font-size:small;font-family:Arial"> | VP, Standards and New T=
echnologies</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"vert=
ical-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><div style=3D"text-align:lef=
t"><span style=3D"vertical-align:baseline"><br></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"><img src=3D"https://valimail-logos.s3.amazonaws=
.com/Valimail__Tag_DarkBlue_TM.png" style=3D"height: 35px; width: 159px;">`=
</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" color=3D"#666666=
"><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></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>

--00000000000026c34a05bbf3ea2a--


From nobody Mon Feb 22 14:05:18 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 0717D3A20D5; Mon, 22 Feb 2021 14:05:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level: 
X-Spam-Status: No, score=-2.086 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, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 20nheCfqPsWT; Mon, 22 Feb 2021 14:05:15 -0800 (PST)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 B35F13A20B9; Mon, 22 Feb 2021 14:05:14 -0800 (PST)
Received: by mail-qk1-x732.google.com with SMTP id x124so3204019qkc.1; Mon, 22 Feb 2021 14:05:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=mUIEMoinCD3pgiUYKzy1QinEnuPysmv+TYWOSQOaz0U=; b=kiv+ZvfO12MIxbaXmSPf0eAvMcouZI4GDRwbV1JEhcK8LE1ygiBHWexfH1oO8aEgWM sAgW6WfqL+4Uk36kCg3XQhAN6MTSy+CVJ8MyOglTl2YVdHses9Ayah1Mzz0k69SBMsVv prokxGuNIYqeiHNK228N+7s1wllFeOpYpZ3YwdcAvhvMEK1R0EtZCYacgvtQ+bkb7OdK cwk0TyNvt4cgNgsFpuBhH8si0G1zi3t2zKxra7mUFscfT/9TB9l4OflgCZ0Pt3NCgCt3 VwIDGkresR9M83UDXLs7QekW0+UZqQ6VQ22BfOyJ51mLtqtZ4j0IYlUtfqhB/ZAE5CZP DE1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=mUIEMoinCD3pgiUYKzy1QinEnuPysmv+TYWOSQOaz0U=; b=O45ob1eJt9U002HT0ARzurMAVBm5PtpPmc17RnJLCbRe07tjJULPqEDqndukpcleYi nVxRzOZ494qTfFRbc5rahjvYpYUcqSX2CWhnYaFxdEfd0FM+1uVTng4hjiTPfP77ylRA xg/sABELlZmlhQOzukHrZTvgtLrzqoYwPKfbOO5UXr3H2XQql3BEJE5vBWF/hjY7/ndo rZ4QXj4duLwsZtD5FEUI9WoZLJerUCf3I4DcbeWpWtiN8EwDhoK0Bdg9onkTWosdh1u8 aFY6uTDutL6I3U9SeIsl0eCYUNLYsVExl9Caa4mkZ66oZ+TcSmqU4fzHjcd5QGttwd+t R23Q==
X-Gm-Message-State: AOAM5307vT7lod9bYuaXn7TLxidqfcN6uZrLxxD5eTXGX7BxsxCGexzC JHrCVt/CtiXdBd8iq8kud7JwlcnpgaQ=
X-Google-Smtp-Source: ABdhPJzjbgUwz5t6bSsdhDrz2P8CTN2LclBoGa2WM9tPyiyD3PE/VEDIsdDxxWLFRh3mvLFkcvv1nw==
X-Received: by 2002:ae9:de85:: with SMTP id s127mr6754037qkf.468.1614031513602;  Mon, 22 Feb 2021 14:05:13 -0800 (PST)
Received: from [192.168.1.89] ([184.15.40.21]) by smtp.gmail.com with ESMTPSA id 82sm13778284qkd.48.2021.02.22.14.05.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 22 Feb 2021 14:05:13 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-A7BA87CB-F53E-4098-BF12-17322B8E992E
Content-Transfer-Encoding: 7bit
From: tjw ietf <tjw.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 22 Feb 2021 17:05:10 -0500
Message-Id: <D6273AEF-E108-4136-819F-9DD471F9E7A4@gmail.com>
References: <CAJ4XoYfNYHb0psvRhF1H0avNx-dauGPQuaSmPUk50Tf=0_vfFQ@mail.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
In-Reply-To: <CAJ4XoYfNYHb0psvRhF1H0avNx-dauGPQuaSmPUk50Tf=0_vfFQ@mail.gmail.com>
To: Dotzero <dotzero@gmail.com>
X-Mailer: iPhone Mail (18D52)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rO9KkEHiOcOthI3WhlYJ_V0NTJk>
Subject: Re: [dmarc-ietf] Announcement - DMARC bis Design Team
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 22 Feb 2021 22:05:17 -0000

--Apple-Mail-A7BA87CB-F53E-4098-BF12-17322B8E992E
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

We=E2=80=99re working on canceling the meeting.=20

Tim

Sent from my iPhone

> On Feb 22, 2021, at 16:59, Dotzero <dotzero@gmail.com> wrote:
>=20
> =EF=BB=BF
> So I'm assuming there won't be anything to talk about at the next IETF mee=
ting.
>=20
> Michael Hammer
>=20
>> On Mon, Feb 22, 2021 at 12:59 PM Seth Blank <seth=3D40valimail.com@dmarc.=
ietf.org> wrote:
>> On 27 October 2020, in post https://mailarchive.ietf.org/arch/msg/dmarc/q=
tCDyGbeDHz96G8FaCxJvhJKrvo/ the chairs announced a split of RFC7489 into thr=
ee documents, to be scoped as follows:
>>=20
>> The DMARC Base Spec (editors - Emil Gustafsson, Todd Herr, and John Levin=
e)
>> Aggregate Reporting (editor - Alex Brotman)
>> Forensic Reporting (editors - Steve Jones and Alessandro Vesely)
>>=20
>> The chairs are of the opinion that discussion of topics related to the DM=
ARC bis documents on the mailing list has reached a point where it would be u=
nreasonable to expect any timely progress toward completion of the refinemen=
t of the DMARC bis at this point.
>>=20
>> Our charter (https://datatracker.ietf.org/wg/dmarc/about/) is clear on wh=
at this working group=E2=80=99s priority should be when reviewing and improv=
ing the DMARC specification: =E2=80=9CIssues based on operational experience=
 and/or data aggregated from multiple sources will be given priority.=E2=80=9D=

>>=20
>> We are spending too much time on items that are at best incidental to DMA=
RC, and rarely are informed by operational practice or data from multiple so=
urces. Efforts by the chairs to weigh in and declare discussions unproductiv=
e work for that particular thread, but the involved parties just move on to a=
nother thread, and consensus remains well over the horizon.
>>=20
>> We have therefore decided that the best approach to achieve progress for t=
he DMARC bis documents is to form a design team, per RFC 2418, Section 6.5. T=
he team will be composed of the editors, focused on their designated documen=
ts, as defined above. The team will be charged with working through all exis=
ting tickets and producing an updated version of each DMARC bis document to p=
resent to the working group, at which point discussion would resume on-list w=
ith respect to the updated documents.
>>=20
>> The design team will operate as follows:
>>=20
>> A moratorium is hereby imposed on creating tickets for this working group=
, effective at 5pm PT, Friday, February 26th.
>> The design team will have until 5pm PT, Friday, April 23rd, to work throu=
gh all applicable tickets, and come to agreement on each to either modify DM=
ARC bis documents (and make such modification) or reject the ticket, with th=
e reason for rejection added to the ticket's comments. No tickets will be cl=
osed during this process, everything will be transparent for working group r=
eview after the design period.
>> Changes made to the DMARC bis documents will be tracked in the following m=
anner:
>> By comments added to the ticket driving the change
>> By comments in the markdown (.md) and/or XML version of the documents
>> Through an Appendix section added temporarily to the documents, so that c=
hanges can be easily summarized for the next step in the process.
>> All changes throughout the process will be publicly visible within GitHub=
 (https://github.com/ietf-wg-dmarc).
>> At the end of the time period, in roughly sixty days (or earlier if their=
 work is finished before then), the design team will deliver updated version=
s of the DMARC bis documents to the working group, and the working group wil=
l have a chance to review that version and make comments/recommending edits,=
 etc., using https://trac.ietf.org/trac/dmarc/report/1 to create tickets as n=
eeded. Initial discussion will be limited to what=E2=80=99s in the documents=
.
>> The design team will consult with each other and the chairs during their w=
ork as needed.
>>=20
>> The chairs spent a great deal of time discussing this, and we don=E2=80=99=
t take this action lightly or without hesitation, but in the end we feel it=E2=
=80=99s the best way to not only make progress on the working group's effort=
s, but also to allow for working group participants to reset and perhaps gai=
n a fresh perspective on this important work.
>>=20
>> After the updated documents have been presented to the working group, we w=
ill hold an interim to discuss them and hear all feedback.
>>=20
>> Seth, Tim, and Alexey, as Co-Chairs
>>=20
>> --=20
>> Seth Blank | VP, Standards and New Technologies
>> e: seth@valimail.com
>> p: 415.273.8818
>>=20
>> `
>> This email and all data transmitted with it contains confidential and/or p=
roprietary information intended solely for the use of individual(s) authoriz=
ed 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 inf=
ormation included in this transmission is prohibited and may be unlawful. Pl=
ease 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

--Apple-Mail-A7BA87CB-F53E-4098-BF12-17322B8E992E
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">We=E2=80=99re working on canceling the meet=
ing.&nbsp;<div><br></div><div>Tim<br><br><div dir=3D"ltr">Sent from my iPhon=
e</div><div dir=3D"ltr"><br><blockquote type=3D"cite">On Feb 22, 2021, at 16=
:59, Dotzero &lt;dotzero@gmail.com&gt; wrote:<br><br></blockquote></div><blo=
ckquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<div dir=3D"ltr"><div>So I'm=
 assuming there won't be anything to talk about at the next IETF meeting.</d=
iv><div><br></div><div>Michael Hammer<br></div></div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Feb 22, 2021 at 12:59 P=
M Seth Blank &lt;seth=3D<a href=3D"mailto:40valimail.com@dmarc.ietf.org">40v=
alimail.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr">On 27 October 2020, in post <a href=
=3D"https://mailarchive.ietf.org/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/=
" target=3D"_blank">https://mailarchive.ietf.org/arch/msg/dmarc/qtCDyGbeDHz9=
6G8FaCxJvhJKrvo/</a> the chairs announced a split of RFC7489 into three docu=
ments, to be scoped as follows:<br><br><ul><li>The DMARC Base Spec (editors -=
 Emil Gustafsson, Todd Herr, and John Levine)</li><li>Aggregate Reporting (e=
ditor - Alex Brotman)</li><li>Forensic Reporting (editors - Steve Jones and A=
lessandro Vesely)</li></ul><br>The chairs are of the opinion that discussion=
 of topics related to the DMARC bis documents on the mailing list has reache=
d a point where it would be unreasonable to expect any timely progress towar=
d completion of the refinement of the DMARC bis at this point.<br><br>Our ch=
arter (<a href=3D"https://datatracker.ietf.org/wg/dmarc/about/" target=3D"_b=
lank">https://datatracker.ietf.org/wg/dmarc/about/</a>) is clear on what thi=
s working group=E2=80=99s priority should be when reviewing and improving th=
e DMARC specification: =E2=80=9CIssues based on operational experience and/o=
r data aggregated from multiple sources will be given priority.=E2=80=9D<br>=
<br>We are spending too much time on items that are at best incidental to DM=
ARC, and rarely are informed by operational practice or data from multiple s=
ources. Efforts by the chairs to weigh in and declare discussions unproducti=
ve work for that particular thread, but the involved parties just move on to=
 another thread, and consensus remains well over the horizon.<br><br>We have=
 therefore decided that the best approach to achieve progress for the DMARC b=
is documents is to form a design team, per RFC 2418, Section 6.5. The team w=
ill be composed of the editors, focused on their designated documents, as de=
fined above. The team will be charged with working through all existing tick=
ets and producing an updated version of each DMARC bis document to present t=
o the working group, at which point discussion would resume on-list with res=
pect to the updated documents.<br><br><font face=3D"arial, sans-serif">The d=
esign team will operate as follows:<br></font><div><div><font face=3D"arial,=
 sans-serif"><br></font></div><div><span id=3D"gmail-m_8798824106628230483gm=
ail-docs-internal-guid-a6c9442d-7fff-4a08-1ee6-09197df4af94"><ol style=3D"ma=
rgin-top:0px;margin-bottom:0px"><font face=3D"arial, sans-serif"><li dir=3D"=
ltr" style=3D"list-style-type:decimal;background-color:transparent;font-vari=
ant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;wh=
ite-space:pre-wrap;margin-left:11pt"><p dir=3D"ltr" style=3D"line-height:1.3=
8;margin-top:10pt;margin-bottom:0pt"><span style=3D"background-color:transpa=
rent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-ali=
gn:baseline;white-space:pre-wrap">A moratorium is hereby imposed on creating=
 tickets for this working group, effective at 5pm PT, Friday, February 26th.=
</span></p></li><li dir=3D"ltr" style=3D"list-style-type:decimal;background-=
color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal=
;vertical-align:baseline;white-space:pre-wrap;margin-left:11pt"><p dir=3D"lt=
r" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D=
"background-color:transparent;font-variant-numeric:normal;font-variant-east-=
asian:normal;vertical-align:baseline;white-space:pre-wrap">The design team w=
ill have until 5pm PT, Friday, April 23rd, to work through all applicable ti=
ckets, and come to agreement on each to either modify DMARC bis documents (a=
nd make such modification) or reject the ticket, with the reason for rejecti=
on added to the ticket's comments. No tickets will be closed during this pro=
cess, everything will be transparent for working group review after the desi=
gn period.</span></p></li><li dir=3D"ltr" style=3D"list-style-type:decimal;b=
ackground-color:transparent;font-variant-numeric:normal;font-variant-east-as=
ian:normal;vertical-align:baseline;white-space:pre-wrap;margin-left:11pt"><p=
 dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><sp=
an style=3D"background-color:transparent;font-variant-numeric:normal;font-va=
riant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Change=
s made to the DMARC bis documents will be tracked in the following manner:</=
span></p></li><ol style=3D"margin-top:0px;margin-bottom:0px"><li dir=3D"ltr"=
 style=3D"list-style-type:lower-alpha;background-color:transparent;font-vari=
ant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;wh=
ite-space:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;=
margin-bottom:0pt"><span style=3D"background-color:transparent;font-variant-=
numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-=
space:pre-wrap">By comments added to the ticket driving the change</span></p=
></li><li dir=3D"ltr" style=3D"list-style-type:lower-alpha;background-color:=
transparent;font-variant-numeric:normal;font-variant-east-asian:normal;verti=
cal-align:baseline;white-space:pre-wrap"><p dir=3D"ltr" style=3D"line-height=
:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"background-color:tran=
sparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-=
align:baseline;white-space:pre-wrap">By comments in the markdown (.md) and/o=
r XML version of the documents</span></p></li><li dir=3D"ltr" style=3D"list-=
style-type:lower-alpha;background-color:transparent;font-variant-numeric:nor=
mal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-w=
rap"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0=
pt"><span style=3D"background-color:transparent;font-variant-numeric:normal;=
font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"=
>Through an Appendix section added temporarily to the documents, so that cha=
nges can be easily summarized for the next step in the process.</span></p></=
li><li dir=3D"ltr" style=3D"list-style-type:lower-alpha;background-color:tra=
nsparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical=
-align:baseline;white-space:pre-wrap"><p dir=3D"ltr" style=3D"line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><span style=3D"background-color:transpa=
rent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-ali=
gn:baseline;white-space:pre-wrap">All changes throughout the process will be=
 publicly visible within GitHub (<a href=3D"https://github.com/ietf-wg-dmarc=
" target=3D"_blank">https://github.com/ietf-wg-dmarc</a>).</span></p></li></=
ol><li dir=3D"ltr" style=3D"list-style-type:decimal;background-color:transpa=
rent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-ali=
gn:baseline;white-space:pre-wrap;margin-left:11pt"><p dir=3D"ltr" style=3D"l=
ine-height:1.38;margin-top:0pt;margin-bottom:0pt;padding:0pt 0pt 10pt"><span=
 style=3D"background-color:transparent;font-variant-numeric:normal;font-vari=
ant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">At the e=
nd of the time period, in roughly sixty days (or earlier if their work is fi=
nished before then), the design team will deliver updated versions of the DM=
ARC bis documents to the working group, and the working group will have a ch=
ance to review that version and make comments/recommending edits, etc., usin=
g <a href=3D"https://trac.ietf.org/trac/dmarc/report/1" target=3D"_blank">ht=
tps://trac.ietf.org/trac/dmarc/report/1</a> to create tickets as needed. Ini=
tial discussion will be limited to what=E2=80=99s in the documents.</span></=
p></li><li dir=3D"ltr" style=3D"list-style-type:decimal;background-color:tra=
nsparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical=
-align:baseline;white-space:pre-wrap;margin-left:11pt"><p dir=3D"ltr" style=3D=
"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"color:rgb=
(0,0,0);background-color:transparent;font-variant-numeric:normal;font-varian=
t-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">The design=
 team will consult with each other and the chairs during their work as neede=
d.</span></p></li></font></ol></span></div><div><br></div><div>The chairs sp=
ent a great deal of time discussing this, and we don=E2=80=99t take this act=
ion lightly or without hesitation, but in the end we feel it=E2=80=99s the b=
est way to not only make progress on the working group's efforts, but also t=
o allow for working group participants to reset and perhaps gain a fresh per=
spective on this important work.<br><br></div><div>After the updated documen=
ts have been presented to the working group, we will hold an interim to disc=
uss them and hear all feedback.<br></div><div><br></div><div>Seth, Tim, and A=
lexey, as Co-Chairs</div><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><d=
iv style=3D"text-align:left"><span style=3D"vertical-align:baseline;white-sp=
ace:pre-wrap;font-size:small;font-family:Arial"><b>Seth Blank</b></span><spa=
n 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:baselin=
e"><b>e:</b></span><span style=3D"vertical-align:baseline"> <a href=3D"mailt=
o: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></span=
></div><div style=3D"text-align:left"><span style=3D"vertical-align:baseline=
"><br></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,25=
5,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><img src=3D"https:=
//valimail-logos.s3.amazonaws.com/Valimail__Tag_DarkBlue_TM.png" style=3D"he=
ight: 35px; width: 159px;" data-unique-identifier=3D"">`</p><p dir=3D"ltr" s=
tyle=3D"background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;ma=
rgin-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 wit=
h it contains confidential and/or proprietary information intended solely fo=
r the use of individual(s) authorized to receive it. If you are not an inten=
ded 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 rep=
lying to this email and then delete it from your system.</span></font></p></=
span></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" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>
</div></blockquote></div></body></html>=

--Apple-Mail-A7BA87CB-F53E-4098-BF12-17322B8E992E--


From nobody Tue Feb 23 04:37:30 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 75E033A2AAF for <dmarc@ietfa.amsl.com>; Tue, 23 Feb 2021 04:37: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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=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 VCCpyn0mZiM4 for <dmarc@ietfa.amsl.com>; Tue, 23 Feb 2021 04:37: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 CBF863A2AAE for <dmarc@ietf.org>; Tue, 23 Feb 2021 04:37:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1614083844; bh=jKO6qU0JG8JAs/C9vplFleX3EExVl0eOc28KzslqkgY=; l=1006; h=To:References:From:Date:In-Reply-To; b=BWXbdzRBZjc2SA+TfcTBKWJJdp1jT1S3Ht+MEdWrNob7+s2MLLfwRQa2fmB+cDPeC 3rMVB/bssZXKTz4HvB9RIdDW8eZtL/6VVQDioUofpt5nIkM5Jz0+fMdjcbxGllEAwL KG5Scvs6pr3tCEMkNt4TtoUI9xeqXZAc18Q7yTdHfq6WPnpoRps233XYVRcI5
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 00000000005DC050.000000006034F703.0000568B; Tue, 23 Feb 2021 13:37:23 +0100
To: 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> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <VI1PR01MB705365834B737AF46A2DF099C7819@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <7f7dc32b-eccc-5aae-1780-a8cf07c32fac@tana.it>
Date: Tue, 23 Feb 2021 13:37:23 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <VI1PR01MB705365834B737AF46A2DF099C7819@VI1PR01MB7053.eurprd01.prod.exchangelabs.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/9eIlsLQv6zIMoPZOfHT4kmh8l7s>
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: Tue, 23 Feb 2021 12:37:29 -0000

On Mon 22/Feb/2021 15:36:00 +0100 Ken O'Driscoll wrote:
> I would go even further and not even talk about the trees and nodes. Also, 
> echoing elsewhere in this thread, making it really clear that this is not a 
> case of /DMARC is coming for your TLD/. So, I’d propose something super basic 
> like this for the second paragraph:
> 
>     Domain name suffixes (for example .com, .eu, and .co.uk) are controlled by 
>     registries, who either directly or through accredited registrars, facilitate 
>     the registration and management of domain names below these suffixes. DMARC 
>     currently permits expression of policy only for domain names and not for domain 
>     suffixes. Since its deployment in 2015, specialist use cases have been 
>     identified where it may be desirable for a suffix to express a DMARC policy. 
>     This document describes an experimental extension to DMARC to add that capability.


Clear and concise.  Just s/only for domain names/only for registered domain names/.


Best
Ale
-- 
















From nobody Wed Feb 24 21:10:30 2021
Return-Path: <barryleiba.mailing.lists@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 4EEF63A1254 for <dmarc@ietfa.amsl.com>; Wed, 24 Feb 2021 21:10:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Level: 
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 AceUmggivbBb for <dmarc@ietfa.amsl.com>; Wed, 24 Feb 2021 21:10:26 -0800 (PST)
Received: from mail-ej1-f52.google.com (mail-ej1-f52.google.com [209.85.218.52]) (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 454343A1252 for <dmarc@ietf.org>; Wed, 24 Feb 2021 21:10:26 -0800 (PST)
Received: by mail-ej1-f52.google.com with SMTP id w1so6658240ejf.11 for <dmarc@ietf.org>; Wed, 24 Feb 2021 21:10:26 -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:content-transfer-encoding; bh=nJIL3NtY7/Cg0zIjYOJg0+AWRGq8s86IYpzY0NdmJTk=; b=HuVbnHBdzqL0bQhearqeHEbYbYnhJ6ym0K04eCi+GPZiNS4lM1dwuA30h0ltfEB47O 5oHpP2824i+jMtD7lz1cgrrDAyWga6ZP5veMdOiLpFs7CXKvXmkJ+AaNBq7o4Hd/MxJ3 jZ46zqodgFADpsJSlDL8z6w5K/hFcHMWLZUNuzCwFSq9czE7LfQIde73Gua4ykPmWZ3L C42HZE5emIIx5IA/Q6qAgnV/cSFKvma+Jm42+5/2rgCJUJAlQATmRexpj1DUxICTfjW3 R23kMICDN/4zyF+c7kJlW8XplKx0TtX9gnT4gicY/CLT0n/k9pExeMVjsZTSwyFEbJXb HBfg==
X-Gm-Message-State: AOAM5331WzoaaZH2XTcAM37jpBoH6bFVLeSwipRycbRtZjD33evpRLjj dy7NSwDvuz0S6uvB+Ux//by6VgN7QisnW8tsGhs=
X-Google-Smtp-Source: ABdhPJwMXzGMVwjNCPlm8W22FC9j0pqwxX29CfsFkI5ncFhjUEAGhGQDoNsqNpe1uorO0y6vd6nN1iJmLm7AjwRN1D4=
X-Received: by 2002:a17:907:2513:: with SMTP id y19mr963560ejl.241.1614229824576;  Wed, 24 Feb 2021 21:10:24 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com>
In-Reply-To: <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 25 Feb 2021 00:10:13 -0500
Message-ID: <CAC4RtVARxfJNUs+ve1ViDTF385QjLoyhw8JyKc-nALhuu=xoPA@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Qzld0b9Dp25KAEGL8j_kHygPLAw>
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: Thu, 25 Feb 2021 05:10:28 -0000

OK, here's my proposal; please let me know what you think:

=E2=80=94 Abstract =E2=80=94

OLD
   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.

NEW
   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.

   DMARC uses a Public Suffix List (PSL) to determine what part of a
   domain name is the Public Suffix Domain (PSD), below which
   organizational domain names are created.  DMARC allows organizational
   domains to specify policies that apply to their subdomains, but it
   does not give that flexibility to PSDs.

   This document describes an extension to DMARC to fully enable DMARC
   functionality for PSDs.  This document also addresses implementations
   that consider a domain on a public Suffix list to be ineligible for
   DMARC enforcement.


=E2=80=94 Section 1 =E2=80=94

OLD
   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.

NEW
   DMARC as specified presumes that domain names present in a Public
   Suffix List (PSL) =E2=80=94 Public Suffix Domains (PSDs) =E2=80=94 are n=
ot
   organizational domains and are thus not subject to DMARC processing.
   In DMARC, domains fall into one of three categories: organizational
   domains, sub-domains of organizational domains, or PSDs.  For PSDs,
   policy can only be published for the exact domain: no mechanism is
   available for PSDs to express policy or receive feedback reporting
   for sub-domains.  The lack of such a mechanism allows for the abuse
   of non-existent organizational-level domains and hampers
   identification of domain abuse in email.

=E2=80=94 Section 1.1 =E2=80=94

OLD
   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 structurewould 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.

NEW
   As an example, imagine a Top-Level Domain (TLD), ".example", that has
   public subdomains for government and commercial use (".gov.example"
   and ".com.example").  A PSL whose maintainer is aware of this TLD=E2=80=
=99s
   domain structure would include entries for both of these in the PSL,
   indicating that they are PSDs below which organizational domains can
   be registered.  Suppose further that there exists a legitimate domain
   called "tax.gov.example", registered within ".gov.example".



OLD
   This DMARC record provides policy and a reporting destination for
   mail sent from @gov.example.  However, due to DMARC's current method
   of discovering and applying policy at the organizational domain
   level, the non-existent organizational domain of @t4x.gov.example
   does not and cannot fall under a DMARC policy.

NEW
   This DMARC record provides policy and a reporting destination for
   mail sent from @gov.example.  Similarly, "tax.gov.example" will have
   a DMARC record that specifies policy for mail sent from addresses
   @tax.gov.example.  However, due to DMARC's current method of
   discovering and applying policy at the organizational domain
   level, the non-existent organizational domain of @t4x.gov.example
   does not and cannot fall under a DMARC policy.


--=20
Barry

On Mon, Feb 22, 2021 at 9:33 AM Barry Leiba <barryleiba@computer.org> wrote=
:
>
> >> > I'm at a loss to understand what's confusing.  I'm not convinced tha=
t "registrations" in the
> >> > context of domain names is unclear to a reader familiar with this sp=
ace.
> >>
> >> I am absolutely convinced that it is.  Think of people in M3AAWG, for
> >> whom this is very relevant.  Many of them don't know much about
> >> registries, registrars, and such, and in general, the average reader
> >> won't understand the difference, from a "registration" standpoint,
> >> between facebook.com (which is registered) and "www.facebook.com"
> >> (which is not).  To the average reader, "facebook.com" is registered
> >> under com, and "www.facebook.com" is registered under facebook.  And
> >> the ones who don't think that will likely not understand why we can't
> >> just talk about second-level domains and be done with it.
> >
> > Actually that's a community that I would expect to know exactly what al=
l those terms mean and
> > how they are all related.
>
> There clearly are some in that community who do.  But there are many
> there who don't.  This stuff is more esoteric than those of us who are
> in the middle of it often realize.
>
> > I think the use of "registered" seems to be the source of some of this =
confusion.
>
> Yes, exactly.
>
> > To work with the example you gave here, I agree that "facebook.com" is =
registered (under "com"), but
> > disagree that "www.facebook.com" is registered at all;
>
> Right, of course it's not.  I didn't say that it is: I said that
> people who don't fully understand this stuff *think* it is, and that's
> the part that the text isn't making clear.
>
> > To my mind, "register" involves a specific transaction, sometimes invol=
ving money, with whoever gates
> > access to make those delegations.
>
> And that's what we need to explain better in the Introduction.
>
> > How's this?:
> >
> >    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-receivin=
g
> >    organization can use to improve mail handling.
> >
> >    Within the Domain Name System (DNS) on the public Internet, which is
> >    organized as a tree, some nodes of that tree are reserved for use by
> >    registrars, who delegate sub-trees to other operators on request.  D=
MARC currently
> >    permits expression of policy only for such sub-trees.  There is a ma=
rked desire to
> >    be able to express policy for the reserved nodes as well.  This docu=
ment
> >    describes an experimental extension to DMARC to add that capability.
> >
> > If we like that as a replacement Abstract, I'll carry on and propose a =
revision to the Introduction.
>
> I don't think that really explains it properly either -- I think with
> the above text, it's less confusing, but also not correct, or at least
> not really indicative of what the document is proposing.
>
> I don't have time today, but give me a couple of days to work on the
> Abstract and the Introduction/Example, and I'll propose some specific
> text that we can try out.
>
> Barry
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


From nobody Thu Feb 25 06:13:32 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 F12BE3A1A5A for <dmarc@ietfa.amsl.com>; Thu, 25 Feb 2021 06:13:30 -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, FREEMAIL_FROM=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 mYFIY9Lo06RL for <dmarc@ietfa.amsl.com>; Thu, 25 Feb 2021 06:13:29 -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 631723A1A58 for <dmarc@ietf.org>; Thu, 25 Feb 2021 06:13:29 -0800 (PST)
Received: by mail-ot1-x330.google.com with SMTP id f33so5744716otf.11 for <dmarc@ietf.org>; Thu, 25 Feb 2021 06:13:29 -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=3fW8n+4OffSs+d6s2K7bFd4gR2RlNMN5pGw818cYFo0=; b=X94CsM5JeEjWc74HfJ5C4R+uLjfwwlF6u95bksTKJaP+ZHs1VO/pEnu7txAVexIduL akd28b/x+euTZ8NOM0QFeC/Fmcteh6kiyQIlDosxbUcVfFtVvHMqDqoWfjLgLXdsBp0+ ++ZlNWvECSdRRe0M8L9J28HB4MW9qyrWegGyPBYxu2Z0PrQuah5bIYr3BEWSsGShs19p cnsk7DBjgWCWpalMcS0np4p883VcHJxrBw6tS+A+/9eq7ThB7Jo53f3YgkvPKtJm+cP8 1jz1H2IZbqZozmPzH3xBbyW3zO1PutuRPQEMGOgBxLmQl1Oqv2RnK3vjrHECpK0jod3h AFog==
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=3fW8n+4OffSs+d6s2K7bFd4gR2RlNMN5pGw818cYFo0=; b=ujV8AajmpB9EyCGMHnXz0TX/Dmi1jgogy/fOfPXZKbe+TgH9wd8I5q3p3TaoyvMWMK r2u11UqNQUnQ+W5wnzIQ5eKRVXLBBjjC8XJxsxZna7aHjtiU1zxu2FCnWIAisPedo2EE aeyEdZ2t66la5AbXU8WtuzQP6AlS0Wtyc3vJb/po5Qp7EyBeqzRpMFG8FR39Famt3RrO 8W2TFpwvJTI7RELpxbZFJdiTj/eq7+aBq42HvsrRWY9DMVn0J9koigAq8fdAKNF5QGpz M5z35cg1GgPIPXI9qW0aknglJ45v87Y8KqWZyWsopxPsKMUfZ34H3NjOENq5HRQZRCUJ Hlng==
X-Gm-Message-State: AOAM5329IrMtynl5nUnoDVd6aysLoDRAMlUNTHeZ9bulRonojySj8lTF +BRjLq+baZihGs2LiQOQbUmb0368eBgxJw==
X-Google-Smtp-Source: ABdhPJxWFTsIttt9svrON1GvJPWPwEPqj9o+pKFKnQXx3cHsNqbvxYJ05V+xlivAr173LB7+rhTqmA==
X-Received: by 2002:a05:6830:1d43:: with SMTP id p3mr2481467oth.184.1614262408500;  Thu, 25 Feb 2021 06:13:28 -0800 (PST)
Received: from [192.168.0.102] (108-226-162-63.lightspeed.sntcca.sbcglobal.net. [108.226.162.63]) by smtp.gmail.com with ESMTPSA id w22sm1080206otm.73.2021.02.25.06.13.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 25 Feb 2021 06:13:27 -0800 (PST)
To: Barry Leiba <barryleiba@computer.org>
Cc: 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> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <CAC4RtVARxfJNUs+ve1ViDTF385QjLoyhw8JyKc-nALhuu=xoPA@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <81c05041-a4ad-a473-701c-0027cd503696@gmail.com>
Date: Thu, 25 Feb 2021 06:13:24 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <CAC4RtVARxfJNUs+ve1ViDTF385QjLoyhw8JyKc-nALhuu=xoPA@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/W0eZBGE1cPHktPrViLeDbwTvf0o>
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: Thu, 25 Feb 2021 14:13:31 -0000

If everyone liked using the PSL and making it integral to DMARC, then 
that would be fine.  But they don't; so it isn't.

The suggested revisions to Barry's suggested revisions, below, primarily 
serve to reference the PSD construct without needing to reference the 
PSL.  And, of course, there are various other suggested wording tweaks...


On 2/24/2021 9:10 PM, Barry Leiba wrote:
> — Abstract —
>
>
> NEW
>     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.
>
>     DMARC uses a Public Suffix List (PSL) to determine what part of a
>     domain name is the Public Suffix Domain (PSD), below which
>     organizational domain names are created.  DMARC allows organizational
>     domains to specify policies that apply to their subdomains, but it
>     does not give that flexibility to PSDs.
>
>     This document describes an extension to DMARC to fully enable DMARC
>     functionality for PSDs.  This document also addresses implementations
>     that consider a domain on a public Suffix list to be ineligible for
>     DMARC enforcement.

The major intention is removal of reference to /how/ it does the hierarchy distinction.  In case it ever uses a different mechanism that people like better...

EVEN NEWER
    Domain-based Message Authentication, Reporting, and
    Conformance (DMARC) permits a mail-originating
    organization to express domain-level policies and preferences for
    message validation, disposition, and reporting, which a mail-receiving
    organization can use to improve mail handling.

    DMARC distinguishes the portion of a name that is a
       Public Suffix Domain (PSD), below which
    organizational domain names are created.  The basic DMARC capability allows organizational
    domains to specify policies that apply to their subdomains, but it
    does not give that capability to PSDs. This document describes an extension to DMARC to
       fully enable DMARC
    functionality for PSDs.

    Some implementations of DMARC consider a PSD to be ineligible for
    DMARC enforcement.  This specification addresses that case.




> — Section 1 —
>
> NEW
>     DMARC as specified presumes that domain names present in a Public
>     Suffix List (PSL) — Public Suffix Domains (PSDs) — are not
>     organizational domains and are thus not subject to DMARC processing.
>     In DMARC, domains fall into one of three categories: organizational
>     domains, sub-domains of organizational domains, or PSDs.  For PSDs,
>     policy can only be published for the exact domain: no mechanism is
>     available for PSDs to express policy or receive feedback reporting
>     for sub-domains.  The lack of such a mechanism allows for the abuse
>     of non-existent organizational-level domains and hampers
>     identification of domain abuse in email.

EVEN NEWER

NEW
    In the basic DMARC model, PSDs are not
    organizational domains and are thus not subject to DMARC processing.
    In DMARC, domains fall into one of three categories: organizational
    domains, sub-domains of organizational domains, or PSDs.  A PSD
    can only publish DMARC policy for itself, and not for any sub-domains under it.
       In some cases, this limitation allows for the abuse
    of non-existent organizational-level domains and hampers
    identification of domain abuse in email.




> — Section 1.1 —
>
> OLD
>     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 structurewould 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.
>
> NEW
>     As an example, imagine a Top-Level Domain (TLD), ".example", that has
>     public subdomains for government and commercial use (".gov.example"
>     and ".com.example").  A PSL whose maintainer is aware of this TLD’s
>     domain structure would include entries for both of these in the PSL,
>     indicating that they are PSDs below which organizational domains can
>     be registered.  Suppose further that there exists a legitimate domain
>     called "tax.gov.example", registered within ".gov.example".


EVEN NEWER
    As an example, imagine a Top-Level Domain (TLD), ".example", that has
    public subdomains for government and commercial use (".gov.example"
    and ".com.example").  The maintainer of a list of such a PSD structure
    would include entries for both of these sub-domains, thereby
    indicating that they are PSDs, below which organizational domains can
    be registered.  Suppose further that there exists a legitimate domain
    called "tax.gov.example", registered within ".gov.example".




> NEW
>     This DMARC record provides policy and a reporting destination for
>     mail sent from @gov.example.  Similarly, "tax.gov.example" will have
>     a DMARC record that specifies policy for mail sent from addresses
>     @tax.gov.example.  However, due to DMARC's current method of
>     discovering and applying policy at the organizational domain
>     level, the non-existent organizational domain of @t4x.gov.example
>     does not and cannot fall under a DMARC policy.

darn.  couldn't find anything to suggest changing for this one...


d/

  

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


From nobody Thu Feb 25 08:42:10 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 A2C323A1C1F for <dmarc@ietfa.amsl.com>; Thu, 25 Feb 2021 08:42: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, 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 dh9WDW63W5JT for <dmarc@ietfa.amsl.com>; Thu, 25 Feb 2021 08:42:07 -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 0CA0D3A1C1D for <dmarc@ietf.org>; Thu, 25 Feb 2021 08:42:07 -0800 (PST)
Received: by mail-io1-xd34.google.com with SMTP id u20so6517949iot.9 for <dmarc@ietf.org>; Thu, 25 Feb 2021 08:42:06 -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=ZlIMjycjmc5cCzO9hYGoAOb3lrNn87bTlYOIbYjtwDg=; b=C1cOzq6XAsiVCt6p9+iyVF5lfDl/ZcqpcFMP98H3qMsse6c0gP0BEwqwXU7Wk4yOOi ljq2S7weHJGBhCDoNVKpiQZcwRYxYkpRQOnH8R2/uEqK7memd+8ASpCDHt1GAQXkRkVf nz86vobID6mtA1BBxqAS/IN3x12563pfl9h/8=
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=ZlIMjycjmc5cCzO9hYGoAOb3lrNn87bTlYOIbYjtwDg=; b=fan+o3S2+l7dVq5vGFnYTZdOVnJYCALr80Jt3vHLjskFz8fe6+SkDu9V12kp8z0E3h QA/EkW3g01JOibHmWr+YzUNm4uDfHv4L7PIJEpeURjxKZZjVZZjbyVhtiWxFbiTITNEx FtJkZRb4X7XT+bMoQMq7gmrHwUl964gcSD5/TpAw71wdS/gcRJCFAfn7ImlhHs/6RjuB jJRM52SR5MBilHedAOovwistVsi7/5CCpzmnBTHQBsvHmmSFXy2ktTg++qJPfGfzpkBZ qenbtuMZF67+ZDxPJWUusQ4gte3sIrzISAycPrl84g1ifBil4Uacw3PsaLXt29wNFika 42cg==
X-Gm-Message-State: AOAM531lKGt0UXKozUGCSwYriTHP3c0qu1txFbFaK4MOHQSqAddwIbyB NdBaFTRacStCC1AVDx5vxZIbswOJFcYZSKAQiZUOFg==
X-Google-Smtp-Source: ABdhPJw2jfIlQ5L3CvPtEJd4aLAuK/oXlaWXcPvbLT8orcuF9kBwYnfUzYgG3R5Oa93qRUZn4L5wslwJYhbzDYjCMvI=
X-Received: by 2002:a05:6638:eca:: with SMTP id q10mr4031577jas.116.1614271326236;  Thu, 25 Feb 2021 08:42:06 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <CAC4RtVARxfJNUs+ve1ViDTF385QjLoyhw8JyKc-nALhuu=xoPA@mail.gmail.com> <81c05041-a4ad-a473-701c-0027cd503696@gmail.com>
In-Reply-To: <81c05041-a4ad-a473-701c-0027cd503696@gmail.com>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Thu, 25 Feb 2021 08:41:54 -0800
Message-ID: <CABuGu1pncrHQ-Ba7t7VEcbYrjfoc_Ek_3B5X66owSE2GWRdPSg@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: Barry Leiba <barryleiba@computer.org>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f8cbb205bc2bd4a8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/wFiws1Iru-3sMdOD06vA37OI_OQ>
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: Thu, 25 Feb 2021 16:42:09 -0000

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

This is getting much better - thanks for all the wordsmithing. I have one
nuance to add...

On Thu, Feb 25, 2021 at 6:13 AM Dave Crocker <dcrocker@gmail.com> wrote:

>
> The suggested revisions to Barry's suggested revisions, below, primarily
> serve to reference the PSD construct without needing to reference the
> PSL.  And, of course, there are various other suggested wording tweaks...
>
> EVEN NEWER
>     Domain-based Message Authentication, Reporting, and
>     Conformance (DMARC) permits a mail-originating
>     organization to express domain-level policies and preferences for
>     message validation, disposition, and reporting, which a mail-receiving
>     organization can use to improve mail handling.
>

Especially in the case of the PSD policies, one should not expect that the
controlling organization would necessarily be "a mail-originating
organization". Generally the idea is to *disavow* being such :-)

Suggested alternate text:

Domain-based Message Authentication, Reporting, and Conformance (DMARC)
permits a domain-controlling
organization to express domain-level policies and preferences for message
validation, disposition, and reporting,
which a mail-receiving organization can use to improve mail handling.

--Kurt

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

<div dir=3D"ltr"><div>This is getting much better - thanks for all the word=
smithing. I have one nuance to add...</div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Thu, Feb 25, 2021 at 6:13 AM Dave C=
rocker &lt;<a href=3D"mailto:dcrocker@gmail.com">dcrocker@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"><br>
The suggested revisions to Barry&#39;s suggested revisions, below, primaril=
y <br>
serve to reference the PSD construct without needing to reference the <br>
PSL.=C2=A0 And, of course, there are various other suggested wording tweaks=
...<br><br>
EVEN NEWER<br>
=C2=A0 =C2=A0 Domain-based Message Authentication, Reporting, and<br>
=C2=A0 =C2=A0 Conformance (DMARC) permits a mail-originating<br>
=C2=A0 =C2=A0 organization to express domain-level policies and preferences=
 for<br>
=C2=A0 =C2=A0 message validation, disposition, and reporting, which a mail-=
receiving<br>
=C2=A0 =C2=A0 organization can use to improve mail handling.<br></blockquot=
e><div><br></div><div>Especially in the case of the PSD policies, one shoul=
d not expect that the controlling organization would necessarily be &quot;a=
 mail-originating organization&quot;. Generally the idea is to *disavow* be=
ing such :-)</div><div><br></div><div>Suggested alternate text:</div><div><=
br></div><div>Domain-based Message Authentication, Reporting, and Conforman=
ce (DMARC) permits a domain-controlling</div>organization to express domain=
-level policies and preferences for message validation, disposition, and re=
porting,=C2=A0</div><div class=3D"gmail_quote">which a mail-receiving organ=
ization can use to improve mail handling.</div><div class=3D"gmail_quote"><=
br></div><div class=3D"gmail_quote">--Kurt</div></div>

--000000000000f8cbb205bc2bd4a8--


From nobody Thu Feb 25 09:13: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 E32C13A1CA5 for <dmarc@ietfa.amsl.com>; Thu, 25 Feb 2021 09:13: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 fB5rbLCgN5WL for <dmarc@ietfa.amsl.com>; Thu, 25 Feb 2021 09:13:13 -0800 (PST)
Received: from mail-oo1-xc34.google.com (mail-oo1-xc34.google.com [IPv6:2607:f8b0:4864:20::c34]) (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 05F0A3A1CA3 for <dmarc@ietf.org>; Thu, 25 Feb 2021 09:13:12 -0800 (PST)
Received: by mail-oo1-xc34.google.com with SMTP id g46so1539482ooi.9 for <dmarc@ietf.org>; Thu, 25 Feb 2021 09:13: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=1qq2DQ5jDwO7bZWoKDw1yQoLUnJpdNHeIaHdehCvgck=; b=XHSMWIWLIwha4xZFWU0MPCKYJqS4XWlDx0eR4u/Y1m6wSX7/VtnoCzoJynNhPF0Qea bAqIDVyMPHxGi/fUGVZEQz97LwDQy2EnAK4WiZFigUswGnJaNWrKBIaYB+vcROAtxYO/ 73qbcQ63JRSIJaBCxTlYLex+Rmla5GyF2kL+It26NrmtCUtqSnwBJDUxHX/Og9WSF3Xs tbgNl8823BkXvFrM4wNV+HGa90pkYFDQYBdGnJH65uq9aFi2cBPIl6hjg29jFr8NrlTs THnr2h7xi0NVY2RxZIUooX3K9EoDTJvDbesxloiixHFpbJ2KA4F+SLIQ5aaCvEB3twbu rcyQ==
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=1qq2DQ5jDwO7bZWoKDw1yQoLUnJpdNHeIaHdehCvgck=; b=ETClmqFD4lQjlIynY7SofJmssY3MfYVJv/PKNDh7hnu3HWgf3ws03GASELMyZWv8dY uQxTAe9m0x3zDHqYYFdlnTQ1IbXnITugWHVgFzvsxNqhzVVxHfTvESuDLtZRfc3VMzDk zK1BnZIu1N9idBgxgpaWBS1+h/v+4Qte9ZPmcFw0m0FW6qRFAI0d/TK744W9lZ2dRYOH eZd3kqT3B//nLPXs+2I+4gthwVF1vRATLce1jO6aLr8MOV5dkET2H0mZudveFE/S5cho S4BImXHTx0cPF/gj0v+TgThFeb3vBGBtuY0TSy4DkzyH0JAa3d07IvaaM2n8mzqC61td A1Gw==
X-Gm-Message-State: AOAM531vnfNnhT4jaiY+96bczk4g/1uLOODiAnLSYN40Q34ARvDm/LA6 vUkDkIzBDNbPtKna7orV8vd6hiyumEC7lQ==
X-Google-Smtp-Source: ABdhPJx029q0IH5EakXtSbOSH5RdPeiuM/J8HC3cj/imPEPrJYb4btb+JRml1RZEsNb+0DiHpb29Pg==
X-Received: by 2002:a4a:d994:: with SMTP id k20mr3169356oou.70.1614273190652;  Thu, 25 Feb 2021 09:13:10 -0800 (PST)
Received: from [192.168.0.102] (108-226-162-63.lightspeed.sntcca.sbcglobal.net. [108.226.162.63]) by smtp.gmail.com with ESMTPSA id q131sm718163oic.45.2021.02.25.09.13.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 25 Feb 2021 09:13:10 -0800 (PST)
To: "Kurt Andersen (b)" <kboth@drkurt.com>
Cc: Barry Leiba <barryleiba@computer.org>, 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> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <CAC4RtVARxfJNUs+ve1ViDTF385QjLoyhw8JyKc-nALhuu=xoPA@mail.gmail.com> <81c05041-a4ad-a473-701c-0027cd503696@gmail.com> <CABuGu1pncrHQ-Ba7t7VEcbYrjfoc_Ek_3B5X66owSE2GWRdPSg@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <8c715354-54ed-434a-c630-bb3c902cb8da@gmail.com>
Date: Thu, 25 Feb 2021 09:13:08 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <CABuGu1pncrHQ-Ba7t7VEcbYrjfoc_Ek_3B5X66owSE2GWRdPSg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------88483E2A993058BE440B93CE"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/yrV-trPSwQ5-apH_QkMGYqF5y80>
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: Thu, 25 Feb 2021 17:13:15 -0000

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

On 2/25/2021 8:41 AM, Kurt Andersen (b) wrote:
> Especially in the case of the PSD policies, one should not expect that 
> the controlling organization would necessarily be "a mail-originating 
> organization". Generally the idea is to *disavow* being such :-)
>
> Suggested alternate text:
>
> Domain-based Message Authentication, Reporting, and Conformance 
> (DMARC) permits a domain-controlling
> organization to express domain-level policies and preferences for 
> message validation, disposition, and reporting,
> which a mail-receiving organization can use to improve mail handling.

+1

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

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


--------------88483E2A993058BE440B93CE
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 2/25/2021 8:41 AM, Kurt Andersen (b)
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABuGu1pncrHQ-Ba7t7VEcbYrjfoc_Ek_3B5X66owSE2GWRdPSg@mail.gmail.com">
      <div class="gmail_quote">
        <div>Especially in the case of the PSD policies, one should not
          expect that the controlling organization would necessarily be
          "a mail-originating organization". Generally the idea is to
          *disavow* being such :-)</div>
        <div><br>
        </div>
        <div>Suggested alternate text:</div>
        <div><br>
        </div>
        <div>Domain-based Message Authentication, Reporting, and
          Conformance (DMARC) permits a domain-controlling</div>
        organization to express domain-level policies and preferences
        for message validation, disposition, and reporting, </div>
      <div class="gmail_quote">which a mail-receiving organization can
        use to improve mail handling.</div>
    </blockquote>
    <p>+1</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>

--------------88483E2A993058BE440B93CE--


From nobody Fri Feb 26 18:15:12 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 7AFBD3A08A5 for <dmarc@ietfa.amsl.com>; Fri, 26 Feb 2021 18:15:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.088
X-Spam-Level: 
X-Spam-Status: No, score=-7.088 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 PG_LH6o9so_Y for <dmarc@ietfa.amsl.com>; Fri, 26 Feb 2021 18:15:10 -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 0C7C63A08AA for <dmarc@ietf.org>; Fri, 26 Feb 2021 18:15:09 -0800 (PST)
Received: by mail-vs1-xe2c.google.com with SMTP id g4so5722391vsb.11 for <dmarc@ietf.org>; Fri, 26 Feb 2021 18:15:09 -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=UIdkFOTicfJody2VUoXi306pr0L5PYuG7nKiXrYS03E=; b=eD3xYYUuuzyIoLCn/rdAXT+S/IkBBgrxNLOEDJ5o6dly9sGZVYz6wMt3E8VWuNlsXS h8TRogXpf/9iTRZyYfpj5oE0O5KyjFc90exp5NkYzIZqNs964jKNI3KxlhQbUp83EsPl xhnSF4+U3aVTxeXTEpb49En2nmAWLW8K7w/fBYaSTUF3VN/NwFa6s5osBobGevxaUiq1 nTkeKUwOQAEglfZa7Q6IkC2uzLbM8XYMQ9kc/raNkN8UCtkr2QbXxJoZsKox5SFtHSMo xQ7sHNrTVjPs9FQsLHRm9dnm96FGrb/t/HTtQZz+t5vx8HPe2R4cfrbM9YJO4foRzTbz seRA==
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=UIdkFOTicfJody2VUoXi306pr0L5PYuG7nKiXrYS03E=; b=Spl7YMAVnZurhNdRyHX/rkAJAVeB9ZsK7q7Ydd2JQBiFRqLI9e4UwgobtaFti0dDrB iXNZ6osflWdH4ydOyOyofM9WQ4JWH6aka92Yn16VwKhd2Q3cakaEbhS0jHilWi9RYTsv v98DQangz7s7j97bgWWudYGtKGrf766uSaCfylrWzWjvNokrhipq48Wv2IOJysfLAJwI 1nlyVwt5EsFdZJ4c4hXx9qYiOoXeMcYJ0jolXulviv6O37OyaOHHLAfXTAuoan4SHOlb 3z0TX8aDbh+fDh2N9OWHqDrGOK41udyQDb3QdC/EhIKtxdkwB8+XOySCfp1IlVEEhzUT iO2A==
X-Gm-Message-State: AOAM532jwND79GSTckPKVfZ0JyzJ4JC9S/Lzp4UYTd1QKf8Hw3jTxs/0 KdRrxg1T9irwXR+CpYs3LhqyK3enKh95XroC8LaG0bpnMXA=
X-Google-Smtp-Source: ABdhPJz35syw/KCewHrUMBFySdQMb0HeJqSLGRJfJqL7/yyYwUkwnGnjdVVS9MkcoJ9iY3mZ1LfZ8S7Af3zgUKFfpVo=
X-Received: by 2002:a67:c182:: with SMTP id h2mr3707678vsj.56.1614392108597; Fri, 26 Feb 2021 18:15:08 -0800 (PST)
MIME-Version: 1.0
References: <CAOZAAfPbzfJvn5XQ=4d_jHcv8cSLR-R3pxCREKzT4U3pUzzNCg@mail.gmail.com>
In-Reply-To: <CAOZAAfPbzfJvn5XQ=4d_jHcv8cSLR-R3pxCREKzT4U3pUzzNCg@mail.gmail.com>
From: Seth Blank <seth@valimail.com>
Date: Fri, 26 Feb 2021 18:14:57 -0800
Message-ID: <CAOZAAfPNJBvm3AMp25cVfDeQ9-YXHvx1kBYkmeq6wLB2e2nrWQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Cc: dmarc-chairs@ietf.org, ART ADs <art-ads@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002955c605bc47f4b4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/P8QSasJ9bnVqrbBBqswpUdR5-vc>
Subject: Re: [dmarc-ietf] Announcement - DMARC bis Design Team
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 27 Feb 2021 02:15:12 -0000

--0000000000002955c605bc47f4b4
Content-Type: text/plain; charset="UTF-8"

On Mon, Feb 22, 2021 at 9:58 AM Seth Blank <seth@valimail.com> wrote:

>
>    1.
>
>    A moratorium is hereby imposed on creating tickets for this working
>    group, effective at 5pm PT, Friday, February 26th.
>    2.
>
>    The design team will have until 5pm PT, Friday, April 23rd, to work
>    through all applicable tickets, and come to agreement on each to either
>    modify DMARC bis documents (and make such modification) or reject the
>    ticket, with the reason for rejection added to the ticket's comments. No
>    tickets will be closed during this process, everything will be transparent
>    for working group review after the design period.
>
>
Tickets are now officially frozen through April 23rd, while the design team
gets to work.

Seth, for the Chairs

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

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Feb 22, 2021 at 9:58 AM Seth Blan=
k &lt;<a href=3D"mailto:seth@valimail.com">seth@valimail.com</a>&gt; wrote:=
</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"ltr"><div><div><span id=3D"gmail-m_4054310547320081322g=
mail-docs-internal-guid-a6c9442d-7fff-4a08-1ee6-09197df4af94"><ol style=3D"=
margin-top:0px;margin-bottom:0px"><font face=3D"arial, sans-serif"><li dir=
=3D"ltr" style=3D"list-style-type:decimal;background-color:transparent;font=
-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:basel=
ine;white-space:pre-wrap;margin-left:11pt"><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:10pt;margin-bottom:0pt"><span style=3D"background-color=
:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;ver=
tical-align:baseline;white-space:pre-wrap">A moratorium is hereby imposed o=
n creating tickets for this working group, effective at 5pm PT, Friday, Feb=
ruary 26th.</span></p></li><li dir=3D"ltr" style=3D"list-style-type:decimal=
;background-color:transparent;font-variant-numeric:normal;font-variant-east=
-asian:normal;vertical-align:baseline;white-space:pre-wrap;margin-left:11pt=
"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt=
"><span style=3D"background-color:transparent;font-variant-numeric:normal;f=
ont-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"=
>The design team will have until 5pm PT, Friday, April 23rd, to work throug=
h all applicable tickets, and come to agreement on each to either modify DM=
ARC bis documents (and make such modification) or reject the ticket, with t=
he reason for rejection added to the ticket&#39;s comments. No tickets will=
 be closed during this process, everything will be transparent for working =
group review after the design period.</span></p></li></font></ol></span></d=
iv></div></div></blockquote><div><br></div><div>Tickets are now officially =
frozen through April 23rd, while the design team gets to work.</div></div><=
div><br></div><div>Seth, for the Chairs</div></div>

--0000000000002955c605bc47f4b4--


From nobody Sun Feb 28 03:00:12 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 4BC663A132F for <dmarc@ietfa.amsl.com>; Sun, 28 Feb 2021 03:00:11 -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 DZE1_qtMU-e1 for <dmarc@ietfa.amsl.com>; Sun, 28 Feb 2021 03:00:09 -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 90CED3A132E for <dmarc@ietf.org>; Sun, 28 Feb 2021 03:00:09 -0800 (PST)
Received: (qmail 17818 invoked by uid 100); 28 Feb 2021 11:00:07 -0000
Date: 28 Feb 2021 10:59:43 -0000
Message-ID: <20210228105943.17799.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/BoVr8D8wozzmocExkkVLgX4cXz0>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Feb 28 06:00:07 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, 28 Feb 2021 11:00:11 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
  4 (17.4%) |  32829 (12.2%) | Dave Crocker <dcrocker@gmail.com>
  2 ( 8.7%) |  46876 (17.5%) | Ken O'Driscoll <ken@wemonitoremail.com>
  2 ( 8.7%) |  44435 (16.6%) | Tim Wicinski <tjw.ietf@gmail.com>
  2 ( 8.7%) |  27810 (10.4%) | Seth Blank <seth@valimail.com>
  2 ( 8.7%) |  20391 ( 7.6%) | Barry Leiba <barryleiba@computer.org>
  2 ( 8.7%) |  18703 ( 7.0%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  1 ( 4.3%) |  21861 ( 8.1%) | Dotzero <dotzero@gmail.com>
  1 ( 4.3%) |  14267 ( 5.3%) | Murray S. Kucherawy <superuser@gmail.com>
  1 ( 4.3%) |  10053 ( 3.7%) | Chudow, Eric B CIV NSA DSAW (USA) <eric.b.chudow.civ@mail.mil>
  1 ( 4.3%) |   8185 ( 3.0%) | Kurt Andersen (b) <kboth@drkurt.com>
  1 ( 4.3%) |   6568 ( 2.4%) |  <ned+dmarc@mrochek.com>
  1 ( 4.3%) |   5211 ( 1.9%) | Steven M Jones <smj@crash.com>
  1 ( 4.3%) |   5083 ( 1.9%) | Alessandro Vesely <vesely@tana.it>
  1 ( 4.3%) |   3163 ( 1.2%) | John Levine <johnl@taugh.com>
  1 ( 4.3%) |   3004 ( 1.1%) |  <internet-drafts@ietf.org>


From nobody Sun Feb 28 13:35: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 8E6933A1CCE for <dmarc@ietfa.amsl.com>; Sun, 28 Feb 2021 13:35:11 -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, 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 sEc-A4ayjQkL for <dmarc@ietfa.amsl.com>; Sun, 28 Feb 2021 13:35:10 -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 BA2253A1CCD for <dmarc@ietf.org>; Sun, 28 Feb 2021 13:35:09 -0800 (PST)
Received: by mail-vk1-xa33.google.com with SMTP id j188so3153296vke.13 for <dmarc@ietf.org>; Sun, 28 Feb 2021 13:35: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=dFOcyxUwObVALOhYaC3ykHKEWgEJcb5HEtk3ZUR3H8c=; b=NfdD/OSoG1nnW1w2L7WJLXGSZUpQRzpr3IdZIM8swYjb7nX9IKpaKJDmHETthIMqWn rv8oL2+1FIGrpN1ZlsZhzP1yAk9kZVt0+ajIb3+Pbvw3GbgA2tHZC3VPZFgQc3xsvhDg Db3+lr7PMf9pN9zMeWglKXG2Rc5k8LsiwAzxjYS1G3hUFqRoOFZl9HTy1O1ykaOBYdyw vmYkyazNPTZM9SKdw6hce62GmBEv9IPO0j1nXKg1YHKPtGI2DLJoP4eWKtNa3Omh7AxM /5etGMFAagwSlN6H6hQXCEVm4T+bJdmgQVZHN8RBVv1XIgpT5f98cNfPJk8LR8S88VKn flWQ==
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=dFOcyxUwObVALOhYaC3ykHKEWgEJcb5HEtk3ZUR3H8c=; b=Ofx+vSnvs9G2wd1z5v1jlBdTo2FY0nT6L1JZ0l0CsyCUKQGQXHdj/E8zDOkvQddOVp RAYERVuO6pjUUpPKaip+JZd2ZGFTTinJGEdQxD7pktdgf/JNZJfiIR6BwebMVfRJCX12 NBvZTO4l9PxVNwRC+gmO/9bgvYpSldrlt27yNnRJfu0DQsDrqW+2xSEkXYkGgSixL4qh aqyMvqmGrcZM2JkmWsjxYAyrUmF7JQ3bRVhyI5ECyLV02eitmtXPmnX4O8JHTaK1TMOy k+GCDOXbNg5Gt1BrobmH7/8D3W/+PHFH9kh2zR05+6DswTjrWLmC4Q3DKqqW6WjPiGni 9+vg==
X-Gm-Message-State: AOAM533F6OvZaMrgfX8xGu2+qpXCarXPiu3QYTIesoLoDicx4xECLhFb 2MNxS7G1vQBeXKQaCBrubb//rlff/v3hJMG75UA=
X-Google-Smtp-Source: ABdhPJzfTXIKdVSCTWAaysWRRiPD9WDgoaTL8f/qkQYfY8GdkoUC/lvwXVTKmff5pCu13wJ3ych6HhpqzRzrMJte7Vk=
X-Received: by 2002:a1f:a9c9:: with SMTP id s192mr6795346vke.22.1614548106556;  Sun, 28 Feb 2021 13:35:06 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <CAC4RtVARxfJNUs+ve1ViDTF385QjLoyhw8JyKc-nALhuu=xoPA@mail.gmail.com> <81c05041-a4ad-a473-701c-0027cd503696@gmail.com> <CABuGu1pncrHQ-Ba7t7VEcbYrjfoc_Ek_3B5X66owSE2GWRdPSg@mail.gmail.com> <8c715354-54ed-434a-c630-bb3c902cb8da@gmail.com>
In-Reply-To: <8c715354-54ed-434a-c630-bb3c902cb8da@gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sun, 28 Feb 2021 13:34:50 -0800
Message-ID: <CAL0qLwaZh_HHCVfVkHki497uaSSN-GCy2U=aueg7iR+jBGA0xg@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: "Kurt Andersen (b)" <kboth@drkurt.com>, IETF DMARC WG <dmarc@ietf.org>,  Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary="0000000000005d392705bc6c46ac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/3NL1DjKNgLH77SZNa8Y7JwBrCQA>
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: Sun, 28 Feb 2021 21:35:12 -0000

--0000000000005d392705bc6c46ac
Content-Type: text/plain; charset="UTF-8"

These all work for me.  Thanks for the contributions.

Scott, please work your magic with a revision so the chairs can request
publication and we can get this on its way.

-MSK

On Thu, Feb 25, 2021 at 9:13 AM Dave Crocker <dcrocker@gmail.com> wrote:

> On 2/25/2021 8:41 AM, Kurt Andersen (b) wrote:
>
> Especially in the case of the PSD policies, one should not expect that the
> controlling organization would necessarily be "a mail-originating
> organization". Generally the idea is to *disavow* being such :-)
>
> Suggested alternate text:
>
> Domain-based Message Authentication, Reporting, and Conformance (DMARC)
> permits a domain-controlling
> organization to express domain-level policies and preferences for message
> validation, disposition, and reporting,
> which a mail-receiving organization can use to improve mail handling.
>
> +1
>
> d/
>
> --
> Dave Crockerdcrocker@gmail.com
> 408.329.0791
>
> Volunteer, Silicon Valley Chapter
> American Red Crossdave.crocker2@redcross.org
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr"><div>These all work for me.=C2=A0 Thanks for the contribut=
ions.<br><br></div><div>Scott, please work your magic with a revision so th=
e chairs can request publication and we can get this on its way.</div><div>=
<br></div><div>-MSK<br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, Feb 25, 2021 at 9:13 AM Dave Crocker =
&lt;<a href=3D"mailto:dcrocker@gmail.com">dcrocker@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">
 =20
   =20
 =20
  <div>
    <div>On 2/25/2021 8:41 AM, Kurt Andersen (b)
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div class=3D"gmail_quote">
        <div>Especially in the case of the PSD policies, one should not
          expect that the controlling organization would necessarily be
          &quot;a mail-originating organization&quot;. Generally the idea i=
s to
          *disavow* being such :-)</div>
        <div><br>
        </div>
        <div>Suggested alternate text:</div>
        <div><br>
        </div>
        <div>Domain-based Message Authentication, Reporting, and
          Conformance (DMARC) permits a domain-controlling</div>
        organization to express domain-level policies and preferences
        for message validation, disposition, and reporting,=C2=A0</div>
      <div class=3D"gmail_quote">which a mail-receiving organization can
        use to improve mail handling.</div>
    </blockquote>
    <p>+1</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>

_______________________________________________<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>

--0000000000005d392705bc6c46ac--


From nobody Sun Feb 28 13:53: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 3E09D3A1D09 for <dmarc@ietfa.amsl.com>; Sun, 28 Feb 2021 13:53:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.196
X-Spam-Level: 
X-Spam-Status: No, score=-0.196 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, 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 HwT0JjPG80OF for <dmarc@ietfa.amsl.com>; Sun, 28 Feb 2021 13:53:12 -0800 (PST)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (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 5757A3A1D08 for <dmarc@ietf.org>; Sun, 28 Feb 2021 13:53:12 -0800 (PST)
Received: by mail-oi1-x22f.google.com with SMTP id l133so16134100oib.4 for <dmarc@ietf.org>; Sun, 28 Feb 2021 13:53: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=FjSYbYXT4jNdbQzthlSew90t+z+sa/jYe3Lwo1rxhJg=; b=iYf+uWKfltrqRRbeaOOraOFllrtVAVN8sUHtpzT+SMPNRt5LRP6sNWuS4nffrd11ow MzrlUTBPvvZNustPLuV3t9YDUbC9OMaQSpqQBdeBMbtfiyxJRJusqAofqVCtKRfvIP4u nTPK7YOU+4c/2RqZs9VxhLNlN6eE9wenmLIw/bkLIT/FgH3lyhX5CNSw5F333YsL+/8w GAfYXXmyD7C41M3F02RJWs/Yfa/hwrcusDqw781dXSePQ9JuRIW/Y+NfgTq1Pep2fhqz wp+mIzrxrE8hkg49N4ytX63Q8yFhV3Owu6gifj6JZ0tzfYiP5GHttN3ydNyrpRkDoTjN 4eaA==
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=FjSYbYXT4jNdbQzthlSew90t+z+sa/jYe3Lwo1rxhJg=; b=AibzRtRafxfN8sCAA2ZedcmPCT4RID7rsPWRv0tQKxrl78Z9bWkhagN2q4xI1Cmgt1 tXd9uegDwy9z7b2gB9zjU3KGC0IgsBMz2RR47u9u/UXbfY0uQ0WH1W7w25G1uPrNR8gj ri4XApTUtjJtoSuKGiLRFfpbJuUufYHVaTbiM9FYVQECxMN0sSkQYK/tXtcigIHBmiEY 3GUFMzu/DLnotZlJ4grOyXHmlQsa0R5XH4iqwHVrELK6FzM1xvrdbSpzX0BP0Ioem64f jCcDyr5v4x26ThYklsKj97M+tPFB+lIaUyRxTquAgZghWaQiUEbGEcJfBmnYo/K7DfUw H0aQ==
X-Gm-Message-State: AOAM531MyxLszGLEArtk8gaEDfN5kxkMyVlc+NJzep5winUQ5DXly9FU 2p8h/Tf3VjT2sbzsX0ayofix3WXJQxNlQjhxOSE=
X-Google-Smtp-Source: ABdhPJwOJTxTpQp33UQLdUYV5H3O+F30CiLCYWtieO9g1ZhgOafSmCYDto9+yhI7X8ufXyJyCnvxY9w6LMzyUgNbqZA=
X-Received: by 2002:aca:4cd1:: with SMTP id z200mr9417211oia.21.1614549189880;  Sun, 28 Feb 2021 13:53:09 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <CAC4RtVARxfJNUs+ve1ViDTF385QjLoyhw8JyKc-nALhuu=xoPA@mail.gmail.com> <81c05041-a4ad-a473-701c-0027cd503696@gmail.com> <CABuGu1pncrHQ-Ba7t7VEcbYrjfoc_Ek_3B5X66owSE2GWRdPSg@mail.gmail.com> <8c715354-54ed-434a-c630-bb3c902cb8da@gmail.com> <CAL0qLwaZh_HHCVfVkHki497uaSSN-GCy2U=aueg7iR+jBGA0xg@mail.gmail.com>
In-Reply-To: <CAL0qLwaZh_HHCVfVkHki497uaSSN-GCy2U=aueg7iR+jBGA0xg@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Sun, 28 Feb 2021 16:52:58 -0500
Message-ID: <CADyWQ+EtHS_Ke6b+fyuLrE2c1DL3a4XKCnf3745o=GvHfB1TxQ@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>,  "Kurt Andersen (b)" <kboth@drkurt.com>, Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/mixed; boundary="000000000000efe44c05bc6c8671"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/09zTLVa-9VrXNPXwkZmguUyDjK0>
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: Sun, 28 Feb 2021 21:53:14 -0000

--000000000000efe44c05bc6c8671
Content-Type: multipart/alternative; boundary="000000000000efe44905bc6c866f"

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

I was just working on merging Barry's comments with Dave's and Kurt's.

I attached what should be correct.  I would like someone to just double
check my work.

tim


On Sun, Feb 28, 2021 at 4:35 PM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> These all work for me.  Thanks for the contributions.
>
> Scott, please work your magic with a revision so the chairs can request
> publication and we can get this on its way.
>
> -MSK
>
> On Thu, Feb 25, 2021 at 9:13 AM Dave Crocker <dcrocker@gmail.com> wrote:
>
>> On 2/25/2021 8:41 AM, Kurt Andersen (b) wrote:
>>
>> Especially in the case of the PSD policies, one should not expect that
>> the controlling organization would necessarily be "a mail-originating
>> organization". Generally the idea is to *disavow* being such :-)
>>
>> Suggested alternate text:
>>
>> Domain-based Message Authentication, Reporting, and Conformance (DMARC)
>> permits a domain-controlling
>> organization to express domain-level policies and preferences for message
>> validation, disposition, and reporting,
>> which a mail-receiving organization can use to improve mail handling.
>>
>> +1
>>
>> d/
>>
>> --
>> Dave Crockerdcrocker@gmail.com
>> 408.329.0791
>>
>> Volunteer, Silicon Valley Chapter
>> American Red Crossdave.crocker2@redcross.org
>>
>> _______________________________________________
>> 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
>

--000000000000efe44905bc6c866f
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">I was just working on merging Barry&#39;s comments with Dave&#39;s and K=
urt&#39;s.=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:mon=
ospace"><br></div><div class=3D"gmail_default" style=3D"font-family:monospa=
ce">I attached what should be correct.=C2=A0 I would like someone to just d=
ouble check my work.</div><div class=3D"gmail_default" style=3D"font-family=
:monospace"><br></div><div class=3D"gmail_default" style=3D"font-family:mon=
ospace">tim</div><div class=3D"gmail_default" style=3D"font-family:monospac=
e"><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D=
"gmail_attr">On Sun, Feb 28, 2021 at 4:35 PM Murray S. Kucherawy &lt;<a hre=
f=3D"mailto:superuser@gmail.com">superuser@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"ltr"><div>T=
hese all work for me.=C2=A0 Thanks for the contributions.<br><br></div><div=
>Scott, please work your magic with a revision so the chairs can request pu=
blication and we can get this on its way.</div><div><br></div><div>-MSK<br>=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Thu, Feb 25, 2021 at 9:13 AM Dave Crocker &lt;<a href=3D"mailto:dc=
rocker@gmail.com" target=3D"_blank">dcrocker@gmail.com</a>&gt; 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
   =20
 =20
  <div>
    <div>On 2/25/2021 8:41 AM, Kurt Andersen (b)
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div class=3D"gmail_quote">
        <div>Especially in the case of the PSD policies, one should not
          expect that the controlling organization would necessarily be
          &quot;a mail-originating organization&quot;. Generally the idea i=
s to
          *disavow* being such :-)</div>
        <div><br>
        </div>
        <div>Suggested alternate text:</div>
        <div><br>
        </div>
        <div>Domain-based Message Authentication, Reporting, and
          Conformance (DMARC) permits a domain-controlling</div>
        organization to express domain-level policies and preferences
        for message validation, disposition, and reporting,=C2=A0</div>
      <div class=3D"gmail_quote">which a mail-receiving organization can
        use to improve mail handling.</div>
    </blockquote>
    <p>+1</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>

_______________________________________________<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>
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>

--000000000000efe44905bc6c866f--

--000000000000efe44c05bc6c8671
Content-Type: text/plain; charset="UTF-8"; name="psd-edits.txt"
Content-Disposition: attachment; filename="psd-edits.txt"
Content-Transfer-Encoding: base64
Content-ID: <f_klposrqd0>
X-Attachment-Id: f_klposrqd0

4oCUIEFic3RyYWN0IOKAlAoKT0xECiAgIERNQVJDIChEb21haW4tYmFzZWQgTWVzc2FnZSBBdXRo
ZW50aWNhdGlvbiwgUmVwb3J0aW5nLCBhbmQKICAgQ29uZm9ybWFuY2UpIGlzIGEgc2NhbGFibGUg
bWVjaGFuaXNtIGJ5IHdoaWNoIGEgbWFpbC1vcmlnaW5hdGluZwogICBvcmdhbml6YXRpb24gY2Fu
IGV4cHJlc3MgZG9tYWluLWxldmVsIHBvbGljaWVzIGFuZCBwcmVmZXJlbmNlcyBmb3IKICAgbWVz
c2FnZSB2YWxpZGF0aW9uLCBkaXNwb3NpdGlvbiwgYW5kIHJlcG9ydGluZywgdGhhdCBhIG1haWwt
cmVjZWl2aW5nCiAgIG9yZ2FuaXphdGlvbiBjYW4gdXNlIHRvIGltcHJvdmUgbWFpbCBoYW5kbGlu
Zy4gIFRoZSBkZXNpZ24gb2YgRE1BUkMKICAgcHJlc3VtZXMgdGhhdCBkb21haW4gbmFtZXMgcmVw
cmVzZW50IGVpdGhlciBub2RlcyBpbiB0aGUgdHJlZSBiZWxvdwogICB3aGljaCByZWdpc3RyYXRp
b25zIG9jY3VyLCBvciBub2RlcyB3aGVyZSByZWdpc3RyYXRpb25zIGhhdmUKICAgb2NjdXJyZWQ7
IGl0IGRvZXMgbm90IHBlcm1pdCBhIGRvbWFpbiBuYW1lIHRvIGhhdmUgYm90aCBvZiB0aGVzZQog
ICBwcm9wZXJ0aWVzIHNpbXVsdGFuZW91c2x5LiAgU2luY2UgaXRzIGRlcGxveW1lbnQgaW4gMjAx
NSwgdXNlIG9mCiAgIERNQVJDIGhhcyBzaG93biBhIGNsZWFyIG5lZWQgZm9yIHRoZSBhYmlsaXR5
IHRvIGV4cHJlc3MgcG9saWN5IGZvcgogICB0aGVzZSBkb21haW5zIGFzIHdlbGwuCgogICBEb21h
aW5zIGF0IHdoaWNoIHJlZ2lzdHJhdGlvbnMgY2FuIG9jY3VyIGFyZSByZWZlcnJlZCB0byBhcyBQ
dWJsaWMKICAgU3VmZml4IERvbWFpbnMgKFBTRHMpLiAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMg
YW4gZXh0ZW5zaW9uIHRvIERNQVJDCiAgIHRvIGVuYWJsZSBETUFSQyBmdW5jdGlvbmFsaXR5IGZv
ciBQU0RzLgoKICAgVGhpcyBkb2N1bWVudCBhbHNvIHNlZWtzIHRvIGFkZHJlc3MgaW1wbGVtZW50
YXRpb25zIHRoYXQgY29uc2lkZXIgYQogICBkb21haW4gb24gYSBwdWJsaWMgU3VmZml4IGxpc3Qg
dG8gYmUgaW5lbGlnaWJsZSBmb3IgRE1BUkMKICAgZW5mb3JjZW1lbnQuCgpORVcKICAgRG9tYWlu
LWJhc2VkIE1lc3NhZ2UgQXV0aGVudGljYXRpb24sIFJlcG9ydGluZywgYW5kIENvbmZvcm1hbmNl
CiAgIChETUFSQykgcGVybWl0cyBhIGRvbWFpbi1jb250cm9sbGluZyBvcmdhbml6YXRpb24gdG8g
ZXhwcmVzcwogICBkb21haW4tbGV2ZWwgcG9saWNpZXMgYW5kIHByZWZlcmVuY2VzIGZvciBtZXNz
YWdlIHZhbGlkYXRpb24sCiAgIGRpc3Bvc2l0aW9uLCBhbmQgcmVwb3J0aW5nLCB3aGljaCBhIG1h
aWwtcmVjZWl2aW5nIG9yZ2FuaXphdGlvbgogICBjYW4gdXNlIHRvIGltcHJvdmUgbWFpbCBoYW5k
bGluZy4KCiAgICBETUFSQyBkaXN0aW5ndWlzaGVzIHRoZSBwb3J0aW9uIG9mIGEgbmFtZSB0aGF0
IGlzIGEKICAgIFB1YmxpYyBTdWZmaXggRG9tYWluIChQU0QpLCBiZWxvdyB3aGljaAogICAgb3Jn
YW5pemF0aW9uYWwgZG9tYWluIG5hbWVzIGFyZSBjcmVhdGVkLiAgVGhlIGJhc2ljIERNQVJDCiAg
ICBjYXBhYmlsaXR5IGFsbG93cyBvcmdhbml6YXRpb25hbCBkb21haW5zIHRvIHNwZWNpZnkgcG9s
aWNpZXMKICAgIHRoYXQgYXBwbHkgdG8gdGhlaXIgc3ViZG9tYWlucywgYnV0IGl0IGRvZXMgbm90
IGdpdmUgdGhhdAogICAgY2FwYWJpbGl0eSB0byBQU0RzLiBUaGlzIGRvY3VtZW50IGRlc2NyaWJl
cyBhbiBleHRlbnNpb24gdG8KICAgIERNQVJDIHRvIGZ1bGx5IGVuYWJsZSBETUFSQyBmdW5jdGlv
bmFsaXR5IGZvciBQU0RzLgoKICAgIFNvbWUgaW1wbGVtZW50YXRpb25zIG9mIERNQVJDIGNvbnNp
ZGVyIGEgUFNEIHRvIGJlIGluZWxpZ2libGUgZm9yCiAgICBETUFSQyBlbmZvcmNlbWVudC4gIFRo
aXMgc3BlY2lmaWNhdGlvbiBhZGRyZXNzZXMgdGhhdCBjYXNlLgoKCuKAlCBTZWN0aW9uIDEg4oCU
CgpPTEQKICAgRE1BUkMgYXMgc3BlY2lmaWVkIHByZXN1bWVzIHRoYXQgZG9tYWluIG5hbWVzIHBy
ZXNlbnQgaW4gYSBQU0wgYXJlCiAgIG5vdCBvcmdhbml6YXRpb25hbCBkb21haW5zIGFuZCB0aHVz
IG5vdCBzdWJqZWN0IHRvIERNQVJDIHByb2Nlc3Npbmc7CiAgIGRvbWFpbnMgYXJlIGVpdGhlciBv
cmdhbml6YXRpb25hbCBkb21haW5zLCBzdWItZG9tYWlucyBvZgogICBvcmdhbml6YXRpb25hbCBk
b21haW5zLCBvciBsaXN0ZWQgb24gYSBQU0wuICBGb3IgZG9tYWlucyBsaXN0ZWQgaW4gYQogICBQ
U0wsIGkuZS4sIFRMRHMgYW5kIGRvbWFpbnMgdGhhdCBleGlzdCBiZXR3ZWVuIFRMRHMgYW5kIG9y
Z2FuaXphdGlvbgogICBsZXZlbCBkb21haW5zLCBwb2xpY3kgY2FuIG9ubHkgYmUgcHVibGlzaGVk
IGZvciB0aGUgZXhhY3QgZG9tYWluLiAgTm8KICAgbWV0aG9kIGlzIGF2YWlsYWJsZSBmb3IgdGhl
c2UgZG9tYWlucyB0byBleHByZXNzIHBvbGljeSBvciByZWNlaXZlCiAgIGZlZWRiYWNrIHJlcG9y
dGluZyBmb3Igc3ViLWRvbWFpbnMuICBUaGlzIG1pc3NpbmcgbWV0aG9kIGFsbG93cyBmb3IKICAg
dGhlIGFidXNlIG9mIG5vbi1leGlzdGVudCBvcmdhbml6YXRpb25hbC1sZXZlbCBkb21haW5zIGFu
ZCBwcmV2ZW50cwogICBpZGVudGlmaWNhdGlvbiBvZiBkb21haW4gYWJ1c2UgaW4gZW1haWwuCgpO
RVcKICBJbiB0aGUgYmFzaWMgRE1BUkMgbW9kZWwsIFBTRHMgYXJlIG5vdCBvcmdhbml6YXRpb25h
bCBkb21haW5zCiAgYW5kIGFyZSB0aHVzIG5vdCBzdWJqZWN0IHRvIERNQVJDIHByb2Nlc3Npbmcu
ICBJbiBETUFSQywgZG9tYWlucwogIGZhbGwgaW50byBvbmUgb2YgdGhyZWUgY2F0ZWdvcmllczog
b3JnYW5pemF0aW9uYWwgZG9tYWlucywKICBzdWItZG9tYWlucyBvZiBvcmdhbml6YXRpb25hbCBk
b21haW5zLCBvciBQU0RzLiAgQSBQU0QgY2FuIG9ubHkKICBwdWJsaXNoIERNQVJDIHBvbGljeSBm
b3IgaXRzZWxmLCBhbmQgbm90IGZvciBhbnkgc3ViLWRvbWFpbnMKICB1bmRlciBpdC4gIEluIHNv
bWUgY2FzZXMsIHRoaXMgbGltaXRhdGlvbiBhbGxvd3MgZm9yIHRoZSBhYnVzZQogIG9mIG5vbi1l
eGlzdGVudCBvcmdhbml6YXRpb25hbC1sZXZlbCBkb21haW5zIGFuZCBoYW1wZXJzCiAgaWRlbnRp
ZmljYXRpb24gb2YgZG9tYWluIGFidXNlIGluIGVtYWlsLgoK4oCUIFNlY3Rpb24gMS4xIOKAlAoK
T0xECiAgIEFzIGFuIGV4YW1wbGUsIGltYWdpbmUgYSBjb3VudHJ5IGNvZGUgVExEIChjY1RMRCkg
d2hpY2ggaGFzIHB1YmxpYwogICBzdWJkb21haW5zIGZvciBnb3Zlcm5tZW50IGFuZCBjb21tZXJj
aWFsIHVzZSAoIi5nb3YuZXhhbXBsZSIgYW5kCiAgICIuY29tLmV4YW1wbGUiKS4gIEEgUFNMIHdo
b3NlIG1haW50YWluZXIgaXMgYXdhcmUgb2YgdGhpcyBjb3VudHJ5J3MKICAgZG9tYWluIHN0cnVj
dHVyZXdvdWxkIGluY2x1ZGUgZW50cmllcyBmb3IgYm90aCBvZiB0aGVzZSBpbiB0aGUgUFNMLAog
ICBpbmRpY2F0aW5nIHRoYXQgdGhleSBhcmUgUFNEcyBiZWxvdyB3aGljaCByZWdpc3RyYXRpb25z
IGNhbiBvY2N1ci4KICAgU3VwcG9zZSBmdXJ0aGVyIHRoYXQgdGhlcmUgZXhpc3RzIGEgZG9tYWlu
ICJ0YXguZ292LmV4YW1wbGUiLAogICByZWdpc3RlcmVkIHdpdGhpbiAiLmdvdi5leGFtcGxlIiwg
dGhhdCBpcyByZXNwb25zaWJsZSBmb3IgdGF4YXRpb24gaW4KICAgdGhpcyBpbWFnaW5lZCBjb3Vu
dHJ5LgoKTkVXCiAgICBBcyBhbiBleGFtcGxlLCBpbWFnaW5lIGEgVG9wLUxldmVsIERvbWFpbiAo
VExEKSwgIi5leGFtcGxlIiwgdGhhdCBoYXMKICAgIHB1YmxpYyBzdWJkb21haW5zIGZvciBnb3Zl
cm5tZW50IGFuZCBjb21tZXJjaWFsIHVzZSAoIi5nb3YuZXhhbXBsZSIKICAgIGFuZCAiLmNvbS5l
eGFtcGxlIikuICBUaGUgbWFpbnRhaW5lciBvZiBhIGxpc3Qgb2Ygc3VjaCBhIFBTRCBzdHJ1Y3R1
cmUKICAgIHdvdWxkIGluY2x1ZGUgZW50cmllcyBmb3IgYm90aCBvZiB0aGVzZSBzdWItZG9tYWlu
cywgdGhlcmVieQogICAgaW5kaWNhdGluZyB0aGF0IHRoZXkgYXJlIFBTRHMsIGJlbG93IHdoaWNo
IG9yZ2FuaXphdGlvbmFsIGRvbWFpbnMgY2FuCiAgICBiZSByZWdpc3RlcmVkLiAgU3VwcG9zZSBm
dXJ0aGVyIHRoYXQgdGhlcmUgZXhpc3RzIGEgbGVnaXRpbWF0ZSBkb21haW4KICAgIGNhbGxlZCAi
dGF4Lmdvdi5leGFtcGxlIiwgcmVnaXN0ZXJlZCB3aXRoaW4gIi5nb3YuZXhhbXBsZSIuCgoKCk9M
RAogICBUaGlzIERNQVJDIHJlY29yZCBwcm92aWRlcyBwb2xpY3kgYW5kIGEgcmVwb3J0aW5nIGRl
c3RpbmF0aW9uIGZvcgogICBtYWlsIHNlbnQgZnJvbSBAZ292LmV4YW1wbGUuICBIb3dldmVyLCBk
dWUgdG8gRE1BUkMncyBjdXJyZW50IG1ldGhvZAogICBvZiBkaXNjb3ZlcmluZyBhbmQgYXBwbHlp
bmcgcG9saWN5IGF0IHRoZSBvcmdhbml6YXRpb25hbCBkb21haW4KICAgbGV2ZWwsIHRoZSBub24t
ZXhpc3RlbnQgb3JnYW5pemF0aW9uYWwgZG9tYWluIG9mIEB0NHguZ292LmV4YW1wbGUKICAgZG9l
cyBub3QgYW5kIGNhbm5vdCBmYWxsIHVuZGVyIGEgRE1BUkMgcG9saWN5LgoKTkVXCiAgIFRoaXMg
RE1BUkMgcmVjb3JkIHByb3ZpZGVzIHBvbGljeSBhbmQgYSByZXBvcnRpbmcgZGVzdGluYXRpb24g
Zm9yCiAgIG1haWwgc2VudCBmcm9tIEBnb3YuZXhhbXBsZS4gIFNpbWlsYXJseSwgInRheC5nb3Yu
ZXhhbXBsZSIgd2lsbCBoYXZlCiAgIGEgRE1BUkMgcmVjb3JkIHRoYXQgc3BlY2lmaWVzIHBvbGlj
eSBmb3IgbWFpbCBzZW50IGZyb20gYWRkcmVzc2VzCiAgIEB0YXguZ292LmV4YW1wbGUuICBIb3dl
dmVyLCBkdWUgdG8gRE1BUkMncyBjdXJyZW50IG1ldGhvZCBvZgogICBkaXNjb3ZlcmluZyBhbmQg
YXBwbHlpbmcgcG9saWN5IGF0IHRoZSBvcmdhbml6YXRpb25hbCBkb21haW4KICAgbGV2ZWwsIHRo
ZSBub24tZXhpc3RlbnQgb3JnYW5pemF0aW9uYWwgZG9tYWluIG9mIEB0NHguZ292LmV4YW1wbGUK
ICAgZG9lcyBub3QgYW5kIGNhbm5vdCBmYWxsIHVuZGVyIGEgRE1BUkMgcG9saWN5Lgo=
--000000000000efe44c05bc6c8671--


From nobody Sun Feb 28 14:02:14 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 8B66A3A040F for <dmarc@ietfa.amsl.com>; Sun, 28 Feb 2021 14:02:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.501
X-Spam-Level: 
X-Spam-Status: No, score=0.501 tagged_above=-999 required=5 tests=[FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 BdyhwbIfcn8J for <dmarc@ietfa.amsl.com>; Sun, 28 Feb 2021 14:02:11 -0800 (PST)
Received: from mail-lf1-f53.google.com (mail-lf1-f53.google.com [209.85.167.53]) (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 A9CB53A03FA for <dmarc@ietf.org>; Sun, 28 Feb 2021 14:02:10 -0800 (PST)
Received: by mail-lf1-f53.google.com with SMTP id e7so22363300lft.2 for <dmarc@ietf.org>; Sun, 28 Feb 2021 14:02:10 -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=Zfj69WENN5xJBPAu0febor88Sm6jti284mTU4ESMbsY=; b=eu5UZ4OsMYdTcREYZIX7r85ooQn+OGcNiW7vrwuafevBzXhVzqnlv6eyfwJkcHnMbY v3efYselfZLxmBETEWM5dBWw8ECIbk6omFlXu2uCyOEFVwNV186CXBGLiSY96yZc425m ytw/VPReXNueMY21KwbOCflESKMPRK9rNFPwJVt9liMHbVKJLeSFx3fvJtD7rID5eceD m4+jk0yypkzFbmKOvWUsu8tKMo1TyxGGbzruIqB03d3ll+aV2BbYIVZk9gG325pYgTsQ dhviJtyZTMnU+u3CAx3GE47P8iFrMhRZy+7sVmGgCS9omPHKsay2UYpiBKa18BOBvGkF bRYA==
X-Gm-Message-State: AOAM53126LD88DWtRH41pKUrNXz17YjO0mRlAFLIrVudwOe7C4Vs8cr8 2bVBqYXzMX2wFu4AqCNzzERDPLtNjWqFfmegmGk=
X-Google-Smtp-Source: ABdhPJwIsBc5GvsgLFz2Gfdk2npNVwGc3WSxXVItQvaURUdtex5I82FDrR8vMQOzb99Yps/RAcg1faK0UkuSMXjfDg0=
X-Received: by 2002:a19:ed03:: with SMTP id y3mr6822357lfy.377.1614549728603;  Sun, 28 Feb 2021 14:02:08 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <CAC4RtVARxfJNUs+ve1ViDTF385QjLoyhw8JyKc-nALhuu=xoPA@mail.gmail.com> <81c05041-a4ad-a473-701c-0027cd503696@gmail.com> <CABuGu1pncrHQ-Ba7t7VEcbYrjfoc_Ek_3B5X66owSE2GWRdPSg@mail.gmail.com> <8c715354-54ed-434a-c630-bb3c902cb8da@gmail.com> <CAL0qLwaZh_HHCVfVkHki497uaSSN-GCy2U=aueg7iR+jBGA0xg@mail.gmail.com> <CADyWQ+EtHS_Ke6b+fyuLrE2c1DL3a4XKCnf3745o=GvHfB1TxQ@mail.gmail.com>
In-Reply-To: <CADyWQ+EtHS_Ke6b+fyuLrE2c1DL3a4XKCnf3745o=GvHfB1TxQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Sun, 28 Feb 2021 17:01:57 -0500
Message-ID: <CALaySJJZWKyYO0xvJbTvc0xcjOxOQ6pJPGJVkViN+nkC_rT9hg@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Cc: Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>,  "Kurt Andersen (b)" <kboth@drkurt.com>, "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000000bb01305bc6ca729"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/5XOCvUUL0tz_SrYP17Qg66J8B_A>
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: Sun, 28 Feb 2021 22:02:13 -0000

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

It looks right to me.  Thanks, Tim.

Barry

On Sun, Feb 28, 2021 at 4:53 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:

> I was just working on merging Barry's comments with Dave's and Kurt's.
>
> I attached what should be correct.  I would like someone to just double
> check my work.
>
> tim
>
>
> On Sun, Feb 28, 2021 at 4:35 PM Murray S. Kucherawy <superuser@gmail.com>
> wrote:
>
>> These all work for me.  Thanks for the contributions.
>>
>> Scott, please work your magic with a revision so the chairs can request
>> publication and we can get this on its way.
>>
>> -MSK
>>
>> On Thu, Feb 25, 2021 at 9:13 AM Dave Crocker <dcrocker@gmail.com> wrote:
>>
>>> On 2/25/2021 8:41 AM, Kurt Andersen (b) wrote:
>>>
>>> Especially in the case of the PSD policies, one should not expect that
>>> the controlling organization would necessarily be "a mail-originating
>>> organization". Generally the idea is to *disavow* being such :-)
>>>
>>> Suggested alternate text:
>>>
>>> Domain-based Message Authentication, Reporting, and Conformance (DMARC)
>>> permits a domain-controlling
>>> organization to express domain-level policies and preferences for
>>> message validation, disposition, and reporting,
>>> which a mail-receiving organization can use to improve mail handling.
>>>
>>> +1
>>>
>>> d/
>>>
>>> --
>>> Dave Crockerdcrocker@gmail.com
>>> 408.329.0791
>>>
>>> Volunteer, Silicon Valley Chapter
>>> American Red Crossdave.crocker2@redcross.org
>>>
>>> _______________________________________________
>>> 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
>>
>

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

<div dir=3D"auto">It looks right to me.=C2=A0 Thanks, Tim.</div><div dir=3D=
"auto"><br></div><div dir=3D"auto">Barry</div><div><br><div class=3D"gmail_=
quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Feb 28, 2021 at 4:53 P=
M Tim Wicinski &lt;<a href=3D"mailto:tjw.ietf@gmail.com">tjw.ietf@gmail.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"><div dir=3D"ltr"><d=
iv class=3D"gmail_default" style=3D"font-family:monospace">I was just worki=
ng on merging Barry&#39;s comments with Dave&#39;s and Kurt&#39;s.=C2=A0</d=
iv><div class=3D"gmail_default" style=3D"font-family:monospace"><br></div><=
div class=3D"gmail_default" style=3D"font-family:monospace">I attached what=
 should be correct.=C2=A0 I would like someone to just double check my work=
.</div></div><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-fa=
mily:monospace"><br></div><div class=3D"gmail_default" style=3D"font-family=
:monospace">tim</div><div class=3D"gmail_default" style=3D"font-family:mono=
space"><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Sun, Feb 28, 2021 at 4:35 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:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div dir=3D"ltr"><div>These all work for me.=C2=A0 Thanks for the contributi=
ons.<br><br></div><div>Scott, please work your magic with a revision so the=
 chairs can request publication and we can get this on its way.</div><div><=
br></div><div>-MSK<br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, Feb 25, 2021 at 9:13 AM Dave Crocker =
&lt;<a href=3D"mailto:dcrocker@gmail.com" target=3D"_blank">dcrocker@gmail.=
com</a>&gt; wrote:<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">
 =20
   =20
 =20
  <div>
    <div>On 2/25/2021 8:41 AM, Kurt Andersen (b)
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div class=3D"gmail_quote">
        <div>Especially in the case of the PSD policies, one should not
          expect that the controlling organization would necessarily be
          &quot;a mail-originating organization&quot;. Generally the idea i=
s to
          *disavow* being such :-)</div>
        <div><br>
        </div>
        <div>Suggested alternate text:</div>
        <div><br>
        </div>
        <div>Domain-based Message Authentication, Reporting, and
          Conformance (DMARC) permits a domain-controlling</div>
        organization to express domain-level policies and preferences
        for message validation, disposition, and reporting,=C2=A0</div>
      <div class=3D"gmail_quote">which a mail-receiving organization can
        use to improve mail handling.</div>
    </blockquote>
    <p>+1</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>

_______________________________________________<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>
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></div>

--0000000000000bb01305bc6ca729--


From nobody Sun Feb 28 14:22:38 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 F1E053A09B9 for <dmarc@ietfa.amsl.com>; Sun, 28 Feb 2021 14:22:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.187
X-Spam-Level: 
X-Spam-Status: No, score=-5.187 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, RCVD_IN_DNSWL_HI=-5, 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 b_OnjdVYWV3z for <dmarc@ietfa.amsl.com>; Sun, 28 Feb 2021 14:22:32 -0800 (PST)
Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) (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 C634F3A09B5 for <dmarc@ietf.org>; Sun, 28 Feb 2021 14:22:31 -0800 (PST)
Received: by mail-oi1-x229.google.com with SMTP id 21so6564282oiq.7 for <dmarc@ietf.org>; Sun, 28 Feb 2021 14:22: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=QKQ9EbEMHALU7lPDnkglceWXenihIcDl7P+YRsWZs+A=; b=X3X9VboXgZfH/EaRHeP0V+K8IyL9+2eKqR+rgeJo/As7Jitpmlc6YwQA+E+pMBDj3R ayW8fU9sXDbsJFpcXeUCYRNlkJUPjt5+ZltUzgrfRoVOW9jdf1ZMMINe6ClWb/vQM9k/ 8z9j4ZoQoyimDMPCpzJ6wXZyetBGRzMiwyD6tmd5ms/2BCgOJcK5z/mxjqjPYXAtDqGP vjE8F+QnxdqsCPh8Ls7juzuaGPVkLk8lUqlV8K+AsVtbQxAHSyGIXvaOTEPsS44XYTxf izHlCKI49b/jzqIj35dnMFAIOcVZ0tu9bK7BerT9+MdU9RZk1vlsxwc3jHEnpI4ZJam+ e3pw==
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=QKQ9EbEMHALU7lPDnkglceWXenihIcDl7P+YRsWZs+A=; b=BOzYu5Im0lrDvkmd1M6ndiDsrFvFPdZLrAbUVhFbjSRtBYnXY0TpBxf7uxvx2uUaFl nVR/tvYFno1aMvG5BFjbi3mkpgQcEaoOVQDSt6yZAbxoYlKaaSDzKDZ5AwnOE/aZiAhC +eDiyHJLW/AT99a63IOpVcl2v+9OqCToMIic1W0DEiapO4iHJaijLSAWqKB4ml7UJFH0 5CeSx9oJgppj5GYZ41n2N9J+SV8YJVGvhxOxCVslx8XsRh3LuValozGWJYb9gapeN7vt U8mKbOi74+flkN8pETBC/3mq6zLdGeMSom0TwVzG/pzXsV29qHdbJSdMuT2DssxRJq5h btIg==
X-Gm-Message-State: AOAM5302O56U1tJm66BMDFztOVXM/vvz1KMsF67B9q5HyqZ74wxizUOk QN39u+lT28r0/je8ddVCDz58I4KWO60qh///4tA=
X-Google-Smtp-Source: ABdhPJyTVKyPMt2SBUHCntn10pc30vbL0w/DEWjs72MGN0JJSOrp3zpofIgIoC9SArdVeRCoClTDbp7C0WaQFgeXy/Q=
X-Received: by 2002:a05:6808:154:: with SMTP id h20mr9838840oie.45.1614550950545;  Sun, 28 Feb 2021 14:22:30 -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> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com> <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com> <CAC4RtVDCeFQU9RTN6osPTrMpap-Djkx5+Czx=-nKqVeXnyEy1Q@mail.gmail.com> <CAL0qLwZXkRMLXS7mt28-vEKKk4HgWkP98P8kdYaS1XbcYQvSxQ@mail.gmail.com> <CALaySJLVGhaBhrmDSYayYrcU9JSq_pY6D8=KoirUGCrOeKeHCQ@mail.gmail.com> <CAC4RtVARxfJNUs+ve1ViDTF385QjLoyhw8JyKc-nALhuu=xoPA@mail.gmail.com> <81c05041-a4ad-a473-701c-0027cd503696@gmail.com> <CABuGu1pncrHQ-Ba7t7VEcbYrjfoc_Ek_3B5X66owSE2GWRdPSg@mail.gmail.com> <8c715354-54ed-434a-c630-bb3c902cb8da@gmail.com> <CAL0qLwaZh_HHCVfVkHki497uaSSN-GCy2U=aueg7iR+jBGA0xg@mail.gmail.com> <CADyWQ+EtHS_Ke6b+fyuLrE2c1DL3a4XKCnf3745o=GvHfB1TxQ@mail.gmail.com> <CALaySJJZWKyYO0xvJbTvc0xcjOxOQ6pJPGJVkViN+nkC_rT9hg@mail.gmail.com>
In-Reply-To: <CALaySJJZWKyYO0xvJbTvc0xcjOxOQ6pJPGJVkViN+nkC_rT9hg@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Sun, 28 Feb 2021 17:22:19 -0500
Message-ID: <CADyWQ+E_kgDZahQkjBn-qUw5H_9EO67AYTr_TRi+ukGhKc3-tg@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Dave Crocker <dcrocker@gmail.com>, IETF DMARC WG <dmarc@ietf.org>,  "Kurt Andersen (b)" <kboth@drkurt.com>, "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/mixed; boundary="000000000000e128d205bc6cef14"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/oKHaf6e60sDAv2m8Qp3ypJOmDm4>
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: Sun, 28 Feb 2021 22:22:36 -0000

--000000000000e128d205bc6cef14
Content-Type: multipart/alternative; boundary="000000000000e128d005bc6cef12"

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

Thanks Barry

I sent a pull request along to Scott with the changes.

I also generated an rfcdiff which I include for completeness sake.

thanks
tim


On Sun, Feb 28, 2021 at 5:02 PM Barry Leiba <barryleiba@computer.org> wrote:

> It looks right to me.  Thanks, Tim.
>
> Barry
>
> On Sun, Feb 28, 2021 at 4:53 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:
>
>> I was just working on merging Barry's comments with Dave's and Kurt's.
>>
>> I attached what should be correct.  I would like someone to just double
>> check my work.
>>
>> tim
>>
>>
>> On Sun, Feb 28, 2021 at 4:35 PM Murray S. Kucherawy <superuser@gmail.com>
>> wrote:
>>
>>> These all work for me.  Thanks for the contributions.
>>>
>>> Scott, please work your magic with a revision so the chairs can request
>>> publication and we can get this on its way.
>>>
>>> -MSK
>>>
>>> On Thu, Feb 25, 2021 at 9:13 AM Dave Crocker <dcrocker@gmail.com> wrote:
>>>
>>>> On 2/25/2021 8:41 AM, Kurt Andersen (b) wrote:
>>>>
>>>> Especially in the case of the PSD policies, one should not expect that
>>>> the controlling organization would necessarily be "a mail-originating
>>>> organization". Generally the idea is to *disavow* being such :-)
>>>>
>>>> Suggested alternate text:
>>>>
>>>> Domain-based Message Authentication, Reporting, and Conformance (DMARC)
>>>> permits a domain-controlling
>>>> organization to express domain-level policies and preferences for
>>>> message validation, disposition, and reporting,
>>>> which a mail-receiving organization can use to improve mail handling.
>>>>
>>>> +1
>>>>
>>>> d/
>>>>
>>>> --
>>>> Dave Crockerdcrocker@gmail.com
>>>> 408.329.0791
>>>>
>>>> Volunteer, Silicon Valley Chapter
>>>> American Red Crossdave.crocker2@redcross.org
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>

--000000000000e128d005bc6cef12
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">Thanks Barry</div><div class=3D"gmail_default" style=3D"font-family:mono=
space"><br></div><div class=3D"gmail_default" style=3D"font-family:monospac=
e">I sent a pull request along to Scott with the changes.=C2=A0=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">I also generated=
=C2=A0an rfcdiff which I include for completeness sake.</div><div class=3D"=
gmail_default" style=3D"font-family:monospace"><br></div><div class=3D"gmai=
l_default" style=3D"font-family:monospace">thanks</div><div class=3D"gmail_=
default" style=3D"font-family:monospace">tim</div><div class=3D"gmail_defau=
lt" style=3D"font-family:monospace"><br></div></div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Feb 28, 2021 at 5:02 =
PM Barry Leiba &lt;<a href=3D"mailto:barryleiba@computer.org">barryleiba@co=
mputer.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"auto">It looks right to me.=C2=A0 Thanks, Tim.</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">Barry</div><div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Feb 28, 202=
1 at 4:53 PM Tim Wicinski &lt;<a href=3D"mailto:tjw.ietf@gmail.com" target=
=3D"_blank">tjw.ietf@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"ltr"><div class=3D"gmail_default"=
 style=3D"font-family:monospace">I was just working on merging Barry&#39;s =
comments with Dave&#39;s and Kurt&#39;s.=C2=A0</div><div class=3D"gmail_def=
ault" style=3D"font-family:monospace"><br></div><div class=3D"gmail_default=
" style=3D"font-family:monospace">I attached what should be correct.=C2=A0 =
I would like someone to just double check my work.</div></div><div dir=3D"l=
tr"><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></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, F=
eb 28, 2021 at 4:35 PM Murray S. Kucherawy &lt;<a href=3D"mailto:superuser@=
gmail.com" target=3D"_blank">superuser@gmail.com</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>These=
 all work for me.=C2=A0 Thanks for the contributions.<br><br></div><div>Sco=
tt, please work your magic with a revision so the chairs can request public=
ation and we can get this on its way.</div><div><br></div><div>-MSK<br></di=
v></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr=
">On Thu, Feb 25, 2021 at 9:13 AM Dave Crocker &lt;<a href=3D"mailto:dcrock=
er@gmail.com" target=3D"_blank">dcrocker@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">
 =20
   =20
 =20
  <div>
    <div>On 2/25/2021 8:41 AM, Kurt Andersen (b)
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div class=3D"gmail_quote">
        <div>Especially in the case of the PSD policies, one should not
          expect that the controlling organization would necessarily be
          &quot;a mail-originating organization&quot;. Generally the idea i=
s to
          *disavow* being such :-)</div>
        <div><br>
        </div>
        <div>Suggested alternate text:</div>
        <div><br>
        </div>
        <div>Domain-based Message Authentication, Reporting, and
          Conformance (DMARC) permits a domain-controlling</div>
        organization to express domain-level policies and preferences
        for message validation, disposition, and reporting,=C2=A0</div>
      <div class=3D"gmail_quote">which a mail-receiving organization can
        use to improve mail handling.</div>
    </blockquote>
    <p>+1</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>

_______________________________________________<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>
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></div>
</blockquote></div>

--000000000000e128d005bc6cef12--

--000000000000e128d205bc6cef14
Content-Type: text/html; charset="US-ASCII";
 name="draft-ietf-dmarc-psd-10-from-1.diff.html"
Content-Disposition: attachment; 
 filename="draft-ietf-dmarc-psd-10-from-1.diff.html"
Content-Transfer-Encoding: base64
Content-ID: <f_klppwi2c0>
X-Attachment-Id: f_klppwi2c0

PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNpdGlvbmFs
Ly9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwxLXRyYW5zaXRpb25h
bC5kdGQiPiAKPCEtLSBHZW5lcmF0ZWQgYnkgcmZjZGlmZiAxLjM0OiByZmNkaWZmICAtLT4gCjwh
LS0gPCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEgVHJhbnNpdGlv
bmFsIiA+IC0tPgo8IS0tIFN5c3RlbTogRGFyd2luIGJvaWxlci5sb2NhbCAyMC4zLjAgRGFyd2lu
IEtlcm5lbCBWZXJzaW9uIDIwLjMuMDogVGh1IEphbiAyMSAwMDowNzowNiBQU1QgMjAyMTsgcm9v
dDp4bnUtNzE5NS44MS4zfjEvUkVMRUFTRV9YODZfNjQgeDg2XzY0IC0tPiAKPCEtLSBVc2luZyBh
d2s6IC9vcHQvbG9jYWwvYmluL2dhd2s6IEdOVSBBd2sgNS4xLjAsIEFQSTogMy4wIC0tPiAKPCEt
LSBVc2luZyBkaWZmOiAvdXNyL2Jpbi9kaWZmOiBkaWZmIChHTlUgZGlmZnV0aWxzKSAyLjguMSAt
LT4gCjwhLS0gVXNpbmcgd2RpZmY6IC9vcHQvbG9jYWwvYmluL3dkaWZmOiB3ZGlmZiAoR05VIHdk
aWZmKSAxLjIuMiAtLT4gCjxodG1sPiAKPGhlYWQ+IAogIDxtZXRhIGh0dHAtZXF1aXY9IkNvbnRl
bnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWlzby04ODU5LTEiIC8+IAogIDxt
ZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtU3R5bGUtVHlwZSIgY29udGVudD0idGV4dC9jc3MiIC8+
IAogIDx0aXRsZT5EaWZmOiBkcmFmdC1pZXRmLWRtYXJjLXBzZC0xMS50eHQgLSBkcmFmdC1pZXRm
LWRtYXJjLXBzZC0xMC50eHQ8L3RpdGxlPiAKICA8c3R5bGUgdHlwZT0idGV4dC9jc3MiPiAKICAg
IGJvZHkgICAgeyBtYXJnaW46IDAuNGV4OyBtYXJnaW4tcmlnaHQ6IGF1dG87IH0gCiAgICB0ciAg
ICAgIHsgfSAKICAgIHRkICAgICAgeyB3aGl0ZS1zcGFjZTogcHJlOyBmb250LWZhbWlseTogbW9u
b3NwYWNlOyB2ZXJ0aWNhbC1hbGlnbjogdG9wOyBmb250LXNpemU6IDAuODZlbTt9IAogICAgdGgg
ICAgICB7IGZvbnQtc2l6ZTogMC44NmVtOyB9IAogICAgLnNtYWxsICB7IGZvbnQtc2l6ZTogMC42
ZW07IGZvbnQtc3R5bGU6IGl0YWxpYzsgZm9udC1mYW1pbHk6IFZlcmRhbmEsIEhlbHZldGljYSwg
c2Fucy1zZXJpZjsgfSAKICAgIC5sZWZ0ICAgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjRUVFOyB9IAog
ICAgLnJpZ2h0ICB7IGJhY2tncm91bmQtY29sb3I6ICNGRkY7IH0gCiAgICAuZGlmZiAgIHsgYmFj
a2dyb3VuZC1jb2xvcjogI0NDRjsgfSAKICAgIC5sYmxvY2sgeyBiYWNrZ3JvdW5kLWNvbG9yOiAj
QkZCOyB9IAogICAgLnJibG9jayB7IGJhY2tncm91bmQtY29sb3I6ICNGRjg7IH0gCiAgICAuaW5z
ZXJ0IHsgYmFja2dyb3VuZC1jb2xvcjogIzhGRjsgfSAKICAgIC5kZWxldGUgeyBiYWNrZ3JvdW5k
LWNvbG9yOiAjQUNGOyB9IAogICAgLnZvaWQgICB7IGJhY2tncm91bmQtY29sb3I6ICNGRkI7IH0g
CiAgICAuY29udCAgIHsgYmFja2dyb3VuZC1jb2xvcjogI0VFRTsgfSAKICAgIC5saW5lYnIgeyBi
YWNrZ3JvdW5kLWNvbG9yOiAjQUFBOyB9IAogICAgLmxpbmVubyB7IGNvbG9yOiByZWQ7IGJhY2tn
cm91bmQtY29sb3I6ICNGRkY7IGZvbnQtc2l6ZTogMC43ZW07IHRleHQtYWxpZ246IHJpZ2h0OyBw
YWRkaW5nOiAwIDJweDsgfSAKICAgIC5lbGlwc2lzeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQUFBOyB9
IAogICAgLmxlZnQgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjREREOyB9IAogICAgLnJpZ2h0
IC5jb250IHsgYmFja2dyb3VuZC1jb2xvcjogI0VFRTsgfSAKICAgIC5sYmxvY2sgLmNvbnQgeyBi
YWNrZ3JvdW5kLWNvbG9yOiAjOUQ5OyB9IAogICAgLnJibG9jayAuY29udCB7IGJhY2tncm91bmQt
Y29sb3I6ICNERDY7IH0gCiAgICAuaW5zZXJ0IC5jb250IHsgYmFja2dyb3VuZC1jb2xvcjogIzBE
RDsgfSAKICAgIC5kZWxldGUgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjOEFEOyB9IAogICAg
LnN0YXRzLCAuc3RhdHMgdGQsIC5zdGF0cyB0aCB7IGJhY2tncm91bmQtY29sb3I6ICNFRUU7IHBh
ZGRpbmc6IDJweCAwOyB9IAogIDwvc3R5bGU+IAo8L2hlYWQ+IAo8Ym9keSA+IAogIDx0YWJsZSBi
b3JkZXI9IjAiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMCI+IAogIDx0ciBiZ2NvbG9y
PSJvcmFuZ2UiPjx0aD48L3RoPjx0aD4mbmJzcDtkcmFmdC1pZXRmLWRtYXJjLXBzZC0xMS50eHQm
bmJzcDs8L3RoPjx0aD4gPC90aD48dGg+Jm5ic3A7ZHJhZnQtaWV0Zi1kbWFyYy1wc2QtMTAudHh0
Jm5ic3A7PC90aD48dGg+PC90aD48L3RyPiAKICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij5OZXR3b3JrIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBTLiBLaXR0ZXJtYW48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij5O
ZXR3b3JrIFdvcmtpbmcgR3JvdXAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICBTLiBLaXR0ZXJtYW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+SW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBmVExEIFJlZ2lzdHJ5IFNlcnZpY2VzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+SW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBmVExE
IFJlZ2lzdHJ5IFNlcnZpY2VzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAwMSIgLz48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJs
YmxvY2siPkludGVuZGVkIHN0YXR1czogRXhwZXJpbWVudGFsICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIEphbnVhcnkgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+MSw8L3NwYW4+IDIwMjE8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+SW50ZW5kZWQgc3RhdHVzOiBFeHBlcmltZW50YWwg
ICAgICAgICAgICAgICAgICAgICAgICAgICBKYW51YXJ5IDxzcGFuIGNsYXNzPSJpbnNlcnQiPjIz
LDwvc3Bhbj4gMjAyMTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPkV4cGlyZXM6IEp1bHkgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+NSw8L3NwYW4+
IDIwMjE8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+RXhwaXJlczogSnVseSA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij4yNyw8L3NwYW4+IDIwMjE8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgICAgICAgIEV4cGVyaW1lbnRhbCBETUFSQyBFeHRlbnNpb24gRm9yIFB1YmxpYyBTdWZm
aXggRG9tYWluczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgIEV4cGVy
aW1lbnRhbCBETUFSQyBFeHRlbnNpb24gRm9yIFB1YmxpYyBTdWZmaXggRG9tYWluczwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQ+PGEg
bmFtZT0iZGlmZjAwMDIiIC8+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAgICAgICAgICAgICAg
ICAgICBkcmFmdC1pZXRmLWRtYXJjLXBzZC0xPHNwYW4gY2xhc3M9ImRlbGV0ZSI+MTwvc3Bhbj48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAgICAgICAgICAgICAgICAg
ZHJhZnQtaWV0Zi1kbWFyYy1wc2QtMTxzcGFuIGNsYXNzPSJpbnNlcnQiPjA8L3NwYW4+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5BYnN0cmFjdDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPkFic3RyYWN0PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQ+PGEgbmFt
ZT0iZGlmZjAwMDMiIC8+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA8c3BhbiBjbGFzcz0iZGVsZXRl
Ij5Eb21haW4tYmFzZWQ8L3NwYW4+IE1lc3NhZ2UgQXV0aGVudGljYXRpb24sIFJlcG9ydGluZywg
YW5kIDxzcGFuIGNsYXNzPSJkZWxldGUiPkNvbmZvcm1hbmNlPC9zcGFuPjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmJsb2NrIj4gICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5ETUFSQyAoRG9tYWlu
LWJhc2VkPC9zcGFuPiBNZXNzYWdlIEF1dGhlbnRpY2F0aW9uLCBSZXBvcnRpbmcsIGFuZDwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFu
IGNsYXNzPSJkZWxldGUiPiAgIChETUFSQykgcGVybWl0czwvc3Bhbj4gYSA8c3BhbiBjbGFzcz0i
ZGVsZXRlIj5kb21haW4tY29udHJvbGxpbmc8L3NwYW4+IG9yZ2FuaXphdGlvbiA8c3BhbiBjbGFz
cz0iZGVsZXRlIj50bzwvc3Bhbj4gZXhwcmVzcyA8c3BhbiBjbGFzcz0iZGVsZXRlIj5kb21haW4t
PC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA8c3BhbiBjbGFzcz0i
aW5zZXJ0Ij5Db25mb3JtYW5jZSkgaXM8L3NwYW4+IGEgPHNwYW4gY2xhc3M9Imluc2VydCI+c2Nh
bGFibGUgbWVjaGFuaXNtIGJ5IHdoaWNoIGEgbWFpbC1vcmlnaW5hdGluZzwvc3Bhbj48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBj
bGFzcz0iZGVsZXRlIj4gICBsZXZlbDwvc3Bhbj4gcG9saWNpZXMgYW5kIHByZWZlcmVuY2VzIGZv
ciBtZXNzYWdlIHZhbGlkYXRpb24sIGRpc3Bvc2l0aW9uLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmJsb2NrIj4gICBvcmdhbml6YXRpb24gPHNwYW4gY2xhc3M9Imluc2VydCI+Y2FuPC9zcGFu
PiBleHByZXNzIDxzcGFuIGNsYXNzPSJpbnNlcnQiPmRvbWFpbi1sZXZlbDwvc3Bhbj4gcG9saWNp
ZXMgYW5kIHByZWZlcmVuY2VzIGZvcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIGFuZCByZXBvcnRpbmcsIDxzcGFuIGNsYXNzPSJkZWxl
dGUiPndoaWNoPC9zcGFuPiBhIG1haWwtcmVjZWl2aW5nIG9yZ2FuaXphdGlvbiBjYW4gdXNlIHRv
IGltcHJvdmU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgbWVzc2FnZSB2YWxp
ZGF0aW9uLCBkaXNwb3NpdGlvbiwgYW5kIHJlcG9ydGluZywgPHNwYW4gY2xhc3M9Imluc2VydCI+
dGhhdDwvc3Bhbj4gYSBtYWlsLXJlY2VpdmluZzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIG1haWwgaGFuZGxpbmcuPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIG9yZ2FuaXphdGlvbiBjYW4gdXNlIHRvIGltcHJvdmUg
bWFpbCBoYW5kbGluZy4gIDxzcGFuIGNsYXNzPSJpbnNlcnQiPlRoZSBkZXNpZ24gb2YgRE1BUkM8
L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxi
bG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNl
cnQiPiAgIHByZXN1bWVzIHRoYXQgZG9tYWluIG5hbWVzIHJlcHJlc2VudCBlaXRoZXIgbm9kZXMg
aW4gdGhlIHRyZWUgYmVsb3c8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2si
PjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIHdoaWNoIHJlZ2lzdHJhdGlvbnMgb2NjdXIsIG9yIG5v
ZGVzIHdoZXJlIHJlZ2lzdHJhdGlvbnMgaGF2ZTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgb2NjdXJyZWQ7IGl0IGRvZXMgbm90
IHBlcm1pdCBhIGRvbWFpbiBuYW1lIHRvIGhhdmUgYm90aCBvZiB0aGVzZTwvc3Bhbj48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgcHJvcGVy
dGllcyBzaW11bHRhbmVvdXNseS4gIFNpbmNlIGl0cyBkZXBsb3ltZW50IGluIDIwMTUsIHVzZSBv
Zjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imlu
c2VydCI+ICAgRE1BUkMgaGFzIHNob3duIGEgY2xlYXIgbmVlZCBmb3IgdGhlIGFiaWxpdHkgdG8g
ZXhwcmVzcyBwb2xpY3kgZm9yPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICB0aGVzZSBkb21haW5zIGFzIHdlbGwuPC9zcGFuPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDA0IiAvPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+RE1BUkMgZGlzdGluZ3Vp
c2hlcyB0aGUgcG9ydGlvbiBvZiBhIG5hbWUgdGhhdCBpcyBhIFB1YmxpYyBTdWZmaXg8L3NwYW4+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQi
PkRvbWFpbnMgYXQ8L3NwYW4+IHdoaWNoIDxzcGFuIGNsYXNzPSJpbnNlcnQiPnJlZ2lzdHJhdGlv
bnMgY2FuIG9jY3VyPC9zcGFuPiBhcmUgPHNwYW4gY2xhc3M9Imluc2VydCI+cmVmZXJyZWQ8L3Nw
YW4+IHRvIDxzcGFuIGNsYXNzPSJpbnNlcnQiPmFzIFB1YmxpYzwvc3Bhbj48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0i
ZGVsZXRlIj4gICBEb21haW4gKFBTRCksIGJlbG93PC9zcGFuPiB3aGljaCA8c3BhbiBjbGFzcz0i
ZGVsZXRlIj5vcmdhbml6YXRpb25hbCBkb21haW4gbmFtZXM8L3NwYW4+IGFyZSA8c3BhbiBjbGFz
cz0iZGVsZXRlIj5jcmVhdGVkLjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgU3VmZml4IERvbWFpbnMgKFBTRHMpLjwvc3Bhbj4g
IFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGFuIGV4dGVuc2lvbiB0byBETUFSQzwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNz
PSJkZWxldGUiPiAgIFRoZSBiYXNpYyBETUFSQyBjYXBhYmlsaXR5IGFsbG93cyBvcmdhbml6YXRp
b25hbCBkb21haW5zIHRvIHNwZWNpZnk8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPiAgIHRvIGVuYWJsZSBETUFSQyBmdW5jdGlvbmFsaXR5IGZvciBQU0RzLjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNs
YXNzPSJkZWxldGUiPiAgIHBvbGljaWVzIHRoYXQgYXBwbHk8L3NwYW4+IHRvIDxzcGFuIGNsYXNz
PSJkZWxldGUiPnRoZWlyIHN1YmRvbWFpbnMsIGJ1dCBpdCBkb2VzIG5vdCBnaXZlIHRoYXQ8L3Nw
YW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUi
PiAgIGNhcGFiaWxpdHkgdG8gUFNEcy48L3NwYW4+ICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBh
biBleHRlbnNpb24gdG8gRE1BUkMgdG88L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
ICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+ZnVsbHk8L3NwYW4+IGVuYWJsZSBETUFSQyBmdW5jdGlv
bmFsaXR5IGZvciBQU0RzLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAwNSIgLz48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJkZWxldGUiPlNvbWU8L3NwYW4+IGltcGxlbWVu
dGF0aW9ucyA8c3BhbiBjbGFzcz0iZGVsZXRlIj5vZiBETUFSQzwvc3Bhbj4gY29uc2lkZXIgYSA8
c3BhbiBjbGFzcz0iZGVsZXRlIj5QU0Q8L3NwYW4+IHRvIGJlIGluZWxpZ2libGUgZm9yPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPlRoaXMg
ZG9jdW1lbnQgYWxzbyBzZWVrcyB0byBhZGRyZXNzPC9zcGFuPiBpbXBsZW1lbnRhdGlvbnMgPHNw
YW4gY2xhc3M9Imluc2VydCI+dGhhdDwvc3Bhbj4gY29uc2lkZXIgYTwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIERNQVJDIGVuZm9yY2Vt
ZW50LiAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+VGhpcyBzcGVjaWZpY2F0aW9uIGFkZHJlc3NlcyB0
aGF0IGNhc2UuPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij5kb21haW4gb24gYSBwdWJsaWMgU3VmZml4IGxpc3Q8L3NwYW4+IHRv
IGJlIGluZWxpZ2libGUgZm9yIERNQVJDPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2si
PiAgIGVuZm9yY2VtZW50LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+U3RhdHVzIG9mIFRo
aXMgTWVtbzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPlN0YXR1cyBvZiBUaGlzIE1l
bW88L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgaXMg
c3VibWl0dGVkIGluIGZ1bGwgY29uZm9ybWFuY2Ugd2l0aCB0aGU8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBUaGlzIEludGVybmV0LURyYWZ0IGlzIHN1Ym1pdHRlZCBpbiBmdWxs
IGNvbmZvcm1hbmNlIHdpdGggdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHByb3Zpc2lvbnMgb2YgQkNQIDc4IGFuZCBCQ1AgNzkuPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcHJvdmlzaW9ucyBvZiBCQ1AgNzggYW5k
IEJDUCA3OS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEludGVybmV0LURyYWZ0cyBh
cmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5nPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRv
Y3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmc8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGFzayBGb3JjZSAoSUVURikuICBO
b3RlIHRoYXQgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGU8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBUYXNrIEZvcmNlIChJRVRGKS4gIE5vdGUgdGhhdCBvdGhlciBn
cm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC1E
cmFmdHMuICBUaGUgbGlzdCBvZiBjdXJyZW50IEludGVybmV0LTwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LURyYWZ0cy4gIFRo
ZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIERyYWZ0cyBpcyBhdCBodHRwczovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RyYWZ0cy9jdXJyZW50Ly48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBEcmFmdHMgaXMgYXQgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kcmFmdHMv
Y3VycmVudC8uPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBJbnRlcm5ldC1EcmFmdHMg
YXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHM8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0
IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHM8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgYW5kIG1heSBiZSB1
cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnk8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJl
cGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueTwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0aW1lLiAgSXQg
aXMgaW5hcHByb3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZTwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRl
IHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlPC90ZD48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG1hdGVyaWFsIG9yIHRvIGNpdGUg
dGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiI8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAi
d29yayBpbiBwcm9ncmVzcy4iPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQ+PGEg
bmFtZT0iZGlmZjAwMDYiIC8+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBUaGlzIEludGVybmV0LURy
YWZ0IHdpbGwgZXhwaXJlIG9uIEp1bHkgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+NTwvc3Bhbj4sIDIw
MjEuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIFRoaXMgSW50ZXJuZXQtRHJh
ZnQgd2lsbCBleHBpcmUgb24gSnVseSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4yNzwvc3Bhbj4sIDIw
MjEuPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij5Db3B5cmlnaHQgTm90aWNlPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+Q29weXJpZ2h0IE5vdGljZTwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgQ29weXJpZ2h0IChjKSAyMDIxIElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJz
b25zIGlkZW50aWZpZWQgYXMgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
Q29weXJpZ2h0IChjKSAyMDIxIElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQg
YXMgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIGRvY3VtZW50IGF1dGhvcnMuICBBbGwgcmlnaHRzIHJlc2VydmVkLjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGRvY3VtZW50IGF1dGhvcnMuICBBbGwgcmlnaHRzIHJl
c2VydmVkLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhpcyBkb2N1bWVudCBpcyBz
dWJqZWN0IHRvIEJDUCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdhbDwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoaXMgZG9jdW1lbnQgaXMgc3ViamVjdCB0byBCQ1AgNzgg
YW5kIHRoZSBJRVRGIFRydXN0J3MgTGVnYWw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERv
Y3VtZW50czwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFByb3Zpc2lvbnMgUmVs
YXRpbmcgdG8gSUVURiBEb2N1bWVudHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgKGh0dHBzOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNl
LWluZm8pIGluIGVmZmVjdCBvbiB0aGUgZGF0ZSBvZjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIChodHRwczovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZl
Y3Qgb24gdGhlIGRhdGUgb2Y8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgcHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFzZSBy
ZXZpZXcgdGhlc2UgZG9jdW1lbnRzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
cHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2UgZG9jdW1l
bnRzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHIgYmdjb2xvcj0iZ3JheSIgPjx0ZD48L3RkPjx0aD48YSBuYW1lPSJwYXJ0LWwyIiAv
PjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxlbT4gcGFnZSAyLCBsaW5lIDM0
PC9lbT48L3RoPjx0aD4gPC90aD48dGg+PGEgbmFtZT0icGFydC1yMiIgLz48c21hbGw+c2tpcHBp
bmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48ZW0+IHBhZ2UgMiwgbGluZSAzNDwvZW0+PC90aD48dGQ+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAxLjIuICBEaXNjdXNzaW9uICAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICAxLjIuICBEaXNjdXNzaW9uICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gICA0PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIDIuICBUZXJtaW5vbG9neSBhbmQgRGVmaW5pdGlvbnMg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNTwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIDIuICBUZXJtaW5vbG9neSBhbmQgRGVmaW5pdGlvbnMgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDIuMS4gIENvbnZlbnRpb25zIFVzZWQgaW4g
VGhpcyBEb2N1bWVudCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDU8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDIuMS4gIENvbnZlbnRpb25zIFVzZWQgaW4gVGhpcyBEb2N1
bWVudCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAyLjIuICBQdWJsaWMgU3VmZml4IERv
bWFpbiAoUFNEKSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA1PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAyLjIuICBQdWJsaWMgU3VmZml4IERvbWFpbiAoUFNE
KSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA1PC90ZD48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgMi4zLiAgT3JnYW5pemF0aW9u
YWwgRG9tYWluIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgMi4zLiAgT3JnYW5pemF0aW9uYWwgRG9tYWlu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDIuNC4gIExvbmdlc3Qg
UFNEIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDY8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDIuNC4gIExvbmdlc3QgUFNEIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDY8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAyLjUuICBQdWJs
aWMgU3VmZml4IE9wZXJhdG9yIChQU08pICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA2
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAyLjUuICBQdWJsaWMgU3VmZml4
IE9wZXJhdG9yIChQU08pICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA2PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgMi42LiAg
UFNPIENvbnRyb2xsZWQgRG9tYWluIE5hbWVzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICAgNjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgMi42LiAgUFNPIENvbnRy
b2xsZWQgRG9tYWluIE5hbWVzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDIu
Ny4gIE5vbi1leGlzdGVudCBEb21haW5zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAgIDY8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDIuNy4gIE5vbi1l
eGlzdGVudCBEb21haW5zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDY8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
My4gIFBTRCBETUFSQyBVcGRhdGVzIHRvIERNQVJDIFJlcXVpcmVtZW50cyAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gICA2PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgMy4gIFBTRCBE
TUFSQyBVcGRhdGVzIHRvIERNQVJDIFJlcXVpcmVtZW50cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
ICA2PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAwNyIgLz48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgMy4x
LiAgR2VuZXJhbCBVcGRhdGVzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+Njwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJibG9jayI+ICAgICAzLjEuICBHZW5lcmFsIFVwZGF0ZXMgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij43PC9zcGFuPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
IDMuMi4gIENoYW5nZXMgaW4gU2VjdGlvbiA2LjMgIkdlbmVyYWwgUmVjb3JkIEZvcm1hdCIgIC4g
LiAuIC4gLiAgIDc8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDMuMi4gIENo
YW5nZXMgaW4gU2VjdGlvbiA2LjMgIkdlbmVyYWwgUmVjb3JkIEZvcm1hdCIgIC4gLiAuIC4gLiAg
IDc8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgICAzLjMuICBDaGFuZ2VzIGluIFNlY3Rpb24gNi41ICJEb21haW4gT3duZXIgQWN0aW9ucyIg
LiAuIC4gLiAuIC4gICA3PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAzLjMu
ICBDaGFuZ2VzIGluIFNlY3Rpb24gNi41ICJEb21haW4gT3duZXIgQWN0aW9ucyIgLiAuIC4gLiAu
IC4gICA3PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgICAgMy40LiAgQ2hhbmdlcyBpbiBTZWN0aW9uIDYuNi4xICJFeHRyYWN0IEF1dGhvciBE
b21haW4iICAuIC4gLiAuICAgNzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAg
My40LiAgQ2hhbmdlcyBpbiBTZWN0aW9uIDYuNi4xICJFeHRyYWN0IEF1dGhvciBEb21haW4iICAu
IC4gLiAuICAgNzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgIDMuNS4gIENoYW5nZXMgaW4gU2VjdGlvbiA2LjYuMyAiUG9saWN5IERpc2Nv
dmVyeSIgLiAuIC4gLiAuIC4gLiAgIDg8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgIDMuNS4gIENoYW5nZXMgaW4gU2VjdGlvbiA2LjYuMyAiUG9saWN5IERpc2NvdmVyeSIgLiAu
IC4gLiAuIC4gLiAgIDg8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgICAzLjYuICBDaGFuZ2VzIGluIFNlY3Rpb24gNyAiRE1BUkMgRmVlZGJh
Y2siIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA4PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgICAzLjYuICBDaGFuZ2VzIGluIFNlY3Rpb24gNyAiRE1BUkMgRmVlZGJhY2siIC4gLiAu
IC4gLiAuIC4gLiAuIC4gICA4PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIDQuICBQcml2YWN5IENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgODwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIDQuICBQcml2YWN5IENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuICAgODwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQ+PGEgbmFtZT0iZGlmZjAwMDgiIC8+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj4gICAgIDQuMS4gIEZlZWRiYWNrIGxlYWthZ2UgIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDxzcGFuIGNsYXNzPSJkZWxldGUiPjg8L3NwYW4+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgNC4xLiAgRmVlZGJhY2sgbGVha2Fn
ZSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgPHNwYW4gY2xhc3M9
Imluc2VydCI+OTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgNS4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEwPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgNS4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDEwPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIDYuICBJQU5BIENvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIDYuICBJQU5BIENvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDYuMS4gIFN1YmRvbWFpbiBQb2xpY3kgVGFnICAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTA8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAgIDYuMS4gIFN1YmRvbWFpbiBQb2xpY3kgVGFnICAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTA8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgNy4gIFJlZmVyZW5jZXMgIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEwPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgNy4gIFJlZmVyZW5jZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEwPC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgNy4xLiAgTm9ybWF0aXZlIFJlZmVy
ZW5jZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMDwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgNy4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMgIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMDwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDcuMi4gIEluZm9ybWF0aXZl
IFJlZmVyZW5jZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTE8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDcuMi4gIEluZm9ybWF0aXZlIFJlZmVyZW5j
ZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTE8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgQXBwZW5kaXggQS4gIFBT
RCBETUFSQyBQcml2YWN5IENvbmNlcm4gTWl0aWdhdGlvbiBFeHBlcmltZW50ICAuIC4gIDEyPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQXBwZW5kaXggQS4gIFBTRCBETUFSQyBQ
cml2YWN5IENvbmNlcm4gTWl0aWdhdGlvbiBFeHBlcmltZW50ICAuIC4gIDEyPC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEFwcGVuZGl4IEIu
ICBETUFSQyBQU0QgUmVnaXN0cnkgRXhhbXBsZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAx
MjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEFwcGVuZGl4IEIuICBETUFSQyBQ
U0QgUmVnaXN0cnkgRXhhbXBsZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIEIuMS4g
IERNQVJDIFBTRCBETlMgUXVlcnkgU2VydmljZSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgMTI8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIEIuMS4gIERNQVJDIFBT
RCBETlMgUXVlcnkgU2VydmljZSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTI8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICBC
LjIuICBETUFSQyBQdWJsaWMgU3VmZml4IERvbWFpbiAoUFNEKSBSZWdpc3RyeSAuIC4gLiAuIC4g
LiAuIC4gIDEyPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICBCLjIuICBETUFS
QyBQdWJsaWMgU3VmZml4IERvbWFpbiAoUFNEKSBSZWdpc3RyeSAuIC4gLiAuIC4gLiAuIC4gIDEy
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
ICAgQi4zLiAgRE1BUkMgUFNEIFBTTCBFeHRlbnNpb24gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICAxMzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgQi4zLiAg
RE1BUkMgUFNEIFBTTCBFeHRlbnNpb24gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICAxMzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBBcHBlbmRpeCBDLiAgSW1wbGVtZW50YXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAgMTM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBBcHBl
bmRpeCBDLiAgSW1wbGVtZW50YXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAgMTM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgICBDLjEuICBBdXRoaGVhZGVycyBNb2R1bGUgIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDEzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
ICBDLjEuICBBdXRoaGVhZGVycyBNb2R1bGUgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gIDEzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgICAgQy4yLiAgWmRraW1maWx0ZXIgTW9kdWxlICAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxNDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgQy4yLiAgWmRraW1maWx0ZXIgTW9kdWxlICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICAxNDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBBY2tub3dsZWRnZW1lbnRzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBBY2tub3dsZWRnZW1lbnRzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAgMTQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgQXV0aG9yJ3MgQWRkcmVzcyAgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgQXV0aG9yJ3MgQWRkcmVzcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE0PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4xLiAg
SW50cm9kdWN0aW9uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+MS4gIEludHJvZHVj
dGlvbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDA5
IiAvPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgRE1BUkMgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+KFtS
RkM3NDg5XSk8L3NwYW4+IHByb3ZpZGVzIGEgbWVjaGFuaXNtIGZvciBwdWJsaXNoaW5nIG9yZ2Fu
aXphdGlvbmFsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIERNQVJDIDxzcGFu
IGNsYXNzPSJpbnNlcnQiPltSRkM3NDg5XTwvc3Bhbj4gcHJvdmlkZXMgYSBtZWNoYW5pc20gZm9y
IHB1Ymxpc2hpbmcgb3JnYW5pemF0aW9uYWw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgcG9saWN5IGluZm9ybWF0aW9uIHRvIGVtYWlsIHJl
Y2VpdmVycy4gIERNQVJDIGFsbG93cyBwb2xpY3kgdG8gYmU8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBwb2xpY3kgaW5mb3JtYXRpb24gdG8gZW1haWwgcmVjZWl2ZXJzLiAgRE1B
UkMgYWxsb3dzIHBvbGljeSB0byBiZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBzcGVjaWZpZWQgZm9yIGJvdGggaW5kaXZpZHVhbCBkb21h
aW5zIGFuZCBmb3Igb3JnYW5pemF0aW9uYWwgZG9tYWluczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIHNwZWNpZmllZCBmb3IgYm90aCBpbmRpdmlkdWFsIGRvbWFpbnMgYW5kIGZv
ciBvcmdhbml6YXRpb25hbCBkb21haW5zPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGFuZCB0aGVpciBzdWItZG9tYWlucyB3aXRoaW4gYSBz
aW5nbGUgb3JnYW5pemF0aW9uLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFu
ZCB0aGVpciBzdWItZG9tYWlucyB3aXRoaW4gYSBzaW5nbGUgb3JnYW5pemF0aW9uLjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVG8gZGV0ZXJtaW5lIHRoZSBvcmdhbml6YXRpb25hbCBk
b21haW4gZm9yIGEgbWVzc2FnZSB1bmRlcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIFRvIGRldGVybWluZSB0aGUgb3JnYW5pemF0aW9uYWwgZG9tYWluIGZvciBhIG1lc3NhZ2Ug
dW5kZXI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgZXZhbHVhdGlvbiwgYW5kIHRodXMgd2hlcmUgdG8gbG9vayBmb3IgYSBwb2xpY3kgc3Rh
dGVtZW50LCBETUFSQzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGV2YWx1YXRp
b24sIGFuZCB0aHVzIHdoZXJlIHRvIGxvb2sgZm9yIGEgcG9saWN5IHN0YXRlbWVudCwgRE1BUkM8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
bWFrZXMgdXNlIG9mIGEgUHVibGljIFN1ZmZpeCBMaXN0LiAgVGhlIHByb2Nlc3MgZm9yIGRvaW5n
IHRoaXMgY2FuIGJlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbWFrZXMgdXNl
IG9mIGEgUHVibGljIFN1ZmZpeCBMaXN0LiAgVGhlIHByb2Nlc3MgZm9yIGRvaW5nIHRoaXMgY2Fu
IGJlPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIGZvdW5kIGluIFNlY3Rpb24gMy4yIG9mIHRoZSBETUFSQyBzcGVjaWZpY2F0aW9uLjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGZvdW5kIGluIFNlY3Rpb24gMy4yIG9mIHRo
ZSBETUFSQyBzcGVjaWZpY2F0aW9uLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
PjxhIG5hbWU9ImRpZmYwMDEwIiAvPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgPHNwYW4gY2xhc3M9
ImRlbGV0ZSI+SW4gdGhlIGJhc2ljPC9zcGFuPiBETUFSQyA8c3BhbiBjbGFzcz0iZGVsZXRlIj5t
b2RlbCwgUFNEczwvc3Bhbj4gYXJlIG5vdCBvcmdhbml6YXRpb25hbCBkb21haW5zIGFuZCA8c3Bh
biBjbGFzcz0iZGVsZXRlIj5hcmU8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPiAgIERNQVJDIDxzcGFuIGNsYXNzPSJpbnNlcnQiPmFzIHNwZWNpZmllZCBwcmVzdW1lcyB0
aGF0IGRvbWFpbiBuYW1lcyBwcmVzZW50IGluIGEgUFNMPC9zcGFuPiBhcmU8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICB0aHVzIG5vdCBz
dWJqZWN0IHRvIERNQVJDIDxzcGFuIGNsYXNzPSJkZWxldGUiPnByb2Nlc3NpbmcuICBJbiBETUFS
QywgZG9tYWlucyBmYWxsIGludG88L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPiAgIG5vdCBvcmdhbml6YXRpb25hbCBkb21haW5zIGFuZCB0aHVzIG5vdCBzdWJqZWN0IHRv
IERNQVJDIDxzcGFuIGNsYXNzPSJpbnNlcnQiPnByb2Nlc3Npbmc7PC9zcGFuPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNz
PSJkZWxldGUiPiAgIG9uZSBvZiB0aHJlZSBjYXRlZ29yaWVzOjwvc3Bhbj4gb3JnYW5pemF0aW9u
YWwgZG9tYWlucywgc3ViLWRvbWFpbnMgb2Y8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgZG9tYWlucyBhcmUgZWl0aGVyPC9zcGFuPiBvcmdh
bml6YXRpb25hbCBkb21haW5zLCBzdWItZG9tYWlucyBvZjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIG9yZ2FuaXphdGlvbmFsIGRvbWFp
bnMsIG9yIDxzcGFuIGNsYXNzPSJkZWxldGUiPlBTRHMuICBBIFBTRDwvc3Bhbj4gY2FuIG9ubHkg
PHNwYW4gY2xhc3M9ImRlbGV0ZSI+cHVibGlzaCBETUFSQyBwb2xpY3k8L3NwYW4+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIG9yZ2FuaXphdGlvbmFsIGRvbWFpbnMsIG9yIDxz
cGFuIGNsYXNzPSJpbnNlcnQiPmxpc3RlZCBvbiBhIFBTTC4gIEZvciBkb21haW5zIGxpc3RlZCBp
biBhPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsYmxvY2siPiAgIGZvciA8c3BhbiBjbGFzcz0iZGVsZXRlIj5pdHNlbGYsIGFuZCBub3Q8L3Nw
YW4+IGZvciA8c3BhbiBjbGFzcz0iZGVsZXRlIj5hbnkgc3ViLWRvbWFpbnMgdW5kZXIgaXQuICBJ
biBzb21lIGNhc2VzLDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNw
YW4gY2xhc3M9Imluc2VydCI+ICAgUFNMLCBpLmUuLCBUTERzIGFuZCBkb21haW5zIHRoYXQgZXhp
c3QgYmV0d2VlbiBUTERzIGFuZCBvcmdhbml6YXRpb248L3NwYW4+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0
ZSI+ICAgdGhpcyBsaW1pdGF0aW9uPC9zcGFuPiBhbGxvd3MgZm9yIHRoZSBhYnVzZSBvZiBub24t
ZXhpc3RlbnQgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+b3JnYW5pemF0aW9uYWwtPC9zcGFuPjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBsZXZl
bCBkb21haW5zLCBwb2xpY3k8L3NwYW4+IGNhbiBvbmx5IDxzcGFuIGNsYXNzPSJpbnNlcnQiPmJl
IHB1Ymxpc2hlZDwvc3Bhbj4gZm9yIDxzcGFuIGNsYXNzPSJpbnNlcnQiPnRoZSBleGFjdCBkb21h
aW4uICBObzwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBsZXZlbDwvc3Bhbj4gZG9tYWlu
cyBhbmQgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+aGFtcGVyczwvc3Bhbj4gaWRlbnRpZmljYXRpb24g
b2YgZG9tYWluIGFidXNlIGluIGVtYWlsLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBtZXRob2QgaXMgYXZhaWxhYmxlPC9zcGFuPiBmb3Ig
PHNwYW4gY2xhc3M9Imluc2VydCI+dGhlc2UgZG9tYWlucyB0byBleHByZXNzIHBvbGljeSBvciBy
ZWNlaXZlPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3BhbiBjbGFz
cz0iaW5zZXJ0Ij4gICBmZWVkYmFjayByZXBvcnRpbmcgZm9yIHN1Yi1kb21haW5zLiAgVGhpcyBt
aXNzaW5nIG1ldGhvZDwvc3Bhbj4gYWxsb3dzIGZvcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmJsb2NrIj4gICB0aGUgYWJ1c2Ugb2Ygbm9uLWV4aXN0ZW50IDxzcGFuIGNsYXNzPSJpbnNlcnQi
Pm9yZ2FuaXphdGlvbmFsLWxldmVsPC9zcGFuPiBkb21haW5zIGFuZCA8c3BhbiBjbGFzcz0iaW5z
ZXJ0Ij5wcmV2ZW50czwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAg
aWRlbnRpZmljYXRpb24gb2YgZG9tYWluIGFidXNlIGluIGVtYWlsLjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgZXhwZXJpbWVudGFsIHVwZGF0
ZXMgdG8gdGhlIERNQVJDIGFuZCBQU0w8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBleHBlcmltZW50YWwgdXBkYXRlcyB0byB0aGUgRE1B
UkMgYW5kIFBTTDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBhbGdvcml0aG0gY2l0ZWQgYWJvdmUsIGluIGFuIGF0dGVtcHQgdG8gbWl0aWdh
dGUgdGhpcyBhYnVzZS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBhbGdvcml0
aG0gY2l0ZWQgYWJvdmUsIGluIGFuIGF0dGVtcHQgdG8gbWl0aWdhdGUgdGhpcyBhYnVzZS48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjEuMS4gIEV4YW1wbGU8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4xLjEuICBFeGFtcGxlPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQ+PGEgbmFtZT0iZGlmZjAwMTEiIC8+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBBcyBhbiBl
eGFtcGxlLCBpbWFnaW5lIGEgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+VG9wLUxldmVsIERvbWFpbiAo
VExEKSwgIi5leGFtcGxlIiwgdGhhdDwvc3Bhbj4gaGFzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyYmxvY2siPiAgIEFzIGFuIGV4YW1wbGUsIGltYWdpbmUgYSA8c3BhbiBjbGFzcz0iaW5zZXJ0
Ij5jb3VudHJ5IGNvZGUgVExEIChjY1RMRCkgd2hpY2g8L3NwYW4+IGhhcyBwdWJsaWM8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBwdWJs
aWMgc3ViZG9tYWlucyBmb3IgZ292ZXJubWVudCBhbmQgY29tbWVyY2lhbCB1c2UgKCIuZ292LmV4
YW1wbGUiPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIHN1YmRvbWFpbnMgZm9y
IGdvdmVybm1lbnQgYW5kIGNvbW1lcmNpYWwgdXNlICgiLmdvdi5leGFtcGxlIiBhbmQ8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBhbmQg
Ii5jb20uZXhhbXBsZSIpLiAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+VGhlPC9zcGFuPiBtYWludGFp
bmVyIG9mIDxzcGFuIGNsYXNzPSJkZWxldGUiPmEgbGlzdCBvZiBzdWNoIGEgUFNEPC9zcGFuPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAiLmNvbS5leGFtcGxlIikuICA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij5BIFBTTCB3aG9zZTwvc3Bhbj4gbWFpbnRhaW5lciA8c3BhbiBjbGFz
cz0iaW5zZXJ0Ij5pcyBhd2FyZTwvc3Bhbj4gb2YgPHNwYW4gY2xhc3M9Imluc2VydCI+dGhpcyBj
b3VudHJ5J3M8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQg
Y2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgc3RydWN0dXJlIHdvdWxkPC9z
cGFuPiBpbmNsdWRlIGVudHJpZXMgZm9yIGJvdGggb2YgdGhlc2UgPHNwYW4gY2xhc3M9ImRlbGV0
ZSI+c3ViLWRvbWFpbnMsPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48
c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBkb21haW4gc3RydWN0dXJld291bGQ8L3NwYW4+IGluY2x1
ZGUgZW50cmllcyBmb3IgYm90aCBvZiB0aGVzZSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5pbiB0aGUg
UFNMLDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICB0aGVyZWJ5PC9zcGFuPiBpbmRpY2F0
aW5nIHRoYXQgdGhleSBhcmUgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+UFNEcyw8L3NwYW4+IGJlbG93
IHdoaWNoIDxzcGFuIGNsYXNzPSJkZWxldGUiPm9yZ2FuaXphdGlvbmFsPC9zcGFuPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBpbmRpY2F0aW5nIHRoYXQgdGhleSBhcmUgPHNw
YW4gY2xhc3M9Imluc2VydCI+UFNEczwvc3Bhbj4gYmVsb3cgd2hpY2ggPHNwYW4gY2xhc3M9Imlu
c2VydCI+cmVnaXN0cmF0aW9uczwvc3Bhbj4gY2FuIDxzcGFuIGNsYXNzPSJpbnNlcnQiPm9jY3Vy
Ljwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj48c3BhbiBjbGFzcz0iZGVsZXRlIj4gICBkb21haW5zPC9zcGFuPiBjYW4gPHNwYW4g
Y2xhc3M9ImRlbGV0ZSI+YmUgcmVnaXN0ZXJlZC48L3NwYW4+ICBTdXBwb3NlIGZ1cnRoZXIgdGhh
dCB0aGVyZSBleGlzdHMgYTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBTdXBw
b3NlIGZ1cnRoZXIgdGhhdCB0aGVyZSBleGlzdHMgYSBkb21haW4gInRheC5nb3YuZXhhbXBsZSIs
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
ICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+bGVnaXRpbWF0ZTwvc3Bhbj4gZG9tYWluIDxzcGFuIGNs
YXNzPSJkZWxldGUiPmNhbGxlZDwvc3Bhbj4gInRheC5nb3YuZXhhbXBsZSIsIHJlZ2lzdGVyZWQg
d2l0aGluPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIHJlZ2lzdGVyZWQgd2l0
aGluIDxzcGFuIGNsYXNzPSJpbnNlcnQiPiIuZ292LmV4YW1wbGUiLCB0aGF0IGlzIHJlc3BvbnNp
YmxlIGZvciB0YXhhdGlvbiBpbjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4iLmdvdi5l
eGFtcGxlIi48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNs
YXNzPSJpbnNlcnQiPiAgIHRoaXMgaW1hZ2luZWQgY291bnRyeS48L3NwYW4+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICBIb3dldmVyLCBieSBleHBsb2l0aW5nIHRoZSB0eXBpY2FsbHkg
dW5hdXRoZW50aWNhdGVkIG5hdHVyZSBvZiBlbWFpbCw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBIb3dldmVyLCBieSBleHBsb2l0aW5nIHRoZSB0eXBpY2FsbHkgdW5hdXRoZW50
aWNhdGVkIG5hdHVyZSBvZiBlbWFpbCw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdGhlcmUgYXJlIHJlZ3VsYXIgbWFsaWNpb3VzIGNhbXBh
aWducyB0byBpbXBlcnNvbmF0ZSB0aGlzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgdGhlcmUgYXJlIHJlZ3VsYXIgbWFsaWNpb3VzIGNhbXBhaWducyB0byBpbXBlcnNvbmF0ZSB0
aGlzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIG9yZ2FuaXphdGlvbiB0aGF0IHVzZSBzaW1pbGFyLWxvb2tpbmcgKCJjb3VzaW4iKSBkb21h
aW5zIHN1Y2ggYXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBvcmdhbml6YXRp
b24gdGhhdCB1c2Ugc2ltaWxhci1sb29raW5nICgiY291c2luIikgZG9tYWlucyBzdWNoIGFzPC90
ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICJ0
NHguZ292LmV4YW1wbGUiLiAgU3VjaCBkb21haW5zIGFyZSBub3QgcmVnaXN0ZXJlZC48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAidDR4Lmdvdi5leGFtcGxlIi4gIFN1Y2ggZG9t
YWlucyBhcmUgbm90IHJlZ2lzdGVyZWQuPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBX
aXRoaW4gdGhlICIuZ292LmV4YW1wbGUiIHB1YmxpYyBzdWZmaXgsIHVzZSBvZiBETUFSQyBoYXMg
YmVlbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFdpdGhpbiB0aGUgIi5nb3Yu
ZXhhbXBsZSIgcHVibGljIHN1ZmZpeCwgdXNlIG9mIERNQVJDIGhhcyBiZWVuPC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG1hbmRhdGVkLCBz
byAiZ292LmV4YW1wbGUiIHB1Ymxpc2hlcyB0aGUgZm9sbG93aW5nIERNQVJDIEROUyByZWNvcmQ6
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbWFuZGF0ZWQsIHNvICJnb3YuZXhh
bXBsZSIgcHVibGlzaGVzIHRoZSBmb2xsb3dpbmcgRE1BUkMgRE5TIHJlY29yZDo8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIF9kbWFyYy5nb3YuZXhhbXBsZS4gSU4gVFhUICggInY9RE1B
UkMxOyBwPXJlamVjdDsgIjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIF9kbWFy
Yy5nb3YuZXhhbXBsZS4gSU4gVFhUICggInY9RE1BUkMxOyBwPXJlamVjdDsgIjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICJydWE9bWFpbHRvOmRtY0BkbWFyYy5zdmMuZ292LmV4YW1wbGUi
ICk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICJydWE9bWFpbHRvOmRtY0BkbWFyYy5zdmMuZ292LmV4YW1wbGUiICk8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoaXMgRE1BUkMgcmVjb3JkIHByb3ZpZGVzIHBvbGlj
eSBhbmQgYSByZXBvcnRpbmcgZGVzdGluYXRpb24gZm9yPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgVGhpcyBETUFSQyByZWNvcmQgcHJvdmlkZXMgcG9saWN5IGFuZCBhIHJlcG9y
dGluZyBkZXN0aW5hdGlvbiBmb3I8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDEyIiAvPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+ICAgbWFpbCBzZW50IGZyb20gQGdvdi5leGFtcGxlLiAgPHNwYW4gY2xhc3M9ImRl
bGV0ZSI+U2ltaWxhcmx5LCAidGF4Lmdvdi5leGFtcGxlIiB3aWxsIGhhdmU8L3NwYW4+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIG1haWwgc2VudCBmcm9tIEBnb3YuZXhhbXBs
ZS4gIEhvd2V2ZXIsIGR1ZSB0byBETUFSQydzIGN1cnJlbnQgbWV0aG9kPC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRl
bGV0ZSI+ICAgYSBETUFSQyByZWNvcmQgdGhhdCBzcGVjaWZpZXMgcG9saWN5IGZvciBtYWlsIHNl
bnQgZnJvbSBhZGRyZXNzZXM8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2si
PiAgIG9mIGRpc2NvdmVyaW5nIGFuZCBhcHBseWluZyBwb2xpY3kgYXQgdGhlIG9yZ2FuaXphdGlv
bmFsIGRvbWFpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIEB0YXguZ292LmV4YW1wbGUuPC9zcGFu
PiAgSG93ZXZlciwgZHVlIHRvIERNQVJDJ3MgY3VycmVudCBtZXRob2Qgb2Y8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+ICAgbGV2ZWwsIHRoZSBub24tZXhpc3RlbnQgb3JnYW5pemF0
aW9uYWwgZG9tYWluIG9mIEB0NHguZ292LmV4YW1wbGU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBkaXNjb3ZlcmluZyBhbmQgYXBwbHlp
bmcgcG9saWN5IGF0IHRoZSBvcmdhbml6YXRpb25hbCBkb21haW4gbGV2ZWwsPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIGRvZXMgbm90IGFuZCBjYW5ub3QgZmFsbCB1bmRlciBh
IERNQVJDIHBvbGljeS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj4gICB0aGUgbm9uLWV4aXN0ZW50IG9yZ2FuaXphdGlvbmFsIGRvbWFpbiBv
ZiBAdDR4Lmdvdi5leGFtcGxlIGRvZXMgbm90PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPiAgIGFuZCBjYW5ub3QgZmFsbCB1bmRlciBhIERNQVJDIHBvbGljeS48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBEZWZl
bnNpdmVseSByZWdpc3RlcmluZyBhbGwgdmFyaWFudHMgb2YgInRheCIgaXMgb2J2aW91c2x5IG5v
dCBhPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgRGVmZW5zaXZlbHkgcmVnaXN0
ZXJpbmcgYWxsIHZhcmlhbnRzIG9mICJ0YXgiIGlzIG9idmlvdXNseSBub3QgYTwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBzY2FsYWJsZSBz
dHJhdGVneS4gIFRoZSBpbnRlbnQgb2YgdGhpcyBzcGVjaWZpY2F0aW9uLCB0aGVyZWZvcmUsIGlz
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgc2NhbGFibGUgc3RyYXRlZ3kuICBU
aGUgaW50ZW50IG9mIHRoaXMgc3BlY2lmaWNhdGlvbiwgdGhlcmVmb3JlLCBpczwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0byBlbmhhbmNl
IHRoZSBETUFSQyBhbGdvcml0aG0gYnkgZW5hYmxpbmcgYW4gYWdlbnQgcmVjZWl2aW5nIHN1Y2gg
YTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRvIGVuaGFuY2UgdGhlIERNQVJD
IGFsZ29yaXRobSBieSBlbmFibGluZyBhbiBhZ2VudCByZWNlaXZpbmcgc3VjaCBhPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG1lc3NhZ2Ug
dG8gYmUgYWJsZSB0byBkZXRlcm1pbmUgdGhhdCBhIHJlbGV2YW50IHBvbGljeSBpcyBwcmVzZW50
IGF0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbWVzc2FnZSB0byBiZSBhYmxl
IHRvIGRldGVybWluZSB0aGF0IGEgcmVsZXZhbnQgcG9saWN5IGlzIHByZXNlbnQgYXQ8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgImdvdi5l
eGFtcGxlIiwgd2hpY2ggaXMgcHJlY2x1ZGVkIGJ5IHRoZSBjdXJyZW50IERNQVJDIGFsZ29yaXRo
bS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAiZ292LmV4YW1wbGUiLCB3aGlj
aCBpcyBwcmVjbHVkZWQgYnkgdGhlIGN1cnJlbnQgRE1BUkMgYWxnb3JpdGhtLjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+MS4yLiAgRGlzY3Vzc2lvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjEuMi4gIERpc2N1c3Npb248L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249
InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZD48YSBuYW1lPSJkaWZmMDAxMyIgLz48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIFRoaXMgZG9j
dW1lbnQgcHJvdmlkZXMgYSBzaW1wbGUgZXh0ZW5zaW9uIHRvIFtSRkM3NDg5XSB0byBhbGxvdzwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBUaGlzIGRvY3VtZW50IHByb3ZpZGVz
IGEgc2ltcGxlIGV4dGVuc2lvbiB0byA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5ETUFSQyA8L3NwYW4+
W1JGQzc0ODldIHRvIGFsbG93PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIG9wZXJhdG9ycyBvZiBQdWJsaWMgU3VmZml4IERvbWFpbnMgKFBT
RHMpIHRvOjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG9wZXJhdG9ycyBvZiBQ
dWJsaWMgU3VmZml4IERvbWFpbnMgKFBTRHMpIHRvOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgbyAgRXhwcmVzcyBwb2xpY3kgYXQgdGhlIGxldmVsIG9mIHRoZSBQU0QgdGhhdCBjb3Zl
cnMgYWxsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbyAgRXhwcmVzcyBwb2xp
Y3kgYXQgdGhlIGxldmVsIG9mIHRoZSBQU0QgdGhhdCBjb3ZlcnMgYWxsPC90ZD48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIG9yZ2FuaXphdGlv
bmFsIGRvbWFpbnMgdGhhdCBkbyBub3QgZXhwbGljaXRseSBwdWJsaXNoIERNQVJDPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgb3JnYW5pemF0aW9uYWwgZG9tYWlucyB0aGF0
IGRvIG5vdCBleHBsaWNpdGx5IHB1Ymxpc2ggRE1BUkM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgcmVjb3JkczwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIHJlY29yZHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIG8gIEV4dGVuZHMgdGhlIERNQVJDIHBvbGljeSBxdWVyeSBmdW5jdGlvbmFsaXR5IHRv
IGRldGVjdCBhbmQgcHJvY2VzczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG8g
IEV4dGVuZHMgdGhlIERNQVJDIHBvbGljeSBxdWVyeSBmdW5jdGlvbmFsaXR5IHRvIGRldGVjdCBh
bmQgcHJvY2VzczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICBzdWNoIGEgcG9saWN5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgICAgc3VjaCBhIHBvbGljeTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9w
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbyAg
RGVzY3JpYmVzIHJlY2VpdmVyIGZlZWRiYWNrIGZvciBzdWNoIHBvbGljaWVzPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgbyAgRGVzY3JpYmVzIHJlY2VpdmVyIGZlZWRiYWNrIGZv
ciBzdWNoIHBvbGljaWVzPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHIgYmdjb2xvcj0iZ3JheSIgPjx0ZD48L3RkPjx0aD48YSBuYW1l
PSJwYXJ0LWwzIiAvPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxlbT4gcGFn
ZSA0LCBsaW5lIDQ4PC9lbT48L3RoPjx0aD4gPC90aD48dGg+PGEgbmFtZT0icGFydC1yMyIgLz48
c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48ZW0+IHBhZ2UgNCwgbGluZSA0OTwv
ZW0+PC90aD48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIFRoaXMgZG9jdW1lbnQgYWxzbyBwcm92aWRlcyBhIG5ldyBETUFSQyB0YWcgdG8gaW5k
aWNhdGUgcmVxdWVzdGVkPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhpcyBk
b2N1bWVudCBhbHNvIHByb3ZpZGVzIGEgbmV3IERNQVJDIHRhZyB0byBpbmRpY2F0ZSByZXF1ZXN0
ZWQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgaGFuZGxpbmcgcG9saWN5IGZvciBub24tZXhpc3RlbnQgc3ViZG9tbWFpbnMuICBUaGlzIGlz
IHByb3ZpZGVkPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgaGFuZGxpbmcgcG9s
aWN5IGZvciBub24tZXhpc3RlbnQgc3ViZG9tbWFpbnMuICBUaGlzIGlzIHByb3ZpZGVkPC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHNwZWNp
ZmljYWxseSB0byBzdXBwb3J0IHBoYXNlZCBkZXBsb3ltZW50IG9mIFBTRCBETUFSQywgYnV0IGlz
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgc3BlY2lmaWNhbGx5IHRvIHN1cHBv
cnQgcGhhc2VkIGRlcGxveW1lbnQgb2YgUFNEIERNQVJDLCBidXQgaXM8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZXhwZWN0ZWQgdG8gYmUg
dXNlZnVsIG1vcmUgZ2VuZXJhbGx5LiAgVW5kZXNpcmVkIHJlamVjdGlvbiByaXNrcyBmb3I8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBleHBlY3RlZCB0byBiZSB1c2VmdWwgbW9y
ZSBnZW5lcmFsbHkuICBVbmRlc2lyZWQgcmVqZWN0aW9uIHJpc2tzIGZvcjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBtYWlsIHB1cnBvcnRp
bmcgdG8gYmUgZnJvbSBkb21haW5zIHRoYXQgZG8gbm90IGV4aXN0IGFyZTwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIG1haWwgcHVycG9ydGluZyB0byBiZSBmcm9tIGRvbWFpbnMg
dGhhdCBkbyBub3QgZXhpc3QgYXJlPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHN1YnN0YW50aWFsbHkgbG93ZXIgdGhhbiBmb3IgdGhvc2Ug
dGhhdCBkbywgc28gdGhlIG9wZXJhdGlvbmFsIHJpc2s8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBzdWJzdGFudGlhbGx5IGxvd2VyIHRoYW4gZm9yIHRob3NlIHRoYXQgZG8sIHNv
IHRoZSBvcGVyYXRpb25hbCByaXNrPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG9mIHJlcXVlc3RpbmcgaGFyc2ggcG9saWN5IHRyZWF0bWVu
dCAoZS5nLiByZWplY3QpIGlzIGxvd2VyLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIG9mIHJlcXVlc3RpbmcgaGFyc2ggcG9saWN5IHRyZWF0bWVudCAoZS5nLiByZWplY3QpIGlz
IGxvd2VyLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgQXMgYW4gYWRkaXRpb25hbCBi
ZW5lZml0LCB0aGUgUFNEIERNQVJDIGV4dGVuc2lvbiBjbGFyaWZpZXMgZXhpc3Rpbmc8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBBcyBhbiBhZGRpdGlvbmFsIGJlbmVmaXQsIHRo
ZSBQU0QgRE1BUkMgZXh0ZW5zaW9uIGNsYXJpZmllcyBleGlzdGluZzwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQ+PGEgbmFtZT0iZGlm
ZjAwMTQiIC8+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICByZXF1aXJlbWVudHMuICBCYXNlZCBvbiB0
aGUgcmVxdWlyZW1lbnRzIG9mIFtSRkM3NDg5XSwgRE1BUkMgc2hvdWxkPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyYmxvY2siPiAgIHJlcXVpcmVtZW50cy4gIEJhc2VkIG9uIHRoZSByZXF1aXJl
bWVudHMgb2YgPHNwYW4gY2xhc3M9Imluc2VydCI+RE1BUkM8L3NwYW4+IFtSRkM3NDg5XSwgRE1B
UkM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2Nr
Ij4gICBmdW5jdGlvbiBhYm92ZSB0aGUgb3JnYW5pemF0aW9uYWwgbGV2ZWwgZm9yIGV4YWN0IGRv
bWFpbiBtYXRjaGVzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIHNob3VsZCBm
dW5jdGlvbiBhYm92ZSB0aGUgb3JnYW5pemF0aW9uYWwgbGV2ZWwgZm9yIGV4YWN0IGRvbWFpbjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAg
IChpLmUuIGlmIGEgRE1BUkMgcmVjb3JkIHdlcmUgcHVibGlzaGVkIGZvciAnZXhhbXBsZScsIHRo
ZW4gbWFpbCBmcm9tPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIG1hdGNoZXMg
KGkuZS4gaWYgYSBETUFSQyByZWNvcmQgd2VyZSBwdWJsaXNoZWQgZm9yICdleGFtcGxlJywgdGhl
bjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PiAgIGV4YW1wbGVAZXhhbXBsZSBzaG91bGQgYmUgc3ViamVjdCB0byBETUFSQyBwcm9jZXNzaW5n
KS4gIFRlc3RpbmcgaGFkPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIG1haWwg
ZnJvbSBleGFtcGxlQGV4YW1wbGUgc2hvdWxkIGJlIHN1YmplY3QgdG8gRE1BUkMgcHJvY2Vzc2lu
ZykuPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+ICAgcmV2ZWFsZWQgdGhhdCB0aGlzIGlzIG5vdCBjb25zaXN0ZW50bHkgYXBwbGllZCBpbiBk
aWZmZXJlbnQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PiAgIGltcGxlbWVudGF0aW9ucy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAg
VGVzdGluZyBoYWQgcmV2ZWFsZWQgdGhhdCB0aGlzIGlzIG5vdCBjb25zaXN0ZW50bHkgYXBwbGll
ZCBpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBkaWZmZXJlbnQgaW1wbGVt
ZW50YXRpb25zLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhlcmUgYXJlIHR3byB0
eXBlcyBvZiBQdWJsaWMgU3VmZml4IE9wZXJhdG9ycyAoUFNPcykgZm9yIHdoaWNoIHRoaXM8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGVyZSBhcmUgdHdvIHR5cGVzIG9mIFB1
YmxpYyBTdWZmaXggT3BlcmF0b3JzIChQU09zKSBmb3Igd2hpY2ggdGhpczwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBleHRlbnNpb24gd291
bGQgYmUgdXNlZnVsIGFuZCBhcHByb3ByaWF0ZTo8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBleHRlbnNpb24gd291bGQgYmUgdXNlZnVsIGFuZCBhcHByb3ByaWF0ZTo8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIG8gIEJyYW5kZWQgUFNEcyAoZS5nLiwgIi5nb29nbGUi
KTogVGhlc2UgZG9tYWlucyBhcmUgZWZmZWN0aXZlbHk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBvICBCcmFuZGVkIFBTRHMgKGUuZy4sICIuZ29vZ2xlIik6IFRoZXNlIGRvbWFp
bnMgYXJlIGVmZmVjdGl2ZWx5PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAxNSIgLz48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJs
YmxvY2siPiAgICAgIE9yZ2FuaXphdGlvbmFsIERvbWFpbnMgYXMgZGlzY3Vzc2VkIGluIFtSRkM3
NDg5XS4gIFRoZXkgY29udHJvbDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAg
ICBPcmdhbml6YXRpb25hbCBEb21haW5zIGFzIGRpc2N1c3NlZCBpbiA8c3BhbiBjbGFzcz0iaW5z
ZXJ0Ij5ETUFSQzwvc3Bhbj4gW1JGQzc0ODldLiAgVGhleTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgIGFsbCBzdWJkb21haW5zIG9m
IHRoZSB0cmVlLiAgVGhlc2UgYXJlIGVmZmVjdGl2ZWx5IHByaXZhdGU8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJibG9jayI+ICAgICAgY29udHJvbCBhbGwgc3ViZG9tYWlucyBvZiB0aGUgdHJl
ZS4gIFRoZXNlIGFyZSBlZmZlY3RpdmVseSBwcml2YXRlPC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGRvbWFpbnMsIGJ1dCBsaXN0ZWQg
aW4gdGhlIFB1YmxpYyBTdWZmaXggTGlzdC4gIFRoZXkgYXJlIHRyZWF0ZWQ8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBkb21haW5zLCBidXQgbGlzdGVkIGluIHRoZSBQdWJs
aWMgU3VmZml4IExpc3QuICBUaGV5IGFyZSB0cmVhdGVkPC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGFzIFB1YmxpYyBmb3IgRE1BUkMg
cHVycG9zZXMuICBUaGV5IHJlcXVpcmUgdGhlIHNhbWUgcHJvdGVjdGlvbnM8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBhcyBQdWJsaWMgZm9yIERNQVJDIHB1cnBvc2VzLiAg
VGhleSByZXF1aXJlIHRoZSBzYW1lIHByb3RlY3Rpb25zPC90ZD48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGFzIERNQVJDIE9yZ2FuaXphdGlv
bmFsIERvbWFpbnMsIGJ1dCBhcmUgY3VycmVudGx5IHVuYWJsZSB0bzwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgICAgIGFzIERNQVJDIE9yZ2FuaXphdGlvbmFsIERvbWFpbnMsIGJ1
dCBhcmUgY3VycmVudGx5IHVuYWJsZSB0bzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBiZW5lZml0IGZyb20gRE1BUkMuPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgYmVuZWZpdCBmcm9tIERNQVJDLjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbyAgTXVsdGktb3JnYW5pemF0aW9uIFBTRHMgdGhhdCBy
ZXF1aXJlIERNQVJDIHVzYWdlIChlLmcuLCAiLmJhbmsiKTo8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBvICBNdWx0aS1vcmdhbml6YXRpb24gUFNEcyB0aGF0IHJlcXVpcmUgRE1B
UkMgdXNhZ2UgKGUuZy4sICIuYmFuayIpOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBCZWNhdXNlIGV4aXN0aW5nIE9yZ2FuaXphdGlv
bmFsIERvbWFpbnMgdXNpbmcgdGhpcyBQU0QgaGF2ZSB0aGVpcjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgICAgIEJlY2F1c2UgZXhpc3RpbmcgT3JnYW5pemF0aW9uYWwgRG9tYWlu
cyB1c2luZyB0aGlzIFBTRCBoYXZlIHRoZWlyPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIG93biBETUFSQyBwb2xpY3ksIHRoZSBhcHBs
aWNhYmlsaXR5IG9mIHRoaXMgZXh0ZW5zaW9uIGlzIGZvciBub24tPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgb3duIERNQVJDIHBvbGljeSwgdGhlIGFwcGxpY2FiaWxpdHkg
b2YgdGhpcyBleHRlbnNpb24gaXMgZm9yIG5vbi08L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgZXhpc3RlbnQgZG9tYWlucy4gIFRoZSBl
eHRlbnNpb24gYWxsb3dzIHRoZSBicmFuZCBwcm90ZWN0aW9uPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgZXhpc3RlbnQgZG9tYWlucy4gIFRoZSBleHRlbnNpb24gYWxsb3dz
IHRoZSBicmFuZCBwcm90ZWN0aW9uPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGJlbmVmaXRzIG9mIERNQVJDIHRvIGV4dGVuZCB0byB0
aGUgZW50aXJlIFBTRCwgaW5jbHVkaW5nIGNvdXNpbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgICAgIGJlbmVmaXRzIG9mIERNQVJDIHRvIGV4dGVuZCB0byB0aGUgZW50aXJlIFBT
RCwgaW5jbHVkaW5nIGNvdXNpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBkb21haW5zIG9mIHJlZ2lzdGVyZWQgb3JnYW5pemF0aW9u
cy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBkb21haW5zIG9mIHJlZ2lz
dGVyZWQgb3JnYW5pemF0aW9ucy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIER1ZSB0
byB0aGUgZGVzaWduIG9mIERNQVJDIGFuZCB0aGUgbmF0dXJlIG9mIHRoZSBJbnRlcm5ldCBlbWFp
bDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIER1ZSB0byB0aGUgZGVzaWduIG9m
IERNQVJDIGFuZCB0aGUgbmF0dXJlIG9mIHRoZSBJbnRlcm5ldCBlbWFpbDwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhcmNoaXRlY3R1cmUg
W1JGQzU1OThdLCB0aGVyZSBhcmUgaW50ZXJvcGVyYWJpbGl0eSBpc3N1ZXMgYXNzb2NpYXRlZDwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFyY2hpdGVjdHVyZSBbUkZDNTU5OF0s
IHRoZXJlIGFyZSBpbnRlcm9wZXJhYmlsaXR5IGlzc3VlcyBhc3NvY2lhdGVkPC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZD48YSBuYW1l
PSJkaWZmMDAxNiIgLz48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIHdpdGggRE1BUkMgZGVwbG95bWVu
dC4gIFRoZXNlIGFyZSBkaXNjdXNzZWQgaW4gSW50ZXJvcGVyYWJpbGl0eTwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmJsb2NrIj4gICB3aXRoIERNQVJDIDxzcGFuIGNsYXNzPSJpbnNlcnQiPltS
RkM3NDg5XTwvc3Bhbj4gZGVwbG95bWVudC4gIFRoZXNlIGFyZSBkaXNjdXNzZWQgaW48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBJc3N1
ZXMgYmV0d2VlbiBETUFSQyBhbmQgSW5kaXJlY3QgRW1haWwgRmxvd3MgW1JGQzc5NjBdLiAgVGhl
c2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgSW50ZXJvcGVyYWJpbGl0eSBJ
c3N1ZXMgYmV0d2VlbiBETUFSQyBhbmQgSW5kaXJlY3QgRW1haWwgRmxvd3M8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBpc3N1ZXMgYXJl
IG5vdCB0eXBpY2FsbHkgYXBwbGljYWJsZSB0byBQU0RzLCBzaW5jZSB0aGV5IChlLmcuLCB0aGU8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgW1JGQzc5NjBdLiAgVGhlc2UgaXNz
dWVzIGFyZSBub3QgdHlwaWNhbGx5IGFwcGxpY2FibGUgdG8gUFNEcywgc2luY2U8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAiLmdvdi5l
eGFtcGxlIiB1c2VkIGFib3ZlKSBkbyBub3QgdHlwaWNhbGx5IHNlbmQgbWFpbC48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgdGhleSAoZS5nLiwgdGhlICIuZ292LmV4YW1wbGUi
IHVzZWQgYWJvdmUpIGRvIG5vdCB0eXBpY2FsbHkgc2VuZDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmJsb2NrIj4gICBtYWlsLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+Mi4gIFRlcm1p
bm9sb2d5IGFuZCBEZWZpbml0aW9uczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjIu
ICBUZXJtaW5vbG9neSBhbmQgRGVmaW5pdGlvbnM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIFRoaXMgc2VjdGlvbiBkZWZpbmVzIHRlcm1zIHVzZWQgaW4gdGhlIHJlc3Qgb2YgdGhlIGRv
Y3VtZW50LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoaXMgc2VjdGlvbiBk
ZWZpbmVzIHRlcm1zIHVzZWQgaW4gdGhlIHJlc3Qgb2YgdGhlIGRvY3VtZW50LjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+Mi4xLiAgQ29udmVudGlvbnMgVXNlZCBpbiBUaGlzIERvY3VtZW50
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+Mi4xLiAgQ29udmVudGlvbnMgVXNlZCBp
biBUaGlzIERvY3VtZW50PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGUga2V5IHdv
cmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNIQUxMIE5PVCIs
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhlIGtleSB3b3JkcyAiTVVTVCIs
ICJNVVNUIE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLDwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAiU0hPVUxEIiwg
IlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTk9UIFJFQ09NTUVOREVEIiwgIk1BWSIsIGFu
ZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICJTSE9VTEQiLCAiU0hPVUxEIE5P
VCIsICJSRUNPTU1FTkRFRCIsICJOT1QgUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICJPUFRJT05B
TCIgaW4gdGhpcyBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGlu
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgIk9QVElPTkFMIiBpbiB0aGlzIGRv
Y3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQgaW48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBiZ2NvbG9y
PSJncmF5IiA+PHRkPjwvdGQ+PHRoPjxhIG5hbWU9InBhcnQtbDQiIC8+PHNtYWxsPnNraXBwaW5n
IHRvIGNoYW5nZSBhdDwvc21hbGw+PGVtPiBwYWdlIDYsIGxpbmUgMTY8L2VtPjwvdGg+PHRoPiA8
L3RoPjx0aD48YSBuYW1lPSJwYXJ0LXI0IiAvPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8
L3NtYWxsPjxlbT4gcGFnZSA2LCBsaW5lIDE3PC9lbT48L3RoPjx0ZD48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICB0cmVlIGF0IHdoaWNoIHRvIHJlZ2lzdGVyIGRvbWFpbiBuYW1lcyAib3duZWQiIGJ5IGlu
ZGVwZW5kZW50PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgdHJlZSBhdCB3aGlj
aCB0byByZWdpc3RlciBkb21haW4gbmFtZXMgIm93bmVkIiBieSBpbmRlcGVuZGVudDwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBvcmdhbml6
YXRpb25zLiAgUmVhbC13b3JsZCBleGFtcGxlcyBhcmUgIi5jb20iLCAiLm9yZyIsICIudXMiLCBh
bmQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBvcmdhbml6YXRpb25zLiAgUmVh
bC13b3JsZCBleGFtcGxlcyBhcmUgIi5jb20iLCAiLm9yZyIsICIudXMiLCBhbmQ8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgIi5nb3YudWsi
LiAgTmFtZXMgYXQgd2hpY2ggc3VjaCByZWdpc3RyYXRpb25zIG9jY3VyIGFyZSBjYWxsZWQgUHVi
bGljPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgIi5nb3YudWsiLiAgTmFtZXMg
YXQgd2hpY2ggc3VjaCByZWdpc3RyYXRpb25zIG9jY3VyIGFyZSBjYWxsZWQgUHVibGljPC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFN1ZmZp
eCBEb21haW5zIChQU0RzKSwgYW5kIGEgcmVnaXN0cmF0aW9uIGNvbnNpc3RzIG9mIGEgbGFiZWw8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBTdWZmaXggRG9tYWlucyAoUFNEcyks
IGFuZCBhIHJlZ2lzdHJhdGlvbiBjb25zaXN0cyBvZiBhIGxhYmVsPC90ZD48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
IiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHNlbGVjdGVkIGJ5IHRoZSBy
ZWdpc3RyYW50IHRvIHdoaWNoIGEgZGVzaXJhYmxlIFBTRCBpcyBhcHBlbmRlZC4gIEZvcjwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHNlbGVjdGVkIGJ5IHRoZSByZWdpc3RyYW50
IHRvIHdoaWNoIGEgZGVzaXJhYmxlIFBTRCBpcyBhcHBlbmRlZC4gIEZvcjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBleGFtcGxlLCAiaWV0
Zi5vcmciIGlzIGEgcmVnaXN0ZXJlZCBkb21haW4gbmFtZSwgYW5kICIub3JnIiBpcyBpdHM8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBleGFtcGxlLCAiaWV0Zi5vcmciIGlzIGEg
cmVnaXN0ZXJlZCBkb21haW4gbmFtZSwgYW5kICIub3JnIiBpcyBpdHM8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgUFNELjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFBTRC48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjIuMy4gIE9yZ2FuaXphdGlvbmFsIERvbWFpbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPjIuMy4gIE9yZ2FuaXphdGlvbmFsIERvbWFpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZh
bGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkPjxhIG5hbWU9ImRpZmYwMDE3IiAvPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgVGhl
IHRlcm0gT3JnYW5pemF0aW9uYWwgRG9tYWlucyBpcyBkZWZpbmVkIGluIFtSRkM3NDg5XSBTZWN0
aW9uIDMuMi48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgVGhlIHRlcm0gT3Jn
YW5pemF0aW9uYWwgRG9tYWlucyBpcyBkZWZpbmVkIGluIDxzcGFuIGNsYXNzPSJpbnNlcnQiPkRN
QVJDPC9zcGFuPiBbUkZDNzQ4OV08L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAg
U2VjdGlvbiAzLjIuPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4yLjQuICBMb25nZXN0IFBT
RDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjIuNC4gIExvbmdlc3QgUFNEPC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGUgbG9uZ2VzdCBQU0QgaXMgdGhlIE9yZ2FuaXph
dGlvbmFsIERvbWFpbiB3aXRoIG9uZSBsYWJlbCByZW1vdmVkLjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIFRoZSBsb25nZXN0IFBTRCBpcyB0aGUgT3JnYW5pemF0aW9uYWwgRG9t
YWluIHdpdGggb25lIGxhYmVsIHJlbW92ZWQuPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWdu
PSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRv
cCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEl0IG5hbWVzIHRoZSBpbW1lZGlhdGUgcGFyZW50
IG5vZGUgb2YgdGhlIE9yZ2FuaXphdGlvbmFsIERvbWFpbiBpbjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIEl0IG5hbWVzIHRoZSBpbW1lZGlhdGUgcGFyZW50IG5vZGUgb2YgdGhl
IE9yZ2FuaXphdGlvbmFsIERvbWFpbiBpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0aGUgRE5TIG5hbWVzcGFjZSB0cmVlLjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRoZSBETlMgbmFtZXNwYWNlIHRyZWUuPC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3Ai
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4yLjUuICBQdWJsaWMgU3VmZml4IE9wZXJhdG9yIChQU08p
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+Mi41LiAgUHVibGljIFN1ZmZpeCBPcGVy
YXRvciAoUFNPKTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgQSBQdWJsaWMgU3VmZml4
IE9wZXJhdG9yIGlzIGFuIG9yZ2FuaXphdGlvbiB3aGljaCBtYW5hZ2VzIG9wZXJhdGlvbnM8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBBIFB1YmxpYyBTdWZmaXggT3BlcmF0b3Ig
aXMgYW4gb3JnYW5pemF0aW9uIHdoaWNoIG1hbmFnZXMgb3BlcmF0aW9uczwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGJnY29sb3I9
ImdyYXkiID48dGQ+PC90ZD48dGg+PGEgbmFtZT0icGFydC1sNSIgLz48c21hbGw+c2tpcHBpbmcg
dG8gY2hhbmdlIGF0PC9zbWFsbD48ZW0+IHBhZ2UgMTEsIGxpbmUgNDY8L2VtPjwvdGg+PHRoPiA8
L3RoPjx0aD48YSBuYW1lPSJwYXJ0LXI1IiAvPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8
L3NtYWxsPjxlbT4gcGFnZSAxMSwgbGluZSA0NjwvZW0+PC90aD48dGQ+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgICAgICAgICAgICBET0kgMTAuMTc0ODcvUkZDNjk3MywgSnVseSAyMDEzLDwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgRE9JIDEwLjE3NDg3L1JGQzY5
NzMsIEp1bHkgMjAxMyw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAmbHQ7aHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcv
aW5mby9yZmM2OTczJmd0Oy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAg
ICAgICAgICZsdDtodHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzY5NzMmZ3Q7Ljwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW1JGQzc2MjRdICBCYXJuZXMsIFIuLCBTY2hu
ZWllciwgQi4sIEplbm5pbmdzLCBDLiwgSGFyZGllLCBULiw8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBbUkZDNzYyNF0gIEJhcm5lcywgUi4sIFNjaG5laWVyLCBCLiwgSmVubmlu
Z3MsIEMuLCBIYXJkaWUsIFQuLDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIFRyYW1tZWxsLCBCLiwgSHVpdGVtYSwgQy4s
IGFuZCBELiBCb3JrbWFubiw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAg
ICAgICAgIFRyYW1tZWxsLCBCLiwgSHVpdGVtYSwgQy4sIGFuZCBELiBCb3JrbWFubiw8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAg
ICAgICAiQ29uZmlkZW50aWFsaXR5IGluIHRoZSBGYWNlIG9mIFBlcnZhc2l2ZSBTdXJ2ZWlsbGFu
Y2U6IEE8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICJDb25m
aWRlbnRpYWxpdHkgaW4gdGhlIEZhY2Ugb2YgUGVydmFzaXZlIFN1cnZlaWxsYW5jZTogQTwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAg
ICAgICAgIFRocmVhdCBNb2RlbCBhbmQgUHJvYmxlbSBTdGF0ZW1lbnQiLCBSRkMgNzYyNCw8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIFRocmVhdCBNb2RlbCBh
bmQgUHJvYmxlbSBTdGF0ZW1lbnQiLCBSRkMgNzYyNCw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBET0kgMTAuMTc0ODcv
UkZDNzYyNCwgQXVndXN0IDIwMTUsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
ICAgICAgICAgICBET0kgMTAuMTc0ODcvUkZDNzYyNCwgQXVndXN0IDIwMTUsPC90ZD48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAg
Jmx0O2h0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNzYyNCZndDsuPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAmbHQ7aHR0cHM6Ly93d3cucmZj
LWVkaXRvci5vcmcvaW5mby9yZmM3NjI0Jmd0Oy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxp
Z249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0i
dG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZD48YSBuYW1lPSJkaWZmMDAxOCIgLz48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIFtSRkM3
OTYwXSAgTWFydGluLCBGLiwgRWQuLCBMZWFyLCBFLiwgRWQuLCBEcmFlZ2VuPHNwYW4gY2xhc3M9
ImRlbGV0ZSI+LCBULiwgRWQ8L3NwYW4+LiwgWndpY2t5LDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmJsb2NrIj4gICBbUkZDNzk2MF0gIE1hcnRpbiwgRi4sIEVkLiwgTGVhciwgRS4sIEVkLiwg
RHJhZWdlbjxzcGFuIGNsYXNzPSJpbnNlcnQiPi4gRWQuLCBUPC9zcGFuPi4sIFp3aWNreSw8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAg
ICAgICAgICBFLiwgRWQuLCBhbmQgSy4gQW5kZXJzZW4sIEVkLiwgIkludGVyb3BlcmFiaWxpdHkg
SXNzdWVzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICBFLiwg
RWQuLCBhbmQgSy4gQW5kZXJzZW4sIEVkLiwgIkludGVyb3BlcmFiaWxpdHkgSXNzdWVzPC90ZD48
dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAg
ICAgICAgYmV0d2VlbiBEb21haW4tYmFzZWQgTWVzc2FnZSBBdXRoZW50aWNhdGlvbiwgUmVwb3J0
aW5nLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgYmV0d2Vl
biBEb21haW4tYmFzZWQgTWVzc2FnZSBBdXRoZW50aWNhdGlvbiwgUmVwb3J0aW5nLDwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAg
ICAgIGFuZCBDb25mb3JtYW5jZSAoRE1BUkMpIGFuZCBJbmRpcmVjdCBFbWFpbCBGbG93cyIsPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICBhbmQgQ29uZm9ybWFu
Y2UgKERNQVJDKSBhbmQgSW5kaXJlY3QgRW1haWwgRmxvd3MiLDwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iIHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIg
dmFsaWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIFJGQyA3OTYw
LCBET0kgMTAuMTc0ODcvUkZDNzk2MCwgU2VwdGVtYmVyIDIwMTYsPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICBSRkMgNzk2MCwgRE9JIDEwLjE3NDg3L1JGQzc5
NjAsIFNlcHRlbWJlciAyMDE2LDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGlnbj0idG9wIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICZsdDtodHRwczovL3d3dy5yZmMtZWRpdG9y
Lm9yZy9pbmZvL3JmYzc5NjAmZ3Q7LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
ICAgICAgICAgICAgJmx0O2h0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNzk2MCZn
dDsuPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyIgdmFs
aWduPSJ0b3AiPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBbUkZDODAyMF0gIEJvcnR6bWV5ZXIs
IFMuIGFuZCBTLiBIdXF1ZSwgIk5YRE9NQUlOOiBUaGVyZSBSZWFsbHkgSXM8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBbUkZDODAyMF0gIEJvcnR6bWV5ZXIsIFMuIGFuZCBTLiBI
dXF1ZSwgIk5YRE9NQUlOOiBUaGVyZSBSZWFsbHkgSXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIiB2
YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iIHZhbGln
bj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICBOb3RoaW5nIFVuZGVy
bmVhdGgiLCBSRkMgODAyMCwgRE9JIDEwLjE3NDg3L1JGQzgwMjAsPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICBOb3RoaW5nIFVuZGVybmVhdGgiLCBSRkMgODAy
MCwgRE9JIDEwLjE3NDg3L1JGQzgwMjAsPC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0
b3AiPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIiB2YWxpZ249InRvcCI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgTm92ZW1iZXIgMjAxNiwgJmx0O2h0
dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjODAyMCZndDsuPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICBOb3ZlbWJlciAyMDE2LCAmbHQ7aHR0cHM6
Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM4MDIwJmd0Oy48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIiB2YWxpZ249InRvcCI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
IHZhbGlnbj0idG9wIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyIgdmFsaWduPSJ0b3AiPjwvdGQ+PC90
cj4KCiAgICAgPHRyPjx0ZD48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQ+PC90ZD48L3RyPgogICAgIDx0ciBiZ2NvbG9yPSJncmF5
Ij48dGggY29sc3Bhbj0iNSIgYWxpZ249ImNlbnRlciI+PGEgbmFtZT0iZW5kIj4mbmJzcDtFbmQg
b2YgY2hhbmdlcy4gMTggY2hhbmdlIGJsb2Nrcy4mbmJzcDs8L2E+PC90aD48L3RyPgogICAgIDx0
ciBjbGFzcz0ic3RhdHMiPjx0ZD48L3RkPjx0aD48aT41NiBsaW5lcyBjaGFuZ2VkIG9yIGRlbGV0
ZWQ8L2k+PC90aD48dGg+PGk+IDwvaT48L3RoPjx0aD48aT42NCBsaW5lcyBjaGFuZ2VkIG9yIGFk
ZGVkPC9pPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICA8dHI+PHRkIGNvbHNwYW49IjUiIGFsaWdu
PSJjZW50ZXIiIGNsYXNzPSJzbWFsbCI+PGJyLz5UaGlzIGh0bWwgZGlmZiB3YXMgcHJvZHVjZWQg
YnkgcmZjZGlmZiAxLjM0LiBUaGUgbGF0ZXN0IHZlcnNpb24gaXMgYXZhaWxhYmxlIGZyb20gPGEg
aHJlZj0iaHR0cDovL3d3dy50b29scy5pZXRmLm9yZy90b29scy9yZmNkaWZmLyIgPmh0dHA6Ly90
b29scy5pZXRmLm9yZy90b29scy9yZmNkaWZmLzwvYT4gPC90ZD48L3RyPgogICA8L3RhYmxlPgog
ICA8L2JvZHk+CiAgIDwvaHRtbD4K
--000000000000e128d205bc6cef14--

