
From nobody Wed Jun  2 20:45:52 2021
Return-Path: <superuser@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D83783A2749 for <dmarc@ietfa.amsl.com>; Wed,  2 Jun 2021 20:45:50 -0700 (PDT)
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 tCvaXGeuWTdC for <dmarc@ietfa.amsl.com>; Wed,  2 Jun 2021 20:45:46 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B6113A2748 for <dmarc@ietf.org>; Wed,  2 Jun 2021 20:45:46 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id z15so2280140vsn.13 for <dmarc@ietf.org>; Wed, 02 Jun 2021 20:45:46 -0700 (PDT)
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=uQYkA6yV4LJu076VpUDQBlSiAj8sdzraTXoBYkyv2I4=; b=a5SD2myWYOdM3spdBwfnWAV9rlKIcTq23W56AGV5zhX8gNr2NMYej6irdD71rfEoun HZqIQpK3G0JHXlMrUcnZdn20t74tZ3vcAK3QHnT4xH35ok4udccG2hEP2+Ig/sH6Zmlq a5WrzHbIrDXfIJDy744XMWPgkY+EZecySc1CboM2BCSGMzuEXosAF9jFH2/pCI9EQowF NtA1Q2Jwh/oWk6cjDyXIKC4rOmHEQD0XkyrrEVz/8yY3Kel99w5wSeGRuwqskrqzQCRQ /MkL4Q7h8i5cBGv/GFNjTeeEXW9W+kJ+NNIdstHiDk3SyR+4dVxjvkdCJ9eKCi4Gjn+Z pZCQ==
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=uQYkA6yV4LJu076VpUDQBlSiAj8sdzraTXoBYkyv2I4=; b=jsswZQHCjbcW09FVt2pKNX5YWalVqD2lR764BLPFUWpjTh/SysepvyjJjXZ+bt6lSd aDTjhD5BJMz/mZmISEKHEyZXMEaPbUhdjrpDmNTFFysgHPBSxyN9q6Davbhz0JLs2uxu 7PJ3OQrbEhA/TaeXs1QkIWtNJQzuLH0l+X02o1c9K3LRTyBYAwlCahaO3V+hFdc6IGDh z4Muux5QawzqDK2LToUVAVNPvfjVVJmWLPnm9xvuYMeKjzujSxFKuSbsrfgWQ/HPv5zh hvZ8d24mTwp447hezv6/i6FLSccneU/Tn9Ygy8OCavofhetGXmdi5RQg/JMh4Z+pmfiZ 5Ekw==
X-Gm-Message-State: AOAM532iIkQuxd/g7EyXzah3x5JJ1Mez/mVM5ZUGYR4KZYgU1X6ng5PA ygTV/76yIqToPn5qbxHTvRuooJSatnICLRKlXoa2jBfZ79/Nqg==
X-Google-Smtp-Source: ABdhPJwNf45sIt6jl9vbvdPYt6nhNmK6L+5wQ/V/x2wEGc3LCv3eOcgOuNQuyOjM48RKYz+j8k8J+wE3SzNbw9LPKxY=
X-Received: by 2002:a67:de17:: with SMTP id q23mr12067003vsk.54.1622691944755;  Wed, 02 Jun 2021 20:45:44 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8muJPMFY7LXmz9RnCTHP5emwn=bspDtP8_KZNza1oAc6A@mail.gmail.com> <196e1a7d-95f0-9d44-d4c8-8889e508f62c@tana.it>
In-Reply-To: <196e1a7d-95f0-9d44-d4c8-8889e508f62c@tana.it>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 2 Jun 2021 20:45:33 -0700
Message-ID: <CAL0qLwbdLpjiv7Hb3FfNhtq2VxBnz6PwrrmWZzE8wzpDRR-QZw@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f274e405c3d4680f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/nFIu_-lhg4ezLysrq9EFu5IOm0U>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #47 (Removal of "pct" tag) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 03 Jun 2021 03:45:51 -0000

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

I don't understand what "demeaning a domain's policy" means.

On Fri, May 28, 2021 at 10:20 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Fri 28/May/2021 17:43:37 +0200 Todd Herr wrote:
> >
> > Consensus on Ticket #47 <https://trac.ietf.org/trac/dmarc/ticket/47>
> (Removal
> > of "pct" tag) was reached during the May 27 DMARC Interim to keep the
> tag, but
> > to rewrite its definition in whole or in part to make its usage better
> understood.
>
>
> I think the text in RFC 7489 is quite good.  Perhaps a word could be added
> for
> pct=0; for example:
>
> OLD
>     pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
>        default is 100).  Percentage of messages from the Domain Owner's
>        mail stream to which the DMARC policy is to be applied.  However,
>        this MUST NOT be applied to the DMARC-generated reports, all of
>        which must be sent and received unhindered.  The purpose of the
>        "pct" tag is to allow Domain Owners to enact a slow rollout
>        enforcement of the DMARC mechanism.  The prospect of "all or
>        nothing" is recognized as preventing many organizations from
>        experimenting with strong authentication-based mechanisms.  See
>        Section 6.6.4 for details.  Note that random selection based on
>        this percentage, such as the following pseudocode, is adequate:
>
>         if (random mod 100) < pct then
>           selected = true
>         else
>           selected = false
>
> NEW
>     pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
>        default is 100).  Percentage of messages from the Domain Owner's
>        mail stream to which the DMARC policy is to be applied.  However,
>        this MUST NOT be applied to any other use, such as skipping DMARC
>        reports or demeaning a domain's policy.  The purpose of the
>        "pct" tag is to allow Domain Owners to enact a slow rollout
>        enforcement of the DMARC mechanism.  Using this tag, organizations
>        can experiment with strong authentication-based mechanisms while
>        lowering or even voiding the risk of non-delivery.  See Section
> 6.6.4
>        for details.  Note that random selection based on this percentage,
>        such as the following pseudocode, is adequate:
>
>         if (random mod 100) < pct then
>           selected = true
>         else
>           selected = false
>
> jm2c
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr">I don&#39;t understand what &quot;demeaning a domain&#39;s=
 policy&quot; means.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Fri, May 28, 2021 at 10:20 AM Alessandro Vesely &lt;=
<a href=3D"mailto:vesely@tana.it">vesely@tana.it</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">On Fri 28/May/2021 17:43:37=
 +0200 Todd Herr wrote:<br>
&gt; <br>
&gt; Consensus on Ticket #47 &lt;<a href=3D"https://trac.ietf.org/trac/dmar=
c/ticket/47" rel=3D"noreferrer" target=3D"_blank">https://trac.ietf.org/tra=
c/dmarc/ticket/47</a>&gt; (Removal <br>
&gt; of &quot;pct&quot; tag) was reached during the May 27 DMARC Interim to=
 keep the tag, but <br>
&gt; to rewrite its definition in whole or in part to make its usage better=
 understood.<br>
<br>
<br>
I think the text in RFC 7489 is quite good.=C2=A0 Perhaps a word could be a=
dded for <br>
pct=3D0; for example:<br>
<br>
OLD<br>
=C2=A0 =C2=A0 pct:=C2=A0 (plain-text integer between 0 and 100, inclusive; =
OPTIONAL;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0default is 100).=C2=A0 Percentage of messages fr=
om the Domain Owner&#39;s<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0mail stream to which the DMARC policy is to be a=
pplied.=C2=A0 However,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0this MUST NOT be applied to the DMARC-generated =
reports, all of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0which must be sent and received unhindered.=C2=
=A0 The purpose of the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;pct&quot; tag is to allow Domain Owners to=
 enact a slow rollout<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0enforcement of the DMARC mechanism.=C2=A0 The pr=
ospect of &quot;all or<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0nothing&quot; is recognized as preventing many o=
rganizations from<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0experimenting with strong authentication-based m=
echanisms.=C2=A0 See<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Section 6.6.4 for details.=C2=A0 Note that rando=
m selection based on<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0this percentage, such as the following pseudocod=
e, is adequate:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (random mod 100) &lt; pct then<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 selected =3D true<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 else<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 selected =3D false<br>
<br>
NEW<br>
=C2=A0 =C2=A0 pct:=C2=A0 (plain-text integer between 0 and 100, inclusive; =
OPTIONAL;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0default is 100).=C2=A0 Percentage of messages fr=
om the Domain Owner&#39;s<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0mail stream to which the DMARC policy is to be a=
pplied.=C2=A0 However,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0this MUST NOT be applied to any other use, such =
as skipping DMARC<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0reports or demeaning a domain&#39;s policy.=C2=
=A0 The purpose of the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;pct&quot; tag is to allow Domain Owners to=
 enact a slow rollout<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0enforcement of the DMARC mechanism.=C2=A0 Using =
this tag, organizations<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0can experiment with strong authentication-based =
mechanisms while<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0lowering or even voiding the risk of non-deliver=
y.=C2=A0 See Section 6.6.4<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0for details.=C2=A0 Note that random selection ba=
sed on this percentage,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0such as the following pseudocode, is adequate:<b=
r>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (random mod 100) &lt; pct then<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 selected =3D true<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 else<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 selected =3D false<br>
<br>
jm2c<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>
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>

--000000000000f274e405c3d4680f--


From nobody Thu Jun  3 04:07:47 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A320A3A3469 for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 04:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qHELqig-m5bY for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 04:07:40 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D8463A3467 for <dmarc@ietf.org>; Thu,  3 Jun 2021 04:07:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1622718455; bh=mkkvc+mPzvZD8WRfyQd62boZmP3qeCmsEG24Eys7+/Y=; l=3466; h=To:Cc:References:From:Date:In-Reply-To; b=CuN/N58KnwRZGiCZ+6iedzwfKmLj+TrF7KtrU76gi/epS9UxrG1uTwuphuNhAUcYZ C2ndHaDPZCH2trLp2IQ4W+fTCVtQa3LsQRwMKISnEkoI+03VUxRywUYIOYu6tnhsxH dEIr8oCeAZ1gT80X0xFtJytWorfxlNcpemjrexUs1gFkW3N0b6mQ1DVy7s9Xl
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 00000000005DC0C0.0000000060B8B7F7.00003776; Thu, 03 Jun 2021 13:07:35 +0200
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8muJPMFY7LXmz9RnCTHP5emwn=bspDtP8_KZNza1oAc6A@mail.gmail.com> <196e1a7d-95f0-9d44-d4c8-8889e508f62c@tana.it> <CAL0qLwbdLpjiv7Hb3FfNhtq2VxBnz6PwrrmWZzE8wzpDRR-QZw@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <e6403b99-dcc2-1507-4187-a7586c9f5eea@tana.it>
Date: Thu, 3 Jun 2021 13:07:34 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwbdLpjiv7Hb3FfNhtq2VxBnz6PwrrmWZzE8wzpDRR-QZw@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/puO4iuOhvrOS1_GYwLsRQqpjAiI>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #47 (Removal of "pct" tag) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 03 Jun 2021 11:07:46 -0000

On Thu 03/Jun/2021 05:45:33 +0200 Murray S. Kucherawy wrote:
> I don't understand what "demeaning a domain's policy" means.


I meant to say that p=quarantine; pct=0 is to be considered a strict policy to 
all effects.  Saying so should prevent reasoning something like "Oh, they said 
quarantine, but since pct=0 it is somewhat faked, so I'll skip X", where X 
could be rewriting From:, displaying a BIMI image, record aggregate data, or 
any other action that might depend on the policy.  That is to say pct=0 does 
not alter the value of p=, otherwise testing becomes a nightmare.

Perhaps my point would be obvious if the protocol allowed floating point 
values.  Setting pct=1e-37 would have effects equivalent to pct=0, and setting 
a boundary somewhere to distinguish what is valid from what is not would show 
up all of its arbitrariness.


Best
Ale
-- 

> On Fri, May 28, 2021 at 10:20 AM Alessandro Vesely <vesely@tana.it> wrote:
>> On Fri 28/May/2021 17:43:37 +0200 Todd Herr wrote:
>>>
>>> Consensus on Ticket #47 <https://trac.ietf.org/trac/dmarc/ticket/47>
>>> (Removal of "pct" tag) was reached during the May 27 DMARC Interim to
>>> keep the tag, but to rewrite its definition in whole or in part to make
>>> its usage better understood. >>
>>
>> I think the text in RFC 7489 is quite good.  Perhaps a word could be added
>> for pct=0; for example:
>>
>> OLD
>>     pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
>>        default is 100).  Percentage of messages from the Domain Owner's
>>        mail stream to which the DMARC policy is to be applied.  However,
>>        this MUST NOT be applied to the DMARC-generated reports, all of
>>        which must be sent and received unhindered.  The purpose of the
>>        "pct" tag is to allow Domain Owners to enact a slow rollout
>>        enforcement of the DMARC mechanism.  The prospect of "all or
>>        nothing" is recognized as preventing many organizations from
>>        experimenting with strong authentication-based mechanisms.  See
>>        Section 6.6.4 for details.  Note that random selection based on
>>        this percentage, such as the following pseudocode, is adequate:
>>
>>         if (random mod 100) < pct then
>>           selected = true
>>         else
>>           selected = false
>>
>> NEW
>>     pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
>>        default is 100).  Percentage of messages from the Domain Owner's
>>        mail stream to which the DMARC policy is to be applied.  However,
>>        this MUST NOT be applied to any other use, such as skipping DMARC
>>        reports or demeaning a domain's policy.  The purpose of the
>>        "pct" tag is to allow Domain Owners to enact a slow rollout
>>        enforcement of the DMARC mechanism.  Using this tag, organizations
>>        can experiment with strong authentication-based mechanisms while
>>        lowering or even voiding the risk of non-delivery.  See Section
>> 6.6.4
>>        for details.  Note that random selection based on this percentage,
>>        such as the following pseudocode, is adequate:
>>
>>         if (random mod 100) < pct then
>>           selected = true
>>         else
>>           selected = false
>>
>> jm2c
>> Ale
>> --
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
> 


From nobody Thu Jun  3 05:47:52 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 D5F023A0EB8 for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 05:47:49 -0700 (PDT)
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, 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=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 DsJiO2KYGi4Q for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 05:47:44 -0700 (PDT)
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 A37A93A0EA0 for <dmarc@ietf.org>; Thu,  3 Jun 2021 05:47:44 -0700 (PDT)
Received: from pps.filterd (m0184889.ppops.net [127.0.0.1]) by mx0b-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 153ClAW0012846 for <dmarc@ietf.org>; Thu, 3 Jun 2021 08:47:43 -0400
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=Z9z0avutwoDnMz02cKnjgT4iktUYQv09nSgePZetOWk=; b=O8zCkQQVcE3liPIt8+IzlmAzUiKPslIQtW+UALoBMtNEsxx1MzxnY8ejb7lD0JSimISr +cbMTmpIz6FMBZbFftwsbJMiqP6aK1ySu52DubBAtmSj0LbvIyXwIlHPkV8Xryeppii7 36ZSkvDGg2GKseH+6pbwpg3usX/BRTM4jNTPpUk6RiUnkai9+LMKmm/Mi6CZgAEtKmge PCYIknguDKMlllRaahFw48DRicS+2KlTbaZEUIu7Soj0MggFcVw4VypmCxW1UshGTna4 vTajEi6mt7cXtu39dp1534CkWTyZ9wBBv3JxIED8/LDhKSGZbyC4gNh/mJ/rYuTIIk74 yg== 
Received: from copdcexc36.cable.comcast.com (dlppfpt-po-1p.slb.comcast.com [96.99.226.137]) by mx0b-00143702.pphosted.com with ESMTP id 38xc7qq9f9-6 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Thu, 03 Jun 2021 08:47:43 -0400
Received: from copdcexc33.cable.comcast.com (147.191.125.132) by COPDCEXC36.cable.comcast.com (147.191.125.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2242.10; Thu, 3 Jun 2021 06:47:37 -0600
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.2242.10 via Frontend Transport; Thu, 3 Jun 2021 06:47:37 -0600
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (104.47.59.177) by webmail.comcast.com (96.114.158.213) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Thu, 3 Jun 2021 06:47:23 -0600
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by BL1PR11MB5238.namprd11.prod.outlook.com (2603:10b6:208:313::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4173.22; Thu, 3 Jun 2021 12:47:21 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::1dc0:e771:def5:fde8]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::1dc0:e771:def5:fde8%3]) with mapi id 15.20.4173.030; Thu, 3 Jun 2021 12:47:21 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: Extensions in Aggregate Reporting - Feedback Requested
Thread-Index: AddYdpfWt/LpopsnRqmW8ZVx8+CfOw==
Date: Thu, 3 Jun 2021 12:47:21 +0000
Message-ID: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@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: [216.105.213.51]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9603cd22-a3af-44e1-d91f-08d9268dbaf6
x-ms-traffictypediagnostic: BL1PR11MB5238:
x-microsoft-antispam-prvs: <BL1PR11MB52387F99EEFE82B46AFEA8F4F73C9@BL1PR11MB5238.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: 9rVSRCS8h2Z1DtwEaoW5f5yXtoAkdSkzzhRJuSGmaJhhSkBhkq3DqbQhuceDmh5EKU2qs/IYbZyba14E7AEghp54LOdYAVDWLbMrwhuMLCqdfy/aRU7nKdx42ONn9qX81vI5C+7hX2GE+6WPX9fVdF6XXKEnoFOmQeYUl6xiPdniexQbbrYwdN16mLCkjUmAfN+MHqunFRHS9DQ0JxnbyFGUwI5RUupCXE+Mr8+35snwYJW1FgfYjNpAY+3FhHuVmsGdcbfgtHbCCQDYWI7GF8Vh/Gn1tSLIdb8nlT/z+0xt7u9+gat6h8xC3hBE/FedKO+cvcpyqD4upJbJK0sjfSJgQK2be2NOIWlgQ2lCNS06GxZJw6Th9djMiZSaqq5oeWXl2ZNsKP2MdnKrgMg/oIOz0Uyywdb6Nw9nNWdt2qLFf83m+lY5kFdTfy/iMxaT2DwiImeUC7NK9z0Paa25Bdv+OGEj2A0DjM4O58JaM7vAfucWJRdro700X0LJ6B3O7VluYwoVPPkL+96Zkqr44cfM0RwD3qdVsgFQBnSUNum3yFkVBpzCyEZo7HenzF2cwNDvlE3IV6tByj8/KToZUB8nEYt7nwS9/v3ZXwkxQ74dhsOquhauWxdKfMbpQY8ewnAkt55LtjkCC4PQ9ZOg74RwjcQYXFasJKaW5YILiEZob12R0IzJx2F+Usvhz8HxYE6d0v7rQlfdxzF6u+DAUQ==
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)(136003)(396003)(39860400002)(346002)(366004)(376002)(26005)(71200400001)(66946007)(66476007)(7696005)(6506007)(66556008)(55016002)(76116006)(38100700002)(64756008)(83380400001)(316002)(8676002)(122000001)(66446008)(186003)(86362001)(9686003)(2906002)(478600001)(966005)(8936002)(33656002)(5660300002)(52536014)(6916009); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?cU4gOC0CRPngGybmlVuMwxV275dS2Qk+vPA1cebLBNR4c+lIQZdu+20iSiZD?= =?us-ascii?Q?9IBf4hD3Llf18Q2e6W0NS3aj8b0gDHGhV6FEX+4DPhleOKfrAFa3OhpQfc5E?= =?us-ascii?Q?EkjjpJVSyWy7b8jrrT5R5xKXg4mwcLN+I3CIFPpnE8M/RdP1VCQERIJZNUHM?= =?us-ascii?Q?B8n5F5Tj3xqTQiGCQAwGXNYdIB9YPbRlygvJcncu0rJ5ynuD62JOOdYHarS2?= =?us-ascii?Q?je0RfShpfAY7VzES4uBYRNi1ozSb748PKuw+CSNLbbJjQX6zEsuOBDb45Teh?= =?us-ascii?Q?k3MztM0O3fItlNInxKlyPDd5d7DjDzgscEa0R58Gyx7QYjVOOXlcBgQGX4oc?= =?us-ascii?Q?GsBKlkm1Ouco+AuIZPwCpzAqut3Sfz9/LzB3c3sOYcVyfJKcKtQW7/MS7kkq?= =?us-ascii?Q?FnxAGnYPptPV9f6Shq3AjO3PbWH+OdIZnpMpD3yApUuO4Acf7SVVeovmQUoN?= =?us-ascii?Q?02cgbrq8aXBCfPr3QpHfvprc480XLWQZWcP7Y4CK8K914ix3ngYkq6JPAWo/?= =?us-ascii?Q?CdirUnCgaBrYYJSaDD88OmLZJ1PFvODlBX4wgc4yJGgSvXqujUeerJAVjc5w?= =?us-ascii?Q?m77YP8j1JXyxGO/6Rhs8UdFJxRJwUb+wI5ccypKa7PsOh6rqWBlkgv08C9hA?= =?us-ascii?Q?Av2Kicw26YnXbNvlMWNb3fluUoA8A9xiOeMKB91kK0oUiokxHK+NgCMDiHe7?= =?us-ascii?Q?ifuPzoMdq5a8aWBeaPlBLC+/HBspxL779iuQkoA2Z6tm57fHCihLKSqvhM+N?= =?us-ascii?Q?D9nt7QHisz5hBnMYGtSPFTHN3eG/PpTpBC2gQFLVFNxWUoBUTIU2/weACpu/?= =?us-ascii?Q?JqXR/ynYVvYAF8TUBd6sGbK64CaN5BNqDHkbtT5/sEDSyj3kw1DSYoLl+oAd?= =?us-ascii?Q?+4/LajGCe+JxJrZjiyOmZrIWw42W36h/SYiEWTYKr0tjKnOauCrvEway8sXu?= =?us-ascii?Q?/wGymCcX40Z7BmQtW5A1b8eIqO6xJ0vSyQOxeE5T0d+XxjR5fji6WzJcdRs8?= =?us-ascii?Q?f214GR/l+9BxafQQcHZJpaHTVEhiEK7aJB2s06NSD0rsFCr9qTIJdKdYMbya?= =?us-ascii?Q?DWFbw2EmcTtoiBRis8G92huCLX4s8bz7w0kDsxPVwA64by2xj6iYUvXgG5EK?= =?us-ascii?Q?Dk4/gqWmt6F8IfaS7gpa6qhtFTPHF8Hzd+SdBleRS59gVUwYyQaGf9TrQHTO?= =?us-ascii?Q?dr+TNXURDKn9JGm4Aq14k1TzV2zJhS1mbBGy7XfEqbwgiOAZbBmY1ylSfDp4?= =?us-ascii?Q?ToIqLVQiyc0AuwaTKLPI6KOuoIP9VrG7As/HMbx2178AJaK7yejqJQyGKrRg?= =?us-ascii?Q?7Ae+iXBN3v1L46aHnud02x+f?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iPWDCmcjwrCL+qmQ23IIkxExIKjOYKCa5dw/lSfZOM1c52i01PT5Vu/nezTmyykoE2p1B4b/n3PLm79XCCPvtqFPdLqeYcfyyHHSQZq5sr0MA6EKvceIvbjRsIYEM+49fRx25JDVzAEauJ5V0yOF3H115BXKRMhL6mIv8QpfA/WgtViXIfZa8hqKbsPrhwzGE6HWx9ZYZPQZ3k/XwzXxnlgo6lcRjLwF8VhecO3s7XHutPvgD00bIQ54cCg9HrFYdLF0/1/6+F/WGB1RKfj8OuAU5Add6wACKB/btGsqUQUVwJ9ke/RYkszNkmNR9xPVXA6v/FDLUP50fKRqNitgAw==
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=ZGZfKZTNzYFKMXYwJU4Bz6YB1IN0cRH3K5E5LwAD4JU=; b=Oq6qX3Q79efvjy3pbGULfOU830BgL/++keakgKjJDU2iA8k5cpbzEBOmPgl7lSBLRas2ysjlNdWKkUjMkZm/WRPoJN+QYMNHrg6NTBv6FjCF7WL8ec8FyZINgnz+zVSlp04nk8/JozqW9Agw8JNqtrngkYLKqJReyAMQRfcafi9t8PE/bs6bjguqq7SR3hGlzIB8yqyOL4dAhLKlDXPXPv2kpRC4VPe+e/+3qNkcGHiGVaWhKlqJm5ofhTCQMVia9rW0eNn0BdvmL2/G1/5Zapshz7dBufzb69Mnq0CpqVldQn73cfc22ZHF90A7DSoTzR8ONhMXd5njjwOkiqY0Jw==
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: 9603cd22-a3af-44e1-d91f-08d9268dbaf6
x-ms-exchange-crosstenant-originalarrivaltime: 03 Jun 2021 12:47:21.6950 (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: lZSOot7cWC/D8nGdcs6kqH36beiMir/a1e23KqU3l4BG3kxC9b+oWP0vbcmVciieBD5EDvN6SEXsnHwis7F6bmUl1/7o/9FTCivAzRF3TxM=
x-ms-exchange-transport-crosstenantheadersstamped: BL1PR11MB5238
x-originatororg: comcast.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWO
X-Proofpoint-GUID: DorzMi5BU4qCYf99SDidFeSBQLD84goT
X-Proofpoint-ORIG-GUID: DorzMi5BU4qCYf99SDidFeSBQLD84goT
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-06-03_08:2021-06-02, 2021-06-03 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/xRu6a0o5CjVBz9kuoIpVnK5RzLo>
Subject: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 03 Jun 2021 12:47:50 -0000

Hello folks,

During our interim call last week the topic of extensions within the DMARC =
aggregate report came up.  There was a discussion about how to best introdu=
ce these, but also how they might be best used.  I noted three cases that I=
 could see today; ARC, PSD, and BIMI.   And indeed we have tickets relating=
 to the first two.  The original thought was that the aggregate draft would=
 allow a place for extensions, and then additional drafts would define thos=
e within the IETF.  When -02 was originally being worked on, there was a th=
read about how we might like to see this, though not many responses.  The r=
esult is in section 4 of the -02 draft [1]. and I thought we'd enhance that=
 as we progressed.  At the time, I didn't intend to limit the extensions to=
 IETF-approved extensions, though wasn't sure how else this might be used b=
y reporting entities (I mentioned domain reputation-ish things during the c=
all).  I'd consider that if we don't enforce IETF-registered extensions, th=
e receivers could still ignore extensions they don't want to handle.  I'm a=
lso aware this could bloat a report in terms of size, though we've already =
indicated we don't seem overly concerned with the size of the XML body.  A =
few things I'd like to see the group reach consensus on are:

1) Extensions in their own section (as it is now) or within each <row> elem=
ent
2) Must extensions be IETF-approved
3) If (2) is true, do we want to define any during the DMARCbis process (es=
sentially a demonstration of how it is to be done)

Thank you for your continued feedback

1: https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-aggregate-reporti=
ng-02#section-4

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


From nobody Thu Jun  3 15:17:49 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 052D93A1C9B for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 15:17:47 -0700 (PDT)
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=znGeP5v9; dkim=pass (2048-bit key) header.d=taugh.com header.b=VlNoWWF5
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHiisKwcZCS1 for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 15:17:41 -0700 (PDT)
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 838703A1C99 for <dmarc@ietf.org>; Thu,  3 Jun 2021 15:17:41 -0700 (PDT)
Received: (qmail 31332 invoked from network); 3 Jun 2021 22:17:38 -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=7a61.60b95502.k2106; bh=oOn0mbDSYlQePfsLnoe/hW378mY7BoKFk18xyI9PD1s=; b=znGeP5v9WxYeiwz0uVswnBKG5RMFCEKT2tKI1puCQVdN/wtvICk9kFTaBf5YPNAyIHdr2g0o1vHzVWFsd5s5r6eqvVqzs6XqJY/ki4D4oTFhiBghe92EYKCXMSFY0yoABWIHGw8HBiLt/CBL65UX0tpcv5Guj8ysPf2XFvjHT8LcfIlwgYMHf7l9kQviDbtmVJeuRNsspFILG6bm+v1fRyTBqPr+/9m4NUKz34U2hgCBpVxQjQ/vanJTOIMyGzQC9y6O9FYPdJFZFZogCm3B2fKER+iKTzUzJ39tvsr90ch/pTkoNhHwsCxBeC+0QHWpYa0fNtiiuTp/HOd5hdJzhw==
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=7a61.60b95502.k2106; bh=oOn0mbDSYlQePfsLnoe/hW378mY7BoKFk18xyI9PD1s=; b=VlNoWWF5+seB1Vjcu9fCvPXIeBF46pikWLJwlVIsYydJSgSei+t/n/JbRVvUFBIMaRUoWMhT94ipXFoxhVlfNMLJ/DRSyTfRsNnlSvR4nuNLrqh06yVe11sc2jX0oWQMoVjhe9Yu6+VTHAPS5Ish4lYZD8vcv87Z/2EN0vmMJj22nJ89C2rjIEYYgrjUDKCYlVk/g+YaOH5SF53gWg2CVbW5z3aMZUoqnQ65ItZTbcYj1aLLlcHCTNeBELruRsQNe0U7zhVitdOf50xnIhCohD7mmvxdkDaeYbNpEJvB9RNmKGKDv2rqxVpTVwS90oVhJvV0l8dTJbLPUTeLNcYfxA==
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 Jun 2021 22:17:38 -0000
Received: by ary.qy (Postfix, from userid 501) id C8146B6B7BB; Thu,  3 Jun 2021 18:17:36 -0400 (EDT)
Date: 3 Jun 2021 18:17:36 -0400
Message-Id: <20210603221737.C8146B6B7BB@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <e6403b99-dcc2-1507-4187-a7586c9f5eea@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/YJ_4NloeMaU0PVbj87Ub80nQuuE>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #47 (Removal of "pct" tag) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 03 Jun 2021 22:17:47 -0000

It appears that Alessandro Vesely  <vesely@tana.it> said:
>On Thu 03/Jun/2021 05:45:33 +0200 Murray S. Kucherawy wrote:
>> I don't understand what "demeaning a domain's policy" means.
>
>I meant to say that p=quarantine; pct=0 is to be considered a strict policy to 
>all effects.  Saying so should prevent reasoning something like "Oh, they said 
>quarantine, but since pct=0 it is somewhat faked, so I'll skip X", where X 
>could be rewriting From:, displaying a BIMI image, record aggregate data, or 
>any other action that might depend on the policy.  That is to say pct=0 does 
>not alter the value of p=, otherwise testing becomes a nightmare.

If we agree that's what we mean, that's what we should say, e.g., add something
like this:

 Senders may use pct=0 to signal an intention to apply a stricter
 DMARC policy in the future, and to request receivers that do special
 processing based on DMARC policy to do that processing. Examples of
 special processing might include mailing list software rewriting
 addresses in From headers.


From nobody Thu Jun  3 16:16:47 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 206AD3A1E78 for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 16:16:45 -0700 (PDT)
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 n8xvM0hlN-Ei for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 16:16:40 -0700 (PDT)
Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 018813A1E75 for <dmarc@ietf.org>; Thu,  3 Jun 2021 16:16:39 -0700 (PDT)
Received: by mail-qv1-xf35.google.com with SMTP id a7so4080035qvf.11 for <dmarc@ietf.org>; Thu, 03 Jun 2021 16:16:39 -0700 (PDT)
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=LKY20CEpcenx8zryWQ4a087fEzrZ1Lh4pzElBLeKnOY=; b=RykCFtRfDxdNFdLaPE50WN6mokDDmRhlULR988ClMY372I1R6fRpWhRp1Dyy6q1wDo ntUP7M6n1GZewV2583NP6xVJUIhd3V3Rwd+RLF5J37s1XSbyjyUd1UCqFnrYcj/dW3Hq BvWb3u1EWrJW/lNnaGpJ3qjN1dDTTDlT5vvEKvMsSKJj9GtdtDkfobMVP3/VcH9joPtu nLz2hppjpMxzpumwCzgcyXnztU4gs1O+epY6meHZXbInmh3JZ9vec6XWI25ZFuETlIuq JMFU2xFrozU7+IuxRVjD6y5CCanEU8FMKIwfha35UFgtnedh8vAgcLoMYHwd8DVqsvnF 96Dg==
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=LKY20CEpcenx8zryWQ4a087fEzrZ1Lh4pzElBLeKnOY=; b=KyBlfH6AfcnMCygZr1ljEnC4EWyGLFpa9NAATIVf7F9OdVDajxqcHM3Y5lqZMh7AYU P6tyE35FhKHBipxWj84aPQoGqjOqwjHzOILTQyDGo2hxBV4sf20OLb4HOho+MXtbK8Mk gyIl2GeKgBkUrbpZjTLLMf92LCCXiYfGeGQ3LtWc2lmY9G79Lr+21QtDmlOvVlqW5r+S 2pBIU/HdAezFZMPRDF2RJ4esYUWA3mCAHAUEgF4fwrWeNYo38EM/1OpY5aVhBYvWE+fW SyDLh3Bq0/OXwdpwIib2ZiyqBXjatU9UCkIR5gpssXKbYs2msmzI4Sqh1OdpQeb4Mt1Y ybMA==
X-Gm-Message-State: AOAM531KDHeVWHVRn/34C4gCcc3i+Gk6SPx7qlRRy0pKfp/0PPIjdx1h Wzbj4/rKc5ZMOxBp6ZQ2aFN5SRFzbM02VO2eBoINKCkBBzE=
X-Google-Smtp-Source: ABdhPJx5X5rzmzqluusblTG9MC01e6cigy7ebxUQkuCCgJf8w9tUtkGMWIEY2XxfO1NGaXbSkeLKHb5dq9SkuO3Uq3o=
X-Received: by 2002:a0c:eda5:: with SMTP id h5mr1818410qvr.26.1622762198293; Thu, 03 Jun 2021 16:16:38 -0700 (PDT)
MIME-Version: 1.0
References: <e6403b99-dcc2-1507-4187-a7586c9f5eea@tana.it> <20210603221737.C8146B6B7BB@ary.qy>
In-Reply-To: <20210603221737.C8146B6B7BB@ary.qy>
From: Dotzero <dotzero@gmail.com>
Date: Thu, 3 Jun 2021 19:16:26 -0400
Message-ID: <CAJ4XoYcek=dW6Q75CTzQzB+9szUWreC8D8_he0SiLw-7m_25UQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006261eb05c3e4c454"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/P2pMeZk6yqxX723voFUk06KExMg>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #47 (Removal of "pct" tag) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 03 Jun 2021 23:16:45 -0000

--0000000000006261eb05c3e4c454
Content-Type: text/plain; charset="UTF-8"

On Thu, Jun 3, 2021 at 6:17 PM John Levine <johnl@taugh.com> wrote:

> It appears that Alessandro Vesely  <vesely@tana.it> said:
> >On Thu 03/Jun/2021 05:45:33 +0200 Murray S. Kucherawy wrote:
> >> I don't understand what "demeaning a domain's policy" means.
> >
> >I meant to say that p=quarantine; pct=0 is to be considered a strict
> policy to
> >all effects.  Saying so should prevent reasoning something like "Oh, they
> said
> >quarantine, but since pct=0 it is somewhat faked, so I'll skip X", where
> X
> >could be rewriting From:, displaying a BIMI image, record aggregate data,
> or
> >any other action that might depend on the policy.  That is to say pct=0
> does
> >not alter the value of p=, otherwise testing becomes a nightmare.
>
> If we agree that's what we mean, that's what we should say, e.g., add
> something
> like this:
>
>  Senders may use pct=0 to signal an intention to apply a stricter
>  DMARC policy in the future, and to request receivers that do special
>  processing based on DMARC policy to do that processing. Examples of
>  special processing might include mailing list software rewriting
>  addresses in From headers.
>

As long as we get the wording right, I agree with your line of thinking
John. Again, we don't have insight as to the extent that receivers will
honor the request.

Michael Hammer

--0000000000006261eb05c3e4c454
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, Jun 3, 2021 at 6:17 PM John L=
evine &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.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">It appears that=
 Alessandro Vesely=C2=A0 &lt;<a href=3D"mailto:vesely@tana.it" target=3D"_b=
lank">vesely@tana.it</a>&gt; said:<br>
&gt;On Thu 03/Jun/2021 05:45:33 +0200 Murray S. Kucherawy wrote:<br>
&gt;&gt; I don&#39;t understand what &quot;demeaning a domain&#39;s policy&=
quot; means.<br>
&gt;<br>
&gt;I meant to say that p=3Dquarantine; pct=3D0 is to be considered a stric=
t policy to <br>
&gt;all effects.=C2=A0 Saying so should prevent reasoning something like &q=
uot;Oh, they said <br>
&gt;quarantine, but since pct=3D0 it is somewhat faked, so I&#39;ll skip X&=
quot;, where X <br>
&gt;could be rewriting From:, displaying a BIMI image, record aggregate dat=
a, or <br>
&gt;any other action that might depend on the policy.=C2=A0 That is to say =
pct=3D0 does <br>
&gt;not alter the value of p=3D, otherwise testing becomes a nightmare.<br>
<br>
If we agree that&#39;s what we mean, that&#39;s what we should say, e.g., a=
dd something<br>
like this:<br>
<br>
=C2=A0Senders may use pct=3D0 to signal an intention to apply a stricter<br=
>
=C2=A0DMARC policy in the future, and to request receivers that do special<=
br>
=C2=A0processing based on DMARC policy to do that processing. Examples of<b=
r>
=C2=A0special processing might include mailing list software rewriting<br>
=C2=A0addresses in From headers.<br></blockquote><div><br></div><div>As lon=
g as we get the wording right, I agree with your line of thinking John. Aga=
in, we don&#39;t have insight as to the extent that receivers will honor th=
e request.</div><div><br></div><div>Michael Hammer<br></div></div></div>

--0000000000006261eb05c3e4c454--


From nobody Thu Jun  3 17:27:30 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 1D2083A209B for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 17:27:28 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=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 QdKiifVZ3c-b for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 17:27:22 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CFB13A1FA3 for <dmarc@ietf.org>; Thu,  3 Jun 2021 17:27:22 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id k22-20020a17090aef16b0290163512accedso4254989pjz.0 for <dmarc@ietf.org>; Thu, 03 Jun 2021 17:27:21 -0700 (PDT)
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=tlXtCfuD0jLj8+wVBxb0JaYmKyeUj3DPSsU9tH2sqgE=; b=TztKDBbTFNrw7veDempc7FTv9TszdJAmvK9PLYG3WtTGottVMfmBLj9MTGlcV92PQp I0tVvmrqIT2nNy7qxfFa23e1sE6gS+3cFYLfZC/8NUA0P4glyZ6sZ5yysUXM/LfKz+/A xnARUwhAv+pKTrg7xOdQCm/klguOZnyyz0NSaxodQ0Zou/rngra34tKEEE4y2uH8Qk2r joByhMuxLPnzB5nXWlqzp7ty2If0L4wCbLSvjDWY4sPLMk28M+Q12DnBRyZq+ft4dWug G1Cb4wbzqkku36s9FsVMJzPp605ZHHzPsxMuuddSEXvUOUpOl94WIVogKu9C6FNYZ4c7 0iWA==
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=tlXtCfuD0jLj8+wVBxb0JaYmKyeUj3DPSsU9tH2sqgE=; b=JTkT+tDCqFcEARNTR7/nBekmfaQtnkp/uxqC8/r2wztTn1UOA0Mtt65IncpmkQJbb8 4u7pvOuxrqRHlgeXAPp7gibTCUSD7VZvIntYJZu+kkWaabWUwpiD3IgobezcxH/9SosB KdCdsa9UJtJvo6fChMpptKpCwsPu1sDPVeQm3/+wS9USzhb0nZu8U8JwRI7Ap2A3UldD 9VIb3dcfoOS5YeWDZ2Gf27okMICFquEg7PPqESCrsKPdCcf+t3v4ZejE5sKR/ZQmE5Gi hd545navGbBRjmkmIftRL45VQWh9x4/6mJTGWRe3UYaPgHDtSaiIh/xWbHmu+a3hu/fR WDmw==
X-Gm-Message-State: AOAM530ua98k+4MALAWweaKPeCfY/gb6accnXrJohKtJyj/hpiDK998v Est2D+LRjG4By0BO4jSLSYYS9n3EzYqV0A==
X-Google-Smtp-Source: ABdhPJwVFrSz19GXVozbMBuDLg2s+w7/lXRyiXJisd6P7u8vJ2Up205nzPS0g8TeMBRtWW32/wMDWA==
X-Received: by 2002:a17:90b:4a8a:: with SMTP id lp10mr1955189pjb.121.1622766439429;  Thu, 03 Jun 2021 17:27:19 -0700 (PDT)
Received: from [192.168.0.106] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id x1sm2978561pjk.37.2021.06.03.17.27.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Jun 2021 17:27:18 -0700 (PDT)
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <06fd0594-e86f-ddd4-10bc-165852932479@gmail.com>
Date: Thu, 3 Jun 2021 17:27:17 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------C2FCBCE09FB8378294339A69"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/snjvT32JxG-LZRknnIlqfJRzH-c>
Subject: Re: [dmarc-ietf] Ticket #113 - DMARCbis -01 Introduction Section
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 04 Jun 2021 00:27:28 -0000

This is a multi-part message in MIME format.
--------------C2FCBCE09FB8378294339A69
Content-Type: multipart/alternative;
 boundary="------------88393E647DCA75F4E43A4CD6"


--------------88393E647DCA75F4E43A4CD6
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 5/5/2021 11:48 AM, Todd Herr wrote:
>
>
> We would like to achieve rough consensus on this section of text by 
> Friday, May 21.

Apologies.  I've only just been able to review this text. Attached are 
suggested changes, done as a Word document with revision tracking turned on.

It might appear that the edits effect major substance changes to the 
Introduction, but I believe they do not; the intent was to retain the 
same goals for the Introduction.

Changes were driven by:

  * Providing better lead-in for readers with less background on the
    document's topic
  * Eliminating detail that is not need in an introduction
  * Minimizing PSO text, since I belive the covered domains have Domain
    Owners whether they are PSOs or not; hence the fact of being a PSO
    has minimal import in the Introduction
  * General wordsmithing, to tighten things up

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
Information & Planning Coordinator
American Red Cross
dave.crocker2@redcross.org


--------------88393E647DCA75F4E43A4CD6
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 5/5/2021 11:48 AM, Todd Herr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com">
      <blockquote style="margin:0 0 0 40px;border:none;padding:0px">
        <div class="gmail_default" style=""><font face="tahoma,
            sans-serif"><br>
          </font></div>
      </blockquote>
      <font face="tahoma, sans-serif"><span class="gmail_default"
          style="font-family:tahoma,sans-serif">We would like to achieve
          rough consensus on this section of text by Friday, May 21.</span></font></blockquote>
    <p>Apologies.  I've only just been able to review this text. 
      Attached are suggested changes, done as a Word document with
      revision tracking turned on.</p>
    <p>It might appear that the edits effect major substance changes to
      the Introduction, but I believe they do not; the intent was to
      retain the same goals for the Introduction.</p>
    <p>Changes were driven by:</p>
    <ul>
      <li>Providing better lead-in for readers with less background on
        the document's topic<br>
      </li>
      <li>Eliminating detail that is not need in an introduction</li>
      <li>Minimizing PSO text, since I belive the covered domains have
        Domain Owners whether they are PSOs or not; hence the fact of
        being a PSO has minimal import in the Introduction</li>
      <li>General wordsmithing, to tighten things up</li>
    </ul>
    <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
Information &amp; Planning Coordinator
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------88393E647DCA75F4E43A4CD6--

--------------C2FCBCE09FB8378294339A69
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; 
 name="DMARCbis-Intro-dcrocker.docx"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="DMARCbis-Intro-dcrocker.docx"

UEsDBBQABgAIAAAAIQCw3PgAbgEAACQGAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIo
oAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC0lMtqwzAQRfeF/oPRtthKuiilxMmij2Ub
aPoBijRORPVCo7z+vuM4MaUkMTTJxiDP3HvPCDGD0dqabAkRtXcl6xc9loGTXmk3K9nX5C1/
ZBkm4ZQw3kHJNoBsNLy9GUw2ATAjtcOSzVMKT5yjnIMVWPgAjiqVj1YkOsYZD0J+ixnw+17v
gUvvEriUp9qDDQcvUImFSdnrmn43JBEMsuy5aayzSiZCMFqKRHW+dOpPSr5LKEi57cG5DnhH
DYwfTKgrxwN2ug+6mqgVZGMR07uw1MVXPiquvFxYUhanbQ5w+qrSElp97Rail4BId25N0Vas
0G7Pf5TDLewUIikvD9Jad0Jg2hjAyxM0vt3xkBIJrgGwc+5EWMH082oUv8w7QSrKnYipgctj
tNadEAF8uAZB49sZn2gLQfPtnw2xtTkVSZ3j6APSVov/mHm/tmp1TtMGiEmffvRtIlmfPR/U
G1GBOpDNtzt++AMAAP//AwBQSwMEFAAGAAgAAAAhAB6RGrfvAAAATgIAAAsACAJfcmVscy8u
cmVscyCiBAIooAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACsksFqwzAMQO+D/YPRvVHa
wRijTi9j0NsY2QcIW0lME9vYatf+/TzY2AJd6WFHy9LTk9B6c5xGdeCUXfAallUNir0J1vle
w1v7vHgAlYW8pTF41nDiDJvm9mb9yiNJKcqDi1kVis8aBpH4iJjNwBPlKkT25acLaSIpz9Rj
JLOjnnFV1/eYfjOgmTHV1mpIW3sHqj1FvoYdus4ZfgpmP7GXMy2Qj8Lesl3EVOqTuDKNain1
LBpsMC8lnJFirAoa8LzR6nqjv6fFiYUsCaEJiS/7fGZcElr+54rmGT827yFZtF/hbxucXUHz
AQAA//8DAFBLAwQUAAYACAAAACEASiSZhf0XAACwaAEAEQAAAHdvcmQvZG9jdW1lbnQueG1s
7F3dbuM4lr5fYN+B8M3MAElsy//ZKQ+cOB4EM90VVKqBxQ7mgpZom1uy6CXlpNxX9Q57NcAM
0M/Sj1JPMjyUZEu2JItxgo4oN9BlR7Zo8eM5H885POT545++Ll30RLigzPtQa141aoh4NnOo
N/9Q++nz5LJfQ8LHnoNd5pEPtQ0RtT8N//M//vh87TB7vSSej2QTnrh+XtkfagvfX13X68Je
kCUWV0tqcybYzL+y2bLOZjNqk/oz407dajQb6t2KM5sIIX/vFntPWNTC5uyvxVpzOH6WN0OD
7bq9wNwnX3dtNLUb6dQH9f5hQ9YLGpI9tJqHTbW0m+rW4akOGmq/qCH5VActdV7WUkrnui9r
yTpsqfeyllqHLfVf1tKBOC0PBZytiCc/nDG+xL78k8/rS8y/rFeXsuEV9umUutTfyDYb3agZ
TL0vL3giede2hWXL0W6hV18yh7gtJ2qFfaituXcd3n+5vR8e/Tq4P3yJ7uBF+h/cMg7JQfW8
zokrsWCeWNDVVsOXL21NfriIGnnK68TT0o2+97xqFlSXLHoaB1DuGizy+CH+Szd48vwWm40C
IwJNbO8o8gjJ34yeZCmlcPfDL4ImBm6zIIFEDVgHDXRtUpDwozb6YRt1e6eh0A4tqBpRO8Go
QDt0B2yzII/tP0ysAeH4zkKrFSvCtQ73Yh8vsNgKOrRI9B6qs21us4xhtJqfpgh/5my92rVG
T2vtfkdrz2BgaLQVKlRcycVpD/O4wCvJdkv7+n7uMY6nrnwiqR5ISjhSIwD/SkGBF/WWfFXX
YawRcExtKC2jKXM28LqSn7WvV5jjeymUvXajO+h17mrqqpxXfHU1/E9evZZWmPPpQ63R6Ld6
g7vJ9tIDh4uTfrd329leHJMZXrv+4dcfYpfUUzxweBErbMsuyi/hmU+gRbjBpQC61d7+8WkN
fcZrn9XqcBsP7uYT5vkCbhY2lUM+4hS7cA/Bwh8Jij/UPtMlEehH8ow+sSX24MPFyBPxL9si
+kO1LX6W156wCw8QXbmFH4ldq4ePUN92hKfC8p6e9fnaHzav0L3nc+asbZj54DM/+EbQl0P5
aN3cDcajdvcsH6fIRzq23db47ua2ZSWxtbo3knWtQQLbjtVsBN3dh7HXaLdvoYkdjDHhexUY
qQfdgylMfVN+vmCyDQc/ESR5zP5COFyXkwM017Cal43uZaP1udm5bjevG43/CVt7i9GwmctA
9xT4DfXfKWq862pTr6vWdaenuvrbkcGrQCEJAeYtJTGyiytOBOFPpDYcTdeCShT2OUMilgRO
yWJx4CRqg0PglGSPrWY/YIMywDYkR6FpVVamhtK0d5E0eIiHqGe7a0c+yNoLsKA/Ewdhz0HO
cQjb2hD2TYHQJitfauBRiNRse2auLXOhtbSQ2Qxh5DDwMJGHl0RKIfIXBegMLB+tKa+VInCx
Kbw04vZpcttpWdbVhLPlUZSUJXiWuZ3MLQh2CEczSlzn6riU9atLa5+lFoaK6W9W1Mauu0FT
4jJvLpDP5MSAGJ9jj/6sonWIfF0R25czhvxsStAXjz3LO9lRiJVBXRzi1nWzka7IZgjo92//
f1wsm5oGv0FymQ4bWCnHUdP0HYwRtSEAtV7iqXscI003QWIUuJJmquOmgFTpew/GzBE+Xwug
/OnmOEyaHoLpPH8cME1/wXBNLDYvanoFRumitNc4semKEs+/yoAqTS7K3e1ffwFD9ZF4YNY/
MJfaGzTh0pN8ZvwL+v3fpLvUsxr9v/9BRTLGyqD9C9kIdO9InKh0BJwEVuaTjYlS8AOEsdRg
d1u9rhzsFWc+k80LePdEnciXuXTJE3ERUAQMv618lz14HPmFkE80/efsKEMeyuHFMVEglCse
IbH6TL5myd3zgtoL+Hb4tUIiaCAOuhAYJx9DKlIwCK7A12JTuGbIxZzA3gWarn2EeVYkubC8
lKXHGcriMR85VJoyvrtBWAhmUwxOxjP1F4ex4QRda8aSKkvX2yByrlIaJ3DDg5h5nHks7VV0
U5jnuuKME5iGmbRiacYNq0srF+BkFZzoLc1Ioznqpli3wuo2/mH06XZP29L6XvJuZvOJZsRY
Sn5GKo7pfDJdU9cRiEFOABNk59Vf/foL+gmScANhuijKOZpB6O51IyOmao1bI2tcHs6BsAfH
c/nz0oI+njdgaQafs0W0fF6YYBIj7FedpJVNhD4+e4SLHC7Tz8OpKJeBTCHG6Zx6EpUUwsrF
4xwUM1AkiMq+tLFyPTKnr5iyaYaju9et/DXUAsg22812985YidvBXBifkkCRAcJqPXWpWCCM
xj8+5vC6fhi2mryejvLn//58ljaJAyc243upWQkx047Ytk9mNIPETIXEc+VsZ9K39DcJZUBd
NpOeeo5a6PXme3KY1qtUASq3EmblzRjHQZADQ/neIMc0QDOOm20+lcsoyhILWA25DlLhMyQk
hp12tNYU9khfHKmn7hxtWINGp9+9rR3flZu9czT5yRvvHG1pxyLDcQ2ae7cjB+MTvR6OU7Pb
GfTuBjAisXFqWNbdzeRWIZI/LWgNXkzgw8FbPfobl0QP/lcq/Af5YHOOV4ugX956GQ6U+wSm
UgDF9rN7Z9vpsM/bG15NLjQjpe9dLlQXbxfYmwPuqofaIc5w03Q6XtpxsB1eMZndPuShJIfT
WSk48y7P0Eq1NMowK6TIkHZ+YFKGtrDtDzqgp4JDuYmKxsKqHXwoDutrZciWFFl9f7u4wK4g
+5oSlemX6u0H889Lf73okIQXS+TtH45TWzvlpPA4RaGCCziq0SewHhj4TCfEqkoKsr5P86o0
k26bdgaNm8HNeM+HaN9MrHYz2Pf5Uts0OXTltU3bhvksKZKpb33n2KZtfUu3oG2qpCb55Pp2
8O7JT/FtIzM5eI09aNhobBY6yWgLtcfAKeftjK7cGHawISd3AoqJ8kn2SzR2ZRmkuHH11zwL
NW8iKJkYdk6yEV8yKW/lLy9EXmpI386Y9Idshmzm2YR7aCYfWjmtKtVlJt/tuwJmwPkbm42m
wKhvxRWXymTYBNkLYn/J9ks7r5IWmmMRlCFbNGWEToyQvtQiULsI8i2C2Ni9NPBadOxKql1v
F5nMHTtO/m9NhJ83evVUt7c9mXTHvQYYofGls5u7m8lopBi36ksyHX0DvWRub+fE6GQSr+5L
E162sp+tA/tub/cUE+st3d4YHCeZLe+a/uIz/zgxy9e3lnwMiJeGj1TnURrrvGt0DvWse2J4
Kdf0IoJyAr6AiUZr9+1MoldP3iopwqcEEI/JJicrxiUCeMrWPgrS78NTaKW/kCWwpiH8hovW
1V5d7b7huvUwdkjyHpw7Z6irb0BZ1Vxg7b1dmDFye67gWuUWVXtvGGxMZ5dffymyrNrr3N30
m2pbS0lSM3v6BrsBqZnt7rh/2x7dJMepPe5NBq1+MjVzT2ti4xTG295ynN4/vglZ0vR5uteN
dvmcv3R+UCcEHD87tKcfBG6V0D+2sYds9kSS7lkqIJq+jkkygzzmXZKvVPhQs1asp5eB+SUu
CgiSpgfTyzzpuGyVdqA6wLM6ou37t39+DIsDHMdL0x/pZR50XDK80kUPFqywG56/8P3bv4pI
nKbfYZKmYnkDcV0kX0MVRdhXMuizFTj2x9HTdJokeh1T0AOcVNmdBSUcc3uxuYDlfJ8z11Xn
umfBt/M5+5qeVBK+uPoW38JbrtN3chfMHumSupi7m0DPT/AXy7ZZ8wFOIrDR43o2o1/Rx5UU
QJ9xgX7/8PhR/CEhdwl5097FeZa3uGWzxBvJlFG8c0/echEyEAxdCIwTkqEA9ofMLal16HZH
/eH5Tz9ieD7Ix9i3iKPZls3OcnSWI2VJZItQxaa2q32rKW2veLt/d3OjAjPHApIFZOfIPo/q
Rb/SQW/1+u2e1drbXNNqt0ft3ihZ2vmMby6+MbU16KiUkQiOmX98mAT1Yv5y/8NFcMZo9iFG
fc1AfbpFmjMjdG+tu15pjhvJnSkBpVhibu68EENYP3zdNR/h4S6tORPDXZijrx/fTsGwfGBJ
mFwsxN625Po2kmEijSH5Tk5W2YylH9qvgD5lYClN2CfCHWr7aaq2w8PAruf2tyLjH4aQizCs
5sKPMQybDpyAmHyFSLe2ktNMDclfqMHetxqcUb/HwDFZ0T7K15TZeIQAJzTjbImItLUJV9a2
bByMbUQFgj0klBPnKkN4YvOY/sLXsfr24UXzeGwUujEK/VxGi+GrvzRWWTshtBGKQjvQXzar
gOiq/WNS94WqAsc8dxNsJpYMcba9jB74iP+DyUH+BQFl+UwCzwmY4GpbIWVeWCXRjVXpyNS2
dLRKAkzBXPqdSTHQXxhNYRRjzM8RiEiFzM+Uypgx2dAPUZosG0AyZO9YelOkI9wosicKwT/G
sF7MjtIPDVfBjpIfUui8yuECaoj7WCpujAqXZB7oR47NII/hci18ND1akLka5oV+zNgQKfj+
7Z9mzhSSI+YeSR7+nxhy/YCmMUP+ryop/ba0elQXPKVQdvCPMcRm4jgGll9K3DlmLunHnVOq
LhtnLt1DhVkSRUjDKrMXyH9mqGg964F+LDqjnnXZyDLryJVyq9hQKZNAmBMkMHWQz6QpiGqm
u1YlHzVl0yyJ59cQVad6bNACdBHUW+U6R/vSEvussvlSfwWkCnx5VZAUmw39ZQ5DWPECPS+o
vYAFzeSGNHgbHuYR23Ulv+wSEFVIGt0KK3aW1KPC51JcJXQBjtTfwNI6fOnATtuxb3wQ9Auf
ZeywLFnhs4ziXUlw9EOjZkhoxnSg6sGFAqrU/AC+empqdWd827MGY+DLcz776w0UgB29poDe
mHSbN51JEvS21Rs0JxO4egb9FNBjCm5Skvt+Jkiq5dNsaEfWrcxTkVNNH6vT6o3N2AAW5NsW
3MFrkCiFpXXlM+1yNVIWIuNSpb2Y0Eo5oixHqpqj7s2dVTKpGkaBN4MlaJgSVIzbYdrrC2mC
UT4JyDZSTSSMreeDD2pDlLxj+90xcPCmhHjxipT7KRRJotdePLL0iN4g84Ee2QkXp0ntAH4a
rOXDzx/mHCkd646BamdonpIyFpdBhmcOjWgvq1SBRob/BWY2JxBd9Fhh7tAOZpvCHVfoI9Sp
WnNBLvZqKkuLhATp5jbmfJOhazEUgyKcWijGDoosMYoZ7IQ9I/kpo7fk6wqqHPuQTJfNWk3t
iHuajBjHWnQpwQsSjvb4atdr86y7wrZdU3sp4gizlFoBA2kpYPKVpkOSNgzqTpWM1Ywtf9hd
EwR7Cfj2NJOM+UA/ll6F+QD7PqfTNQQSfIbUUcGFeFI7hmyIBTYMCtdEG9+qYnOlO4lxgdCM
HfeumxmOjRFHSINtGkkKiY7h+/jsZR76Hmcq/bBdBZgqA2cVwuDEJvRJPp5Y2wuEo8Nicsms
3Gq6d75h9I8hNktSHfTDrZVVh1FxR0c/qGfIBH7vOYQ4F4Gtcw5lm2y2QHXBy2BygBwpFss7
ziMc/RhtrJZDKozhxVJ7CmqmXRE+Y3wpinsKln6sNgXNMhJNiJWUvAqpXJjY9hRsfs5XNEs/
RFsFRVN7w1PUa9fnagRoDR7jdBCkslBPOo2eg1Rd3FyKNZE8VGW0BWMCdmrkEYdmlD492JAj
VOWKQUQysgbcFgQFqbC50hMHUz8wqnd2tkk0BSeSA8QrqJwjFueFNLN5eijIE1G7vRgkL3g2
4R6sP0s84PSi8GCXeHgPAn8Pjx9zlS9uHWvG0Y0Jmw5nzHXZc4Lj62m5HpZ2UnIaPZXQf8gM
eCYF7vu3fwTntRIBizgOFSsmKFjeGdimK2vJUUnJTCx5j/a7U+pR2y86Aaczr/leQYCk2usv
gpih9sMLMDKqpLvS1KceREqyT75qWvoVajPC1WZUqD2wOjKrrMYtfc2YfzqIprlNGfsB/CNH
dMeFUzNgbIxwghxmzVOx7qRKTslJy0iCVgsmaCHnHxfWSxxiU6GmawaHQe9lvET/nE2sdzJ2
QYrOVfYk2tJfijHalboPTzFf0vnCjwKPDp3NCIcKq9gGW1UkAY1UvZ5eUfK2375r3MC8eD6B
4/WGEMCOXg9Bb7Zvbm7HKgEtBnqz1Ry3Wz3lRmSBfsY3iW/pOXAim8Fq8SRr2V+sVyvGfbiu
Viov4PthjYPzFPfeV9RVFcH44jIVSNKAD/7PbhyFzwleBqmBqpiRS/HUTe4rOw9tCfooh5vZ
VO1y356Pm2Pe6KcTZBT0MsK8gbM+rsOzxFJNmNLTQWZadSLq0dLf0qVXQcuw9c06zKHe5gIJ
tiQXKpHddcNTE6Gd82qnqTIxHCUOFrl34L0kEJ5fpqLkLAKHdX+GnfwzxqW8c7Ja+4FxoawN
ASfZBuJ/tg7L18fQFgxX6l+WENzSzpBp6eUplvPAtO2pDR4Jdg8GZVqKRMxb+kfQZSQFl+2k
MXVaSObWwTOfvPc+Es9eL6dytlDZP9i22dpT0QSIka+9QKTpz/JjyMbbX5ZL0op+ZktlDVNp
kBZejmvppw6Y4QeqLRpZOhjrj4FqWWD1u6W/j7AC6hZWrClaiK7Z0t83mK9cpRbGjEqPKd0s
uXrRoDpPLKaUZcKUezzBGRztD2fJx64CVll8BUclF0JtDppYKcixw7T3e7b0NkCU072zsQfO
XbR6ouHdBSuhpwJaXu9OOsQ2CCSne4tOptBkVvA4uVxzptF37SokM0h/J6JzwWGLE2Q/7gKh
V/tCnJKE0euPmt1Rb68Myjnz5cShArCj1xTQbxvj8V13P92oI8eh2b89g34i6KVX8jDDJTTe
Y/T8N/XJ5Wg+52Qur1x+ImFWzN8Pdh+cmbsEfQwHdBLsq4kPp8PsNSxhiYsg2THbDm5r5k/0
rpt6yxwGbQ9wiLA5nZLimwTa+nvWM5Y8yrZJQKyIDcvIB+VGUjploGoamnyDwUAMSOY8Xbzj
cZpxvCTPjKsTZWLdilOT/vp2Rky3bP76gWdjsnueM/PrL8frLY2UMwIm7WZVQLjwFK+9oGuK
Hv0kwA+k/kWF9SkuCNor0K1euiDcDNqjRtlXj7DBuyVj2WSpa4FxltVegE6TihyWLZewRIxq
cnJpBnPAOWdz4hEux1ya0fO1i8/Hl5Suj4H/k1e/ua2dLFEFuyodTVs+t6RPRaTYD6aMSrFC
UC4gXMnOlSr99erKSpWAeqkGi1JwKrPtYroMMrDRjB+UeDZsLokZ2h39TINKGtox9uho75Ks
ghWaEeVXFn3xGH9He6vhEXFMhbs03HQ8OdIIrcu0dU0ZyBenXHdeJbBcDUtFTeQmWyrhkck5
k/mrRKHLJxYQaK5giYgVgyq+RFzkuDod/Yh6ZY0VyNszmT8EOUhMikvKq4TcqyEpSIIkCmdz
d14lbF1Ca2+4Z7vuWDmOjn6Ir28GOvPoQJCqTFtRvDe3NElHPziXIg/GLfIwj6DgiPY9ytl1
2kCeze2veYO8ZLzwrNLVj9wZwpsVY03sOByqpeStaHT1Y5JVIE0cK+xRWK/0Q5CG6FWUZlyp
2gkpFYhy1Ew/HFcFNfudCIs2yTcqNHE2U4webxV42khqtRnP59VyU8ZhdnPKFsLWTXMwbjUh
enLet/l68APY0esh6J1Gs21NGqMk6K3W7bjTDeqd6YCeVMbfZiTis4x+GH+gZpmgvbcY0peM
XLJP+nHooE9mMqkrH+ET8Rw4Bu0Bz8kNJ/iLuiui0ruvK8Ip8WyyPQqgkPWqH8VNwbmM1utP
6rS4KpmuwSpQjrWqH3c2Weci9Vkor/CJYJc46ohmRIWQPmIoPYW0TD9mbYiW2ZKofPnjgFuV
dI16ckpnkpLxlLrUN7wUQpxE9MPxVSARVU2BqGpfNNqK4Balj55+6NYU+lhg1yXefG8ru+Hk
oTKTIBBJOUHOmkAhbNlH2L0CB6tN1cHpZjNKucd16JCVyzZwCsiFKpdDbdhx5G6CqipyOGd0
vg6GEw7Og4xy7Mn/1yI4Mh357Dy+73h8p7CL7H+J7RMnrGYgBw6DtlJhr1Wpeknzj/ILoLCD
q332SglRdBuNQbM7goUZg+JCbxAniOATEt2HrRwdw0V1df4Iv/csp1Qr7NNCZZS0QzFYzX/A
0KLPVmqTvvoKh2KFuz+nzPfZcve3S2axTxcEO4Bez1J/zhhTYIZ/ztd+iG0kjtDXUFngO+qy
w+w/c+qEiD9Q35ZP2eqqT+tRv9XbKXM2gc0Qnjk0/DcAAAD//wMAUEsDBBQABgAIAAAAIQDc
PO1bIQEAACgEAAAcAAgBd29yZC9fcmVscy9kb2N1bWVudC54bWwucmVscyCiBAEooAABAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKyTzU7DMBCE70i8g+U7cVKg
IFSnF4TUK5QHcJzNj4i9lr0F8vZYLW1TKBGHHHesnfl2JC+Wn6Zj7+BDi1byLEk5A6uxbG0t
+ev66eqes0DKlqpDC5L3EPgyv7xYPEOnKC6FpnWBRRcbJG+I3IMQQTdgVEjQgY0vFXqjKI6+
Fk7pN1WDmKXpXPihB89PPNmqlNyvymvO1r2D/3hjVbUaHlFvDFg6EyECEMXLQvRUvgaSfK8k
0YuL8wh3UyJQ3IVj/nbcidkYw2zSGqjvYFjCdh6Lz6aMtxtTgI+tHwkO0hjE/A8I02qPAStK
NJrv/JibZT9yHaDrBt3v5rHE2ynPrtDSWhVDgoM0BnEzJcQHFC+/PsFA3IOIk/+dfwEAAP//
AwBQSwMEFAAGAAgAAAAhALb0Z5jSBgAAySAAABUAAAB3b3JkL3RoZW1lL3RoZW1lMS54bWzs
WUuLG0cQvgfyH4a5y3rN6GGsNdJI8mvXNt61g4+9UmumrZ5p0d3atTCGYJ9yCQSckEMMueUQ
QgwxxOSSH2OwSZwfkeoeSTMt9cSPXYMJu4JVP76q/rqquro0c+Hi/Zg6R5gLwpKOWz1XcR2c
jNiYJGHHvX0wLLVcR0iUjBFlCe64Cyzcizuff3YBnZcRjrED8ok4jzpuJOXsfLksRjCMxDk2
wwnMTRiPkYQuD8tjjo5Bb0zLtUqlUY4RSVwnQTGovTGZkBF2DpRKd2elfEDhXyKFGhhRvq9U
Y0NCY8fTqvoSCxFQ7hwh2nFhnTE7PsD3petQJCRMdNyK/nPLOxfKayEqC2RzckP9t5RbCoyn
NS3Hw8O1oOf5XqO71q8BVG7jBs1BY9BY69MANBrBTlMups5mLfCW2BwobVp095v9etXA5/TX
t/BdX30MvAalTW8LPxwGmQ1zoLTpb+H9XrvXN/VrUNpsbOGblW7faxp4DYooSaZb6IrfqAer
3a4hE0YvW+Ft3xs2a0t4hirnoiuVT2RRrMXoHuNDAGjnIkkSRy5meIJGgAsQJYecOLskjCDw
ZihhAoYrtcqwUof/6uPplvYoOo9RTjodGomtIcXHESNOZrLjXgWtbg7y6sWLl4+ev3z0+8vH
j18++nW59rbcZZSEebk3P33zz9Mvnb9/+/HNk2/teJHHv/7lq9d//Plf6qVB67tnr58/e/X9
13/9/MQC73J0mIcfkBgL5zo+dm6xGDZoWQAf8veTOIgQyUt0k1CgBCkZC3ogIwN9fYEosuB6
2LTjHQ7pwga8NL9nEN6P+FwSC/BaFBvAPcZoj3Hrnq6ptfJWmCehfXE+z+NuIXRkWzvY8PJg
PoO4JzaVQYQNmjcpuByFOMHSUXNsirFF7C4hhl33yIgzwSbSuUucHiJWkxyQQyOaMqHLJAa/
LGwEwd+GbfbuOD1Gber7+MhEwtlA1KYSU8OMl9BcotjKGMU0j9xFMrKR3F/wkWFwIcHTIabM
GYyxEDaZG3xh0L0Gacbu9j26iE0kl2RqQ+4ixvLIPpsGEYpnVs4kifLYK2IKIYqcm0xaSTDz
hKg++AElhe6+Q7Dh7ref7duQhuwBombm3HYkMDPP44JOELYp7/LYSLFdTqzR0ZuHRmjvYkzR
MRpj7Ny+YsOzmWHzjPTVCLLKZWyzzVVkxqrqJ1hAraSKG4tjiTBCdh+HrIDP3mIj8SxQEiNe
pPn61AyZAVx1sTVe6WhqpFLC1aG1k7ghYmN/hVpvRsgIK9UX9nhdcMN/73LGQObeB8jg95aB
xP7OtjlA1FggC5gDBFWGLd2CiOH+TEQdJy02t8pNzEObuaG8UfTEJHlrBbRR+/gfr/aBCuPV
D08t2NOpd+zAk1Q6Rclks74pwm1WNQHjY/LpFzV9NE9uYrhHLNCzmuaspvnf1zRF5/mskjmr
ZM4qGbvIR6hksuJFPwJaPejRWuLCpz4TQum+XFC8K3TZI+Dsj4cwqDtaaP2QaRZBc7mcgQs5
0m2HM/kFkdF+hGawTFWvEIql6lA4MyagcNLDVt1qgs7jPTZOR6vV1XNNEEAyG4fCazUOZZpM
RxvN7AHeWr3uhfpB64qAkn0fErnFTBJ1C4nmavAtJPTOToVF28KipdQXstBfS6/A5eQg9Ujc
91JGEG4Q0mPlp1R+5d1T93SRMc1t1yzbayuup+Npg0Qu3EwSuTCM4PLYHD5lX7czlxr0lCm2
aTRbH8PXKols5AaamD3nGM5c3Qc1IzTruBP4yQTNeAb6hMpUiIZJxx3JpaE/JLPMuJB9JKIU
pqfS/cdEYu5QEkOs591Ak4xbtdZUe/xEybUrn57l9FfeyXgywSNZMJJ1YS5VYp09IVh12BxI
70fjY+eQzvktBIbym1VlwDERcm3NMeG54M6suJGulkfReN+SHVFEZxFa3ij5ZJ7CdXtNJ7cP
zXRzV2Z/uZnDUDnpxLfu24XURC5pFlwg6ta054+Pd8nnWGV532CVpu7NXNde5bqiW+LkF0KO
WraYQU0xtlDLRk1qp1gQ5JZbh2bRHXHat8Fm1KoLYlVX6t7Wi212eA8ivw/V6pxKoanCrxaO
gtUryTQT6NFVdrkvnTknHfdBxe96Qc0PSpWWPyh5da9Savndeqnr+/XqwK9W+r3aQzCKjOKq
n649hB/7dLF8b6/Ht97dx6tS+9yIxWWm6+CyFtbv7qu14nf3DgHLPGjUhu16u9cotevdYcnr
91qldtDolfqNoNkf9gO/1R4+dJ0jDfa69cBrDFqlRjUISl6joui32qWmV6t1vWa3NfC6D5e2
hp2vvlfm1bx2/gUAAP//AwBQSwMEFAAGAAgAAAAhAHmcjxKCBAAAag0AABEAAAB3b3JkL3Nl
dHRpbmdzLnhtbLRX32/iOBB+P+n+B5Tno/mdQLR0BQSuXZXbU+nqnk1iwGocR7YDZVf3v9/Y
iQnd5lbtrvrSOvPNfDMez4zNh49PtBgcMBeElRPLvXKsAS4zlpNyN7G+PCyHI2sgJCpzVLAS
T6wTFtbH699/+3BMBJYS1MQAKEqR0Gxi7aWsEtsW2R5TJK5YhUsAt4xTJOGT72yK+GNdDTNG
KyTJhhREnmzPcSKrpWETq+Zl0lIMKck4E2wrlUnCtluS4fafseCv8duYpCyrKS6l9mhzXEAM
rBR7UgnDRn+WDcC9ITn8aBMHWhi9o+u8YrtHxvOzxWvCUwYVZxkWAg6IFiZAUnaOgxdEZ99X
4LvdoqYCc9fRq8vIw7cReC8Iogw/vY1j1HLYYHnJQ/K38URnHtIl1o1+LpgLApHLfP8mFs/k
1Va2SKI9EucqUoz4bUGFZ7oT7XIkitdUTQPdkQ1HvOnJtmRoltzuSsbRpoBwoHQGcPoDHZ36
C0lU//QSP2m5yoN1DTPiK2N0cEwqzDNoFBgwjmPZCpAcZY/3+EDU4BFalOMtqgv5gDZrySqw
OiCIO/Zai2yPwEZivq5QBmU9Z6XkrDB6OfuLyTmMFQ5V31roIdOt1s3AAosSUdjJsyG0YjlM
lGNSc/L6lCsD7d0NL11+74jBgOUkxw8qg2t5KvASgl+Tr3ha5p9qIQkw6lH0CxH8KABcKs+f
4cwfThVeYiRrSNM7OdMnsSxItSKcM35b5nD07+aMbLeYgwOCJF5B+RDOjjrPNxjlcK+9k99a
4H9AGVrOf1ClPGNSMnpzqvaQ6187SV3v9mX5wu2cC7O4Z0yeVZ2RH48XyyZShXaIG7hBtOhH
gnAZ9CLTaLbw+hAv9OM07UXiMPXmvUjqT71em2Dm+m5v1KHnOkHb8c+RaO4t4t79RGns+3Ef
EjtBMO/dT5x67qg3gpEbzzy/F/nfXM/GwdTp3Wk6jkbuqA9ZLOOl37vTZewuRr3nsxxF8VyP
GvtcFTRRL4+/uVmp0TKgjcUc0Q0naLBSbxNbaWz444yUBt9guADwJbKuNwYcDhtAUFQUSyhy
A+igaZITUaV4q9fFCvFdx9tq8F4pzPlPZy51LWD+J2d11aBHjqpmZBgVKNfWkpTyjlAjF/Vm
baxKuLIuoLrMPx+4zlOXHrh0oAX16L1DupW1Li6HX9Ztqxd8rdoUr1BVNd2+2bkTqyC7vXRV
g0r4yuEJqz82O6/FPI15DaY/UKZ2BtrtopN5Rnah5xuZ38kCIws6WWhkYSeLjCxSsj3Md16Q
8hEGj1kq+ZYVBTvi/KbDX4iaJIg9qnDa3MVQXqwRtJezGBwS/AQXOc6JhF8GFckpelL3uhcp
81a7QCdWy2e6ClPK1XMG9eZpR639zFiX+HexqDdCRqAc1ye66a7+qybwgggY0xW8EiTjBvtD
Y26Q5Cy7Ve+UoJH7i3k8gsnVwKF+XUg9yeHc7/F2hgTOW8yYho3pt9jxp36azofjcTgdBrMw
Gs5mi3Dojp1w7MymU993/m2b1PxIuv4PAAD//wMAUEsDBBQABgAIAAAAIQD7cfkcDQQAAMYf
AAASAAAAd29yZC9udW1iZXJpbmcueG1s7JfLbts4FIb3A/QdBO0T3WVHqFOkcV1k0CkGaAaz
piXaIsKLQNK3bV+mj9DH6isMKVmyHbWBRKdTYTKb0CZ5Ph3+4jn+8/rNlmBrDblAjE5s79K1
LUhTliG6nNh/3c8uxrYlJKAZwIzCib2Dwn5z/eq315uErsgccrXRUgwqkk2RTuxcyiJxHJHm
kABxSVDKmWALeZky4rDFAqXQ2TCeOb7rueWngrMUCqE4t4CugbD3uHTbjZZxsFHBGhg6aQ64
hNsDw+sNiZwrZ9wG+QYgdULfa6OC3qjY0Vm1QKERSGXVIkVmpO8cLjYj+W3SyIwUtEljM1Lr
OpH2BWcFpGpxwTgBUn3lS4cA/rAqLhS4ABLNEUZyp5huXGMAog8GGamohkCCrDdh5BCWQRxk
NYVN7BWnyT7+oonXqSdV/H6oI3iX81chU5auCKSyPLnDIVZaMCpyVDQVTkxpajGvIeunDrEm
uN63KbyO5fKj9jStpDwAu6S/15/gKvOniZ7b4Y1oRBPRJYXTZ9aZEHULDw82kuZIXK9jA6kB
fgsQp7Bjw68Z4z3DSQ8VqjmoY2nUnOqtaA46COt17GOPkzkCiExmeS+KX+vq6FggQQ5Ec9E1
EfZLKmpwO3KkUbE8rxDec7YqDjR0Hu3u0NY22mH0YO0L6rjIxXnJfMpBobodSZO7JWUczLHK
SJWHpW64Vb4B/VddFD2UH+G2nNfv2tI9xr5W1gjMheQglR9XxDr5dqfuprJYipZwqHwV15OV
i7pZSMjfcgge9BZNoUI/J1kDPLHDYBpG0ezWdvQKWWGJPsA1xPe7AtZ78t2co+wPvYb1WrVX
kgLXO25mUTy7ct9VK3itF5AaqqQSWWD1C+eG7pXrul6ZQ5ljHe5Vccr4zUgzOV9hDGVDvIfb
Zunb56/N/O9pPYvhYr+9+JPrAVF9TD09sUfxWGeSA7osLWgQu3qv02zm+2HGqBRaXJEidQM/
7cic4TL0Rul2MoGoAmdwAZQye1hJccrEHivhtZQIyhn166N+wtZQ7zhbGdZXFy8cmwlzy1Yc
QW59hJsjdR7NpqK9sZ9qfku16PlV+/b5S1/dfN810+1vtVv/FySOVDud6ydQdYlOC+wnCNS7
4Pwr/1dXXDjIigvicNAVV9XX8CouDAxb+HNXXDzQiotcw1b+fBU3GmTFRWPDXv0vVVyZ3AAr
Lo4MW/j5FeecuFv9jCetry7A3tY3jm/jUTA90/p676Zu/DaOG3Gb1zoY6+uXmfxvfR/p4oWh
mTAv3fp6sZluL8b6jse/uuKGan3dQVfccK2vYQt/OdbXsJX/563vyLBXv3TrGxq28J9hfWlp
eWltdfXUif+tT1RnSL8T5v84rJSzDqvGyj5f/wMAAP//AwBQSwMEFAAGAAgAAAAhAOMtD2qF
DAAAEnkAAA8AAAB3b3JkL3N0eWxlcy54bWzsnVtz27gVx9870+/A0VP74MjyRU4y692xnbj2
bJx4I6d5hkjIQk0SKi++9NMXACkJ9CEoHvCs+9KXxCJ5fgDxx/8Q4PWX356TOHjkWS5kejqa
vNsfBTwNZSTS+9PRj7vLvfejIC9YGrFYpvx09MLz0W+//vUvvzx9zIuXmOeBAqT5xyQ8HS2L
YvVxPM7DJU9Y/k6ueKpWLmSWsEL9zO7HCcseytVeKJMVK8RcxKJ4GR/s709HNSbrQ5GLhQj5
JxmWCU8LEz/OeKyIMs2XYpWvaU99aE8yi1aZDHmeq51O4oqXMJFuMJMjAEpEmMlcLop3amfq
GhmUCp/sm7+SeAs4xgEOAGAa8mcc433NGKtImyMiHGe64YjI4vhVxgLkUREtUZSDdbuOdSwr
2JLlS5vIcZU63uBeEt1GSfjx+j6VGZvHiqRUD5RwgQHrf9X+6//Mn/zZLNe7MPpVeSGS4Se+
YGVc5PpndpvVP+tf5r9LmRZ58PSR5aEQd6qCqpREqAKvztJcjNQazvLiLBesdeVS/9G6JswL
a/G5iMRorEvM/6NWPrL4dHRwsF5yoWvQWBaz9H69jKd7P2Z2TaxFc8U9HbFsb3amA8f1jlX/
W7u7ev3LFLxioTDlsEXBlc0n030NjYXOKgfHH9Y/vpe68VlZyLoQA6j+32DHoMWV+1UumFUp
Sa3liy8yfODRrFArTkemLLXwx/VtJmSm0s7p6IMpUy2c8URciSjiqbVhuhQR/7nk6Y+cR9vl
f1ya1FEvCGWZqr8PT6amF8R59Pk55CudiNTalGlNvuqAWG9dim3hJvzfa9ikVqItfsmZzsbB
5DXCVB+FONARubW37czy1b6brVAFHb5VQUdvVdDxWxU0fauCTt6qoPdvVZDB/JkFiTRSid9s
D4sB1F0chxvRHIfZ0ByHl9Ach1XQHIcT0BxHR0dzHP0YzXF0UwSnkKGrF1qd/dDR27u5u48R
ftzdhwQ/7u4jgB93d8L34+7O737c3encj7s7e/txdydrPLcaagXXymZpMdhlCymLVBY8KPjz
cBpLFctMUWl4+qDHM5KdJMBUma0+EA+mhcz83t1DjEn9j+eFnukFchEsxH2Z8XxwxXn6yGO5
4gGLIsUjBGa8KDNHi/j06YwveMbTkFN2bDqongkGaZnMCfrmit2TsXgaETffmkiSFDYdWs2f
l9okgqBTJyzM5PCqSUaWH76IfHhbaUhwXsYxJ2J9pelihjV8bmAww6cGBjN8ZmAwwycGlmZU
TVTTiFqqphE1WE0jareqf1K1W00jareaRtRuNW14u92JIjYp3h51TPqfu7uIpb6oMLgeM3Gf
MjUAGH64qc+ZBrcsY/cZWy0DfVa6HWvvM7accxm9BHcUx7QNiWpcb7rIhdprkZbDG7RBozLX
hkdkrw2PyGAb3nCL3ahhsh6gXdHMZ2blvGg1rSH1Mu2MxWU1oB3uNlYM72FbA1yKLCezQTuW
oAd/1cNZLSdF5tvWcnjFtqzhtnqdlUirVyMJahnL8IEmDV+9rHimpmUPg0mXMo7lE4/oiLMi
k1Vfsy1/YCTpZfnPyWrJcmHmSg1E/0P9+naE4IatBu/QbcxESqPb572EiTigG0Fc3d18Ce7k
Sk8zdcPQAM9lUciEjFmfCfzbTz7/O00Fz9QkOH0h2tszotNDBnYhCA4yFUlGRCQ1zBSpIDmG
Gt7v/GUuWRbR0G4zXt0BVHAi4owlq2rQQeAtlRefVP4hGA0Z3j9ZJvR5ISpT3ZHArNOGeTn/
Fw+Hp7qvMiA5M/StLMz5RzPUNdF0uOHDhAZu+BDBqKkOD7r/EuxsAzd8Zxs4qp29iFmeC+cl
VG8e1e6uedT7O3zyV/NkLLNFGdM14BpI1oJrIFkTyrhM0pxyjw2PcIcNj3p/CbuM4RGckjO8
f2QiIhPDwKiUMDAqGQyMSgMDIxVg+B06Fmz4bToWbPi9OhWMaAhgwaj6Genhn+gqjwWj6mcG
RtXPDIyqnxkYVT87/BTwxUINgukOMRaSqs9ZSLoDTVrwZCUzlr0QIT/H/J4RnCCtaLeZXOhH
Q2Ra3cRNgNTnqGPCwXaFoxL5J5+TVU2zKOtFcEaUxbGUROfWtgccE9m8d21XmHmSY3AVbmMW
8qWMI5459skdq+bLs+qxjNfVN9Xoddrzi7hfFsFsuTnbb2Om+zsj1xP2RtjuAtvafLp+nqUt
7IZHokzWFYUPU0wP+webHt0IPtodvB1JNCKPe0bCMqe7I7ej5EbkSc9IWOb7npHGp43ILj98
YtlDa0c46eo/mzmeo/OddPWiTXBrsV0daRPZ1gVPunpRwyrBWRjqqwVQnX6eccf3M487HuMi
NwVjJzelt6/ciC6DfeePQh/ZMUnTlLe5ewLkfTOI7pU5/yhldd6+ccGp/0Nd12rglOY8aOUc
9r9w1cgy7nbsnW7ciN55x43onYDciF6ZyBmOSkluSu/c5Eb0TlJuBDpbwSMCLlvBeFy2gvE+
2QpSfLLVgFGAG9F7OOBGoI0KEWijDhgpuBEoo4JwL6NCCtqoEIE2KkSgjQoHYDijwnicUWG8
j1EhxceokII2KkSgjQoRaKNCBNqoEIE2qufY3hnuZVRIQRsVItBGhQi0Uc14cYBRYTzOqDDe
x6iQ4mNUSEEbFSLQRoUItFEhAm1UiEAbFSJQRgXhXkaFFLRRIQJtVIhAG7V61NDfqDAeZ1QY
72NUSPExKqSgjQoRaKNCBNqoEIE2KkSgjQoRKKOCcC+jQgraqBCBNipEoI1qLhYOMCqMxxkV
xvsYFVJ8jAopaKNCBNqoEIE2KkSgjQoRaKNCBMqoINzLqJCCNipEoI0KEV39s75E6brNfoI/
6+m8Y7//pau6Ut/tR7lt1GF/1LpWblb/ZxHOpXwIWh88PDTzjX4QMY+FNKeoHZfVba65JQJ1
4fPbRfcTPjZ94EuX6mchzDVTAD/qGwnOqRx1dXk7Ekzyjrp6uh0JRp1HXdnXjgSHwaOupGt8
ub4pRR2OQHBXmrGCJ47wrmxthcMm7srRViBs4a7MbAXCBu7Kx1bgcaCT8+vo457tNN3cXwoI
Xd3RIpy4CV3dEmq1TsfQGH1FcxP6qucm9JXRTUDp6cTghXWj0Aq7UX5SQ5thpfY3qpuAlRoS
vKQGGH+pIcpbaojykxomRqzUkICV2j85uwleUgOMv9QQ5S01RPlJDQ9lWKkhASs1JGClHnhA
dmL8pYYob6khyk9qOLjDSg0JWKkhASs1JHhJDTD+UkOUt9QQ5Sc1mCWjpYYErNSQgJUaEryk
Bhh/qSHKW2qI6pLanEVpSI1S2ArHDcKsQNwB2QrEJWcr0GO2ZEV7zpYsgudsCWq11hw3W7JF
cxP6qucm9JXRTUDp6cTghXWj0Aq7UX5S42ZLbVL7G9VNwEqNmy05pcbNljqlxs2WOqXGzZbc
UuNmS21S42ZLbVL7J2c3wUtq3GypU2rcbKlTatxsyS01brbUJjVuttQmNW621Cb1wAOyE+Mv
NW621Ck1brbklho3W2qTGjdbapMaN1tqkxo3W3JKjZstdUqNmy11So2bLbmlxs2W2qTGzZba
pMbNltqkxs2WnFLjZkudUuNmS51S42ZLNypEELwCapawrAjo3hd3xfJlwYa/nPBHmvFcxo88
Cmh39QtqL8dPjc9fabb5Np/avlBtpt+Abj2uFFVvgK2BZsPraPOZKh2saxLUHwSrF5sK15dr
qxJNICwqXKqywvrdVY6i6nfQbh6iMm+gfV2w40W1piLbDrjeum7SbXtV2zVaq7Pehe7wHXU2
huhso8ozrgp+qJPArhqq+szj6pNp6o/rNFKAp/pzYVVNo2dWodT6Cx7HN6zaWq7cm8Z8UVRr
J/vmlQWv1s+rt+854zOTpp2AcbMy1c/6s22O9q7ex1/fP+DskjoXtTS3uZllaEu769awS1jm
qmmMs17X716/WXFvNQE13KyoGpepAr9piwNHZbnQApvl+/vvD08+fL6s1oDP5s31K+t0FfaN
QNXPs7KQ9SZ15dZf16u2Mr/gRvVH9442X+Br/+ie48uFygwi4XnwlT8F32XCTNLbfi+wZaX5
cmHrmjCHiyv1tp8urG+aaHy60CyzvkDYJxvtVDJ3KZm3K9maxzp1paopW61ivhfK9JFnBY/2
tLzcUfn2bf/s/UF66MDloXp48X8P/c881FByo5vOwNunoF+LZ8aQ29W7JIRJ/LCu8HbI8Vro
o/PJ4aQptDBHS32s03c01sPlUL9g5rkoWVy/68ISZ7vT67/yX/8LAAD//wMAUEsDBBQABgAI
AAAAIQC5LDVhKQIAANYMAAAUAAAAd29yZC93ZWJTZXR0aW5ncy54bWzsl0uP2jAQx++V+h0i
35c86gBBCyvR1VaVtg+1296NY4hV2xPZhsB++tp5sKH0sKm0bQ9c4vE488s88ifi+mYvRbBj
2nBQcxSPIhQwRSHnajNH3x7urqYoMJaonAhQbI4OzKCbxetX19WsYquvzFp3pwkcRZmZpHNU
WFvOwtDQgkliRlAy5Q7XoCWxbqs3oST6x7a8oiBLYvmKC24PYRJFY9Ri9HMosF5zym6BbiVT
to4PNROOCMoUvDQdrXoOrQKdlxooM8bVI0XDk4SrIybGZyDJqQYDaztyxbQZ1SgXHke1JcUT
IB0GSM4AY8r2wxjTlhG6yD6H58M44yOH5z3OnyXTA5jc5sUgStL1NfSxxJKCmKJPZMOSSo+4
g/Q9knT2fqNAk5VwJDf1wA0uqMH+6ur3S22yfe33JaCFE0TOd6Zdg2rmW4wnaYxxGk/q8xXk
h9v6bEeEExsKvdfJ4Z6tbeeNjt4vfFP8xv0A5blzCdaC/MXv8ljm2lv2KUY5GSO3MY/+Pm+U
hLLWpiDAqY9sLTQI0ctsWOTqJKNhsbpf+ZDQsF+0H8fbgov8dCZxFsc4m0RvcD2US/tfpP2N
2a3dHDpvfx6TSZpFOMPNOC4a+R80gsdJNk2S6UUhL6+QEy3gLMVplF1+mv5y45NomsWpe+Wb
L/Wl8//go9B6/cOgtFzyR3YHeqmhMkw3OTBx+KS+f7ivd0QIqD5/fNc8o/dvZPETAAD//wMA
UEsDBBQABgAIAAAAIQAjaNW9ZwIAAKIKAAASAAAAd29yZC9mb250VGFibGUueG1s3JXbjtow
EIbvK/UdIt8vORAOixZWXbpIlapetFv12jgOsRrbkccs8PYdO4EFBSrSqlu1iZI4Y8+X8e8Z
5+5+K8vgmRsQWk1J3ItIwBXTmVCrKfn6tLgZkwAsVRktteJTsuNA7mdv39xtJrlWFgL0VzCR
bEoKa6tJGAIruKTQ0xVX2JlrI6nFV7MKJTXf19UN07KiVixFKewuTKJoSBqMuYai81ww/l6z
teTKev/Q8BKJWkEhKtjTNtfQNtpkldGMA+CcZVnzJBXqgInTFkgKZjTo3PZwMk1EHoXuceRb
snwBDLoBkhZgyPi2G2PcMEL0POaIrBtneOCI7Ijza8EcASCzWdGJkux1DZ0vtbSgUBwTebeg
BgfcTjqNJJt8WClt6LJEEq56gAsXeLC74/zdwzf51tvdFMisKYVgM1FUoueXnVzq0tsrqjTw
GLueaTkl0QDPOHIpMoqG+BxEIxK6gaygBrhj1AOT2pxTKcrd3mq0pKruqIRlxd7+TI1wQddd
IFbYsYZlhJzmILUlxgo/tSStMf1TC/Oc8aklPhqD3wxrAVpCPAnJIfjEN8FnH/k5RdyyDqM+
KpHilWArPa+I/9LvK/KIMSePi8WLInO0jMaDh5Yitz9TxL/GNed6ReZ6bQQ3TpMLaoxQgVuv
ilMj7aSG1Bk35+TIxZZn12uR9l9Di2+43brfDFyolNbRoVLo2up/qFDmtBRLIy6kxMKngjtT
TI6kU0rARgB0K5D0XFIk6ehVCuQdhnV+60yiB9wo0kYJr8af1cHN+u9tFHVGBB/FqrAX88Jl
w3+aF00DZj8AAAD//wMAUEsDBBQABgAIAAAAIQDwJBCsXQIAAOIJAAAPAAAAd29yZC9wZW9w
bGUueG1spJbLjpswFIb3lfoOiH1iIEOGQUlm0VGrSN211awd2wlW8EW2geTtaxMuaWlHQDYB
Yv+ffx+fc+TN64XlXkmUpoJv/XAZ+B7hSGDKT1v/18+vi8T3tIEcw1xwsvWvRPuvu8+fNlUY
p5IImRPPIrhOK4m2fmaMTAHQKCMM6iWjSAktjmaJBAPieKSIgEooDKIgDOo3qQQiWtv1vkBe
Qu03OHQZR8MKVlbsgE8AZVAZcukZ4WRIDF5AMgRFM0B2h1E4RK0mo9bAuRqAnmaBrKsBKZ5H
+sfm1vNI0ZD0PI+0GpKSeaRBOrFhggtJuB08CsWgsZ/qBBhU50IuLFhCQw80p+ZqmcG6xUDK
zzMcWVVHYCs8mfAMmMAkX+GWIrZ+oXja6Bed3llPb/rm0SrUmP3fJG8CFYxwU+8cKJLbWAiu
Myq7CmdzaXYwayHlR5soWd7Oq2Q4slz+157ebqHsgWPsN/Fn+c35x8QwGHEiDtEpxlj4c83W
CbNZ2C88KzR3wQ1HNpAWEA0Aa0RGNvyWkTQMgPoKdRw6sjRazu1UHIf2gQ1H9rG/zdwBNDY4
m0SJ2rgCp4UGZlB3ie6IZJqpuMNd2V2M5OmxQvimRCF7Gn2Mtu/bWuUuGBNYTUHdF7l+zMyP
DErb7RhK9ycuFDzk1pEtD89muFefgPu1ieIe9Su51P+7s/Zcj/F3zc1IacGdLIWFyYTtnBiW
xLNe0JmodpYi2t62yJ4fRT3XOikpJmpvc/idciwq7X2npbXkRgt9G0EoDl6SeAUPhyDGCfLB
bgP6VbsPdznb/QYAAP//AwBQSwMEFAAGAAgAAAAhAG8BqMd1AQAA8AIAABEACAFkb2NQcm9w
cy9jb3JlLnhtbCCiBAEooAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAIySX0+DMBTF3038DqTv0LI/RgmwRM2eXGLijMa32t5tddA2bTe2b2+BwUT34Nu9Pef+
uJw2nR3KItiDsULJDMURQQFIpriQ6wy9LufhLQqso5LTQknI0BEsmuXXVynTCVMGno3SYJwA
G3iStAnTGdo4pxOMLdtASW3kHdKLK2VK6nxr1lhTtqVrwCNCbnAJjnLqKK6Boe6J6ITkrEfq
nSkaAGcYCihBOovjKMZnrwNT2osDjfLDWQp31HDR2om9+2BFb6yqKqrGjdXvH+P3xdNL86uh
kHVWDFCecpY44QrIU3wufWV3n1/AXHvcN75mBqhTJud0DwEzim3BNKZOqCPfwrFShls/Pui8
jYNlRmjnL7KFDw68u6DWLfzNrgTw++Ov7/zV6xEDe1G/jDwmjaXv01PO7XLAA59P0qbZKW/j
h8flHOUjMopDchOS8TK+S6bThJCPer/B/BlYnjb4D3GyJCSJJ0NiB2gjGr7R/BsAAP//AwBQ
SwMEFAAGAAgAAAAhACoqH9zhAQAA4QMAABAACAFkb2NQcm9wcy9hcHAueG1sIKIEASigAAEA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAnFNNbxMxEL0j8R9WvjdO
UhJo5LhCqVAPQCNl256Ndzax8NqWPY0afj3jXbI4wIk9vfnY5+c3Y3H72tnqCDEZ79ZsNpmy
Cpz2jXH7NXusP119YFVC5RplvYM1O0Fit/LtG7GNPkBEA6kiCpfW7IAYVpwnfYBOpQmVHVVa
HzuFFMY9921rNNx5/dKBQz6fTpccXhFcA81VGAnZwLg64v+SNl5nfempPgXik6KGLliFIL/m
P+2k8dgJPmZF7VHZ2nQg54sbKoyh2Ko9JDkTfADi2ccmycViLvgAxeagotJIHsrr2YI6i4T4
GII1WiHZK78YHX3yLVYPveYqEwhetgi6xw70SzR4klPBy1B8No4UzJeCD4i0RbWPKhySfJ8F
jpHYaWVhQxbIVtkEgv9OiHtQebxbZbLAI66OoNHHKpkfNOA5q76pBNm4NTuqaJRDNrQNQY9t
SBhlbdAS9xj3sGwrsXmXXRzAZWMf9BoIX6rrT0gPLd0N/yF2VortNQxSCzmlsvMZf7BufBeU
I4P5iMjg7+kx1P4ur8cvDy+TxdyfDR52QWmayfXyZlluQFESO8pCQyMdhzImxD1dIdp8AP3r
9tCce/4u5J16Gl6snC0nU/r6JTrnaBPGpyR/AgAA//8DAFBLAQItABQABgAIAAAAIQCw3PgA
bgEAACQGAAATAAAAAAAAAAAAAAAAAAAAAABbQ29udGVudF9UeXBlc10ueG1sUEsBAi0AFAAG
AAgAAAAhAB6RGrfvAAAATgIAAAsAAAAAAAAAAAAAAAAApwMAAF9yZWxzLy5yZWxzUEsBAi0A
FAAGAAgAAAAhAEokmYX9FwAAsGgBABEAAAAAAAAAAAAAAAAAxwYAAHdvcmQvZG9jdW1lbnQu
eG1sUEsBAi0AFAAGAAgAAAAhANw87VshAQAAKAQAABwAAAAAAAAAAAAAAAAA8x4AAHdvcmQv
X3JlbHMvZG9jdW1lbnQueG1sLnJlbHNQSwECLQAUAAYACAAAACEAtvRnmNIGAADJIAAAFQAA
AAAAAAAAAAAAAABWIQAAd29yZC90aGVtZS90aGVtZTEueG1sUEsBAi0AFAAGAAgAAAAhAHmc
jxKCBAAAag0AABEAAAAAAAAAAAAAAAAAWygAAHdvcmQvc2V0dGluZ3MueG1sUEsBAi0AFAAG
AAgAAAAhAPtx+RwNBAAAxh8AABIAAAAAAAAAAAAAAAAADC0AAHdvcmQvbnVtYmVyaW5nLnht
bFBLAQItABQABgAIAAAAIQDjLQ9qhQwAABJ5AAAPAAAAAAAAAAAAAAAAAEkxAAB3b3JkL3N0
eWxlcy54bWxQSwECLQAUAAYACAAAACEAuSw1YSkCAADWDAAAFAAAAAAAAAAAAAAAAAD7PQAA
d29yZC93ZWJTZXR0aW5ncy54bWxQSwECLQAUAAYACAAAACEAI2jVvWcCAACiCgAAEgAAAAAA
AAAAAAAAAABWQAAAd29yZC9mb250VGFibGUueG1sUEsBAi0AFAAGAAgAAAAhAPAkEKxdAgAA
4gkAAA8AAAAAAAAAAAAAAAAA7UIAAHdvcmQvcGVvcGxlLnhtbFBLAQItABQABgAIAAAAIQBv
AajHdQEAAPACAAARAAAAAAAAAAAAAAAAAHdFAABkb2NQcm9wcy9jb3JlLnhtbFBLAQItABQA
BgAIAAAAIQAqKh/c4QEAAOEDAAAQAAAAAAAAAAAAAAAAACNIAABkb2NQcm9wcy9hcHAueG1s
UEsFBgAAAAANAA0APgMAADpLAAAAAA==
--------------C2FCBCE09FB8378294339A69--


From nobody Thu Jun  3 19:46:10 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 362883A24CB for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 19:46:07 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=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 s7svhIiU1aTx for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 19:46:02 -0700 (PDT)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 171B13A24C8 for <dmarc@ietf.org>; Thu,  3 Jun 2021 19:46:01 -0700 (PDT)
Received: by mail-pj1-x102a.google.com with SMTP id i22so4810386pju.0 for <dmarc@ietf.org>; Thu, 03 Jun 2021 19:46:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=GJmDgNQMatl5CJgV5fHlOqXvr78Lrg+TfFmVaiuXbCg=; b=ijCuAuOqRlh6kPyPi3U0Eo32FRfyWUlMY5S1OIz9iIh0Ue75xm6jyIeatiFdcZFDny EwXUXbF9cYKAV1cMTT+rKkqySgKa+fUWhqP+rcthyvgmE98TiR329kvKtAVfzgV8EzPq KsHhRDVwqwuO3TQCo6Fcn9WRUgRixnljsJ+hVdMa+ptEzcJTzG+N2SjVVbE2v2rfQLav yXXMb2u/J3hXRWNFWgIk9fjnvKat0UjIxdaxAVI6MgOzPMq1VbAc/Qtqf5LJd1KwxAkv +Jyd96Q9KahzjoGak2p6Z/ISrp3F8EP1QPFCdsKoHm4qg21RcYv7KuOfxMoHe8GTkf01 iegw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=GJmDgNQMatl5CJgV5fHlOqXvr78Lrg+TfFmVaiuXbCg=; b=VIPvF4gM/fAuvxJVQTtrSSeT49c4MCYKyNb/qE7wI1OIsESEMkW4vr14Xr4ZD9eHGd fODaMxwC10nGGpf7jnhx+jdHYBWY7MN/B3ToyLKZDTnYlwFy9hGjHQHZzlkgXLjGcZ4g 1Vy9z6egS7EbvYEff8IEd6fz71Ei3PBAK3Y+Q+lDuTFiHJi5XAO/PmeGCuCr6w0Xjpzf IqB/x/geaZmBBSEoM0cRJn6vZycnU4PBDl7Y7zz3+HeQre9VU+gb7cu6AWGarVIHGeSg ipwwwlNWFRkTR/flH575JiM5SQiXJiCeCodEkFMLhUVQ5Hk1gtK9AjpSlTxZc/9LT7Ir jI2A==
X-Gm-Message-State: AOAM5301UnEqY28aTwzuOOOdY7XyuDZ9TVN6jBryLyhpsIS0uioFngjI ziMI7iQZwOrBR5G6qWhvYHAHilXvx1H7kA==
X-Google-Smtp-Source: ABdhPJzITfk6BEvIDDsldMon1r3aMljLamj8soh6C9BrmuyWPAGnZqVgYvLFK+kGR4GKfMEvfdDTEQ==
X-Received: by 2002:a17:90a:ad8e:: with SMTP id s14mr2468132pjq.198.1622774760323;  Thu, 03 Jun 2021 19:46:00 -0700 (PDT)
Received: from [192.168.0.106] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id bo14sm3328323pjb.40.2021.06.03.19.45.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Jun 2021 19:45:59 -0700 (PDT)
From: Dave Crocker <dcrocker@gmail.com>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com>
Message-ID: <0358dbc4-e256-0d45-b8ed-d244e15ec552@gmail.com>
Date: Thu, 3 Jun 2021 19:45:58 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------2AA946E4E6BFB1DC0DCE729B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/tZZj3UCDoklZ1kVqWA0q9VVmRCg>
Subject: Re: [dmarc-ietf] Ticket #113 - DMARCbis -01 Introduction Section
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 04 Jun 2021 02:46:08 -0000

This is a multi-part message in MIME format.
--------------2AA946E4E6BFB1DC0DCE729B
Content-Type: multipart/alternative;
 boundary="------------8E2B97E30612672055043698"


--------------8E2B97E30612672055043698
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 5/5/2021 11:48 AM, Todd Herr wrote:
>
>
> We would like to achieve rough consensus on this section of text by 
> Friday, May 21.


Apologies.  I've only just been able to review this text. Here's a link 
to suggested changes, done as a Word document with revision tracking 
turned on:

    https://www.dropbox.com/s/qmp2t5n1g99l9wj/DMARCbis-Intro-dcrocker.docx?dl=0

It might appear that the edits effect major substance changes to the 
Introduction, but I believe they do not; the intent was to retain the 
same goals for the Introduction.

Changes were driven by:

  * Providing better lead-in for readers with less background on the
    document's topic
  * Eliminating detail that is not need in an introduction
  * Minimizing PSO text, since I belive the covered domains have Domain
    Owners whether they are PSOs or not; hence the fact of being a PSO
    has minimal import in the Introduction
  * General wordsmithing, to tighten things up

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
Information & Planning Coordinator
American Red Cross
dave.crocker2@redcross.org


--------------8E2B97E30612672055043698
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 5/5/2021 11:48 AM, Todd Herr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com">
      <blockquote style="margin:0 0 0 40px;border:none;padding:0px">
        <div class="gmail_default" style=""><font face="tahoma,
            sans-serif"><br>
          </font></div>
      </blockquote>
      <font face="tahoma, sans-serif"><span class="gmail_default"
          style="font-family:tahoma,sans-serif">We would like to achieve
          rough consensus on this section of text by Friday, May 21.</span></font></blockquote>
    <p><br>
    </p>
    <p>Apologies.  I've only just been able to review this text. Here's
      a link to suggested changes, done as a Word document with revision
      tracking turned on:</p>
    <blockquote>
      <p><a class="moz-txt-link-freetext" href="https://www.dropbox.com/s/qmp2t5n1g99l9wj/DMARCbis-Intro-dcrocker.docx?dl=0">https://www.dropbox.com/s/qmp2t5n1g99l9wj/DMARCbis-Intro-dcrocker.docx?dl=0</a><br>
      </p>
    </blockquote>
    <p>It might appear that the edits effect major substance changes to
      the Introduction, but I believe they do not; the intent was to
      retain the same goals for the Introduction.</p>
    <p>Changes were driven by:</p>
    <ul>
      <li>Providing better lead-in for readers with less background on
        the document's topic<br>
      </li>
      <li>Eliminating detail that is not need in an introduction</li>
      <li>Minimizing PSO text, since I belive the covered domains have
        Domain Owners whether they are PSOs or not; hence the fact of
        being a PSO has minimal import in the Introduction</li>
      <li>General wordsmithing, to tighten things up</li>
    </ul>
    <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
Information &amp; Planning Coordinator
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>
  </body>
</html>

--------------8E2B97E30612672055043698--

--------------2AA946E4E6BFB1DC0DCE729B
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; 
 name="DMARCbis-Intro-dcrocker.docx"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="DMARCbis-Intro-dcrocker.docx"

UEsDBBQABgAIAAAAIQCw3PgAbgEAACQGAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIo
oAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC0lMtqwzAQRfeF/oPRtthKuiilxMmij2Ub
aPoBijRORPVCo7z+vuM4MaUkMTTJxiDP3HvPCDGD0dqabAkRtXcl6xc9loGTXmk3K9nX5C1/
ZBkm4ZQw3kHJNoBsNLy9GUw2ATAjtcOSzVMKT5yjnIMVWPgAjiqVj1YkOsYZD0J+ixnw+17v
gUvvEriUp9qDDQcvUImFSdnrmn43JBEMsuy5aayzSiZCMFqKRHW+dOpPSr5LKEi57cG5DnhH
DYwfTKgrxwN2ug+6mqgVZGMR07uw1MVXPiquvFxYUhanbQ5w+qrSElp97Rail4BId25N0Vas
0G7Pf5TDLewUIikvD9Jad0Jg2hjAyxM0vt3xkBIJrgGwc+5EWMH082oUv8w7QSrKnYipgctj
tNadEAF8uAZB49sZn2gLQfPtnw2xtTkVSZ3j6APSVov/mHm/tmp1TtMGiEmffvRtIlmfPR/U
G1GBOpDNtzt++AMAAP//AwBQSwMEFAAGAAgAAAAhAB6RGrfvAAAATgIAAAsACAJfcmVscy8u
cmVscyCiBAIooAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACsksFqwzAMQO+D/YPRvVHa
wRijTi9j0NsY2QcIW0lME9vYatf+/TzY2AJd6WFHy9LTk9B6c5xGdeCUXfAallUNir0J1vle
w1v7vHgAlYW8pTF41nDiDJvm9mb9yiNJKcqDi1kVis8aBpH4iJjNwBPlKkT25acLaSIpz9Rj
JLOjnnFV1/eYfjOgmTHV1mpIW3sHqj1FvoYdus4ZfgpmP7GXMy2Qj8Lesl3EVOqTuDKNain1
LBpsMC8lnJFirAoa8LzR6nqjv6fFiYUsCaEJiS/7fGZcElr+54rmGT827yFZtF/hbxucXUHz
AQAA//8DAFBLAwQUAAYACAAAACEASiSZhf0XAACwaAEAEQAAAHdvcmQvZG9jdW1lbnQueG1s
7F3dbuM4lr5fYN+B8M3MAElsy//ZKQ+cOB4EM90VVKqBxQ7mgpZom1uy6CXlpNxX9Q57NcAM
0M/Sj1JPMjyUZEu2JItxgo4oN9BlR7Zo8eM5H885POT545++Ll30RLigzPtQa141aoh4NnOo
N/9Q++nz5LJfQ8LHnoNd5pEPtQ0RtT8N//M//vh87TB7vSSej2QTnrh+XtkfagvfX13X68Je
kCUWV0tqcybYzL+y2bLOZjNqk/oz407dajQb6t2KM5sIIX/vFntPWNTC5uyvxVpzOH6WN0OD
7bq9wNwnX3dtNLUb6dQH9f5hQ9YLGpI9tJqHTbW0m+rW4akOGmq/qCH5VActdV7WUkrnui9r
yTpsqfeyllqHLfVf1tKBOC0PBZytiCc/nDG+xL78k8/rS8y/rFeXsuEV9umUutTfyDYb3agZ
TL0vL3giede2hWXL0W6hV18yh7gtJ2qFfaituXcd3n+5vR8e/Tq4P3yJ7uBF+h/cMg7JQfW8
zokrsWCeWNDVVsOXL21NfriIGnnK68TT0o2+97xqFlSXLHoaB1DuGizy+CH+Szd48vwWm40C
IwJNbO8o8gjJ34yeZCmlcPfDL4ImBm6zIIFEDVgHDXRtUpDwozb6YRt1e6eh0A4tqBpRO8Go
QDt0B2yzII/tP0ysAeH4zkKrFSvCtQ73Yh8vsNgKOrRI9B6qs21us4xhtJqfpgh/5my92rVG
T2vtfkdrz2BgaLQVKlRcycVpD/O4wCvJdkv7+n7uMY6nrnwiqR5ISjhSIwD/SkGBF/WWfFXX
YawRcExtKC2jKXM28LqSn7WvV5jjeymUvXajO+h17mrqqpxXfHU1/E9evZZWmPPpQ63R6Ld6
g7vJ9tIDh4uTfrd329leHJMZXrv+4dcfYpfUUzxweBErbMsuyi/hmU+gRbjBpQC61d7+8WkN
fcZrn9XqcBsP7uYT5vkCbhY2lUM+4hS7cA/Bwh8Jij/UPtMlEehH8ow+sSX24MPFyBPxL9si
+kO1LX6W156wCw8QXbmFH4ldq4ePUN92hKfC8p6e9fnaHzav0L3nc+asbZj54DM/+EbQl0P5
aN3cDcajdvcsH6fIRzq23db47ua2ZSWxtbo3knWtQQLbjtVsBN3dh7HXaLdvoYkdjDHhexUY
qQfdgylMfVN+vmCyDQc/ESR5zP5COFyXkwM017Cal43uZaP1udm5bjevG43/CVt7i9GwmctA
9xT4DfXfKWq862pTr6vWdaenuvrbkcGrQCEJAeYtJTGyiytOBOFPpDYcTdeCShT2OUMilgRO
yWJx4CRqg0PglGSPrWY/YIMywDYkR6FpVVamhtK0d5E0eIiHqGe7a0c+yNoLsKA/Ewdhz0HO
cQjb2hD2TYHQJitfauBRiNRse2auLXOhtbSQ2Qxh5DDwMJGHl0RKIfIXBegMLB+tKa+VInCx
Kbw04vZpcttpWdbVhLPlUZSUJXiWuZ3MLQh2CEczSlzn6riU9atLa5+lFoaK6W9W1Mauu0FT
4jJvLpDP5MSAGJ9jj/6sonWIfF0R25czhvxsStAXjz3LO9lRiJVBXRzi1nWzka7IZgjo92//
f1wsm5oGv0FymQ4bWCnHUdP0HYwRtSEAtV7iqXscI003QWIUuJJmquOmgFTpew/GzBE+Xwug
/OnmOEyaHoLpPH8cME1/wXBNLDYvanoFRumitNc4semKEs+/yoAqTS7K3e1ffwFD9ZF4YNY/
MJfaGzTh0pN8ZvwL+v3fpLvUsxr9v/9BRTLGyqD9C9kIdO9InKh0BJwEVuaTjYlS8AOEsdRg
d1u9rhzsFWc+k80LePdEnciXuXTJE3ERUAQMv618lz14HPmFkE80/efsKEMeyuHFMVEglCse
IbH6TL5myd3zgtoL+Hb4tUIiaCAOuhAYJx9DKlIwCK7A12JTuGbIxZzA3gWarn2EeVYkubC8
lKXHGcriMR85VJoyvrtBWAhmUwxOxjP1F4ex4QRda8aSKkvX2yByrlIaJ3DDg5h5nHks7VV0
U5jnuuKME5iGmbRiacYNq0srF+BkFZzoLc1Ioznqpli3wuo2/mH06XZP29L6XvJuZvOJZsRY
Sn5GKo7pfDJdU9cRiEFOABNk59Vf/foL+gmScANhuijKOZpB6O51IyOmao1bI2tcHs6BsAfH
c/nz0oI+njdgaQafs0W0fF6YYBIj7FedpJVNhD4+e4SLHC7Tz8OpKJeBTCHG6Zx6EpUUwsrF
4xwUM1AkiMq+tLFyPTKnr5iyaYaju9et/DXUAsg22812985YidvBXBifkkCRAcJqPXWpWCCM
xj8+5vC6fhi2mryejvLn//58ljaJAyc243upWQkx047Ytk9mNIPETIXEc+VsZ9K39DcJZUBd
NpOeeo5a6PXme3KY1qtUASq3EmblzRjHQZADQ/neIMc0QDOOm20+lcsoyhILWA25DlLhMyQk
hp12tNYU9khfHKmn7hxtWINGp9+9rR3flZu9czT5yRvvHG1pxyLDcQ2ae7cjB+MTvR6OU7Pb
GfTuBjAisXFqWNbdzeRWIZI/LWgNXkzgw8FbPfobl0QP/lcq/Af5YHOOV4ugX956GQ6U+wSm
UgDF9rN7Z9vpsM/bG15NLjQjpe9dLlQXbxfYmwPuqofaIc5w03Q6XtpxsB1eMZndPuShJIfT
WSk48y7P0Eq1NMowK6TIkHZ+YFKGtrDtDzqgp4JDuYmKxsKqHXwoDutrZciWFFl9f7u4wK4g
+5oSlemX6u0H889Lf73okIQXS+TtH45TWzvlpPA4RaGCCziq0SewHhj4TCfEqkoKsr5P86o0
k26bdgaNm8HNeM+HaN9MrHYz2Pf5Uts0OXTltU3bhvksKZKpb33n2KZtfUu3oG2qpCb55Pp2
8O7JT/FtIzM5eI09aNhobBY6yWgLtcfAKeftjK7cGHawISd3AoqJ8kn2SzR2ZRmkuHH11zwL
NW8iKJkYdk6yEV8yKW/lLy9EXmpI386Y9Idshmzm2YR7aCYfWjmtKtVlJt/tuwJmwPkbm42m
wKhvxRWXymTYBNkLYn/J9ks7r5IWmmMRlCFbNGWEToyQvtQiULsI8i2C2Ni9NPBadOxKql1v
F5nMHTtO/m9NhJ83evVUt7c9mXTHvQYYofGls5u7m8lopBi36ksyHX0DvWRub+fE6GQSr+5L
E162sp+tA/tub/cUE+st3d4YHCeZLe+a/uIz/zgxy9e3lnwMiJeGj1TnURrrvGt0DvWse2J4
Kdf0IoJyAr6AiUZr9+1MoldP3iopwqcEEI/JJicrxiUCeMrWPgrS78NTaKW/kCWwpiH8hovW
1V5d7b7huvUwdkjyHpw7Z6irb0BZ1Vxg7b1dmDFye67gWuUWVXtvGGxMZ5dffymyrNrr3N30
m2pbS0lSM3v6BrsBqZnt7rh/2x7dJMepPe5NBq1+MjVzT2ti4xTG295ynN4/vglZ0vR5uteN
dvmcv3R+UCcEHD87tKcfBG6V0D+2sYds9kSS7lkqIJq+jkkygzzmXZKvVPhQs1asp5eB+SUu
CgiSpgfTyzzpuGyVdqA6wLM6ou37t39+DIsDHMdL0x/pZR50XDK80kUPFqywG56/8P3bv4pI
nKbfYZKmYnkDcV0kX0MVRdhXMuizFTj2x9HTdJokeh1T0AOcVNmdBSUcc3uxuYDlfJ8z11Xn
umfBt/M5+5qeVBK+uPoW38JbrtN3chfMHumSupi7m0DPT/AXy7ZZ8wFOIrDR43o2o1/Rx5UU
QJ9xgX7/8PhR/CEhdwl5097FeZa3uGWzxBvJlFG8c0/echEyEAxdCIwTkqEA9ofMLal16HZH
/eH5Tz9ieD7Ix9i3iKPZls3OcnSWI2VJZItQxaa2q32rKW2veLt/d3OjAjPHApIFZOfIPo/q
Rb/SQW/1+u2e1drbXNNqt0ft3ihZ2vmMby6+MbU16KiUkQiOmX98mAT1Yv5y/8NFcMZo9iFG
fc1AfbpFmjMjdG+tu15pjhvJnSkBpVhibu68EENYP3zdNR/h4S6tORPDXZijrx/fTsGwfGBJ
mFwsxN625Po2kmEijSH5Tk5W2YylH9qvgD5lYClN2CfCHWr7aaq2w8PAruf2tyLjH4aQizCs
5sKPMQybDpyAmHyFSLe2ktNMDclfqMHetxqcUb/HwDFZ0T7K15TZeIQAJzTjbImItLUJV9a2
bByMbUQFgj0klBPnKkN4YvOY/sLXsfr24UXzeGwUujEK/VxGi+GrvzRWWTshtBGKQjvQXzar
gOiq/WNS94WqAsc8dxNsJpYMcba9jB74iP+DyUH+BQFl+UwCzwmY4GpbIWVeWCXRjVXpyNS2
dLRKAkzBXPqdSTHQXxhNYRRjzM8RiEiFzM+Uypgx2dAPUZosG0AyZO9YelOkI9wosicKwT/G
sF7MjtIPDVfBjpIfUui8yuECaoj7WCpujAqXZB7oR47NII/hci18ND1akLka5oV+zNgQKfj+
7Z9mzhSSI+YeSR7+nxhy/YCmMUP+ryop/ba0elQXPKVQdvCPMcRm4jgGll9K3DlmLunHnVOq
LhtnLt1DhVkSRUjDKrMXyH9mqGg964F+LDqjnnXZyDLryJVyq9hQKZNAmBMkMHWQz6QpiGqm
u1YlHzVl0yyJ59cQVad6bNACdBHUW+U6R/vSEvussvlSfwWkCnx5VZAUmw39ZQ5DWPECPS+o
vYAFzeSGNHgbHuYR23Ulv+wSEFVIGt0KK3aW1KPC51JcJXQBjtTfwNI6fOnATtuxb3wQ9Auf
ZeywLFnhs4ziXUlw9EOjZkhoxnSg6sGFAqrU/AC+empqdWd827MGY+DLcz776w0UgB29poDe
mHSbN51JEvS21Rs0JxO4egb9FNBjCm5Skvt+Jkiq5dNsaEfWrcxTkVNNH6vT6o3N2AAW5NsW
3MFrkCiFpXXlM+1yNVIWIuNSpb2Y0Eo5oixHqpqj7s2dVTKpGkaBN4MlaJgSVIzbYdrrC2mC
UT4JyDZSTSSMreeDD2pDlLxj+90xcPCmhHjxipT7KRRJotdePLL0iN4g84Ee2QkXp0ntAH4a
rOXDzx/mHCkd646BamdonpIyFpdBhmcOjWgvq1SBRob/BWY2JxBd9Fhh7tAOZpvCHVfoI9Sp
WnNBLvZqKkuLhATp5jbmfJOhazEUgyKcWijGDoosMYoZ7IQ9I/kpo7fk6wqqHPuQTJfNWk3t
iHuajBjHWnQpwQsSjvb4atdr86y7wrZdU3sp4gizlFoBA2kpYPKVpkOSNgzqTpWM1Ywtf9hd
EwR7Cfj2NJOM+UA/ll6F+QD7PqfTNQQSfIbUUcGFeFI7hmyIBTYMCtdEG9+qYnOlO4lxgdCM
HfeumxmOjRFHSINtGkkKiY7h+/jsZR76Hmcq/bBdBZgqA2cVwuDEJvRJPp5Y2wuEo8Nicsms
3Gq6d75h9I8hNktSHfTDrZVVh1FxR0c/qGfIBH7vOYQ4F4Gtcw5lm2y2QHXBy2BygBwpFss7
ziMc/RhtrJZDKozhxVJ7CmqmXRE+Y3wpinsKln6sNgXNMhJNiJWUvAqpXJjY9hRsfs5XNEs/
RFsFRVN7w1PUa9fnagRoDR7jdBCkslBPOo2eg1Rd3FyKNZE8VGW0BWMCdmrkEYdmlD492JAj
VOWKQUQysgbcFgQFqbC50hMHUz8wqnd2tkk0BSeSA8QrqJwjFueFNLN5eijIE1G7vRgkL3g2
4R6sP0s84PSi8GCXeHgPAn8Pjx9zlS9uHWvG0Y0Jmw5nzHXZc4Lj62m5HpZ2UnIaPZXQf8gM
eCYF7vu3fwTntRIBizgOFSsmKFjeGdimK2vJUUnJTCx5j/a7U+pR2y86Aaczr/leQYCk2usv
gpih9sMLMDKqpLvS1KceREqyT75qWvoVajPC1WZUqD2wOjKrrMYtfc2YfzqIprlNGfsB/CNH
dMeFUzNgbIxwghxmzVOx7qRKTslJy0iCVgsmaCHnHxfWSxxiU6GmawaHQe9lvET/nE2sdzJ2
QYrOVfYk2tJfijHalboPTzFf0vnCjwKPDp3NCIcKq9gGW1UkAY1UvZ5eUfK2375r3MC8eD6B
4/WGEMCOXg9Bb7Zvbm7HKgEtBnqz1Ry3Wz3lRmSBfsY3iW/pOXAim8Fq8SRr2V+sVyvGfbiu
Viov4PthjYPzFPfeV9RVFcH44jIVSNKAD/7PbhyFzwleBqmBqpiRS/HUTe4rOw9tCfooh5vZ
VO1y356Pm2Pe6KcTZBT0MsK8gbM+rsOzxFJNmNLTQWZadSLq0dLf0qVXQcuw9c06zKHe5gIJ
tiQXKpHddcNTE6Gd82qnqTIxHCUOFrl34L0kEJ5fpqLkLAKHdX+GnfwzxqW8c7Ja+4FxoawN
ASfZBuJ/tg7L18fQFgxX6l+WENzSzpBp6eUplvPAtO2pDR4Jdg8GZVqKRMxb+kfQZSQFl+2k
MXVaSObWwTOfvPc+Es9eL6dytlDZP9i22dpT0QSIka+9QKTpz/JjyMbbX5ZL0op+ZktlDVNp
kBZejmvppw6Y4QeqLRpZOhjrj4FqWWD1u6W/j7AC6hZWrClaiK7Z0t83mK9cpRbGjEqPKd0s
uXrRoDpPLKaUZcKUezzBGRztD2fJx64CVll8BUclF0JtDppYKcixw7T3e7b0NkCU072zsQfO
XbR6ouHdBSuhpwJaXu9OOsQ2CCSne4tOptBkVvA4uVxzptF37SokM0h/J6JzwWGLE2Q/7gKh
V/tCnJKE0euPmt1Rb68Myjnz5cShArCj1xTQbxvj8V13P92oI8eh2b89g34i6KVX8jDDJTTe
Y/T8N/XJ5Wg+52Qur1x+ImFWzN8Pdh+cmbsEfQwHdBLsq4kPp8PsNSxhiYsg2THbDm5r5k/0
rpt6yxwGbQ9wiLA5nZLimwTa+nvWM5Y8yrZJQKyIDcvIB+VGUjploGoamnyDwUAMSOY8Xbzj
cZpxvCTPjKsTZWLdilOT/vp2Rky3bP76gWdjsnueM/PrL8frLY2UMwIm7WZVQLjwFK+9oGuK
Hv0kwA+k/kWF9SkuCNor0K1euiDcDNqjRtlXj7DBuyVj2WSpa4FxltVegE6TihyWLZewRIxq
cnJpBnPAOWdz4hEux1ya0fO1i8/Hl5Suj4H/k1e/ua2dLFEFuyodTVs+t6RPRaTYD6aMSrFC
UC4gXMnOlSr99erKSpWAeqkGi1JwKrPtYroMMrDRjB+UeDZsLokZ2h39TINKGtox9uho75Ks
ghWaEeVXFn3xGH9He6vhEXFMhbs03HQ8OdIIrcu0dU0ZyBenXHdeJbBcDUtFTeQmWyrhkck5
k/mrRKHLJxYQaK5giYgVgyq+RFzkuDod/Yh6ZY0VyNszmT8EOUhMikvKq4TcqyEpSIIkCmdz
d14lbF1Ca2+4Z7vuWDmOjn6Ir28GOvPoQJCqTFtRvDe3NElHPziXIg/GLfIwj6DgiPY9ytl1
2kCeze2veYO8ZLzwrNLVj9wZwpsVY03sOByqpeStaHT1Y5JVIE0cK+xRWK/0Q5CG6FWUZlyp
2gkpFYhy1Ew/HFcFNfudCIs2yTcqNHE2U4webxV42khqtRnP59VyU8ZhdnPKFsLWTXMwbjUh
enLet/l68APY0esh6J1Gs21NGqMk6K3W7bjTDeqd6YCeVMbfZiTis4x+GH+gZpmgvbcY0peM
XLJP+nHooE9mMqkrH+ET8Rw4Bu0Bz8kNJ/iLuiui0ruvK8Ip8WyyPQqgkPWqH8VNwbmM1utP
6rS4KpmuwSpQjrWqH3c2Weci9Vkor/CJYJc46ohmRIWQPmIoPYW0TD9mbYiW2ZKofPnjgFuV
dI16ckpnkpLxlLrUN7wUQpxE9MPxVSARVU2BqGpfNNqK4Balj55+6NYU+lhg1yXefG8ru+Hk
oTKTIBBJOUHOmkAhbNlH2L0CB6tN1cHpZjNKucd16JCVyzZwCsiFKpdDbdhx5G6CqipyOGd0
vg6GEw7Og4xy7Mn/1yI4Mh357Dy+73h8p7CL7H+J7RMnrGYgBw6DtlJhr1Wpeknzj/ILoLCD
q332SglRdBuNQbM7goUZg+JCbxAniOATEt2HrRwdw0V1df4Iv/csp1Qr7NNCZZS0QzFYzX/A
0KLPVmqTvvoKh2KFuz+nzPfZcve3S2axTxcEO4Bez1J/zhhTYIZ/ztd+iG0kjtDXUFngO+qy
w+w/c+qEiD9Q35ZP2eqqT+tRv9XbKXM2gc0Qnjk0/DcAAAD//wMAUEsDBBQABgAIAAAAIQDc
PO1bIQEAACgEAAAcAAgBd29yZC9fcmVscy9kb2N1bWVudC54bWwucmVscyCiBAEooAABAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKyTzU7DMBCE70i8g+U7cVKg
IFSnF4TUK5QHcJzNj4i9lr0F8vZYLW1TKBGHHHesnfl2JC+Wn6Zj7+BDi1byLEk5A6uxbG0t
+ev66eqes0DKlqpDC5L3EPgyv7xYPEOnKC6FpnWBRRcbJG+I3IMQQTdgVEjQgY0vFXqjKI6+
Fk7pN1WDmKXpXPihB89PPNmqlNyvymvO1r2D/3hjVbUaHlFvDFg6EyECEMXLQvRUvgaSfK8k
0YuL8wh3UyJQ3IVj/nbcidkYw2zSGqjvYFjCdh6Lz6aMtxtTgI+tHwkO0hjE/A8I02qPAStK
NJrv/JibZT9yHaDrBt3v5rHE2ynPrtDSWhVDgoM0BnEzJcQHFC+/PsFA3IOIk/+dfwEAAP//
AwBQSwMEFAAGAAgAAAAhALb0Z5jSBgAAySAAABUAAAB3b3JkL3RoZW1lL3RoZW1lMS54bWzs
WUuLG0cQvgfyH4a5y3rN6GGsNdJI8mvXNt61g4+9UmumrZ5p0d3atTCGYJ9yCQSckEMMueUQ
QgwxxOSSH2OwSZwfkeoeSTMt9cSPXYMJu4JVP76q/rqquro0c+Hi/Zg6R5gLwpKOWz1XcR2c
jNiYJGHHvX0wLLVcR0iUjBFlCe64Cyzcizuff3YBnZcRjrED8ok4jzpuJOXsfLksRjCMxDk2
wwnMTRiPkYQuD8tjjo5Bb0zLtUqlUY4RSVwnQTGovTGZkBF2DpRKd2elfEDhXyKFGhhRvq9U
Y0NCY8fTqvoSCxFQ7hwh2nFhnTE7PsD3petQJCRMdNyK/nPLOxfKayEqC2RzckP9t5RbCoyn
NS3Hw8O1oOf5XqO71q8BVG7jBs1BY9BY69MANBrBTlMups5mLfCW2BwobVp095v9etXA5/TX
t/BdX30MvAalTW8LPxwGmQ1zoLTpb+H9XrvXN/VrUNpsbOGblW7faxp4DYooSaZb6IrfqAer
3a4hE0YvW+Ft3xs2a0t4hirnoiuVT2RRrMXoHuNDAGjnIkkSRy5meIJGgAsQJYecOLskjCDw
ZihhAoYrtcqwUof/6uPplvYoOo9RTjodGomtIcXHESNOZrLjXgWtbg7y6sWLl4+ev3z0+8vH
j18++nW59rbcZZSEebk3P33zz9Mvnb9/+/HNk2/teJHHv/7lq9d//Plf6qVB67tnr58/e/X9
13/9/MQC73J0mIcfkBgL5zo+dm6xGDZoWQAf8veTOIgQyUt0k1CgBCkZC3ogIwN9fYEosuB6
2LTjHQ7pwga8NL9nEN6P+FwSC/BaFBvAPcZoj3Hrnq6ptfJWmCehfXE+z+NuIXRkWzvY8PJg
PoO4JzaVQYQNmjcpuByFOMHSUXNsirFF7C4hhl33yIgzwSbSuUucHiJWkxyQQyOaMqHLJAa/
LGwEwd+GbfbuOD1Gber7+MhEwtlA1KYSU8OMl9BcotjKGMU0j9xFMrKR3F/wkWFwIcHTIabM
GYyxEDaZG3xh0L0Gacbu9j26iE0kl2RqQ+4ixvLIPpsGEYpnVs4kifLYK2IKIYqcm0xaSTDz
hKg++AElhe6+Q7Dh7ref7duQhuwBombm3HYkMDPP44JOELYp7/LYSLFdTqzR0ZuHRmjvYkzR
MRpj7Ny+YsOzmWHzjPTVCLLKZWyzzVVkxqrqJ1hAraSKG4tjiTBCdh+HrIDP3mIj8SxQEiNe
pPn61AyZAVx1sTVe6WhqpFLC1aG1k7ghYmN/hVpvRsgIK9UX9nhdcMN/73LGQObeB8jg95aB
xP7OtjlA1FggC5gDBFWGLd2CiOH+TEQdJy02t8pNzEObuaG8UfTEJHlrBbRR+/gfr/aBCuPV
D08t2NOpd+zAk1Q6Rclks74pwm1WNQHjY/LpFzV9NE9uYrhHLNCzmuaspvnf1zRF5/mskjmr
ZM4qGbvIR6hksuJFPwJaPejRWuLCpz4TQum+XFC8K3TZI+Dsj4cwqDtaaP2QaRZBc7mcgQs5
0m2HM/kFkdF+hGawTFWvEIql6lA4MyagcNLDVt1qgs7jPTZOR6vV1XNNEEAyG4fCazUOZZpM
RxvN7AHeWr3uhfpB64qAkn0fErnFTBJ1C4nmavAtJPTOToVF28KipdQXstBfS6/A5eQg9Ujc
91JGEG4Q0mPlp1R+5d1T93SRMc1t1yzbayuup+Npg0Qu3EwSuTCM4PLYHD5lX7czlxr0lCm2
aTRbH8PXKols5AaamD3nGM5c3Qc1IzTruBP4yQTNeAb6hMpUiIZJxx3JpaE/JLPMuJB9JKIU
pqfS/cdEYu5QEkOs591Ak4xbtdZUe/xEybUrn57l9FfeyXgywSNZMJJ1YS5VYp09IVh12BxI
70fjY+eQzvktBIbym1VlwDERcm3NMeG54M6suJGulkfReN+SHVFEZxFa3ij5ZJ7CdXtNJ7cP
zXRzV2Z/uZnDUDnpxLfu24XURC5pFlwg6ta054+Pd8nnWGV532CVpu7NXNde5bqiW+LkF0KO
WraYQU0xtlDLRk1qp1gQ5JZbh2bRHXHat8Fm1KoLYlVX6t7Wi212eA8ivw/V6pxKoanCrxaO
gtUryTQT6NFVdrkvnTknHfdBxe96Qc0PSpWWPyh5da9Savndeqnr+/XqwK9W+r3aQzCKjOKq
n649hB/7dLF8b6/Ht97dx6tS+9yIxWWm6+CyFtbv7qu14nf3DgHLPGjUhu16u9cotevdYcnr
91qldtDolfqNoNkf9gO/1R4+dJ0jDfa69cBrDFqlRjUISl6joui32qWmV6t1vWa3NfC6D5e2
hp2vvlfm1bx2/gUAAP//AwBQSwMEFAAGAAgAAAAhAHmcjxKCBAAAag0AABEAAAB3b3JkL3Nl
dHRpbmdzLnhtbLRX32/iOBB+P+n+B5Tno/mdQLR0BQSuXZXbU+nqnk1iwGocR7YDZVf3v9/Y
iQnd5lbtrvrSOvPNfDMez4zNh49PtBgcMBeElRPLvXKsAS4zlpNyN7G+PCyHI2sgJCpzVLAS
T6wTFtbH699/+3BMBJYS1MQAKEqR0Gxi7aWsEtsW2R5TJK5YhUsAt4xTJOGT72yK+GNdDTNG
KyTJhhREnmzPcSKrpWETq+Zl0lIMKck4E2wrlUnCtluS4fafseCv8duYpCyrKS6l9mhzXEAM
rBR7UgnDRn+WDcC9ITn8aBMHWhi9o+u8YrtHxvOzxWvCUwYVZxkWAg6IFiZAUnaOgxdEZ99X
4LvdoqYCc9fRq8vIw7cReC8Iogw/vY1j1HLYYHnJQ/K38URnHtIl1o1+LpgLApHLfP8mFs/k
1Va2SKI9EucqUoz4bUGFZ7oT7XIkitdUTQPdkQ1HvOnJtmRoltzuSsbRpoBwoHQGcPoDHZ36
C0lU//QSP2m5yoN1DTPiK2N0cEwqzDNoFBgwjmPZCpAcZY/3+EDU4BFalOMtqgv5gDZrySqw
OiCIO/Zai2yPwEZivq5QBmU9Z6XkrDB6OfuLyTmMFQ5V31roIdOt1s3AAosSUdjJsyG0YjlM
lGNSc/L6lCsD7d0NL11+74jBgOUkxw8qg2t5KvASgl+Tr3ha5p9qIQkw6lH0CxH8KABcKs+f
4cwfThVeYiRrSNM7OdMnsSxItSKcM35b5nD07+aMbLeYgwOCJF5B+RDOjjrPNxjlcK+9k99a
4H9AGVrOf1ClPGNSMnpzqvaQ6187SV3v9mX5wu2cC7O4Z0yeVZ2RH48XyyZShXaIG7hBtOhH
gnAZ9CLTaLbw+hAv9OM07UXiMPXmvUjqT71em2Dm+m5v1KHnOkHb8c+RaO4t4t79RGns+3Ef
EjtBMO/dT5x67qg3gpEbzzy/F/nfXM/GwdTp3Wk6jkbuqA9ZLOOl37vTZewuRr3nsxxF8VyP
GvtcFTRRL4+/uVmp0TKgjcUc0Q0naLBSbxNbaWz444yUBt9guADwJbKuNwYcDhtAUFQUSyhy
A+igaZITUaV4q9fFCvFdx9tq8F4pzPlPZy51LWD+J2d11aBHjqpmZBgVKNfWkpTyjlAjF/Vm
baxKuLIuoLrMPx+4zlOXHrh0oAX16L1DupW1Li6HX9Ztqxd8rdoUr1BVNd2+2bkTqyC7vXRV
g0r4yuEJqz82O6/FPI15DaY/UKZ2BtrtopN5Rnah5xuZ38kCIws6WWhkYSeLjCxSsj3Md16Q
8hEGj1kq+ZYVBTvi/KbDX4iaJIg9qnDa3MVQXqwRtJezGBwS/AQXOc6JhF8GFckpelL3uhcp
81a7QCdWy2e6ClPK1XMG9eZpR639zFiX+HexqDdCRqAc1ye66a7+qybwgggY0xW8EiTjBvtD
Y26Q5Cy7Ve+UoJH7i3k8gsnVwKF+XUg9yeHc7/F2hgTOW8yYho3pt9jxp36azofjcTgdBrMw
Gs5mi3Dojp1w7MymU993/m2b1PxIuv4PAAD//wMAUEsDBBQABgAIAAAAIQD7cfkcDQQAAMYf
AAASAAAAd29yZC9udW1iZXJpbmcueG1s7JfLbts4FIb3A/QdBO0T3WVHqFOkcV1k0CkGaAaz
piXaIsKLQNK3bV+mj9DH6isMKVmyHbWBRKdTYTKb0CZ5Ph3+4jn+8/rNlmBrDblAjE5s79K1
LUhTliG6nNh/3c8uxrYlJKAZwIzCib2Dwn5z/eq315uErsgccrXRUgwqkk2RTuxcyiJxHJHm
kABxSVDKmWALeZky4rDFAqXQ2TCeOb7rueWngrMUCqE4t4CugbD3uHTbjZZxsFHBGhg6aQ64
hNsDw+sNiZwrZ9wG+QYgdULfa6OC3qjY0Vm1QKERSGXVIkVmpO8cLjYj+W3SyIwUtEljM1Lr
OpH2BWcFpGpxwTgBUn3lS4cA/rAqLhS4ABLNEUZyp5huXGMAog8GGamohkCCrDdh5BCWQRxk
NYVN7BWnyT7+oonXqSdV/H6oI3iX81chU5auCKSyPLnDIVZaMCpyVDQVTkxpajGvIeunDrEm
uN63KbyO5fKj9jStpDwAu6S/15/gKvOniZ7b4Y1oRBPRJYXTZ9aZEHULDw82kuZIXK9jA6kB
fgsQp7Bjw68Z4z3DSQ8VqjmoY2nUnOqtaA46COt17GOPkzkCiExmeS+KX+vq6FggQQ5Ec9E1
EfZLKmpwO3KkUbE8rxDec7YqDjR0Hu3u0NY22mH0YO0L6rjIxXnJfMpBobodSZO7JWUczLHK
SJWHpW64Vb4B/VddFD2UH+G2nNfv2tI9xr5W1gjMheQglR9XxDr5dqfuprJYipZwqHwV15OV
i7pZSMjfcgge9BZNoUI/J1kDPLHDYBpG0ezWdvQKWWGJPsA1xPe7AtZ78t2co+wPvYb1WrVX
kgLXO25mUTy7ct9VK3itF5AaqqQSWWD1C+eG7pXrul6ZQ5ljHe5Vccr4zUgzOV9hDGVDvIfb
Zunb56/N/O9pPYvhYr+9+JPrAVF9TD09sUfxWGeSA7osLWgQu3qv02zm+2HGqBRaXJEidQM/
7cic4TL0Rul2MoGoAmdwAZQye1hJccrEHivhtZQIyhn166N+wtZQ7zhbGdZXFy8cmwlzy1Yc
QW59hJsjdR7NpqK9sZ9qfku16PlV+/b5S1/dfN810+1vtVv/FySOVDud6ydQdYlOC+wnCNS7
4Pwr/1dXXDjIigvicNAVV9XX8CouDAxb+HNXXDzQiotcw1b+fBU3GmTFRWPDXv0vVVyZ3AAr
Lo4MW/j5FeecuFv9jCetry7A3tY3jm/jUTA90/p676Zu/DaOG3Gb1zoY6+uXmfxvfR/p4oWh
mTAv3fp6sZluL8b6jse/uuKGan3dQVfccK2vYQt/OdbXsJX/563vyLBXv3TrGxq28J9hfWlp
eWltdfXUif+tT1RnSL8T5v84rJSzDqvGyj5f/wMAAP//AwBQSwMEFAAGAAgAAAAhAOMtD2qF
DAAAEnkAAA8AAAB3b3JkL3N0eWxlcy54bWzsnVtz27gVx9870+/A0VP74MjyRU4y692xnbj2
bJx4I6d5hkjIQk0SKi++9NMXACkJ9CEoHvCs+9KXxCJ5fgDxx/8Q4PWX356TOHjkWS5kejqa
vNsfBTwNZSTS+9PRj7vLvfejIC9YGrFYpvx09MLz0W+//vUvvzx9zIuXmOeBAqT5xyQ8HS2L
YvVxPM7DJU9Y/k6ueKpWLmSWsEL9zO7HCcseytVeKJMVK8RcxKJ4GR/s709HNSbrQ5GLhQj5
JxmWCU8LEz/OeKyIMs2XYpWvaU99aE8yi1aZDHmeq51O4oqXMJFuMJMjAEpEmMlcLop3amfq
GhmUCp/sm7+SeAs4xgEOAGAa8mcc433NGKtImyMiHGe64YjI4vhVxgLkUREtUZSDdbuOdSwr
2JLlS5vIcZU63uBeEt1GSfjx+j6VGZvHiqRUD5RwgQHrf9X+6//Mn/zZLNe7MPpVeSGS4Se+
YGVc5PpndpvVP+tf5r9LmRZ58PSR5aEQd6qCqpREqAKvztJcjNQazvLiLBesdeVS/9G6JswL
a/G5iMRorEvM/6NWPrL4dHRwsF5yoWvQWBaz9H69jKd7P2Z2TaxFc8U9HbFsb3amA8f1jlX/
W7u7ev3LFLxioTDlsEXBlc0n030NjYXOKgfHH9Y/vpe68VlZyLoQA6j+32DHoMWV+1UumFUp
Sa3liy8yfODRrFArTkemLLXwx/VtJmSm0s7p6IMpUy2c8URciSjiqbVhuhQR/7nk6Y+cR9vl
f1ya1FEvCGWZqr8PT6amF8R59Pk55CudiNTalGlNvuqAWG9dim3hJvzfa9ikVqItfsmZzsbB
5DXCVB+FONARubW37czy1b6brVAFHb5VQUdvVdDxWxU0fauCTt6qoPdvVZDB/JkFiTRSid9s
D4sB1F0chxvRHIfZ0ByHl9Ach1XQHIcT0BxHR0dzHP0YzXF0UwSnkKGrF1qd/dDR27u5u48R
ftzdhwQ/7u4jgB93d8L34+7O737c3encj7s7e/txdydrPLcaagXXymZpMdhlCymLVBY8KPjz
cBpLFctMUWl4+qDHM5KdJMBUma0+EA+mhcz83t1DjEn9j+eFnukFchEsxH2Z8XxwxXn6yGO5
4gGLIsUjBGa8KDNHi/j06YwveMbTkFN2bDqongkGaZnMCfrmit2TsXgaETffmkiSFDYdWs2f
l9okgqBTJyzM5PCqSUaWH76IfHhbaUhwXsYxJ2J9pelihjV8bmAww6cGBjN8ZmAwwycGlmZU
TVTTiFqqphE1WE0jareqf1K1W00jareaRtRuNW14u92JIjYp3h51TPqfu7uIpb6oMLgeM3Gf
MjUAGH64qc+ZBrcsY/cZWy0DfVa6HWvvM7accxm9BHcUx7QNiWpcb7rIhdprkZbDG7RBozLX
hkdkrw2PyGAb3nCL3ahhsh6gXdHMZ2blvGg1rSH1Mu2MxWU1oB3uNlYM72FbA1yKLCezQTuW
oAd/1cNZLSdF5tvWcnjFtqzhtnqdlUirVyMJahnL8IEmDV+9rHimpmUPg0mXMo7lE4/oiLMi
k1Vfsy1/YCTpZfnPyWrJcmHmSg1E/0P9+naE4IatBu/QbcxESqPb572EiTigG0Fc3d18Ce7k
Sk8zdcPQAM9lUciEjFmfCfzbTz7/O00Fz9QkOH0h2tszotNDBnYhCA4yFUlGRCQ1zBSpIDmG
Gt7v/GUuWRbR0G4zXt0BVHAi4owlq2rQQeAtlRefVP4hGA0Z3j9ZJvR5ISpT3ZHArNOGeTn/
Fw+Hp7qvMiA5M/StLMz5RzPUNdF0uOHDhAZu+BDBqKkOD7r/EuxsAzd8Zxs4qp29iFmeC+cl
VG8e1e6uedT7O3zyV/NkLLNFGdM14BpI1oJrIFkTyrhM0pxyjw2PcIcNj3p/CbuM4RGckjO8
f2QiIhPDwKiUMDAqGQyMSgMDIxVg+B06Fmz4bToWbPi9OhWMaAhgwaj6Genhn+gqjwWj6mcG
RtXPDIyqnxkYVT87/BTwxUINgukOMRaSqs9ZSLoDTVrwZCUzlr0QIT/H/J4RnCCtaLeZXOhH
Q2Ra3cRNgNTnqGPCwXaFoxL5J5+TVU2zKOtFcEaUxbGUROfWtgccE9m8d21XmHmSY3AVbmMW
8qWMI5459skdq+bLs+qxjNfVN9Xoddrzi7hfFsFsuTnbb2Om+zsj1xP2RtjuAtvafLp+nqUt
7IZHokzWFYUPU0wP+webHt0IPtodvB1JNCKPe0bCMqe7I7ej5EbkSc9IWOb7npHGp43ILj98
YtlDa0c46eo/mzmeo/OddPWiTXBrsV0daRPZ1gVPunpRwyrBWRjqqwVQnX6eccf3M487HuMi
NwVjJzelt6/ciC6DfeePQh/ZMUnTlLe5ewLkfTOI7pU5/yhldd6+ccGp/0Nd12rglOY8aOUc
9r9w1cgy7nbsnW7ciN55x43onYDciF6ZyBmOSkluSu/c5Eb0TlJuBDpbwSMCLlvBeFy2gvE+
2QpSfLLVgFGAG9F7OOBGoI0KEWijDhgpuBEoo4JwL6NCCtqoEIE2KkSgjQoHYDijwnicUWG8
j1EhxceokII2KkSgjQoRaKNCBNqoEIE2qufY3hnuZVRIQRsVItBGhQi0Uc14cYBRYTzOqDDe
x6iQ4mNUSEEbFSLQRoUItFEhAm1UiEAbFSJQRgXhXkaFFLRRIQJtVIhAG7V61NDfqDAeZ1QY
72NUSPExKqSgjQoRaKNCBNqoEIE2KkSgjQoRKKOCcC+jQgraqBCBNipEoI1qLhYOMCqMxxkV
xvsYFVJ8jAopaKNCBNqoEIE2KkSgjQoRaKNCBMqoINzLqJCCNipEoI0KEV39s75E6brNfoI/
6+m8Y7//pau6Ut/tR7lt1GF/1LpWblb/ZxHOpXwIWh88PDTzjX4QMY+FNKeoHZfVba65JQJ1
4fPbRfcTPjZ94EuX6mchzDVTAD/qGwnOqRx1dXk7Ekzyjrp6uh0JRp1HXdnXjgSHwaOupGt8
ub4pRR2OQHBXmrGCJ47wrmxthcMm7srRViBs4a7MbAXCBu7Kx1bgcaCT8+vo457tNN3cXwoI
Xd3RIpy4CV3dEmq1TsfQGH1FcxP6qucm9JXRTUDp6cTghXWj0Aq7UX5SQ5thpfY3qpuAlRoS
vKQGGH+pIcpbaojykxomRqzUkICV2j85uwleUgOMv9QQ5S01RPlJDQ9lWKkhASs1JGClHnhA
dmL8pYYob6khyk9qOLjDSg0JWKkhASs1JHhJDTD+UkOUt9QQ5Sc1mCWjpYYErNSQgJUaEryk
Bhh/qSHKW2qI6pLanEVpSI1S2ArHDcKsQNwB2QrEJWcr0GO2ZEV7zpYsgudsCWq11hw3W7JF
cxP6qucm9JXRTUDp6cTghXWj0Aq7UX5S42ZLbVL7G9VNwEqNmy05pcbNljqlxs2WOqXGzZbc
UuNmS21S42ZLbVL7J2c3wUtq3GypU2rcbKlTatxsyS01brbUJjVuttQmNW621Cb1wAOyE+Mv
NW621Ck1brbklho3W2qTGjdbapMaN1tqkxo3W3JKjZstdUqNmy11So2bLbmlxs2W2qTGzZba
pMbNltqkxs2WnFLjZkudUuNmS51S42ZLNypEELwCapawrAjo3hd3xfJlwYa/nPBHmvFcxo88
Cmh39QtqL8dPjc9fabb5Np/avlBtpt+Abj2uFFVvgK2BZsPraPOZKh2saxLUHwSrF5sK15dr
qxJNICwqXKqywvrdVY6i6nfQbh6iMm+gfV2w40W1piLbDrjeum7SbXtV2zVaq7Pehe7wHXU2
huhso8ozrgp+qJPArhqq+szj6pNp6o/rNFKAp/pzYVVNo2dWodT6Cx7HN6zaWq7cm8Z8UVRr
J/vmlQWv1s+rt+854zOTpp2AcbMy1c/6s22O9q7ex1/fP+DskjoXtTS3uZllaEu769awS1jm
qmmMs17X716/WXFvNQE13KyoGpepAr9piwNHZbnQApvl+/vvD08+fL6s1oDP5s31K+t0FfaN
QNXPs7KQ9SZ15dZf16u2Mr/gRvVH9442X+Br/+ie48uFygwi4XnwlT8F32XCTNLbfi+wZaX5
cmHrmjCHiyv1tp8urG+aaHy60CyzvkDYJxvtVDJ3KZm3K9maxzp1paopW61ivhfK9JFnBY/2
tLzcUfn2bf/s/UF66MDloXp48X8P/c881FByo5vOwNunoF+LZ8aQ29W7JIRJ/LCu8HbI8Vro
o/PJ4aQptDBHS32s03c01sPlUL9g5rkoWVy/68ISZ7vT67/yX/8LAAD//wMAUEsDBBQABgAI
AAAAIQC5LDVhKQIAANYMAAAUAAAAd29yZC93ZWJTZXR0aW5ncy54bWzsl0uP2jAQx++V+h0i
35c86gBBCyvR1VaVtg+1296NY4hV2xPZhsB++tp5sKH0sKm0bQ9c4vE488s88ifi+mYvRbBj
2nBQcxSPIhQwRSHnajNH3x7urqYoMJaonAhQbI4OzKCbxetX19WsYquvzFp3pwkcRZmZpHNU
WFvOwtDQgkliRlAy5Q7XoCWxbqs3oST6x7a8oiBLYvmKC24PYRJFY9Ri9HMosF5zym6BbiVT
to4PNROOCMoUvDQdrXoOrQKdlxooM8bVI0XDk4SrIybGZyDJqQYDaztyxbQZ1SgXHke1JcUT
IB0GSM4AY8r2wxjTlhG6yD6H58M44yOH5z3OnyXTA5jc5sUgStL1NfSxxJKCmKJPZMOSSo+4
g/Q9knT2fqNAk5VwJDf1wA0uqMH+6ur3S22yfe33JaCFE0TOd6Zdg2rmW4wnaYxxGk/q8xXk
h9v6bEeEExsKvdfJ4Z6tbeeNjt4vfFP8xv0A5blzCdaC/MXv8ljm2lv2KUY5GSO3MY/+Pm+U
hLLWpiDAqY9sLTQI0ctsWOTqJKNhsbpf+ZDQsF+0H8fbgov8dCZxFsc4m0RvcD2US/tfpP2N
2a3dHDpvfx6TSZpFOMPNOC4a+R80gsdJNk2S6UUhL6+QEy3gLMVplF1+mv5y45NomsWpe+Wb
L/Wl8//go9B6/cOgtFzyR3YHeqmhMkw3OTBx+KS+f7ivd0QIqD5/fNc8o/dvZPETAAD//wMA
UEsDBBQABgAIAAAAIQAjaNW9ZwIAAKIKAAASAAAAd29yZC9mb250VGFibGUueG1s3JXbjtow
EIbvK/UdIt8vORAOixZWXbpIlapetFv12jgOsRrbkccs8PYdO4EFBSrSqlu1iZI4Y8+X8e8Z
5+5+K8vgmRsQWk1J3ItIwBXTmVCrKfn6tLgZkwAsVRktteJTsuNA7mdv39xtJrlWFgL0VzCR
bEoKa6tJGAIruKTQ0xVX2JlrI6nFV7MKJTXf19UN07KiVixFKewuTKJoSBqMuYai81ww/l6z
teTKev/Q8BKJWkEhKtjTNtfQNtpkldGMA+CcZVnzJBXqgInTFkgKZjTo3PZwMk1EHoXuceRb
snwBDLoBkhZgyPi2G2PcMEL0POaIrBtneOCI7Ijza8EcASCzWdGJkux1DZ0vtbSgUBwTebeg
BgfcTjqNJJt8WClt6LJEEq56gAsXeLC74/zdwzf51tvdFMisKYVgM1FUoueXnVzq0tsrqjTw
GLueaTkl0QDPOHIpMoqG+BxEIxK6gaygBrhj1AOT2pxTKcrd3mq0pKruqIRlxd7+TI1wQddd
IFbYsYZlhJzmILUlxgo/tSStMf1TC/Oc8aklPhqD3wxrAVpCPAnJIfjEN8FnH/k5RdyyDqM+
KpHilWArPa+I/9LvK/KIMSePi8WLInO0jMaDh5Yitz9TxL/GNed6ReZ6bQQ3TpMLaoxQgVuv
ilMj7aSG1Bk35+TIxZZn12uR9l9Di2+43brfDFyolNbRoVLo2up/qFDmtBRLIy6kxMKngjtT
TI6kU0rARgB0K5D0XFIk6ehVCuQdhnV+60yiB9wo0kYJr8af1cHN+u9tFHVGBB/FqrAX88Jl
w3+aF00DZj8AAAD//wMAUEsDBBQABgAIAAAAIQDwJBCsXQIAAOIJAAAPAAAAd29yZC9wZW9w
bGUueG1spJbLjpswFIb3lfoOiH1iIEOGQUlm0VGrSN211awd2wlW8EW2geTtaxMuaWlHQDYB
Yv+ffx+fc+TN64XlXkmUpoJv/XAZ+B7hSGDKT1v/18+vi8T3tIEcw1xwsvWvRPuvu8+fNlUY
p5IImRPPIrhOK4m2fmaMTAHQKCMM6iWjSAktjmaJBAPieKSIgEooDKIgDOo3qQQiWtv1vkBe
Qu03OHQZR8MKVlbsgE8AZVAZcukZ4WRIDF5AMgRFM0B2h1E4RK0mo9bAuRqAnmaBrKsBKZ5H
+sfm1vNI0ZD0PI+0GpKSeaRBOrFhggtJuB08CsWgsZ/qBBhU50IuLFhCQw80p+ZqmcG6xUDK
zzMcWVVHYCs8mfAMmMAkX+GWIrZ+oXja6Bed3llPb/rm0SrUmP3fJG8CFYxwU+8cKJLbWAiu
Myq7CmdzaXYwayHlR5soWd7Oq2Q4slz+157ebqHsgWPsN/Fn+c35x8QwGHEiDtEpxlj4c83W
CbNZ2C88KzR3wQ1HNpAWEA0Aa0RGNvyWkTQMgPoKdRw6sjRazu1UHIf2gQ1H9rG/zdwBNDY4
m0SJ2rgCp4UGZlB3ie6IZJqpuMNd2V2M5OmxQvimRCF7Gn2Mtu/bWuUuGBNYTUHdF7l+zMyP
DErb7RhK9ycuFDzk1pEtD89muFefgPu1ieIe9Su51P+7s/Zcj/F3zc1IacGdLIWFyYTtnBiW
xLNe0JmodpYi2t62yJ4fRT3XOikpJmpvc/idciwq7X2npbXkRgt9G0EoDl6SeAUPhyDGCfLB
bgP6VbsPdznb/QYAAP//AwBQSwMEFAAGAAgAAAAhAG8BqMd1AQAA8AIAABEACAFkb2NQcm9w
cy9jb3JlLnhtbCCiBAEooAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAIySX0+DMBTF3038DqTv0LI/RgmwRM2eXGLijMa32t5tddA2bTe2b2+BwUT34Nu9Pef+
uJw2nR3KItiDsULJDMURQQFIpriQ6wy9LufhLQqso5LTQknI0BEsmuXXVynTCVMGno3SYJwA
G3iStAnTGdo4pxOMLdtASW3kHdKLK2VK6nxr1lhTtqVrwCNCbnAJjnLqKK6Boe6J6ITkrEfq
nSkaAGcYCihBOovjKMZnrwNT2osDjfLDWQp31HDR2om9+2BFb6yqKqrGjdXvH+P3xdNL86uh
kHVWDFCecpY44QrIU3wufWV3n1/AXHvcN75mBqhTJud0DwEzim3BNKZOqCPfwrFShls/Pui8
jYNlRmjnL7KFDw68u6DWLfzNrgTw++Ov7/zV6xEDe1G/jDwmjaXv01PO7XLAA59P0qbZKW/j
h8flHOUjMopDchOS8TK+S6bThJCPer/B/BlYnjb4D3GyJCSJJ0NiB2gjGr7R/BsAAP//AwBQ
SwMEFAAGAAgAAAAhACoqH9zhAQAA4QMAABAACAFkb2NQcm9wcy9hcHAueG1sIKIEASigAAEA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAnFNNbxMxEL0j8R9WvjdO
UhJo5LhCqVAPQCNl256Ndzax8NqWPY0afj3jXbI4wIk9vfnY5+c3Y3H72tnqCDEZ79ZsNpmy
Cpz2jXH7NXusP119YFVC5RplvYM1O0Fit/LtG7GNPkBEA6kiCpfW7IAYVpwnfYBOpQmVHVVa
HzuFFMY9921rNNx5/dKBQz6fTpccXhFcA81VGAnZwLg64v+SNl5nfempPgXik6KGLliFIL/m
P+2k8dgJPmZF7VHZ2nQg54sbKoyh2Ko9JDkTfADi2ccmycViLvgAxeagotJIHsrr2YI6i4T4
GII1WiHZK78YHX3yLVYPveYqEwhetgi6xw70SzR4klPBy1B8No4UzJeCD4i0RbWPKhySfJ8F
jpHYaWVhQxbIVtkEgv9OiHtQebxbZbLAI66OoNHHKpkfNOA5q76pBNm4NTuqaJRDNrQNQY9t
SBhlbdAS9xj3sGwrsXmXXRzAZWMf9BoIX6rrT0gPLd0N/yF2VortNQxSCzmlsvMZf7BufBeU
I4P5iMjg7+kx1P4ur8cvDy+TxdyfDR52QWmayfXyZlluQFESO8pCQyMdhzImxD1dIdp8AP3r
9tCce/4u5J16Gl6snC0nU/r6JTrnaBPGpyR/AgAA//8DAFBLAQItABQABgAIAAAAIQCw3PgA
bgEAACQGAAATAAAAAAAAAAAAAAAAAAAAAABbQ29udGVudF9UeXBlc10ueG1sUEsBAi0AFAAG
AAgAAAAhAB6RGrfvAAAATgIAAAsAAAAAAAAAAAAAAAAApwMAAF9yZWxzLy5yZWxzUEsBAi0A
FAAGAAgAAAAhAEokmYX9FwAAsGgBABEAAAAAAAAAAAAAAAAAxwYAAHdvcmQvZG9jdW1lbnQu
eG1sUEsBAi0AFAAGAAgAAAAhANw87VshAQAAKAQAABwAAAAAAAAAAAAAAAAA8x4AAHdvcmQv
X3JlbHMvZG9jdW1lbnQueG1sLnJlbHNQSwECLQAUAAYACAAAACEAtvRnmNIGAADJIAAAFQAA
AAAAAAAAAAAAAABWIQAAd29yZC90aGVtZS90aGVtZTEueG1sUEsBAi0AFAAGAAgAAAAhAHmc
jxKCBAAAag0AABEAAAAAAAAAAAAAAAAAWygAAHdvcmQvc2V0dGluZ3MueG1sUEsBAi0AFAAG
AAgAAAAhAPtx+RwNBAAAxh8AABIAAAAAAAAAAAAAAAAADC0AAHdvcmQvbnVtYmVyaW5nLnht
bFBLAQItABQABgAIAAAAIQDjLQ9qhQwAABJ5AAAPAAAAAAAAAAAAAAAAAEkxAAB3b3JkL3N0
eWxlcy54bWxQSwECLQAUAAYACAAAACEAuSw1YSkCAADWDAAAFAAAAAAAAAAAAAAAAAD7PQAA
d29yZC93ZWJTZXR0aW5ncy54bWxQSwECLQAUAAYACAAAACEAI2jVvWcCAACiCgAAEgAAAAAA
AAAAAAAAAABWQAAAd29yZC9mb250VGFibGUueG1sUEsBAi0AFAAGAAgAAAAhAPAkEKxdAgAA
4gkAAA8AAAAAAAAAAAAAAAAA7UIAAHdvcmQvcGVvcGxlLnhtbFBLAQItABQABgAIAAAAIQBv
AajHdQEAAPACAAARAAAAAAAAAAAAAAAAAHdFAABkb2NQcm9wcy9jb3JlLnhtbFBLAQItABQA
BgAIAAAAIQAqKh/c4QEAAOEDAAAQAAAAAAAAAAAAAAAAACNIAABkb2NQcm9wcy9hcHAueG1s
UEsFBgAAAAANAA0APgMAADpLAAAAAA==
--------------2AA946E4E6BFB1DC0DCE729B--


From nobody Thu Jun  3 19:50: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 2C60B3A24E7 for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 19:50:30 -0700 (PDT)
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 PwcXdpm_o6Zv for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 19:50:25 -0700 (PDT)
Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A626B3A24E5 for <dmarc@ietf.org>; Thu,  3 Jun 2021 19:50:25 -0700 (PDT)
Received: by mail-pj1-x102e.google.com with SMTP id pi6-20020a17090b1e46b029015cec51d7cdso5017475pjb.5 for <dmarc@ietf.org>; Thu, 03 Jun 2021 19:50:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=PTc6//m+6YOl81YaBfeht7zpet2DX1BzvW81uC1ImsY=; b=OENh2QRX+8Vj+13qzCjFfygKrlaERKyq8BX4yJiwJetibXNVa/525DoTwzCUbZXVpE 72D3Un4vzhE02Xdc34Xlc5lKJeH5sV3U4VcejohUdBh+UgyJDjQq8BwzgLhR+A8GmWC5 1F6f8hv6yIhha3b0y3wgdm/N2sAsL05Cz/kZJO26XfDvEfW8hKDO9iOb7DYQMcs3PPsT kCBSh3lWcUJE9a1QGlQcbkFtWS/OYuVnl1Flrd4feZUnMurn7yA9FnF6Cv6GGybQSitM M4WooIwncSeDpubn/3NZL39njnLZPeJY8HRNhRMG+XjblfWjDYbbbq60S2vw3wBbm69Y ZFuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=PTc6//m+6YOl81YaBfeht7zpet2DX1BzvW81uC1ImsY=; b=TkE95LpjdKSK47DAtwTdVvmmphFh758txQDOJvDNBU+qRgr8G2Wpsr61Vh8+FIgFAB rT46nwLtWDyEXipaoHFLPG0t+aEer9iDRxocTcrzQn91MF2yddHyLWiuhzZo2XMeOTAH /yKHZNQOWulXOn2FwOAj7JyLpuuW2eGRuUc7hfNxheIzHUVED7pbPFpB7zxcKR75HJ3/ hLhadio9pPgv9z14JYgR0LKGQQOX/kyOWHoP18jQ6AevyAlCb1fk59d3uHrar9DmP91C ePyKT0HKh33Dt/f4yJ36Tj+2DEaTC1yrehQ1uQ/Sh3586YhZAUyy9f0Az1SIFD6wtvva 45Sg==
X-Gm-Message-State: AOAM530kHSu7ZQgBMso8rF4wyBxi4CPOfMjuWe2OnSimhN+fbBOc3prZ IjPLh198AbSqHkWEt0XAUwiaybupxZirdw==
X-Google-Smtp-Source: ABdhPJzw/3H6Ndjy0aKTMymKcrxFIQ6rIhSl16/4goODli6lZ4smd5NMk23p2ZEe6GHzaPTXR42t3A==
X-Received: by 2002:a17:902:a3c3:b029:f0:b297:7778 with SMTP id q3-20020a170902a3c3b02900f0b2977778mr2152483plb.16.1622775023602;  Thu, 03 Jun 2021 19:50:23 -0700 (PDT)
Received: from [192.168.0.106] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id v3sm338595pfb.203.2021.06.03.19.50.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Jun 2021 19:50:23 -0700 (PDT)
From: Dave Crocker <dcrocker@gmail.com>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com>
Message-ID: <fe578817-a213-66e6-f296-f92b17c074af@gmail.com>
Date: Thu, 3 Jun 2021 19:50:22 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------48608DF85815D484140E63BB"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/0zNUAkjIbNMWad4hIQobDoGp5xw>
Subject: Re: [dmarc-ietf] Ticket #113 - DMARCbis -01 Introduction Section
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 04 Jun 2021 02:50:30 -0000

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

(this time without an attachment...)


On 5/5/2021 11:48 AM, Todd Herr wrote:
> We would like to achieve rough consensus on this section of text by 
> Friday, May 21.


Apologies.  I've only just been able to review this text. Here's a link 
to suggested changes, done as a Word document with revision tracking 
turned on:

    https://www.dropbox.com/s/qmp2t5n1g99l9wj/DMARCbis-Intro-dcrocker.docx?dl=0

    (I suggest looking at the document without the revision tracks being
    displayed.)

It might appear that the edits effect major substance changes to the 
Introduction, but I believe they do not; the intent was to retain the 
same goals for the Introduction.

Changes were driven by:

  * Providing better lead-in for readers with less background on the
    document's topic
  * Eliminating detail that is not need in an introduction
  * Minimizing PSO text, since I belive the covered domains have Domain
    Owners whether they are PSOs or not; hence the fact of being a PSO
    has minimal import in the Introduction
  * General wordsmithing, to tighten things up

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
Information & Planning Coordinator
American Red Cross
dave.crocker2@redcross.org


--------------48608DF85815D484140E63BB
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">(this time without an attachment...)</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 5/5/2021 11:48 AM, Todd Herr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com">
      <font face="tahoma, sans-serif"><span class="gmail_default"
          style="font-family:tahoma,sans-serif">We would like to achieve
          rough consensus on this section of text by Friday, May 21.</span></font></blockquote>
    <p><br>
    </p>
    <p>Apologies.  I've only just been able to review this text. Here's
      a link to suggested changes, done as a Word document with revision
      tracking turned on:</p>
    <blockquote>
      <p><a class="moz-txt-link-freetext"
href="https://www.dropbox.com/s/qmp2t5n1g99l9wj/DMARCbis-Intro-dcrocker.docx?dl=0"
          moz-do-not-send="true">https://www.dropbox.com/s/qmp2t5n1g99l9wj/DMARCbis-Intro-dcrocker.docx?dl=0</a></p>
      <p>(I suggest looking at the document without the revision tracks
        being displayed.)<br>
      </p>
    </blockquote>
    <p>It might appear that the edits effect major substance changes to
      the Introduction, but I believe they do not; the intent was to
      retain the same goals for the Introduction.</p>
    <p>Changes were driven by:</p>
    <ul>
      <li>Providing better lead-in for readers with less background on
        the document's topic<br>
      </li>
      <li>Eliminating detail that is not need in an introduction</li>
      <li>Minimizing PSO text, since I belive the covered domains have
        Domain Owners whether they are PSOs or not; hence the fact of
        being a PSO has minimal import in the Introduction</li>
      <li>General wordsmithing, to tighten things up</li>
    </ul>
    <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
Information &amp; Planning Coordinator
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>
  </body>
</html>

--------------48608DF85815D484140E63BB--


From nobody Thu Jun  3 19:55: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 DA4B73A2517 for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 19:55:47 -0700 (PDT)
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 l4XU5P4PQJR1 for <dmarc@ietfa.amsl.com>; Thu,  3 Jun 2021 19:55:43 -0700 (PDT)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7862D3A2516 for <dmarc@ietf.org>; Thu,  3 Jun 2021 19:55:43 -0700 (PDT)
Received: by mail-pf1-x435.google.com with SMTP id d16so6381626pfn.12 for <dmarc@ietf.org>; Thu, 03 Jun 2021 19:55:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:from:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=/K09c+pgkaNkmnFd8zrDqULXEBQyKNWAViMsNZrXgjk=; b=jxYYw2GlbyCG06oA3oA612tpNOHq1M+SOOiFXW1p+uRQu7dZ+U3fFT51dLw+o/sVly 1IyeMOKzDZKkEdMMNFPQX2Ngd6DaTcXKvVLqMyom0BKLU+/UQoPqmpiXicHHgtNnFOZ1 GtT3Xpu/hfgelmeMctyuxy3N1YgAdUrODPasIa6RSyb0cPaHKkoPM87HJHbMiBip3eR4 ol51UUtqYQPaY7mqlBwWvKJHlC0X1cjUJhMhSECitW6jxQCujh6nzcElYX6ILV6EBQiP xjUfxTd0Mdjkhtnej4JluYHkAUjSSWnzahCdy3b5G7wg9Tj16rwaIhg320pxUteICrH+ GXYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=/K09c+pgkaNkmnFd8zrDqULXEBQyKNWAViMsNZrXgjk=; b=buu99y1i0P2QEo7Z4gHDIJ6jSPgLTShAGo0FY50E6oZ5EkxArm9Bqo7kMptJddFdzG bsqt69PH+MmzL3ZEt9jKe6bYzfvZQ16NLc2gWe2tYdXKEMw313mh9wfwNC2teiwWpPSY iMEth3ntiKOyolc2KLSL7ZfaAPi7RKMbQBbfmQdIQSdKP88wr7dwFvypAj06TIjk7A4S bqokN0EIjyOyf9+Z/c6xchfycJ4MyJ50SuLw2oSknnn2RCNDF+FXYxYnlvQOS1R561CL WlDXcT4QV6JdRR7qAOxHnHUXTmJfztsgZr1dZ4MQDsOqbkcf1IrO6LL2cJN5Yp7HaPOD nWHg==
X-Gm-Message-State: AOAM532JPD9EP3jZ5z7PRSOL4dsVuzhezQF5U79UJFjnp8goCg2LcpCY lCU5yId3HULL1y2sq80ueFg13QwFldNWYQ==
X-Google-Smtp-Source: ABdhPJy9Hc1sdpD2dTyLHPOfGEyrJtFlBRf0tYn98G2v2bqVaqNd6IvsScq+KX/OOqlD5dIt64i6XQ==
X-Received: by 2002:a05:6a00:2392:b029:2e9:10d5:3735 with SMTP id f18-20020a056a002392b02902e910d53735mr2169290pfc.73.1622775342279;  Thu, 03 Jun 2021 19:55:42 -0700 (PDT)
Received: from [192.168.0.106] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id k13sm346324pfh.68.2021.06.03.19.55.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Jun 2021 19:55:41 -0700 (PDT)
From: Dave Crocker <dcrocker@gmail.com>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com> <fe578817-a213-66e6-f296-f92b17c074af@gmail.com>
Message-ID: <39da3e21-689c-0199-d0c4-107304303ecf@gmail.com>
Date: Thu, 3 Jun 2021 19:55:40 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <fe578817-a213-66e6-f296-f92b17c074af@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/vbUWujYoXep5ZJ3sRSOi-8fghkw>
Subject: Re: [dmarc-ietf] Ticket #113 - DMARCbis -01 Introduction Section
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 04 Jun 2021 02:55:48 -0000

On 6/3/2021 7:50 PM, Dave Crocker wrote:
> (this time without an attachment...)

Interesting.  My own MUA is not showing a received copy of any of my 
postings of the message through the IETF list.  Hence the re-sends, 
guessing at why not.

Finally looked at the IETF's IMAP archive and there they all are. 
Curious.  Anyhow, another round of apologies.

d/
-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
Information & Planning Coordinator
American Red Cross
dave.crocker2@redcross.org


From nobody Fri Jun  4 02:26:54 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 349E23A308A for <dmarc@ietfa.amsl.com>; Fri,  4 Jun 2021 02:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gu6YUB__bbEE for <dmarc@ietfa.amsl.com>; Fri,  4 Jun 2021 02:26:46 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 077BE3A3084 for <dmarc@ietf.org>; Fri,  4 Jun 2021 02:26:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1622798797; bh=/CRtnpEBhhhBSr3h2MMGWA9VKO6TrLmfhPx+EQ2FwfE=; l=3184; h=To:References:From:Date:In-Reply-To; b=Ay9DgYHROIdH5RzfELjIpNfiVmice6+aKTLTsdb4hPSjp9TApVP8Ch/7Y6nRKZkvQ MZHR4BBpsvI8uwTwxxbX0MDVdkrFWw3b6Tiaxy/8L6y1z3ns7rUQ2AzN2uzBHxDTdS Yx8IIHUO+0RrGiJkhqm20F/cfesDGnp0ulo8J6sNcKvqEUuSVaKjasiD0CdP3
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.0000000060B9F1CD.00006346; Fri, 04 Jun 2021 11:26:37 +0200
To: dmarc@ietf.org
References: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <f04b1dfa-2707-a67e-4df8-bf82d637f4f8@tana.it>
Date: Fri, 4 Jun 2021 11:26:36 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@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/vZhhd_olhAlW9rcwsGvzoKQsRLw>
Subject: Re: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 04 Jun 2021 09:26:52 -0000

On Thu 03/Jun/2021 14:47:21 +0200 Brotman, Alex wrote:
> 
> During our interim call last week the topic of extensions within the DMARC aggregate report came up.  There was a discussion about how to best introduce these, but also how they might be best used.  I noted three cases that I could see today; ARC, PSD, and BIMI.   And indeed we have tickets relating to the first two.  The original thought was that the aggregate draft would allow a place for extensions, and then additional drafts would define those within the IETF.  When -02 was originally being worked on, there was a thread about how we might like to see this, though not many responses.  The result is in section 4 of the -02 draft [1].


I have some comments about that attempt.  First, it shows extensions right below <feedback>, while it seems more useful to have them as child of <record>.  Second, I'm not sure we need an <extensions> container.  I'd go for an example like, say, so:

<feedback xmlns="http://ietf.org/xml-namesapaces/dmarc-xml/1.0">
    <report_metadata>
       ...
    </report_metadata>
    <policy_published>
       ...
    </policy_published>
    <extension_metadata name="bimi" xmlns="http://ietf.org/xml-namesapaces/bimi-xml?/1.0">
       ...
    </extension_metadata>
    <record>
       <row>
          ...
       </row>
       <identifiers>
          ...
       </identifiers>
       <auth_results>
          ...
       </auth_results>
          ...
       <extension name="bimi" xmlns="http://ietf.org/xml-namesapaces/bimi-xml??/1.0">
          ...
       </extension>
    </record>
    <record>
       ...
    </record>
</feedback>


Third, we need to grasp how XML grammars can be composed, and insert it in Appendix A.


>  At the time, I didn't intend to limit the extensions to IETF-approved extensions, though wasn't sure how else this might be used by reporting entities (I mentioned domain reputation-ish things during the call).  I'd consider that if we don't enforce IETF-registered extensions, the receivers could still ignore extensions they don't want to handle.


I assume no one reads the XML directly, except for debugging.  If report consumers don't know about an extension, its content will never reach human eyeballs.  Extension existence will have to be advertised, and a IANA page could be a decent means of doing that.


>  I'm also aware this could bloat a report in terms of size, though we've already indicated we don't seem overly concerned with the size of the XML body.  A few things I'd like to see the group reach consensus on are:
> 
> 1) Extensions in their own section (as it is now) or within each <row> element


Both, and both optional.  An extension can have some data to add in some <record>, but not necessarily in all of them.


> 2) Must extensions be IETF-approved


We cannot stop non-registered extensions.  Yet, developers may want to see an RFC before implementing code that extracts a given extension's content.


> 3) If (2) is true, do we want to define any during the DMARCbis process (essentially a demonstration of how it is to be done)


It would be a good way to show how to define them.  Not our primary task, though.


Best
Ale
-- 

> 1: https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-aggregate-reporting-02#section-4




















From nobody Fri Jun  4 08:45:21 2021
Return-Path: <tadams@proofpoint.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A39F63A16FB for <dmarc@ietfa.amsl.com>; Fri,  4 Jun 2021 08:45:19 -0700 (PDT)
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, 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=proofpoint.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ixtllzv2_GB8 for <dmarc@ietfa.amsl.com>; Fri,  4 Jun 2021 08:45:14 -0700 (PDT)
Received: from mx0a-00148503.pphosted.com (mx0a-00148503.pphosted.com [148.163.157.21]) (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 A2E0F3A16FA for <dmarc@ietf.org>; Fri,  4 Jun 2021 08:45:14 -0700 (PDT)
Received: from pps.filterd (m0162103.ppops.net [127.0.0.1]) by mx0a-00148503.pphosted.com (8.16.1.2/8.16.1.2) with SMTP id 154E6IBx005324;  Fri, 4 Jun 2021 08:45:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proofpoint.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=corp-2019-08-07; bh=VMsE5BaWvQvQM3MRNJ/MmwE4byjo4oSX8grc5TiXrKE=; b=e19LDgnmRaj7kAmJTDfLXkmjZYEs5J5vkXoI07qirBpaCqK6sS1oMQToNugaAtmPPHhi 89dEbODEoSpFIOfcWzR56SWaKt7oQXnXI6eDRwhuIto46yGQ1eLynLAAPfvz+opG27Pt 26za7NVqs9n6CRDDhh+lfUYj0JPHnnTTsj3zZ2uue9L17/QnYusOxcyhmg3Ex6W1yWlG Wgxa9TU+h7L+lwePxZ4WL3/yUg193bpYlYGAOdIf5iGl7SVI+zzwY0U/NoB4jM1yzP5l 1IUFQsYZP3iPvzbxQr93jwjp2B9fK+bOG5VCGqeKRmGdSZW1+2pVNYzc39/YMrulEvEr 3g== 
Received: from lv-exch01.corp.proofpoint.com (spf-mailers.proofpoint.com [136.179.16.100]) by mx0a-00148503.pphosted.com with ESMTP id 38y8sb88vt-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 04 Jun 2021 08:45:12 -0700
Received: from lv-exch06.corp.proofpoint.com (10.19.10.26) by lv-exch01.corp.proofpoint.com (10.94.30.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.2176.2; Fri, 4 Jun 2021 08:45:11 -0700
Received: from lv-exch02.corp.proofpoint.com (10.94.30.38) by lv-exch06.corp.proofpoint.com (10.19.10.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.2176.2; Fri, 4 Jun 2021 08:45:11 -0700
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (10.19.16.20) by lv-exch02.corp.proofpoint.com (10.94.30.38) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.2176.2 via Frontend Transport; Fri, 4 Jun 2021 08:45:11 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eIkFJXvxWkCB5Vm6UyY7kwBNdInrmXjw14tzgELxqqBjrwl1/HmnLFylSv6ordfWHHks3PL0pnUhi7710YMHBzs54qsCxE1MG7PCcrHwhQmGeRWUfEWKJH9LlbtCCJ8fv7mkZa7vUx+/xUFdYkB0lpHMg523BXKmlmWqMUo4WuLPAfNEWz6Ds0ANDSNpGOYBytB8YlqtXcvZ4dLK4y93J0x8HC6RRrYE6KlZShZEBdMDpBK8tMWkcc/zEglNz9TDGmQpu3AaW1JjwBJo1/ti+eBbUkdLnV9dxWA6Vhs8fyyMTMSdBVEkmbKQN/QHHiLAx+jA95D6rtrlUBUEIlbCrw==
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=VMsE5BaWvQvQM3MRNJ/MmwE4byjo4oSX8grc5TiXrKE=; b=TXaxW3xnBKgt2uIWgH16i72Y5o21+Y138fZ5bWmXhcI/VprbGu6mbyM5cGennn8I/KwHMO8iked+ZCWkeJ6Go37uOXI2KvhvYibpMotQymrM13/Weak5Ka4dmpcTVYIPcQxJnxk/xl5Ce0+V+1Jzv4xltPwS/9erZIciXcIv/ZXa/uEZDpustooWJZhUNxNQjhEUoeQHABLDYYZ8TAyX8YmYtb9XewEn0sRGsBaDvV2/hpFudKMQaun2qJdXFdHD3oS35FnXwrQYJurTrSioQsMtMbnh/6gyueVE0SmkFdpXioyiy+IkDUWyAM+NLQcFwPP3rxvu7vLpQUDpmSdAfg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=proofpoint.com; dmarc=pass action=none header.from=proofpoint.com; dkim=pass header.d=proofpoint.com; arc=none
Received: from CY4PR12MB1782.namprd12.prod.outlook.com (2603:10b6:903:123::21) by CY4PR12MB1448.namprd12.prod.outlook.com (2603:10b6:910:f::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4173.29; Fri, 4 Jun 2021 15:45:08 +0000
Received: from CY4PR12MB1782.namprd12.prod.outlook.com ([fe80::1425:9bd7:ee4a:2559]) by CY4PR12MB1782.namprd12.prod.outlook.com ([fe80::1425:9bd7:ee4a:2559%8]) with mapi id 15.20.4195.025; Fri, 4 Jun 2021 15:45:08 +0000
From: Trent Adams <tadams@proofpoint.com>
To: Alessandro Vesely <vesely@tana.it>, "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
Thread-Index: AddYdpfWt/LpopsnRqmW8ZVx8+CfOwArR8sAAACltAA=
Date: Fri, 4 Jun 2021 15:45:08 +0000
Message-ID: <DEC4098D-0D74-4AB0-A390-688D0A32DF50@proofpoint.com>
References: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@MN2PR11MB4351.namprd11.prod.outlook.com> <f04b1dfa-2707-a67e-4df8-bf82d637f4f8@tana.it>
In-Reply-To: <f04b1dfa-2707-a67e-4df8-bf82d637f4f8@tana.it>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.49.21050901
authentication-results: tana.it; dkim=none (message not signed) header.d=none;tana.it; dmarc=none action=none header.from=proofpoint.com;
x-originating-ip: [2601:283:4700:8dc0:91aa:d789:b6f5:9865]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 052d103a-7638-4323-1d45-08d9276fbb61
x-ms-traffictypediagnostic: CY4PR12MB1448:
x-microsoft-antispam-prvs: <CY4PR12MB14484599E95C99CC5F814B67B33B9@CY4PR12MB1448.namprd12.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: sodCMn6t2mPGVRDjmVj+SJtArRGl6UhfiW0SRnpwHWA1UjedNuZm3+4jyjQ/rABuhtv8yszMO6TlUPjn4+sPXQVhrgn52/UUEPC+iBVPmWpBxLUzduErAXjBVJUtFvT10ydkZKqBi2zAUaE/UNGfiLwVfaxUgN7eqhFLH8MxOmv2FOgza0ZVnh+zAb/trLff32Ykn5FQnM3NZKlQW5AZFarcdKFuDjhTaUnzYr/fYvO5d2EMCxOf1lWLv84w1K2Vxw1HyWDyDM49ejFZ62zLI0NeV4Ri2kWsXpHAMqcWXk9ceWXG1Kz5tekETIxXKbUpu24kO7UFcF5D5QUhhD5oilx74WzTjwX2iVtnJI/eAo4g2pTWD1yfjCuoRfBOoNcuH/3HNZq99dfgzWLCi8xr18fKgE5QHPNBETuVZ6loIluT/GSLd7ot/ay8cTb5ilnlS98BAKVIsBJBRAGrCqyAnn3nB1/AJjkLDwJT2EPTNQ0neDmJeMKPsxnv6dEqa1qOITJXOi0NRsU/He1CKrsL56H5aAE3SWftNAWM55wP15y1MAlXztpqCcbtrbHqQvGu6kt48MjM9vIHeDmdn5RVLtP+UBCS4VIckFaN0x+7Nsy0GVYfySuMsAQMkzzXmfkd/E+6w02CZ09OXntRB2aT+UkW0rTbdpOZMNTe2G7jvFaWCUHZgGtTI5Q8bKItigZtFLChV4O5g7Wdv8aWIJ7t5gX4IPf3NjSUiJqf/YN/HjQ+rWSR1ev4BXSf4thwFWyLWdWE3Nj8Cdl+K7Q07u8D6La954M8g2rXA9unY0ytjbnAiR/2zG4aV1lpkH1/tHMY
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CY4PR12MB1782.namprd12.prod.outlook.com; PTR:; CAT:NONE;  SFS:(366004)(39850400004)(136003)(346002)(396003)(376002)(66476007)(66556008)(66946007)(64756008)(66446008)(2906002)(76116006)(86362001)(6512007)(478600001)(33656002)(966005)(316002)(36756003)(8936002)(83380400001)(110136005)(5660300002)(8676002)(6486002)(2616005)(186003)(71200400001)(38100700002)(122000001)(6506007)(45980500001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?Skh1dURPZmZrZzNNejFvWEU2RWpJakcxUlhGaWFvYUt6UlJjcmU5em5XU0VI?= =?utf-8?B?R2EzcGJZZTBYOW9wSDNBcW1CemlvU2lJSmFrbW11T3BSU3R3c1lxN1dFcjBT?= =?utf-8?B?WnBwYnpMdVU5eWR1TWFnTVVNNjVUVDBLVWRDbnUwZElHR2JhMGNzSGtFY2Jm?= =?utf-8?B?T1JJU1JyUklPczRsMUwyUEJNRk9WeWJwMnduRDFFMHlNNXRnVjRxYTJST3Vs?= =?utf-8?B?RzhkR3hQTTdRenV0UUV3QUttRTJ2eEI2VnV1ZFJac2dIQ2k4UHFGalZoaFNj?= =?utf-8?B?UnYwbTlFL1hYblhFdWpsNkE0ZnorYW9JdERJRVRpZUZSYnNLaUpwUlVjTnpn?= =?utf-8?B?UktkU1JseFIzTVVnYjdYOXhOYXJIUlNxR1JnczJFMFlNWlRzeUpRUWk2UXVy?= =?utf-8?B?ZStzSEp3cVBYNXVQRUt4SmdjN2JmdzcweWdJUHRtb2FnSHM0WjRXeE8rTHpo?= =?utf-8?B?czIyZXJ2M3JwdXVEaGRqeU5iUzlKeitFSVoxa3dIdi9UVG8rMmtkVVNteDQy?= =?utf-8?B?YmlqT3h3TzBMT1E0TXc5NDBqTG53WlZlWmxlaXF1WWs4RnB5NnNjOFRacDJS?= =?utf-8?B?WVN0VHVsdzMzWEFjRkE2bkR4Q0RRYU9FYjFkQ2oxNVhXVmV5b0xKenVTMzVT?= =?utf-8?B?WkJ2L1JHWkVTTHI5UzdZcWxWV3dJY2VXbm1ZaHloWTRGYjhSQklCVHdtVERz?= =?utf-8?B?Vktsc3UzL3JYNWZTSjhFTThaUWJaSWYwZHViYVNVTjF2WDlGYm44Q0J0N05s?= =?utf-8?B?MytPeTNPQk1hVGprSXNBdThZVmQxRmNQckhYV0h5d3I0d1hyWDE1ejd2YzBL?= =?utf-8?B?WGQ5enFQdW5IalJOMURuaEVLQUlBQ3RqaVYzTC94RnB3aWNKbU8wRk4vNlQv?= =?utf-8?B?aVpqcnVEMVRlUStpazJiZE1nQ1dubHRIMWxvRGZoZ1FHRzFrZUpFL1VwYnJG?= =?utf-8?B?V3RhRm81MndydXMrVmJOSUxEWXNtckp5bEZ1VjdXR0ZyekJlYWsvRUdwUHdn?= =?utf-8?B?TXI3UjZMQTBraVFkR1RLS3pKSFhnZ1h0dXVvV1BEQlovWWlKSWJaWHFPeEdk?= =?utf-8?B?ajF4UStjeTVHVVYzOGJ5c3J5ZlNMSWExQWNZUFNXRDZuYUFCb0xRL2E2czg0?= =?utf-8?B?RjV1djF3NXRSM3hZbU1pYThtaGRaWEIvdzBOdzB4S3hRaEQyMEFhdzlDOElh?= =?utf-8?B?Z2pKTFZEaU5RNmszNnA4Q2dnVStZUDFYVkNPcmZoMW1oZGtrUlVZQkpVclVj?= =?utf-8?B?bGM3a1YvSXp3OHRPNjYrVjAvSWIwK1p4UE91N0tMR0xJMlh5cElaNUJkdTR6?= =?utf-8?B?NXhacjlpMzdXRUUyRHQ1dTdYck8yejgxckNiMDdhSkR2cXFMbUZnanVHOURB?= =?utf-8?B?WWVtdCtEa3YrWXN2Tnd6UXRIajY4NzRnc3pHWlI2eVVreFNGMmk3UDQvaFV5?= =?utf-8?B?VUFlTUZpQWQ2VVdZaU42bnFWZ0hRSjI1R2RRTTVvcUc5MFVsaUtPaU5NVzd5?= =?utf-8?B?NmFWWEFKL2twM0k3RjJXOGsyMGhhSlRFQ3JlZ2kxZDJ6QjYzOG9NMWVqQ2lr?= =?utf-8?B?YXBseElMV2FXRzBhaURqVnluMjdGQ0JjK0NHNFlhQ3FCUlFQczBVUktrWERO?= =?utf-8?B?V1BRanc0dVBGMGI2YTRtK2ZtdW1wOHlsNHk4bUltTzgyeTlkZVh6OERZVCs2?= =?utf-8?B?RURUNCtyVzBNc1J1a1ZUSFkwZzZ3Q0FOS0ZCTEx3djU2Z1ZHWTdyaDlRM2M5?= =?utf-8?B?RUUwZG15VTlpbVp0d0ZlbFBrSWRKYk9RakhhdUpZeEVxeWFVdk5lSjhyL2tr?= =?utf-8?B?cEVsS3FpMjJDWTVwZTY0Lzh3anpiMWx6aG9iWUdoWXJFSDBxNGE1a29XbUhH?= =?utf-8?B?Z29rL1VMZGIzeWNKT2l5bkxCVXk2QzAyMUVRNitlWkpid0E9PQ==?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <1C64A36EBE3E1D41BD3DBFECC455029C@namprd12.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CY4PR12MB1782.namprd12.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 052d103a-7638-4323-1d45-08d9276fbb61
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2021 15:45:08.6903 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 46785c73-1c32-414b-86bc-fae0377cab01
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 98rEne6IG7FY65XqDV0VNii6pSf6F7nROw9Xtc6in8BWjtSNm7XDzb9q5/fom8yhwgiQ+pB0F+cZS+DUl0Z/JQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR12MB1448
X-PassedThroughOnPremises: Yes
X-OriginatorOrg: proofpoint.com
X-Proofpoint-GUID: bIgkvVudJlwmgUqe_rSfBx1FVpZCOmQd
X-Proofpoint-ORIG-GUID: bIgkvVudJlwmgUqe_rSfBx1FVpZCOmQd
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.182.1,Aquarius:18.0.761,Hydra:6.0.391,FMLib:17.0.607.475 definitions=2021-06-04_08,2021-06-04_01,2020-04-07_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 mlxlogscore=999 lowpriorityscore=0 suspectscore=0 bulkscore=0 priorityscore=1501 mlxscore=0 impostorscore=0 malwarescore=0 phishscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104190000 definitions=main-2106040114
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/fHXCABvWnjnHBVtwM7ogiVS1Cl4>
Subject: Re: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 04 Jun 2021 15:45:20 -0000

DQpJIGFncmVlIHdpdGggQWxlc3NhbmRybydzIHN1Z2dlc3Rpb25zLCBhbmQgcmVhbGx5IGxpa2Ug
dGhlIGZsZXhpYmlsaXR5IG9mIHNlbGYtbGFiZWxlZCBlbGVtZW50cyBzbyB0aGV5IGNhbiBiZSBs
b2NhdGVkIHdoZXJlIGFwcHJvcHJpYXRlIHJhdGhlciB0aGFuIGZvcmNpbmcgYWxsIGV4dGVuc2lv
bnMgaW50byBhIHNpbmdsZSBidWNrZXQuDQoNCk15ICQwLjAyLA0KVHJlbnQNCg0KDQrvu79PbiA2
LzQvMjEsIDM6MjcgQU0sICJkbWFyYyBvbiBiZWhhbGYgb2YgQWxlc3NhbmRybyBWZXNlbHkiIDxk
bWFyYy1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiB2ZXNlbHlAdGFuYS5pdD4gd3JvdGU6
DQoNCiAgICBPbiBUaHUgMDMvSnVuLzIwMjEgMTQ6NDc6MjEgKzAyMDAgQnJvdG1hbiwgQWxleCB3
cm90ZToNCiAgICA+IA0KICAgID4gRHVyaW5nIG91ciBpbnRlcmltIGNhbGwgbGFzdCB3ZWVrIHRo
ZSB0b3BpYyBvZiBleHRlbnNpb25zIHdpdGhpbiB0aGUgRE1BUkMgYWdncmVnYXRlIHJlcG9ydCBj
YW1lIHVwLiAgVGhlcmUgd2FzIGEgZGlzY3Vzc2lvbiBhYm91dCBob3cgdG8gYmVzdCBpbnRyb2R1
Y2UgdGhlc2UsIGJ1dCBhbHNvIGhvdyB0aGV5IG1pZ2h0IGJlIGJlc3QgdXNlZC4gIEkgbm90ZWQg
dGhyZWUgY2FzZXMgdGhhdCBJIGNvdWxkIHNlZSB0b2RheTsgQVJDLCBQU0QsIGFuZCBCSU1JLiAg
IEFuZCBpbmRlZWQgd2UgaGF2ZSB0aWNrZXRzIHJlbGF0aW5nIHRvIHRoZSBmaXJzdCB0d28uICBU
aGUgb3JpZ2luYWwgdGhvdWdodCB3YXMgdGhhdCB0aGUgYWdncmVnYXRlIGRyYWZ0IHdvdWxkIGFs
bG93IGEgcGxhY2UgZm9yIGV4dGVuc2lvbnMsIGFuZCB0aGVuIGFkZGl0aW9uYWwgZHJhZnRzIHdv
dWxkIGRlZmluZSB0aG9zZSB3aXRoaW4gdGhlIElFVEYuICBXaGVuIC0wMiB3YXMgb3JpZ2luYWxs
eSBiZWluZyB3b3JrZWQgb24sIHRoZXJlIHdhcyBhIHRocmVhZCBhYm91dCBob3cgd2UgbWlnaHQg
bGlrZSB0byBzZWUgdGhpcywgdGhvdWdoIG5vdCBtYW55IHJlc3BvbnNlcy4gIFRoZSByZXN1bHQg
aXMgaW4gc2VjdGlvbiA0IG9mIHRoZSAtMDIgZHJhZnQgWzFdLg0KDQoNCiAgICBJIGhhdmUgc29t
ZSBjb21tZW50cyBhYm91dCB0aGF0IGF0dGVtcHQuICBGaXJzdCwgaXQgc2hvd3MgZXh0ZW5zaW9u
cyByaWdodCBiZWxvdyA8ZmVlZGJhY2s+LCB3aGlsZSBpdCBzZWVtcyBtb3JlIHVzZWZ1bCB0byBo
YXZlIHRoZW0gYXMgY2hpbGQgb2YgPHJlY29yZD4uICBTZWNvbmQsIEknbSBub3Qgc3VyZSB3ZSBu
ZWVkIGFuIDxleHRlbnNpb25zPiBjb250YWluZXIuICBJJ2QgZ28gZm9yIGFuIGV4YW1wbGUgbGlr
ZSwgc2F5LCBzbzoNCg0KICAgIDxmZWVkYmFjayB4bWxucz0iaHR0cHM6Ly91cmxkZWZlbnNlLmNv
bS92My9fX2h0dHA6Ly9pZXRmLm9yZy94bWwtbmFtZXNhcGFjZXMvZG1hcmMteG1sLzEuMF9fOyEh
T1JnRWZDQnNyMjgyRnchNlNBNGloWXpsN3hmS2RWZllEZWZLSXNyNFBvdFJiNU5ranMyaFhIUHlJ
VTVLVHBtZmZCRkxrSkVLcXZ3U0p2RiQgIj4NCiAgICAgICAgPHJlcG9ydF9tZXRhZGF0YT4NCiAg
ICAgICAgICAgLi4uDQogICAgICAgIDwvcmVwb3J0X21ldGFkYXRhPg0KICAgICAgICA8cG9saWN5
X3B1Ymxpc2hlZD4NCiAgICAgICAgICAgLi4uDQogICAgICAgIDwvcG9saWN5X3B1Ymxpc2hlZD4N
CiAgICAgICAgPGV4dGVuc2lvbl9tZXRhZGF0YSBuYW1lPSJiaW1pIiB4bWxucz0iaHR0cHM6Ly91
cmxkZWZlbnNlLmNvbS92My9fX2h0dHA6Ly9pZXRmLm9yZy94bWwtbmFtZXNhcGFjZXMvYmltaS14
bWw/KjEuMF9fO0x3ISFPUmdFZkNCc3IyODJGdyE2U0E0aWhZemw3eGZLZFZmWURlZktJc3I0UG90
UmI1TmtqczJoWEhQeUlVNUtUcG1mZkJGTGtKRUt2UTJwUW4tJCAiPg0KICAgICAgICAgICAuLi4N
CiAgICAgICAgPC9leHRlbnNpb25fbWV0YWRhdGE+DQogICAgICAgIDxyZWNvcmQ+DQogICAgICAg
ICAgIDxyb3c+DQogICAgICAgICAgICAgIC4uLg0KICAgICAgICAgICA8L3Jvdz4NCiAgICAgICAg
ICAgPGlkZW50aWZpZXJzPg0KICAgICAgICAgICAgICAuLi4NCiAgICAgICAgICAgPC9pZGVudGlm
aWVycz4NCiAgICAgICAgICAgPGF1dGhfcmVzdWx0cz4NCiAgICAgICAgICAgICAgLi4uDQogICAg
ICAgICAgIDwvYXV0aF9yZXN1bHRzPg0KICAgICAgICAgICAgICAuLi4NCiAgICAgICAgICAgPGV4
dGVuc2lvbiBuYW1lPSJiaW1pIiB4bWxucz0iaHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0
dHA6Ly9pZXRmLm9yZy94bWwtbmFtZXNhcGFjZXMvYmltaS14bWw/KipBMS4wX187UHk4ISFPUmdF
ZkNCc3IyODJGdyE2U0E0aWhZemw3eGZLZFZmWURlZktJc3I0UG90UmI1TmtqczJoWEhQeUlVNUtU
cG1mZkJGTGtKRUt0a0ZOQzZwJCAiPg0KICAgICAgICAgICAgICAuLi4NCiAgICAgICAgICAgPC9l
eHRlbnNpb24+DQogICAgICAgIDwvcmVjb3JkPg0KICAgICAgICA8cmVjb3JkPg0KICAgICAgICAg
ICAuLi4NCiAgICAgICAgPC9yZWNvcmQ+DQogICAgPC9mZWVkYmFjaz4NCg0KDQogICAgVGhpcmQs
IHdlIG5lZWQgdG8gZ3Jhc3AgaG93IFhNTCBncmFtbWFycyBjYW4gYmUgY29tcG9zZWQsIGFuZCBp
bnNlcnQgaXQgaW4gQXBwZW5kaXggQS4NCg0KDQogICAgPiAgQXQgdGhlIHRpbWUsIEkgZGlkbid0
IGludGVuZCB0byBsaW1pdCB0aGUgZXh0ZW5zaW9ucyB0byBJRVRGLWFwcHJvdmVkIGV4dGVuc2lv
bnMsIHRob3VnaCB3YXNuJ3Qgc3VyZSBob3cgZWxzZSB0aGlzIG1pZ2h0IGJlIHVzZWQgYnkgcmVw
b3J0aW5nIGVudGl0aWVzIChJIG1lbnRpb25lZCBkb21haW4gcmVwdXRhdGlvbi1pc2ggdGhpbmdz
IGR1cmluZyB0aGUgY2FsbCkuICBJJ2QgY29uc2lkZXIgdGhhdCBpZiB3ZSBkb24ndCBlbmZvcmNl
IElFVEYtcmVnaXN0ZXJlZCBleHRlbnNpb25zLCB0aGUgcmVjZWl2ZXJzIGNvdWxkIHN0aWxsIGln
bm9yZSBleHRlbnNpb25zIHRoZXkgZG9uJ3Qgd2FudCB0byBoYW5kbGUuDQoNCg0KICAgIEkgYXNz
dW1lIG5vIG9uZSByZWFkcyB0aGUgWE1MIGRpcmVjdGx5LCBleGNlcHQgZm9yIGRlYnVnZ2luZy4g
IElmIHJlcG9ydCBjb25zdW1lcnMgZG9uJ3Qga25vdyBhYm91dCBhbiBleHRlbnNpb24sIGl0cyBj
b250ZW50IHdpbGwgbmV2ZXIgcmVhY2ggaHVtYW4gZXllYmFsbHMuICBFeHRlbnNpb24gZXhpc3Rl
bmNlIHdpbGwgaGF2ZSB0byBiZSBhZHZlcnRpc2VkLCBhbmQgYSBJQU5BIHBhZ2UgY291bGQgYmUg
YSBkZWNlbnQgbWVhbnMgb2YgZG9pbmcgdGhhdC4NCg0KDQogICAgPiAgSSdtIGFsc28gYXdhcmUg
dGhpcyBjb3VsZCBibG9hdCBhIHJlcG9ydCBpbiB0ZXJtcyBvZiBzaXplLCB0aG91Z2ggd2UndmUg
YWxyZWFkeSBpbmRpY2F0ZWQgd2UgZG9uJ3Qgc2VlbSBvdmVybHkgY29uY2VybmVkIHdpdGggdGhl
IHNpemUgb2YgdGhlIFhNTCBib2R5LiAgQSBmZXcgdGhpbmdzIEknZCBsaWtlIHRvIHNlZSB0aGUg
Z3JvdXAgcmVhY2ggY29uc2Vuc3VzIG9uIGFyZToNCiAgICA+IA0KICAgID4gMSkgRXh0ZW5zaW9u
cyBpbiB0aGVpciBvd24gc2VjdGlvbiAoYXMgaXQgaXMgbm93KSBvciB3aXRoaW4gZWFjaCA8cm93
PiBlbGVtZW50DQoNCg0KICAgIEJvdGgsIGFuZCBib3RoIG9wdGlvbmFsLiAgQW4gZXh0ZW5zaW9u
IGNhbiBoYXZlIHNvbWUgZGF0YSB0byBhZGQgaW4gc29tZSA8cmVjb3JkPiwgYnV0IG5vdCBuZWNl
c3NhcmlseSBpbiBhbGwgb2YgdGhlbS4NCg0KDQogICAgPiAyKSBNdXN0IGV4dGVuc2lvbnMgYmUg
SUVURi1hcHByb3ZlZA0KDQoNCiAgICBXZSBjYW5ub3Qgc3RvcCBub24tcmVnaXN0ZXJlZCBleHRl
bnNpb25zLiAgWWV0LCBkZXZlbG9wZXJzIG1heSB3YW50IHRvIHNlZSBhbiBSRkMgYmVmb3JlIGlt
cGxlbWVudGluZyBjb2RlIHRoYXQgZXh0cmFjdHMgYSBnaXZlbiBleHRlbnNpb24ncyBjb250ZW50
Lg0KDQoNCiAgICA+IDMpIElmICgyKSBpcyB0cnVlLCBkbyB3ZSB3YW50IHRvIGRlZmluZSBhbnkg
ZHVyaW5nIHRoZSBETUFSQ2JpcyBwcm9jZXNzIChlc3NlbnRpYWxseSBhIGRlbW9uc3RyYXRpb24g
b2YgaG93IGl0IGlzIHRvIGJlIGRvbmUpDQoNCg0KICAgIEl0IHdvdWxkIGJlIGEgZ29vZCB3YXkg
dG8gc2hvdyBob3cgdG8gZGVmaW5lIHRoZW0uICBOb3Qgb3VyIHByaW1hcnkgdGFzaywgdGhvdWdo
Lg0KDQoNCiAgICBCZXN0DQogICAgQWxlDQogICAgLS0gDQoNCiAgICA+IDE6IGh0dHBzOi8vdXJs
ZGVmZW5zZS5jb20vdjMvX19odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2Ry
YWZ0LWlldGYtZG1hcmMtYWdncmVnYXRlLXJlcG9ydGluZy0wMipzZWN0aW9uLTRfXztJdyEhT1Jn
RWZDQnNyMjgyRnchNlNBNGloWXpsN3hmS2RWZllEZWZLSXNyNFBvdFJiNU5ranMyaFhIUHlJVTVL
VHBtZmZCRkxrSkVLdFNnOEphSCQgDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCiAgICBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
ICAgIGRtYXJjIG1haWxpbmcgbGlzdA0KICAgIGRtYXJjQGlldGYub3JnDQogICAgaHR0cHM6Ly91
cmxkZWZlbnNlLmNvbS92My9fX2h0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
ZG1hcmNfXzshIU9SZ0VmQ0JzcjI4MkZ3ITZTQTRpaFl6bDd4ZktkVmZZRGVmS0lzcjRQb3RSYjVO
a2pzMmhYSFB5SVU1S1RwbWZmQkZMa0pFS25fVXpmNVkkIA0KDQo=


From nobody Fri Jun  4 11:53:40 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 E07113A1CF5 for <dmarc@ietfa.amsl.com>; Fri,  4 Jun 2021 11:53:38 -0700 (PDT)
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 qN-65Udye250 for <dmarc@ietfa.amsl.com>; Fri,  4 Jun 2021 11:53:34 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C2693A1CED for <dmarc@ietf.org>; Fri,  4 Jun 2021 11:53:34 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id h20so10310729qko.11 for <dmarc@ietf.org>; Fri, 04 Jun 2021 11:53:34 -0700 (PDT)
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=8PEC893M9Pb8X29ndShp+sit3F7/g+OGRv5wToBSvxE=; b=M+pZFqO37Z18gVp0HvB1MOGX9y22w7bO2xOMWC0Rs0tw1hg5/0BGbyh1bmj1Vxs2mD MfZ+VnmfUDqtKxp391OTSaAaI4NoYvjI5I16AQDvsulvNQx2aGFxEfKlceB9cfX1bOCa YsnUNUhqnoPYj7ZUq3CReCX3WOpP7J56iirgt/ScRT4/1h3hftkphVe4UvD2cZdZ75XV JG0l5qmhJI8PNQtnC+lpOsuJxkhIiLPJGrlXiv00/RdLb/K4Het4BCW5ASJrpuMukXvo Nlk8wtqX65OO0WypBRWyYmTLPux2oGWWZIUT83x3t0UH1Yxz5ZqW31i4sdTraopT5UkN oqJA==
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=8PEC893M9Pb8X29ndShp+sit3F7/g+OGRv5wToBSvxE=; b=VRSbm83PCXNJ+sAm9Zf8dym90m/8FkL+B67amwK0nqb4rl7SfA6HTNKC0t/OADMn5D pRnRZbXQLfUZI6oqB7iBmrqUZYKB4QDK9b7CSyyk7R8QKfYY1kA6GZ0nmmJljNTUIogO tCglJbxddX71jqoWvLtd31bE34fYS8im5/FLwz756AQXJReJ1pKP4NTpEOXH1VPdDOwC 7IQLut2nxaSwjJMRCcVbi4m4ddBJLGtA8RocWWd3Tt6+tCCl7v45Is1+H38vh1oD2WJv HBZb7/QOsJR8IAUCmZT5w8sSJlspTaNxcxxFvxdjG7ep6mBMag1pNqzXi6qZi8Tagp9q RPJw==
X-Gm-Message-State: AOAM533qlFyZQtqFDKiacjsohZazfF30UymSAZo2++lIGADRlpg12Kki 2+1M9pcdouFU66RFjaFp1ixCDSNwTMI4lI+ZWGSRAXMyEX0=
X-Google-Smtp-Source: ABdhPJyathpA1Q5R4ShnG4xZXPF8asefE/FaydNu85efKKIsEguWOe+MF1i/BNMzfP79jE4TyfOHpJg7w/270tuIo2E=
X-Received: by 2002:a05:620a:704:: with SMTP id 4mr5715754qkc.66.1622832811923;  Fri, 04 Jun 2021 11:53:31 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Dotzero <dotzero@gmail.com>
Date: Fri, 4 Jun 2021 14:53:20 -0400
Message-ID: <CAJ4XoYdn1Z=BkxxJfbkDDoipDHUb2_dCt1k=wfwidVpFN93ZRg@mail.gmail.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Cc: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000048dde905c3f53567"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/c-uTo8_PdzW-0ZirISvHEFPqytg>
Subject: Re: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 04 Jun 2021 18:53:39 -0000

--00000000000048dde905c3f53567
Content-Type: text/plain; charset="UTF-8"

On Thu, Jun 3, 2021 at 8:48 AM Brotman, Alex <Alex_Brotman=
40comcast.com@dmarc.ietf.org> wrote:

> Hello folks,
>
> During our interim call last week the topic of extensions within the DMARC
> aggregate report came up.  There was a discussion about how to best
> introduce these, but also how they might be best used.  I noted three cases
> that I could see today; ARC, PSD, and BIMI.   And indeed we have tickets
> relating to the first two.  The original thought was that the aggregate
> draft would allow a place for extensions, and then additional drafts would
> define those within the IETF.  When -02 was originally being worked on,
> there was a thread about how we might like to see this, though not many
> responses.  The result is in section 4 of the -02 draft [1]. and I thought
> we'd enhance that as we progressed.  At the time, I didn't intend to limit
> the extensions to IETF-approved extensions, though wasn't sure how else
> this might be used by reporting entities (I mentioned domain reputation-ish
> things during the call).  I'd consider that if we don't enforce
> IETF-registered extensions, the receivers could still
>   ignore extensions they don't want to handle.  I'm also aware this could
> bloat a report in terms of size, though we've already indicated we don't
> seem overly concerned with the size of the XML body.  A few things I'd like
> to see the group reach consensus on are:
>
> 1) Extensions in their own section (as it is now) or within each <row>
> element
> 2) Must extensions be IETF-approved
> 3) If (2) is true, do we want to define any during the DMARCbis process
> (essentially a demonstration of how it is to be done)
>
> Thank you for your continued feedback
>
> 1:
> https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-aggregate-reporting-02#section-4
>
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
>



1) Extensions should be in their own extension and seperate from the core
reporting. There is a reason we call them "extensions".
2) Extensions used in reporting under the standard should be IETF-approved.
This is a standards body. Anyone can leverage standards for private use but
our focus as an IETF working group is interoperability. By requiring IETF
approval/registration it puts the extensions under IETF "Note Well" and
makes the extension public.

Michael Hammer

--00000000000048dde905c3f53567
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, Jun 3, 2021 at 8:48 AM Brotma=
n, Alex &lt;Alex_Brotman=3D<a href=3D"mailto:40comcast.com@dmarc.ietf.org">=
40comcast.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">Hello folks,<br>
<br>
During our interim call last week the topic of extensions within the DMARC =
aggregate report came up.=C2=A0 There was a discussion about how to best in=
troduce these, but also how they might be best used.=C2=A0 I noted three ca=
ses that I could see today; ARC, PSD, and BIMI.=C2=A0 =C2=A0And indeed we h=
ave tickets relating to the first two.=C2=A0 The original thought was that =
the aggregate draft would allow a place for extensions, and then additional=
 drafts would define those within the IETF.=C2=A0 When -02 was originally b=
eing worked on, there was a thread about how we might like to see this, tho=
ugh not many responses.=C2=A0 The result is in section 4 of the -02 draft [=
1]. and I thought we&#39;d enhance that as we progressed.=C2=A0 At the time=
, I didn&#39;t intend to limit the extensions to IETF-approved extensions, =
though wasn&#39;t sure how else this might be used by reporting entities (I=
 mentioned domain reputation-ish things during the call).=C2=A0 I&#39;d con=
sider that if we don&#39;t enforce IETF-registered extensions, the receiver=
s could still<br>
=C2=A0 ignore extensions they don&#39;t want to handle.=C2=A0 I&#39;m also =
aware this could bloat a report in terms of size, though we&#39;ve already =
indicated we don&#39;t seem overly concerned with the size of the XML body.=
=C2=A0 A few things I&#39;d like to see the group reach consensus on are:<b=
r>
<br>
1) Extensions in their own section (as it is now) or within each &lt;row&gt=
; element<br>
2) Must extensions be IETF-approved<br>
3) If (2) is true, do we want to define any during the DMARCbis process (es=
sentially a demonstration of how it is to be done)<br>
<br>
Thank you for your continued feedback<br>
<br>
1: <a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-aggreg=
ate-reporting-02#section-4" rel=3D"noreferrer" target=3D"_blank">https://da=
tatracker.ietf.org/doc/html/draft-ietf-dmarc-aggregate-reporting-02#section=
-4</a><br>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br></blockquote><div><br></div><div>=C2=A0</div><div><br></div><div=
>1) Extensions should be in their own extension and seperate from the core =
reporting. There is a reason we call them &quot;extensions&quot;.</div><div=
>2) Extensions used in reporting under the standard should be IETF-approved=
. This is a standards body. Anyone can leverage standards for private use b=
ut our focus as an IETF working group is interoperability. By requiring IET=
F approval/registration it puts the extensions under IETF &quot;Note Well&q=
uot; and makes the extension public.</div><div><br></div><div>Michael Hamme=
r<br></div></div></div>

--00000000000048dde905c3f53567--


From nobody Fri Jun  4 12:59:52 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 0034F3A1EF2 for <dmarc@ietfa.amsl.com>; Fri,  4 Jun 2021 12:59:50 -0700 (PDT)
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 dZMRjsYawrnn for <dmarc@ietfa.amsl.com>; Fri,  4 Jun 2021 12:59:46 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450: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 627A43A1EF5 for <dmarc@ietf.org>; Fri,  4 Jun 2021 12:59:46 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id d2so8890492ljj.11 for <dmarc@ietf.org>; Fri, 04 Jun 2021 12:59:46 -0700 (PDT)
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=m4V+AAJ2a36H5estDQTmzl4e8yvYqpf7+YOL/ICYi88=; b=rGIoIRc5AZTkyibYiMcem5BZOIfqmaev+4yL+p/UfgIXEjTvVoQwNFbJEx5btDCy4d rNQ+rI4fElGC2/H6wA9+2hpxvnDhaK7D1OTvJRjLGIDYW8KTPwXpsxtpPptgXux4dYYd 1wCdiAooOakaQoOwfckq995ioc9eG+VdmEqeHSL1d0zNsEpviMyBTS84QMfffHyriNOM o9fHqeMYnFjdR1pGjkJHQT4PSdhM3W8Cidd7qFZfmHNAHKcBrSyLfFJbvVR+nx6rgS5U UBrIT0aDkQ5BnQlaBPP3O7jgePUJqeQqcq+USJJ+89zU+ALzl3/A4LU20uy7UXDGyGrX wqwg==
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=m4V+AAJ2a36H5estDQTmzl4e8yvYqpf7+YOL/ICYi88=; b=je8Hjp/8Uw3m3IYyz2mXLy961d33KXMhuv95LzKhLZ9WIvnD22T3IejlRyoQxCRGJ4 YmyzPDSWMQEaC+7dxExD5nu/2H5zkxk0WZFVjYKG16e82s7g/VClPtIM0xf/gYKeqhRu ILxUBzYeSn9NV7aC35hSyTRpYljnYs9E7VrzkZLbJErLCZbBmm0/SM4wIK5M0/I9r+wJ R00MA2UlRPEAcBwIbGrV64NMOMJr2o58Z/tfcKXesta4RRXcI8jgoWtt8tjoj7q0iNpS ud4NRDwYXFOXYsB9+OQhRs/IcqbkPY1ibt+pG/kTH840TKx3+ZC0xPcgjWprdgVVAqCy 5v9A==
X-Gm-Message-State: AOAM531wtxXy8JMmfjStndcF1LP8oPKdMqF3zmweG89U0efiuZ4V16T0 UyDY9vb7jKHjHcCzIvNqwktYchn42vrbci2tb44=
X-Google-Smtp-Source: ABdhPJwQxxTNID7fD4bX3f1Sjpyej9tLo6epwXfllBFHJtZmGjd0zZ6A3bFKs3Kc0wx8wD5bsPqAjw8irYrus6onjLQ=
X-Received: by 2002:a05:651c:1105:: with SMTP id d5mr4549931ljo.431.1622836784195;  Fri, 04 Jun 2021 12:59:44 -0700 (PDT)
MIME-Version: 1.0
References: <e6403b99-dcc2-1507-4187-a7586c9f5eea@tana.it> <20210603221737.C8146B6B7BB@ary.qy> <CAJ4XoYcek=dW6Q75CTzQzB+9szUWreC8D8_he0SiLw-7m_25UQ@mail.gmail.com>
In-Reply-To: <CAJ4XoYcek=dW6Q75CTzQzB+9szUWreC8D8_he0SiLw-7m_25UQ@mail.gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 4 Jun 2021 15:59:33 -0400
Message-ID: <CADyWQ+HDHatO8XTzpPZXWL0+BzgJ5=JjAQDoWPi=rFLTO2V=cw@mail.gmail.com>
To: Dotzero <dotzero@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000cea0c05c3f62247"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4j_BQLXEbXq8lR-_qiF4BYUYeaA>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #47 (Removal of "pct" tag) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 04 Jun 2021 19:59:51 -0000

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

+1 With Mr Levine's line of thinking.

I also agree with keeping pct= tag.

tim


On Thu, Jun 3, 2021 at 7:16 PM Dotzero <dotzero@gmail.com> wrote:

>
>
> On Thu, Jun 3, 2021 at 6:17 PM John Levine <johnl@taugh.com> wrote:
>
>> It appears that Alessandro Vesely  <vesely@tana.it> said:
>> >On Thu 03/Jun/2021 05:45:33 +0200 Murray S. Kucherawy wrote:
>> >> I don't understand what "demeaning a domain's policy" means.
>> >
>> >I meant to say that p=quarantine; pct=0 is to be considered a strict
>> policy to
>> >all effects.  Saying so should prevent reasoning something like "Oh,
>> they said
>> >quarantine, but since pct=0 it is somewhat faked, so I'll skip X", where
>> X
>> >could be rewriting From:, displaying a BIMI image, record aggregate
>> data, or
>> >any other action that might depend on the policy.  That is to say pct=0
>> does
>> >not alter the value of p=, otherwise testing becomes a nightmare.
>>
>> If we agree that's what we mean, that's what we should say, e.g., add
>> something
>> like this:
>>
>>  Senders may use pct=0 to signal an intention to apply a stricter
>>  DMARC policy in the future, and to request receivers that do special
>>  processing based on DMARC policy to do that processing. Examples of
>>  special processing might include mailing list software rewriting
>>  addresses in From headers.
>>
>
> As long as we get the wording right, I agree with your line of thinking
> John. Again, we don't have insight as to the extent that receivers will
> honor the request.
>
> Michael Hammer
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--0000000000000cea0c05c3f62247
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">+1 With Mr Levine&#39;s line of thinking.=C2=A0=C2=A0<br></div><div clas=
s=3D"gmail_default" style=3D"font-family:monospace"><br></div><div class=3D=
"gmail_default" style=3D"font-family:monospace">I also agree with keeping p=
ct=3D tag.=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">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"gma=
il_attr">On Thu, Jun 3, 2021 at 7:16 PM Dotzero &lt;<a href=3D"mailto:dotze=
ro@gmail.com">dotzero@gmail.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On T=
hu, Jun 3, 2021 at 6:17 PM John Levine &lt;<a href=3D"mailto:johnl@taugh.co=
m" target=3D"_blank">johnl@taugh.com</a>&gt; wrote:<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex">It appears that Alessandro Vesely=C2=A0=
 &lt;<a href=3D"mailto:vesely@tana.it" target=3D"_blank">vesely@tana.it</a>=
&gt; said:<br>
&gt;On Thu 03/Jun/2021 05:45:33 +0200 Murray S. Kucherawy wrote:<br>
&gt;&gt; I don&#39;t understand what &quot;demeaning a domain&#39;s policy&=
quot; means.<br>
&gt;<br>
&gt;I meant to say that p=3Dquarantine; pct=3D0 is to be considered a stric=
t policy to <br>
&gt;all effects.=C2=A0 Saying so should prevent reasoning something like &q=
uot;Oh, they said <br>
&gt;quarantine, but since pct=3D0 it is somewhat faked, so I&#39;ll skip X&=
quot;, where X <br>
&gt;could be rewriting From:, displaying a BIMI image, record aggregate dat=
a, or <br>
&gt;any other action that might depend on the policy.=C2=A0 That is to say =
pct=3D0 does <br>
&gt;not alter the value of p=3D, otherwise testing becomes a nightmare.<br>
<br>
If we agree that&#39;s what we mean, that&#39;s what we should say, e.g., a=
dd something<br>
like this:<br>
<br>
=C2=A0Senders may use pct=3D0 to signal an intention to apply a stricter<br=
>
=C2=A0DMARC policy in the future, and to request receivers that do special<=
br>
=C2=A0processing based on DMARC policy to do that processing. Examples of<b=
r>
=C2=A0special processing might include mailing list software rewriting<br>
=C2=A0addresses in From headers.<br></blockquote><div><br></div><div>As lon=
g as we get the wording right, I agree with your line of thinking John. Aga=
in, we don&#39;t have insight as to the extent that receivers will honor th=
e request.</div><div><br></div><div>Michael Hammer<br></div></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--0000000000000cea0c05c3f62247--


From nobody Sat Jun  5 04:45:15 2021
Return-Path: <mail@wander.science>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB4803A201C for <dmarc@ietfa.amsl.com>; Sat,  5 Jun 2021 04:45:13 -0700 (PDT)
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=wander.science
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JulMED5VUV9f for <dmarc@ietfa.amsl.com>; Sat,  5 Jun 2021 04:45:09 -0700 (PDT)
Received: from mail.swznet.de (cathay.swznet.de [IPv6:2a01:4f8:13b:2048::113]) (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 E55C83A201D for <dmarc@ietf.org>; Sat,  5 Jun 2021 04:45:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=wander.science; s=cathay; h=Subject:Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Sender:Reply-To: Cc: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=ZzcwSWP9br3Gmhp/Af1pP4dD1LDRfjsGVfr853iAw/Y=; b=IwVcUxMabDZlf3QYlIswcj61IT 7JmrpZQ50I/KCZpwRcWJo+eGbR+X+ySPJZnOeR7gOn6BjPAVHYsBVLfIHjrb95/oA7YKBRC+hZFYM 2CvBWyDoS3Yff94uMYGW6qdUEEevsI/Ic+hmSkML2pw/DqG4Q8+04RmtY/Gt2ugd1WzKZHJlFzOf8 JnWfVByjGZAjaCJ34/kEANPNejolblunjsf70igU2liYHP07cfAcKDTvpINVN5vkFY+0GkTp6HyRp R2HQo2tirD7TSrrWHnxUbfj8kIWXi0hCpvf7K8/i+0sCTaElZP3YKLYLK5OAw/j9o57U7hKzfElDe s+ZzqAnA==;
Received: from dynamic-2a01-0c22-b826-2100-284a-ff4d-6201-9b43.c22.pool.telefonica.de ([2a01:c22:b826:2100:284a:ff4d:6201:9b43]) by mail.swznet.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <mail@wander.science>) id 1lpUjd-0002k7-77 for dmarc@ietf.org; Sat, 05 Jun 2021 13:45:05 +0200
To: dmarc@ietf.org
References: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@MN2PR11MB4351.namprd11.prod.outlook.com>
From: =?UTF-8?Q?Matth=c3=a4us_Wander?= <mail@wander.science>
Message-ID: <e6575d23-7d8f-fcb8-ae21-72ce46f4600c@wander.science>
Date: Sat, 5 Jun 2021 13:45:00 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@MN2PR11MB4351.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:c22:b826:2100:284a:ff4d:6201:9b43
X-SA-Exim-Mail-From: mail@wander.science
X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000)
X-SA-Exim-Scanned: Yes (on mail.swznet.de)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/55ZPD_E2dZT_wj903WGxJQ-JaWU>
Subject: Re: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 05 Jun 2021 11:45:14 -0000

ARC shows the need for extension data within <record> elements:
<https://datatracker.ietf.org/doc/html/rfc8617#section-7.2.2>

Example from RFC 8617:
<policy_evaluated>
  <disposition>none</disposition>
  <dkim>fail</dkim>
  <spf>fail</spf>
  <reason>
   <type>local_policy</type>
   <comment>arc=pass as[2].d=d2.example as[2].s=s2
	as[1].d=d1.example as[1].s=s3
	remote-ip[1]=2001:DB8::1A</comment>
  </reason>
</policy_evaluated>

With proper extension support, this example could look like this:
<row>
   <policy_evaluated>
     <disposition>none</disposition>
     <dkim>fail</dkim>
     <spf>fail</spf>
     <reason>
       <type>extension</type>
       <comment>arc=pass</comment>
     </reason>
   </policy_evaluated>
</row>
<auth_results>...</auth_results>
<extensions>
   <arc xmlns="(...)">
     <result>pass</result>
     <sets>
       <as>
         <instance>2</instance>
         <domain>d2.example</domain>
         <selector>s2</domain>
       </as>
       <as>
         <instance>1</instance>
         <domain>d1.example</domain>
         <selector>s3</domain>
         <remote_ip>2001:DB8::1A</remote_ip>
       </as>
     </sets>
   </arc>
</extensions>

An IANA registry could serve as repository of IETF-approved extensions.

It's worth considering whether certain elements should be defined as 
extensible. In the above example, the <arc> element could be placed 
below <auth_results> next to the existing <dkim> and <spf> elements. 
Implementations support this behavior by simply ignoring unknown 
elements. XML Schema supports extensibility in well-defined places with 
the <xsd:any> element.

Regards,
Matt


From nobody Sat Jun  5 04:56:18 2021
Return-Path: <mail@wander.science>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C039D3A2079 for <dmarc@ietfa.amsl.com>; Sat,  5 Jun 2021 04:56:16 -0700 (PDT)
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, NICE_REPLY_A=-0.001, 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=wander.science
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I8BVdxMDKhKq for <dmarc@ietfa.amsl.com>; Sat,  5 Jun 2021 04:56:12 -0700 (PDT)
Received: from mail.swznet.de (cathay.swznet.de [IPv6:2a01:4f8:13b:2048::113]) (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 07D733A2075 for <dmarc@ietf.org>; Sat,  5 Jun 2021 04:56:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=wander.science; s=cathay; h=Subject:Content-Type:In-Reply-To:MIME-Version: Date:Message-ID:From:References:To:Sender:Reply-To:Cc: Content-Transfer-Encoding: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=LbN6xIyZLwzi/UBZMHeOwrqreySaPx9pxdxZI+VDJWU=; b=jC0Uc0IAr48rUdMgt3jJVZnQt YmdsZQ54Vv4dwDPpOG17O/pBD+ELc1G1coPbgqgPctOchgFPN365ot5bh9sxySbdX5dNsG0zWlUkO BOJVgrYNaKR3sTtD4pzEIpLB35vrD0kQek3wQn4bqqhlYyqSJI6LaPjRps8D2DSSBfKYdmpq9O0jd 4yG64mzErUMQVe3CYGW90kCK5VIWazLFILeGbre4od1wtYq31p4iWVYYNIViQh7TEPuEYpKalJ/r9 fyiNW1C9OgXhAKTaF9zLUVBOHxFp4ixIhnsVw6f2yuFk2gJL/Yf6yun1eDEQaYtXNbFuk6nqjtnNs /fU3QXS3A==;
Received: from dynamic-2a01-0c22-b826-2100-284a-ff4d-6201-9b43.c22.pool.telefonica.de ([2a01:c22:b826:2100:284a:ff4d:6201:9b43]) by mail.swznet.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <mail@wander.science>) id 1lpUuL-0003Eu-HT for dmarc@ietf.org; Sat, 05 Jun 2021 13:56:09 +0200
To: dmarc@ietf.org
References: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@MN2PR11MB4351.namprd11.prod.outlook.com> <f04b1dfa-2707-a67e-4df8-bf82d637f4f8@tana.it>
From: =?UTF-8?Q?Matth=c3=a4us_Wander?= <mail@wander.science>
Message-ID: <e213afa6-c777-d0a6-48ac-43965ff264cd@wander.science>
Date: Sat, 5 Jun 2021 13:56:04 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <f04b1dfa-2707-a67e-4df8-bf82d637f4f8@tana.it>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms080505080001080801090801"
X-SA-Exim-Connect-IP: 2a01:c22:b826:2100:284a:ff4d:6201:9b43
X-SA-Exim-Mail-From: mail@wander.science
X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000)
X-SA-Exim-Scanned: Yes (on mail.swznet.de)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/KY7tK1bON6WVsPLrwbfCKRGvhng>
Subject: Re: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 05 Jun 2021 11:56:17 -0000

This is a cryptographically signed message in MIME format.

--------------ms080505080001080801090801
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Alessandro Vesely wrote on 2021-06-04 11:26:
> Second, I'm not sure we need an <extensions> container. =20
> I'd go for an example like, say, so:
>=20
> [...]
>  =C2=A0=C2=A0 <extension_metadata name=3D"bimi"=20
> xmlns=3D"http://ietf.org/xml-namesapaces/bimi-xml?/1.0">
 > [...]
>  =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <extension name=3D"bimi"=20
> xmlns=3D"http://ietf.org/xml-namesapaces/bimi-xml??/1.0">

If we use an attribute for the extension name, then we don't the=20
container section.
As the current schema does not use attributes at all, I'm more inclined=20
to define the extension name in a different way for consistent non-use=20
of attributes. But that's a minor detail.

>> 1) Extensions in their own section (as it is now) or within each <row>=
=20
>> element
>=20
>=20
> Both, and both optional.=C2=A0 An extension can have some data to add i=
n some=20
> <record>, but not necessarily in all of them.

+1

Regards,
Matt


--------------ms080505080001080801090801
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CicwggUCMIID6qADAgECAhMG/v9jPKQMdbI65QUQ8a5ne+QtMA0GCSqGSIb3DQEBCwUAMIGk
MQswCQYDVQQGEwJVUzERMA8GA1UECBMISWxsaW5vaXMxEDAOBgNVBAcTB0NoaWNhZ28xITAf
BgNVBAoTGFRydXN0d2F2ZSBIb2xkaW5ncywgSW5jLjEsMCoGA1UEAxMjVHJ1c3R3YXZlIFMv
TUlNRSBTSEEyNTYgQ0EsIExldmVsIDExHzAdBgkqhkiG9w0BCQEWEGNhQHRydXN0d2F2ZS5j
b20wHhcNMTkwNjEwMDkwMjM3WhcNMjIwNjA5MTUwMjM3WjBCMRwwGgYDVQQDDBNtYWlsQHdh
bmRlci5zY2llbmNlMSIwIAYJKoZIhvcNAQkBFhNtYWlsQHdhbmRlci5zY2llbmNlMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr6WOVa7d9CO/gDeD5sYNTUshzO9rKp6pjLaM
0RXlHjzJvUgpCvEDvS37WBq6R4mXhssI1maxKBFd7UJvf+NUrqQArnY8SNoSB+0wDqjXB2ZT
Y4ddZTcCboezo7irDkDEZmDJe7eRtHw/Uf1N0QC6HsCFQPQAOopH738DIP4oM/0mXpZBYzzs
M7SLnz3CgCR61yAB4ePtlgTc8FhK5mRhR7L6AIBkiv7u77nju18UqRkzny9XJ/I8s2KpdCCr
vLuIMNGs21PRIqTNvUjVEJ01wjklrAEuZskB8R+1JoCJsfda+WNmzEstQRpESqE/aw6+9eDz
Gh+nJZi6V4kzx+FK5wIDAQABo4IBjDCCAYgwDAYDVR0TAQH/BAIwADAOBgNVHQ8BAf8EBAMC
BaAwEwYDVR0lBAwwCgYIKwYBBQUHAwQwHQYDVR0OBBYEFAtDGeK+i+tXLp/fNLame6BvnkY6
MB8GA1UdIwQYMBaAFAwzo1eq46vWS3AbNp6j7WFQ5q90MEgGA1UdIARBMD8wPQYPKwYBBAGB
7RgDAwMFBAMDMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vc3NsLnRydXN0d2F2ZS5jb20vQ0Ew
HgYDVR0RBBcwFYETbWFpbEB3YW5kZXIuc2NpZW5jZTA2BgNVHR8ELzAtMCugKaAnhiVodHRw
Oi8vY3JsLnRydXN0d2F2ZS5jb20vU01DQTJfTDEuY3JsMHEGCCsGAQUFBwEBBGUwYzAmBggr
BgEFBQcwAYYaaHR0cDovL29jc3AudHJ1c3R3YXZlLmNvbS8wOQYIKwYBBQUHMAKGLWh0dHA6
Ly9zc2wudHJ1c3R3YXZlLmNvbS9pc3N1ZXJzL1NNQ0EyX0wxLmNydDANBgkqhkiG9w0BAQsF
AAOCAQEASigcyuW1rKeXr5BAfvZbfAZtybP1r7vj0BHVTQ5Uvja97n3vOTrMEHsfaPWRi/9r
tihSgkhKoVBcZ17oTbaYmoPQFXwfMsnexdT9eCoSPYjx2iRp6py3vUFe6cN5ciJCTi1+mGf9
m+rei88Zg/0rv236fuh+Wsis1zOolgBTqNeMEnXnVEPxd6wtQV7TGOcWa3t/qldRweRT5siS
WGoBPrq6LECg8sUbYAimzMUAJcBtrNCyuxcPdFCp+Zh3aNiQW5sz/jk0xZay2by9fVv9b4y/
fBS1EPCeNvVkwPgOBqYGc5J98dPu2xhj2qxFEla1mQKyIQttwE22KXI0LIgcpzCCBR0wggQF
oAMCAQICEDqDtx7gLDzKHOGiZD6bZuowDQYJKoZIhvcNAQELBQAwgYIxCzAJBgNVBAYTAlVT
MR4wHAYDVQQLExV3d3cueHJhbXBzZWN1cml0eS5jb20xJDAiBgNVBAoTG1hSYW1wIFNlY3Vy
aXR5IFNlcnZpY2VzIEluYzEtMCsGA1UEAxMkWFJhbXAgR2xvYmFsIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE0MTAwMTE5MjIzOFoXDTI0MDkyODE5MjIzOFowgaQxCzAJBgNVBAYT
AlVTMREwDwYDVQQIEwhJbGxpbm9pczEQMA4GA1UEBxMHQ2hpY2FnbzEhMB8GA1UEChMYVHJ1
c3R3YXZlIEhvbGRpbmdzLCBJbmMuMSwwKgYDVQQDEyNUcnVzdHdhdmUgUy9NSU1FIFNIQTI1
NiBDQSwgTGV2ZWwgMTEfMB0GCSqGSIb3DQEJARYQY2FAdHJ1c3R3YXZlLmNvbTCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBAOHOSOYIg9MBIfkbqCyCZA+2upgZZvmM07V0nnxn
o1VWLaY3JZFJeAuIRH0DAlHKwZ1NzkR1aa14v0PNnSjRT2nPBSPW4/JratHI3Ug31ySn3X+d
sD1504wEsCsoSbfgqCYpPhc+9igJI8YvjlEqVnUAXgEK2nW7buFBhU4D3LlP3MKRfCdIOAhp
P7GlSpJCTaaucKqX0EWJdNuRcim85kY6oQf02qaB5WxzEO2nqGfqrQwvnlpxNwKk1B8deGeX
3oIy0EZj1qqnXmWn7YaLoJWxLh7eAHss3n0wzcMl41IkQ/59JGjTVvpXLC6cO6LsNTlPJsEN
Auy6DyZY6V0Y7zsCAwEAAaOCAWkwggFlMBIGA1UdEwEB/wQIMAYBAf8CAQAwHQYDVR0OBBYE
FAwzo1eq46vWS3AbNp6j7WFQ5q90MA4GA1UdDwEB/wQEAwIBhjBIBgNVHSAEQTA/MD0GDysG
AQQBge0YAwMDBQQDAzAqMCgGCCsGAQUFBwIBFhxodHRwczovL3NzbC50cnVzdHdhdmUuY29t
L0NBMDIGA1UdHwQrMCkwJ6AloCOGIWh0dHA6Ly9jcmwudHJ1c3R3YXZlLmNvbS9YR0NBLmNy
bDBsBggrBgEFBQcBAQRgMF4wJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnRydXN0d2F2ZS5j
b20wNQYIKwYBBQUHMAKGKWh0dHA6Ly9zc2wudHJ1c3R3YXZlLmNvbS9pc3N1ZXJzL1hHQ0Eu
Y3J0MBMGA1UdJQQMMAoGCCsGAQUFBwMEMB8GA1UdIwQYMBaAFMZPoj0GY4QJnM5i5ASsjVy1
6bYbMA0GCSqGSIb3DQEBCwUAA4IBAQCHRix7n1HoMxSlQUFVrN2ACBagnCb3WpNeEzESJsSb
J0Fi8/oyFtKJQtCQE2OjYMQG4yCQOMLVv7QPq4BOlnAOct2yzd20TEFQ0rul9uoZFY78KOP1
WMpDqd3vQqpX3oCQLK6gUCl5FKRG2BJpqK18Y+v++Hv/8cF089F0tAUvXF4TjZU0H38iZzHi
2rp80EtcfzLwC3zwhwmQkznyw5sMpSrRx7vldirNB1fma8wgUUeVtzIRk1Oz6TRDEMMhhfjB
uXmU3dI8sTkjo2l0Ju4g4dLRv4imWXoJ+QITXWhxO+EBB04yvrXi0JaOtEBgZHnMs2pIFWGf
xM2pc/J0MIQgMYIEZTCCBGECAQEwgbwwgaQxCzAJBgNVBAYTAlVTMREwDwYDVQQIEwhJbGxp
bm9pczEQMA4GA1UEBxMHQ2hpY2FnbzEhMB8GA1UEChMYVHJ1c3R3YXZlIEhvbGRpbmdzLCBJ
bmMuMSwwKgYDVQQDEyNUcnVzdHdhdmUgUy9NSU1FIFNIQTI1NiBDQSwgTGV2ZWwgMTEfMB0G
CSqGSIb3DQEJARYQY2FAdHJ1c3R3YXZlLmNvbQITBv7/YzykDHWyOuUFEPGuZ3vkLTANBglg
hkgBZQMEAgEFAKCCAnkwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx
DxcNMjEwNjA1MTE1NjA0WjAvBgkqhkiG9w0BCQQxIgQgpTisOOJkVJuK3fFGCH6QGAxnPJeA
RRl3g8WHgk9ciqowbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAEC
MAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzAN
BggqhkiG9w0DAgIBKDCBzQYJKwYBBAGCNxAEMYG/MIG8MIGkMQswCQYDVQQGEwJVUzERMA8G
A1UECBMISWxsaW5vaXMxEDAOBgNVBAcTB0NoaWNhZ28xITAfBgNVBAoTGFRydXN0d2F2ZSBI
b2xkaW5ncywgSW5jLjEsMCoGA1UEAxMjVHJ1c3R3YXZlIFMvTUlNRSBTSEEyNTYgQ0EsIExl
dmVsIDExHzAdBgkqhkiG9w0BCQEWEGNhQHRydXN0d2F2ZS5jb20CEwb+/2M8pAx1sjrlBRDx
rmd75C0wgc8GCyqGSIb3DQEJEAILMYG/oIG8MIGkMQswCQYDVQQGEwJVUzERMA8GA1UECBMI
SWxsaW5vaXMxEDAOBgNVBAcTB0NoaWNhZ28xITAfBgNVBAoTGFRydXN0d2F2ZSBIb2xkaW5n
cywgSW5jLjEsMCoGA1UEAxMjVHJ1c3R3YXZlIFMvTUlNRSBTSEEyNTYgQ0EsIExldmVsIDEx
HzAdBgkqhkiG9w0BCQEWEGNhQHRydXN0d2F2ZS5jb20CEwb+/2M8pAx1sjrlBRDxrmd75C0w
DQYJKoZIhvcNAQEBBQAEggEAdo3DzhLjYliOQnD27T4Qe4acWEhs2pHYfufU3dyAvDw7cKnl
WVOcEoC9YJnfOM5ZiPByvMaKbxwiA3k+3OlGxCiPRlC2+HzeUlBsS6jGhYefDes/S7SjR8BQ
e6FMP6XM+VRD/b4tfp2DX15r/qIx4yqWR6lRxM5KfCjsuWQdzM1R+2PaWRD6Dxcr2wCeGw0Q
YjYhl+FrDSJyXxYruPjttPdf4/un+Ni/9w+dkHlMMD/LPp+GFR+TYyOIlkQE7Tb8rSqKK/qm
4p4uSOINQtQ/rvbQ4sA03yIFOb/XFb6i6yvjN14VnDe45XWmIieqtn2lsqRGFBkuxBUfdWaK
K4lXYgAAAAAAAA==
--------------ms080505080001080801090801--


From nobody Sun Jun  6 03:00:25 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 D72B43A13FC for <dmarc@ietfa.amsl.com>; Sun,  6 Jun 2021 03:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Ru3OEss4PGcj for <dmarc@ietfa.amsl.com>; Sun,  6 Jun 2021 03:00:12 -0700 (PDT)
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 AA6E03A13FD for <dmarc@ietf.org>; Sun,  6 Jun 2021 03:00:11 -0700 (PDT)
Received: (qmail 62356 invoked by uid 100); 6 Jun 2021 10:00:10 -0000
Date: 6 Jun 2021 09:59:48 -0000
Message-ID: <20210606095948.62355.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/fFHVTZ-7lm1XtXzEl56kk4J7CXM>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Jun 6 06:00:09 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, 06 Jun 2021 10:00:18 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
  4 (21.1%) |  87544 (40.7%) | Dave Crocker <dcrocker@gmail.com>
  3 (15.8%) |  18955 ( 8.8%) | Alessandro Vesely <vesely@tana.it>
  2 (10.5%) |  18122 ( 8.4%) | Dotzero <dotzero@gmail.com>
  2 (10.5%) |  16658 ( 7.7%) | Matthäus Wander <mail@wander.science>
  2 (10.5%) |   8432 ( 3.9%) | John Levine <johnl@taugh.com>
  1 ( 5.3%) |  18800 ( 8.7%) | Trent Adams <tadams@proofpoint.com>
  1 ( 5.3%) |  12728 ( 5.9%) | Brotman, Alex <alex_brotman@comcast.com>
  1 ( 5.3%) |  11601 ( 5.4%) | Murray S. Kucherawy <superuser@gmail.com>
  1 ( 5.3%) |   9642 ( 4.5%) | Tim Wicinski <tjw.ietf@gmail.com>
  1 ( 5.3%) |   7765 ( 3.6%) | Barry Leiba <barryleiba@computer.org>
  1 ( 5.3%) |   5080 ( 2.4%) | Steven M Jones <smj@crash.com>


From nobody Mon Jun  7 12:44: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 9F0723A0653 for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 12:44:53 -0700 (PDT)
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 7XO0gvwV02Dl for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 12:44:49 -0700 (PDT)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 188673A0602 for <dmarc@ietf.org>; Mon,  7 Jun 2021 12:44:48 -0700 (PDT)
Received: by mail-pj1-x102d.google.com with SMTP id h16so10529128pjv.2 for <dmarc@ietf.org>; Mon, 07 Jun 2021 12:44:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=to:from:subject:message-id:date:user-agent:mime-version :content-language; bh=bWIw6BBszJjGqxA0J1mtAgXwzGq3Xh5eCwWkzUfcw9g=; b=PPMjnH+1LqoRqNg1g62lhzPvh1ok10zj63mA7ydkT3j5aBuESVnGa6O7SOkLmWAZSC zL/gFkl5igPjClN04qCB8bySm/rwRYPpov2JQcGEUdFp0QSAXSa3/dYiEWPye33GVJr3 7l05kpVnJ+Ki7pVJrgaElVaq94GTCXcRa6ZymgXyO8EMZrqxAXPJGdF4qO7lyN+qMsn9 tkGwEDzg96LBNPvLDfRjCBy0MFnqdTwL+rAUaObHDIAP8ABK8tqGqR48iA5dl7S0qUb5 yFBAXdi+OewqM2GUeG6PgSDorX49FnxjgYGHeVEgFA8Iqi4NAZVAk55EEFkPiyIK8krr FFdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language; bh=bWIw6BBszJjGqxA0J1mtAgXwzGq3Xh5eCwWkzUfcw9g=; b=HD+4dnFF3Fgn7tczJ4PajDOJx36nZYtTU78hw1sUkbqUE3VDdv8kffNtpvfAd/25hb MMAc+/YDj+FM8Cak3UeGAuN//kwz++jWEWVXRE+Mv50gDUDs+gDnz4oyyPeXst+i6W9/ yy/s9OBtxCyXY5YGFf+1Ib/NIqvZqhQbs90hCZsS1Os3Ks1f+bATpgo5USHO32bCmmdP VJzzZ/En2R4FgRnvYRFCTVYoYLvG2++6sHN0m48wjI4IPF60lE7ScnSxR3qCCBQchYwX HDKNqHJRliJdMeGVNi44w9oVv+yKNoEuN4yAJrFuCRkKoz5TVaewTTRe+TAwUn2zB6AL dbBA==
X-Gm-Message-State: AOAM532p6giqGrmZsOTa+FV1/khx25+Wp+dVoDshXz7BRMkNW3dpadTe uoGx/a8k0isLnoB+x7BLDGboj2Y6Gmg6bg==
X-Google-Smtp-Source: ABdhPJxhX42zdmNHATGbUwxcJW1ZlUONkSeMfIaYV1Z41Gvrb/SniQcYks1dr07qFAXGMGsnt4KTQg==
X-Received: by 2002:a17:90a:4a0e:: with SMTP id e14mr751190pjh.209.1623095087651;  Mon, 07 Jun 2021 12:44:47 -0700 (PDT)
Received: from [192.168.0.106] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id w21sm4448017pfq.143.2021.06.07.12.44.46 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 07 Jun 2021 12:44:47 -0700 (PDT)
To: IETF DMARC WG <dmarc@ietf.org>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <e85c8df6-779c-4870-21b6-4ce6b343736b@gmail.com>
Date: Mon, 7 Jun 2021 12:44:45 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------461EDA0CA6D1795F1E1D0213"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/OFDuLlugTdF55bdlqL8j9TRbc_w>
Subject: [dmarc-ietf] Ticket 7, 47, and 52_
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 07 Jun 2021 19:44:54 -0000

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

Sorry, not sure which ticket this is tied to.


> *_Ticket 7, 47, and 52_*
>
>       dmarc-record    = dmarc-version dmarc-sep
>                         [dmarc-request] [dmarc-sep dmarc-srequest] [dmarc-sep dmarc-auri] 
> [dmarc-sep dmarc-furi] [dmarc-sep dmarc-adkim] [dmarc-sep dmarc-aspf] 
> [dmarc-sep dmarc-ainterval] [dmarc-sep dmarc-fo] [dmarc-sep 
> dmarc-rfmt] [dmarc-sep dmarc-percent] [dmarc-sep]  **(dmarc-tag dmarc-sep) dmarc-tag = dmarc-request / dmarc-srequest / 
> dmarc-auri / dmarc-furi / dmarc-ainterval / dmarc-fo / dmarc-rfmt*
>                         ; components other than dmarc-version and
>                         ; dmarc-request may appear in any order

1. I just had cause to review the previous ABNF and thought that 
something like this change would be quite nice.  Then saw that you'd 
done it.  So, good job!

Reviewing the above text, I realized that the comment text is no longer 
needed and might even be confusing.


d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
Information & Planning Coordinator
American Red Cross
dave.crocker2@redcross.org


--------------461EDA0CA6D1795F1E1D0213
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>Sorry, not sure which ticket this is tied to.<br>
    </p>
    <p><br>
      <blockquote type="cite">
        <pre><strong><font color="green">_Ticket 7, 47, and 52_</font></strong>

     dmarc-record    = dmarc-version dmarc-sep
                       <strike><font color="red">[dmarc-request]
                       [dmarc-sep dmarc-srequest]
                       [dmarc-sep dmarc-auri]
                       [dmarc-sep dmarc-furi]
                       [dmarc-sep dmarc-adkim]
                       [dmarc-sep dmarc-aspf]
                       [dmarc-sep dmarc-ainterval]
                       [dmarc-sep dmarc-fo]
                       [dmarc-sep dmarc-rfmt]
                       [dmarc-sep dmarc-percent]
                       [dmarc-sep]</font></strike> <strong><font color="green">*(dmarc-tag dmarc-sep)

     dmarc-tag       = dmarc-request /
                       dmarc-srequest /
                       dmarc-auri /
                       dmarc-furi /
                       dmarc-ainterval /
                       dmarc-fo /
                       dmarc-rfmt</font></strong>
                       ; components other than dmarc-version and
                       ; dmarc-request may appear in any order</pre>
      </blockquote>
    </p>
    <p>1. I just had cause to review the previous ABNF and thought that
      something like this change would be quite nice.  Then saw that
      you'd done it.  So, good job!<br>
    </p>
    <p>Reviewing the above text, I realized that the comment text is no
      longer needed and might even be confusing.</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
Information &amp; Planning Coordinator
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------461EDA0CA6D1795F1E1D0213--


From nobody Mon Jun  7 14:31:24 2021
Return-Path: <todd.herr@valimail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1260A3A1207 for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 14:31:23 -0700 (PDT)
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_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XQY6t65cbXtg for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 14:31:17 -0700 (PDT)
Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 835763A1203 for <dmarc@ietf.org>; Mon,  7 Jun 2021 14:31:17 -0700 (PDT)
Received: by mail-qv1-xf2e.google.com with SMTP id u14so6808762qvq.6 for <dmarc@ietf.org>; Mon, 07 Jun 2021 14:31:17 -0700 (PDT)
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=HXLXRZMGLfHxPX3gNEn8Hp01eTXV32HQxE3bvOBFwA8=; b=QAbu2BsOKnLrefFGgONrjHRiz0Sj4uBDsNB8cxN2ImrLfSK1zlcrNLDvqvAzGleSzH HO6ZwLwoJNWGhztqkLB6yfajYD06Vj/1/amAnNDlC2Gb0YtbZJO5Ae9mCq6sJ132OMGe i+NQkkk87OSl8cY+VXOGDBPF/t8BYo7/UQZSLJ5XiduGE75ID1W1zFqZQlMnzXAeib0C mEr2HLjXgBLqvNymrPbdq7cFNnh5hfUJvCg1TvjZHpJROTMbGljZKw0FwJokmwu4Yha8 hDOFa3lVZbEhvy+jm5RjzYCOvHYXyWtylZNcC/OutGgxSBZ3yYXfyA3gIFkI2XgqnXrG l8fw==
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=HXLXRZMGLfHxPX3gNEn8Hp01eTXV32HQxE3bvOBFwA8=; b=ai7dOmB9UBp+/OA1hnstM0FPtOdJgLPwpgxKWR884hPLsmOa+XCvGVQRymokgxX7pU e2Oo+0WYqp+S5j/l3HUqcl5yaZCKx+toYpGl73DisL3PZM0y8CAkOsY1TzDTUcdPJxVF cA10YD6rKbvvBj2j+1JURvoDZLHyUA4qZWfD9dJyzY9ezeU/sYEoLWoRrgl4PNQecMMt 7rZ0uRvMRNoZpXM/gwu3GbDWi0+iXgOvSXF5L+JzzJuNBd5/FN3GZ8PanHsm8dPTp3Uh 7jk5tyVUyb/gdCNwp4/5Jts7MPqB1Ed3GqEtGwdcCD8aH7GzfyfbGp5GCvAaY1A47qDl XmRQ==
X-Gm-Message-State: AOAM53098LPXytPfA6eLSnZBDi2s7Gc30LJb93ROnRzzhqlHyrC381E3 wnw6Dfl2aa5BDR+KodB4sEf/PfXF0r6yVWVOotrTk+rcKVo=
X-Google-Smtp-Source: ABdhPJy2TUJ2p4a7cPCB1KXqBq7hcndPJcevirUhGGYR0BrJ6MCY0mRIBIkWnh/mJ5o6/jNXL8nyS3jKndPfZz7hwiU=
X-Received: by 2002:a05:6214:252a:: with SMTP id gg10mr8697159qvb.17.1623101475099;  Mon, 07 Jun 2021 14:31:15 -0700 (PDT)
MIME-Version: 1.0
References: <e85c8df6-779c-4870-21b6-4ce6b343736b@gmail.com>
In-Reply-To: <e85c8df6-779c-4870-21b6-4ce6b343736b@gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Mon, 7 Jun 2021 17:30:59 -0400
Message-ID: <CAHej_8kr6=ah5JekSZj6fT7oyPE8ztbw3A4UbYHfRYs7XC_Geg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dba7a405c433c2ab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/b6cbyJlmPbVxbLETFy2klOksTcs>
Subject: Re: [dmarc-ietf] Ticket 7, 47, and 52_
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 07 Jun 2021 21:31:23 -0000

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

On Mon, Jun 7, 2021 at 3:45 PM Dave Crocker <dcrocker@gmail.com> wrote:

> Sorry, not sure which ticket this is tied to.
>
>
> *_Ticket 7, 47, and 52_*
>
> [snip]

> Reviewing the above text, I realized that the comment text is no longer
> needed and might even be confusing.
>

I have plans to remove the comments when version -02 is released soon.

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*m:* 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.

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

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:tahoma,sans-serif"><span style=3D"font-family:Arial,Helvetica,sans=
-serif">On Mon, Jun 7, 2021 at 3:45 PM Dave Crocker &lt;<a href=3D"mailto:d=
crocker@gmail.com">dcrocker@gmail.com</a>&gt; wrote:</span><br></div></div>=
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
 =20

   =20
 =20
  <div>
    <p>Sorry, not sure which ticket this is tied to.<br>
    </p>
    <p><br>
      </p><blockquote type=3D"cite">
        <pre><strong><font color=3D"green">_Ticket 7, 47, and 52_</font></s=
trong>
</pre></blockquote></div></blockquote><div><span class=3D"gmail_default" st=
yle=3D"font-family:tahoma,sans-serif">[snip]</span>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div><blockquote type=3D"cite"><pre><=
/pre></blockquote>
    <p>Reviewing the above text, I realized that the comment text is no
      longer needed and might even be confusing.</p></div></blockquote><div=
><br></div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-se=
rif">I have plans to remove the comments when version -02 is released soon.=
</div></div><div><br></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature=
"><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bot=
tom:0pt"></p><div style=3D"text-align:left"><span style=3D"vertical-align:b=
aseline;white-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd Her=
r</b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;fon=
t-size:small;font-family:Arial"> | Sr. Technical Program Manager</span></di=
v><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:sma=
ll;font-family:Arial"><div style=3D"text-align:left"><span style=3D"vertica=
l-align:baseline"><b>e:</b></span><span style=3D"vertical-align:baseline"> =
<a href=3D"mailto:todd.herr@valimail.com" target=3D"_blank">todd.herr@valim=
ail.com</a> </span></div></span><span><div><span><b>m:</b></span><span> 703=
.220.4153</span><span></span></div><div style=3D"text-align:left"><img styl=
e=3D"width: 175px; height: 43px;" src=3D"https://hosted-packages.s3-us-west=
-1.amazonaws.com/Valimail+Logo.png"></div></span><p dir=3D"ltr" style=3D"ba=
ckground-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-bott=
om:0pt"><font face=3D"Arial" color=3D"#666666"><span style=3D"font-size:10.=
6667px;white-space:pre-wrap">This email and all data transmitted with it co=
ntains confidential and/or proprietary information intended solely for the =
use of individual(s) authorized to receive it. If you are not an intended a=
nd authorized recipient you are hereby notified of any use, disclosure, cop=
ying or distribution of the information included in this transmission is pr=
ohibited and may be unlawful. Please immediately notify the sender by reply=
ing to this email and then delete it from your system.</span></font></p></s=
pan></div></div>

--000000000000dba7a405c433c2ab--


From nobody Mon Jun  7 14:39:42 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 17A173A126B for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 14:39:40 -0700 (PDT)
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=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 csx9Yx0ZcI0s for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 14:39:35 -0700 (PDT)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E7333A1266 for <dmarc@ietf.org>; Mon,  7 Jun 2021 14:39:35 -0700 (PDT)
Received: by mail-pl1-x634.google.com with SMTP id o12so6094185plk.8 for <dmarc@ietf.org>; Mon, 07 Jun 2021 14:39:35 -0700 (PDT)
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=PgqbiJRuzv9UZpOK/UyGUAJy1fG5HTKF85CcCZy/UMg=; b=iW0AUkyTwiQKH5bB7UrliwbZPHzhRgp0oRV9uxsHIAw6i4TItHjTsKmnOt9NbSNIln Wr/BhJNHqg8HcJ7QTJ3JR/Fb8vr6kvwXdwvTqV7S+UcgE3GUnwmld2ZcB5XLukNsoA3/ qviihmEIJP7lrKNd+ZjyivEva01Fcgs1zjsqRy8n8Te90eFJTHGQsA68p4u5KsGDPxjm 3TrXh/IKx698aKQHa5p8OBufPsmDy/RpqcebpVm6rs1F/zoJzk6Vq1RNCY/8RZ3Spnm7 KuQzuyCmcmWmEIbZ70yIaRnFHLnl5LJO59I5EOpghXDQsYDexnadKVbPk5WoTWEJ06b0 N/yg==
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=PgqbiJRuzv9UZpOK/UyGUAJy1fG5HTKF85CcCZy/UMg=; b=GUZSYknrYjmMA864sq7GO9Y4Vr6CCjC1FCxy7Da7EpT2w01tYtH34iFhExdJ+lFDH/ pocnZ8XwGmaztuGPQOW3/RsShHxx0/BLLcJFasihhYO+Qtb2ZBlOoyfL7kWCZE8cShWa yBRWtau7jPUqfzr8nA0bTIERntHKnJRuk3Vgpoc4afTMEzKyqkhTNJHxRN7rfOK2VSwb Grv3RKOMpR/4OWTV9TU8gmai6J1vTzQ6sb7dNq/OmP7HOrzzW3rZdM4fET6C/9U9VqlS 96QoLYFn9pXnhiBV3NP1KBAcijK1f6u5zSYWGoeFbsd22u9NEf+X5VTyR5/mUvLQh+r+ JPbA==
X-Gm-Message-State: AOAM531s+P5j7aBQ5ZrrVbVtDT1QMuqfvCk4LnMwIEBn/NWgefRYv3l5 /pGeHi+zcAW/eq7xdo2ovLpHRaG4S3HCCA==
X-Google-Smtp-Source: ABdhPJwCelFgubzJXIbEaWyVcDaQoGGukVIDRDY7De+zxOiDi9Ob9IUYdc2r0lIunMissONatdmr9w==
X-Received: by 2002:a17:902:e80e:b029:10a:c1c:c6e5 with SMTP id u14-20020a170902e80eb029010a0c1cc6e5mr20261987plg.54.1623101973561;  Mon, 07 Jun 2021 14:39:33 -0700 (PDT)
Received: from [192.168.0.106] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id 192sm8756218pfw.200.2021.06.07.14.39.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 07 Jun 2021 14:39:33 -0700 (PDT)
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
References: <e85c8df6-779c-4870-21b6-4ce6b343736b@gmail.com> <CAHej_8kr6=ah5JekSZj6fT7oyPE8ztbw3A4UbYHfRYs7XC_Geg@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <cba43012-020b-bb0b-9655-64162592d131@gmail.com>
Date: Mon, 7 Jun 2021 14:39:31 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8kr6=ah5JekSZj6fT7oyPE8ztbw3A4UbYHfRYs7XC_Geg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/o08kig-uNZRy1N66Irh0rdyFIIo>
Subject: Re: [dmarc-ietf] Ticket 7, 47, and 52_
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 07 Jun 2021 21:39:40 -0000

On 6/7/2021 2:30 PM, Todd Herr wrote:
> I have plans to remove the comments when version -02 is released soon.

dandy. tnx. /d

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
Information & Planning Coordinator
American Red Cross
dave.crocker2@redcross.org


From nobody Mon Jun  7 15:10:37 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 2E0873A13B7 for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 15:10:35 -0700 (PDT)
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 0wOGPB5iakBO for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 15:10:33 -0700 (PDT)
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 774AC3A13B9 for <dmarc@ietf.org>; Mon,  7 Jun 2021 15:10:33 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id o8so24315609ljp.0 for <dmarc@ietf.org>; Mon, 07 Jun 2021 15:10:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=Gnwt+8anRQPAjltv9Cv0wtKPauJ498JKPmv4fP3o66M=; b=A0Q02rKrdKijjxPQqAQOKzCGpYLIyl149wsEECYu3WaNgdaQGYvYr3pt0zIMjtGX12 VqrqausanH/AbJVdlAu3P9JCx+CPtYVw1Wz0UPPLXjpx0vR98k1E/0Q0bKLDm1DcApOd 3YJLM8hFoTHixHQfwZ8YinHqRZeLnvJcL4h6aInlJAPBFlvQhRSJlDyex5/uzqdFa0nQ dFIc7/oYvz/M0lfnHfSXZCVT0tbMxSpT4oN1s4Aa/pDUe+joSvXrlg6PhePwOJXINLDe zNcsZXK25W7UI2dEVVmRiYgw8Kh95YOCxbTLU6n+KqGAZpBIYMAhNZoI3r5/Oht0NZ3B aGOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Gnwt+8anRQPAjltv9Cv0wtKPauJ498JKPmv4fP3o66M=; b=WwrSIEByg27e1X7z4t31bgTmDKY1cImC+aL2n/gwSgwQmjwsMkwqv+KqW3mNGCvScW EyYYElrbYkTrNmLQ5DVMK14ZkoBuNRl3HM3hTxRlUD+1B4E2rtGkkdF1h9I4PpVflqmM 1+OwZf4NfO73scqhiHWt9et/U98RdBCBuvzuU32/+qhumiZmmOUTrTKTrPzKGCXmI/yV n2e+CXWSBDbTAA1EGoxgae2XZRHXPqKjheU5SIRe/B7RJx3+l2ijFQ6aESLG7m2W2VuS ugsU9wn7mEODLtgMDP9P1IFJmF80hn/u4RCbQmiNFeShD2QgXtdZogK1EjuwZ3buAMIG wG4g==
X-Gm-Message-State: AOAM533bI5rzER8mLHlL97cqx+Go9nJ+BtE6MpHOwClSzk3KjdkcbSoL yk7emdD5grCcMcBojoorg3Z/WaGvZem75ijImMbAKYNj+rQ=
X-Google-Smtp-Source: ABdhPJwJVSNOuR4eAmeyAa/ldNzuoxeAH/ZqQPlHm+mXfDTjcIQ854FSn7Cjkgta3EDYXflAE2vjx9RTGg5oKMCmqck=
X-Received: by 2002:a2e:5347:: with SMTP id t7mr15986177ljd.464.1623103827091;  Mon, 07 Jun 2021 15:10:27 -0700 (PDT)
MIME-Version: 1.0
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Mon, 7 Jun 2021 18:10:16 -0400
Message-ID: <CADyWQ+FkHUr1DPHpepFU=1_HQi3hOKvSe3bvb4QC+cOqy-OGEg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000c250705c4344f5d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WY5iMAdZTXZL25KRn0w7yGwPv4g>
Subject: [dmarc-ietf] ABNF update to dmarc-psd
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 07 Jun 2021 22:10:35 -0000

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

All

When I raised the point for dmarc-bis making sure that new tags define
their ABNF, I realized that the PSD document does no such thing.
It does describe the definition, as it's the same as the "sp" tag.


I added the following section to dmarc-psd updating 7489 as such:

3.3.  Changes in Section 6.4 "Formal Definition"

   The ABNF for DMARC shall updated to include a new definition "dmarc-
   nprequest" which is defined as:

               dmarc-nprequest =  "np" *WSP "=" *WSP
                   ( "none" / "quarantine" / "reject" )


   The "dmarc-record" definition is also updated to include the
   following:

                 [dmarc-sep dmarc-nprequest]



I am well aware that the dmarc-bis draft has much cleaner ABNF, but this
document still updates 7489, so
we must follow what is there.


I've pushed a new version -15 into my own repo:
https://github.com/moonshiner/draft-ietf-dmarc-psd

I'd like the WG to double check what is here, making sure this will be
enough.  I'll push out -15 by the
end of the week.

thanks
tim

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e">All</div><div class=3D"gmail_default" style=3D"font-family:monospace"><b=
r></div><div class=3D"gmail_default" style=3D"font-family:monospace">When I=
 raised the point for dmarc-bis making sure that new tags define their ABNF=
, I realized that the PSD document does no such thing.</div><div class=3D"g=
mail_default" style=3D"font-family:monospace">It does describe the definiti=
on, as it&#39;s the same as the &quot;sp&quot; tag.=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"><br></div><div class=3D"gmai=
l_default" style=3D"font-family:monospace">I added the following section to=
 dmarc-psd updating 7489 as such:</div><div class=3D"gmail_default" style=
=3D"font-family:monospace"><br></div><blockquote style=3D"margin:0 0 0 40px=
;border:none;padding:0px"><div class=3D"gmail_default" style=3D"font-family=
:monospace">3.3.=C2=A0 Changes in Section 6.4 &quot;Formal Definition&quot;=
</div><div class=3D"gmail_default" style=3D"font-family:monospace"><br></di=
v><div class=3D"gmail_default" style=3D"font-family:monospace">=C2=A0 =C2=
=A0The ABNF for DMARC shall updated to include a new definition &quot;dmarc=
-</div><div class=3D"gmail_default" style=3D"font-family:monospace">=C2=A0 =
=C2=A0nprequest&quot; which is defined as:</div><div class=3D"gmail_default=
" style=3D"font-family:monospace"><br></div><div class=3D"gmail_default" st=
yle=3D"font-family:monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0dmarc-nprequest =3D =C2=A0&quot;np&quot; *WSP &quot;=3D&quot; *WS=
P</div><div class=3D"gmail_default" style=3D"font-family:monospace">=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( &quot;none&=
quot; / &quot;quarantine&quot; / &quot;reject&quot; )</div><div class=3D"gm=
ail_default" style=3D"font-family:monospace"><br></div><div class=3D"gmail_=
default" style=3D"font-family:monospace"><br></div><div class=3D"gmail_defa=
ult" style=3D"font-family:monospace">=C2=A0 =C2=A0The &quot;dmarc-record&qu=
ot; definition is also updated to include the</div><div class=3D"gmail_defa=
ult" style=3D"font-family:monospace">=C2=A0 =C2=A0following:</div><div clas=
s=3D"gmail_default" style=3D"font-family:monospace"><br></div><div class=3D=
"gmail_default" style=3D"font-family:monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[dmarc-sep dmarc-nprequest]</div></block=
quote><div class=3D"gmail_default" style=3D"font-family:monospace"><br></di=
v><div class=3D"gmail_default" style=3D"font-family:monospace"><br></div><d=
iv class=3D"gmail_default" style=3D"font-family:monospace">I am well aware =
that the dmarc-bis draft has much cleaner ABNF, but this document still upd=
ates 7489, so</div><div class=3D"gmail_default" style=3D"font-family:monosp=
ace">we must follow what is there.=C2=A0</div><div class=3D"gmail_default" =
style=3D"font-family:monospace"><br></div><div class=3D"gmail_default" styl=
e=3D"font-family:monospace"><br>I&#39;ve pushed a new version=C2=A0-15 into=
 my own repo:=C2=A0 <a href=3D"https://github.com/moonshiner/draft-ietf-dma=
rc-psd">https://github.com/moonshiner/draft-ietf-dmarc-psd</a></div><div cl=
ass=3D"gmail_default" style=3D"font-family:monospace"><br></div><div class=
=3D"gmail_default" style=3D"font-family:monospace">I&#39;d like the WG to d=
ouble check what is here, making sure this will be enough.=C2=A0 I&#39;ll p=
ush out -15 by the=C2=A0</div><div class=3D"gmail_default" style=3D"font-fa=
mily:monospace">end of the week.</div><div class=3D"gmail_default" style=3D=
"font-family:monospace"><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:monospace">thanks</div><div class=3D"gmail_default" style=3D"font-=
family:monospace">tim</div><div class=3D"gmail_default" style=3D"font-famil=
y:monospace"><br></div><div class=3D"gmail_default" style=3D"font-family:mo=
nospace"><br></div><div class=3D"gmail_default" style=3D"font-family:monosp=
ace"><br></div></div>

--0000000000000c250705c4344f5d--


From nobody Mon Jun  7 15:26: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 A858F3A1471 for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 15:26:26 -0700 (PDT)
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 3i-W9kHeiMer for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 15:26:21 -0700 (PDT)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FFBC3A146E for <dmarc@ietf.org>; Mon,  7 Jun 2021 15:26:21 -0700 (PDT)
Received: by mail-pf1-x42c.google.com with SMTP id k15so14182836pfp.6 for <dmarc@ietf.org>; Mon, 07 Jun 2021 15:26:21 -0700 (PDT)
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=LdYjbeHTt8fc+Pj3Lnexi4oD/qBxt7sJR0ggYrVBWH0=; b=gMDOcOZlKrrR/YxRDvfNxnw9tO7XA+7//f9f3JZiMlxVlZI1iKsaITv714kgQCEI9p cN1urgqK5Z9KKzzefrULaDhBciWMRH4XNsZcQzK27PQFYch5PodlhmWHkRWCloL0Lju/ S8dQVhpiubPnO6W5beUrdAFXduJjYTTjZONW5Fu1zCZgSojTK4qZz+dLLK1BR6vSz7Xl sFZJAdg/3Sj3DLS3c9rl+sUbxbXuTVXW5wZ+sdx8cSurok5Penc808J+h6HU8xJnY1gS cSZ5A9uhyNp7u2mQuw7APNzDSA/mNy/ShfTtsIWgTHj0tRA9WwOYzday57e3evlEUTzz h1sQ==
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=LdYjbeHTt8fc+Pj3Lnexi4oD/qBxt7sJR0ggYrVBWH0=; b=eyxguNkawvOYSFN8UwMVxmpq+l2//rEJruvOHKNKpze8FAMw3GT1vIMLmc95Zxr7II vevRR1KZuWaIfJsPaMz9nf3oeGK1Xl+WIIY+MeY+rbfSO7lOwJ5KpE/G5SywTRxUI0tC PwecEAjkApIkP2CL6nIDDRjYYJouLV7EzZKbObnn4e9WzCTiYPOTgDN9MKJR2ZvhUahu 4kzPEAeWLq2keB9UCF46f+f5dhusgdYkoaU5yPvNQf+96acxqdfGz99B55RHgnd6BPO4 jbshBjGQwPUT1kDlX9oJd31yWhkNugD5hTn0EZ2frYwppvr+oPqgeR3O4caU/lyir/hd RRig==
X-Gm-Message-State: AOAM533k+3QBiYx0Nx2q5/qtDozedU/zAVOd1f4C8Hgm+80RY8sC4P9w dPI+Q+SWiYAnBOZJ4S/W1EBrKvsDnHEPMg==
X-Google-Smtp-Source: ABdhPJyOjdGz/lUxaqDLgO3+e0CD8wknJm6lwUf/PnpPk4O0oxaRsCVph88G7Z+NTgTW/smke5eAOw==
X-Received: by 2002:aa7:93b8:0:b029:2e9:df8c:d5e0 with SMTP id x24-20020aa793b80000b02902e9df8cd5e0mr19334213pff.19.1623104779865;  Mon, 07 Jun 2021 15:26:19 -0700 (PDT)
Received: from [192.168.0.106] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id c190sm8803941pfc.26.2021.06.07.15.26.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 07 Jun 2021 15:26:19 -0700 (PDT)
To: Tim Wicinski <tjw.ietf@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <CADyWQ+FkHUr1DPHpepFU=1_HQi3hOKvSe3bvb4QC+cOqy-OGEg@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <b81542f9-b04c-f815-dfab-61e649f578e8@gmail.com>
Date: Mon, 7 Jun 2021 15:26:17 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CADyWQ+FkHUr1DPHpepFU=1_HQi3hOKvSe3bvb4QC+cOqy-OGEg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------6AD66B1FF2CB5B19F5DF21F4"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rkOfLGzz2RgzStUHG13s9rc37OM>
Subject: Re: [dmarc-ietf] ABNF update to dmarc-psd
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 07 Jun 2021 22:26:27 -0000

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

On 6/7/2021 3:10 PM, Tim Wicinski wrote:
>      dmarc-nprequest =  "np" *WSP "=" *WSP
>          ( "none" / "quarantine" / "reject" )

I suggest adding a comment that makes the linkage of 'nprequest' to the 
prose text explicit.

d/

-- 
Dave Crocker
dcrocker@gmail.com
408.329.0791

Volunteer, Silicon Valley Chapter
Information & Planning Coordinator
American Red Cross
dave.crocker2@redcross.org


--------------6AD66B1FF2CB5B19F5DF21F4
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 6/7/2021 3:10 PM, Tim Wicinski
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CADyWQ+FkHUr1DPHpepFU=1_HQi3hOKvSe3bvb4QC+cOqy-OGEg@mail.gmail.com">
      <div class="gmail_default" style="font-family:monospace">         
             dmarc-nprequest =  "np" *WSP "=" *WSP</div>
      <div class="gmail_default" style="font-family:monospace">         
                 ( "none" / "quarantine" / "reject" )</div>
    </blockquote>
    <p>I suggest adding a comment that makes the linkage of 'nprequest'
      to the prose text explicit.</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
Information &amp; Planning Coordinator
American Red Cross
<a class="moz-txt-link-abbreviated" href="mailto:dave.crocker2@redcross.org">dave.crocker2@redcross.org</a></pre>
  </body>
</html>

--------------6AD66B1FF2CB5B19F5DF21F4--


From nobody Mon Jun  7 16:21:08 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 66D133A1677 for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 16:21:06 -0700 (PDT)
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, NICE_REPLY_A=-0.001, 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=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 eHAJTDQSseTc for <dmarc@ietfa.amsl.com>; Mon,  7 Jun 2021 16:21:00 -0700 (PDT)
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 D22AD3A1676 for <dmarc@ietf.org>; Mon,  7 Jun 2021 16:21:00 -0700 (PDT)
Received: from shiny.crash.com (192-184-141-33.fiber.dynamic.sonic.net [192.184.141.33]) (authenticated bits=0) by segv.crash.com (8.15.2/8.15.2/cci-colo-1.16) with ESMTPSA id 157NKlfT080205 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 7 Jun 2021 23:20:55 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 157NKlfT080205
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1623108057; bh=6y3XjHEzj61hxsexAisvOkx6WZKQ0BMQF3hCwBpTecg=; h=Subject:To:References:From:Date:In-Reply-To; b=W+puBuaNZjOFOMcUQn6hwQ3+9MH/k+uMHOgcOq95cji5p52lxuyqMuPQn8lBamSEv hpYeBtIBV2kQz8bsi34/Rs/cd/YB+1UitUcdr8Qt3DTm44Tj/tSsUx/6NanT40QPbv h0TxmeWVREARjACLDyxBU8gopTFPCQO1eXX6473bcstY6ajHckGTg7OpL8by06OOpi Y+divscic5LYCW261ONBQQ4tLnwOlSGyUSPP/ESrrLi9hOkuwSrP43j2GoaQdR9diR IE2B1XsLpATzAjxLoEl14T7jIMWGctFLToOChGMMq2gWZr8m5yDApSN7SlafYd146k 5btRTJ75vH0UQ==
X-Authentication-Warning: segv.crash.com: Host 192-184-141-33.fiber.dynamic.sonic.net [192.184.141.33] claimed to be shiny.crash.com
To: dmarc@ietf.org
References: <CAHej_8npHwekgJDLOV=hVPdd0OFoMumJCKL5Yitz5oWrhkQdNg@mail.gmail.com> <a8ef636c-815a-6b40-a955-b7049afba82f@crash.com> <a7fc5ba7-e17b-72b5-e81a-1dd0ac6cb418@tana.it> <CALaySJ+FGMBA2AuNzwUOyA5eccUkQ399Kc3c-oj99oZRov8oPQ@mail.gmail.com> <88957ada-7514-f664-6269-88503c1a81fd@tana.it> <fc795d67-1003-32cd-d99a-fa9256a802a1@crash.com>
From: Steven M Jones <smj@crash.com>
Message-ID: <c2ae5c84-53fa-8d5e-b912-8433d5798698@crash.com>
Date: Mon, 7 Jun 2021 16:20:55 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:78.0) Gecko/20100101 Thunderbird/78.10.2
MIME-Version: 1.0
In-Reply-To: <fc795d67-1003-32cd-d99a-fa9256a802a1@crash.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Mon, 07 Jun 2021 23:20:55 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qB2UsXDI8UTjP4Vfsn0j0ix3xhU>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #53 (Remove reporting message size chunking) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 07 Jun 2021 23:21:07 -0000

On 5/31/21 15:49, Steven M Jones wrote:
> I think we can get the input needed to resolve this by Todd's requested
> deadline, and be able to show we did the due diligence to back up the
> decision.


I got three responses - unfortunately I discovered I don't have as many
of these contacts as I used to. So it's still anecdotal, but it includes
two of the (I don't know) dozen top mailbox providers in the world - for
whatever positive or negative weighting that may carry with you.

I'm about to add the following comment to the TRAC ticket:



I offered to try and get information on the frequency of use of this
feature from mailbox providers/report generators. I received three
responses, which I will rephrase to protect the sources. They can speak
up if they wish to go on the record.

1. Global mailbox provider A: Our code doesn't handle the syntax, and
will try to send to the address including the size specification. So if
you use that in your domain's RUA tag, our reports to you are probably
bouncing. There's a bug filed to fix it, but no commitment to do so.

2. Global mailbox provider B: We had the same bug, but fixed it - so
reports will be sent to the correct address. But regarding the limit, we
checked to see if anybody who specified a limit was receiving reports
large enough to trigger it, and nobody was. Large operators who might
actually trigger it, didn't specify a size. So we never implemented it.

3. National mailbox provider: I wrote code to implement it, but to my
knowledge it has never been triggered. Maybe our operation isn't big
enough. But implementing it was painful - guessing what the compressed
size would be, how to trim or truncate the report to fit the limit, who
to notify in the event of truncation and how... I would prefer removal,
but failing that please simplify it. [I can share the suggestions if we
go that way. --S.]



--Steve.



From nobody Tue Jun  8 01:32:31 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1D1B3A27E8 for <dmarc@ietfa.amsl.com>; Tue,  8 Jun 2021 01:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Ssj6xZUXYbo for <dmarc@ietfa.amsl.com>; Tue,  8 Jun 2021 01:32:24 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73FAC3A27E7 for <dmarc@ietf.org>; Tue,  8 Jun 2021 01:32:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1623141139; bh=bYDIM9CsKYuuSvuwU9NRlzNWfev0VjR+I0FNMXJ8JiQ=; l=2303; h=To:References:From:Date:In-Reply-To; b=DRpFveOtWlgp1jP/gNyWjSSp8zy8PNwG+oXP+FMz4IduBW/sAHLT5grUjaAuTNCwl ZVqP63ZYNCRn4L9wfftjldqUpVX0zzjPNFAwpEYJYAh7kneUcrtZK59MgoZdN+VAqj wQn4rSYEKm8WVo3yCR20QxsuJAU9tn6jVDy8NYbWiLssMs5qVBgyG0jsFy4cf
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 00000000005DC02A.0000000060BF2B13.0000054A; Tue, 08 Jun 2021 10:32:19 +0200
To: Steven M Jones <smj@crash.com>, dmarc@ietf.org
References: <CAHej_8npHwekgJDLOV=hVPdd0OFoMumJCKL5Yitz5oWrhkQdNg@mail.gmail.com> <a8ef636c-815a-6b40-a955-b7049afba82f@crash.com> <a7fc5ba7-e17b-72b5-e81a-1dd0ac6cb418@tana.it> <CALaySJ+FGMBA2AuNzwUOyA5eccUkQ399Kc3c-oj99oZRov8oPQ@mail.gmail.com> <88957ada-7514-f664-6269-88503c1a81fd@tana.it> <fc795d67-1003-32cd-d99a-fa9256a802a1@crash.com> <c2ae5c84-53fa-8d5e-b912-8433d5798698@crash.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <8f57f42c-735e-0bb3-98a7-06514687342f@tana.it>
Date: Tue, 8 Jun 2021 10:32:19 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <c2ae5c84-53fa-8d5e-b912-8433d5798698@crash.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/0LNJw3gfuqc2DwLLZhNQW92rz8Y>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #53 (Remove reporting message size chunking) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 08 Jun 2021 08:32:30 -0000

Thank you Steve, this confirms size limits are a useless encumbrance on reporting.

Best
Ale


On Tue 08/Jun/2021 01:20:55 +0200 Steven M Jones wrote:
> On 5/31/21 15:49, Steven M Jones wrote:
>> I think we can get the input needed to resolve this by Todd's requested
>> deadline, and be able to show we did the due diligence to back up the
>> decision.
> 
> 
> I got three responses - unfortunately I discovered I don't have as many
> of these contacts as I used to. So it's still anecdotal, but it includes
> two of the (I don't know) dozen top mailbox providers in the world - for
> whatever positive or negative weighting that may carry with you.
> 
> I'm about to add the following comment to the TRAC ticket:
> 
> 
> 
> I offered to try and get information on the frequency of use of this
> feature from mailbox providers/report generators. I received three
> responses, which I will rephrase to protect the sources. They can speak
> up if they wish to go on the record.
> 
> 1. Global mailbox provider A: Our code doesn't handle the syntax, and
> will try to send to the address including the size specification. So if
> you use that in your domain's RUA tag, our reports to you are probably
> bouncing. There's a bug filed to fix it, but no commitment to do so.
> 
> 2. Global mailbox provider B: We had the same bug, but fixed it - so
> reports will be sent to the correct address. But regarding the limit, we
> checked to see if anybody who specified a limit was receiving reports
> large enough to trigger it, and nobody was. Large operators who might
> actually trigger it, didn't specify a size. So we never implemented it.
> 
> 3. National mailbox provider: I wrote code to implement it, but to my
> knowledge it has never been triggered. Maybe our operation isn't big
> enough. But implementing it was painful - guessing what the compressed
> size would be, how to trim or truncate the report to fit the limit, who
> to notify in the event of truncation and how... I would prefer removal,
> but failing that please simplify it. [I can share the suggestions if we
> go that way. --S.]
> 
> 
> 
> --Steve.
> 
> 
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
> 


From nobody Tue Jun  8 06:54:13 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 ED6E13A317D for <dmarc@ietfa.amsl.com>; Tue,  8 Jun 2021 06:54:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level: 
X-Spam-Status: No, score=-1.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c_eFN5sQOm2X for <dmarc@ietfa.amsl.com>; Tue,  8 Jun 2021 06:54:07 -0700 (PDT)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450: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 4AB733A317B for <dmarc@ietf.org>; Tue,  8 Jun 2021 06:54:07 -0700 (PDT)
Received: by mail-lj1-x230.google.com with SMTP id e11so27071753ljn.13 for <dmarc@ietf.org>; Tue, 08 Jun 2021 06:54:06 -0700 (PDT)
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=lYwKpnENJhd8Ty6n1MMqClKE73jVJM68wfPrhzFSS9k=; b=Tds4orBMoQnRQH96Tv9ybvKWo1eFUhEqPqFQSpogVWDoX2t87ibfhVHgbN2ixTxXop ObcGTeha8iFx1blPY2RSZhErX1EQDaN4skd9AXyD2tDdSGd9sXPFxKwe930+wQmSOFKR WTFbICBkJiWxayuF+2cPURmGuJzr1cVc9q9sFx3wq2InpfRGv66Fkh+Psu9nhOqDGlOe i5PpEEjZIr2e6Ss+3SqrvzAciLznEOLV9GbBEXck0MC/0kLMj6j5mKrcJjXMrnq5/vPK fUa8Pio8IRCHj8uXDkRfqXPsEgzFNFWUwr1ONTHj3y6hpgJT2vsmHeXoL2JWl/CRLGZO znGg==
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=lYwKpnENJhd8Ty6n1MMqClKE73jVJM68wfPrhzFSS9k=; b=mDfFCoubf08Wmf+eh+PDABri5JnAoP7YdNEnEWxvaFvNhNN3vRgq7n4b9b1mJFi5Lz iFkIH67Fgm8JiNjmWxuZBo8NexYD5VH+k/otytJusLHZo4ruvY7ebJK96Fd41L0EQgPq 7EkbLGchFm3YmglDx5yc1P82wXh54i4V7bB4Pk/h38la/R95d0r7zjA5pIc6zZ0815Hr FKhXeBX4S7Cq0munRFtaXXbMLuN8qjiPccR3ICd+E8voaYbKExsLAjoMS9jehjcYMgLt AHTJoToZvO+Qgfl3yKK1G0SmFR4dXljh+YJetcHfpekxQoCCJokcHbTQy0WUJJka3aDS pySQ==
X-Gm-Message-State: AOAM532yCjlHuHLeHo+PuY2sFsVzQAjaJMO7Kyd06zbDhVGEJeHppwbQ rjfsDKniDsRwx2mZjBo3NtgnoGeQX+1sSouOJp0=
X-Google-Smtp-Source: ABdhPJzI4olovda14jVoV3JvF4fh6hNrgVHgqrPM1yzuOHt4pKgEXqHB0YFXzPdeGQ4ZhRrxefnHGOwY7tgCk5uWJwA=
X-Received: by 2002:a2e:2f14:: with SMTP id v20mr18857195ljv.363.1623160440045;  Tue, 08 Jun 2021 06:54:00 -0700 (PDT)
MIME-Version: 1.0
References: <CADyWQ+FkHUr1DPHpepFU=1_HQi3hOKvSe3bvb4QC+cOqy-OGEg@mail.gmail.com> <b81542f9-b04c-f815-dfab-61e649f578e8@gmail.com>
In-Reply-To: <b81542f9-b04c-f815-dfab-61e649f578e8@gmail.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Tue, 8 Jun 2021 09:53:49 -0400
Message-ID: <CADyWQ+FOZHKwES4JpfLOt13M7Chimc6B1LfoLuoH-CTEBG+VgQ@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000071422d05c4417d9c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/B5hDztAJY1jbqT60CvbxJBeVJfA>
Subject: Re: [dmarc-ietf] ABNF update to dmarc-psd
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 08 Jun 2021 13:54:12 -0000

--00000000000071422d05c4417d9c
Content-Type: text/plain; charset="UTF-8"

Dave,

I agree but was scrabbling with the wording. How about


   The "dmarc-record" definition is also updated to include the
   following:

                 [dmarc-sep dmarc-nprequest]

which will go in the next to last line of the definition, as so:

[dmarc-sep dmarc-percent]

[dmarc-sep dmarc-nprequest]

[dmarc-sep]


My first instinct is some sort of diff type output, but that isn't right.

tim


On Mon, Jun 7, 2021 at 6:26 PM Dave Crocker <dcrocker@gmail.com> wrote:

> On 6/7/2021 3:10 PM, Tim Wicinski wrote:
>
>                dmarc-nprequest =  "np" *WSP "=" *WSP
>                    ( "none" / "quarantine" / "reject" )
>
> I suggest adding a comment that makes the linkage of 'nprequest' to the
> prose text explicit.
>
> d/
>
> --
> Dave Crockerdcrocker@gmail.com
> 408.329.0791
>
> Volunteer, Silicon Valley Chapter
> Information & Planning Coordinator
> American Red Crossdave.crocker2@redcross.org
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e">Dave,</div><div class=3D"gmail_default" style=3D"font-family:monospace">=
<br></div><div class=3D"gmail_default" style=3D"font-family:monospace">I ag=
ree but was scrabbling with the wording. How about</div><div class=3D"gmail=
_default" style=3D"font-family:monospace"><br></div><div class=3D"gmail_def=
ault" style=3D"font-family:monospace"><br></div><div class=3D"gmail_default=
" style=3D"font-family:monospace"><div class=3D"gmail_default">=C2=A0 =C2=
=A0The &quot;dmarc-record&quot; definition is also updated to include the</=
div><div class=3D"gmail_default">=C2=A0 =C2=A0following:</div><div class=3D=
"gmail_default"><br></div><div class=3D"gmail_default">=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[dmarc-sep dmarc-nprequest]</div>=
<div class=3D"gmail_default"><br></div></div><blockquote style=3D"margin:0 =
0 0 40px;border:none;padding:0px"><div class=3D"gmail_default" style=3D"fon=
t-family:monospace"><div class=3D"gmail_default">which will go in the next =
to last line of the definition, as so:</div><div class=3D"gmail_default"><b=
r></div></div></blockquote><blockquote style=3D"margin:0 0 0 40px;border:no=
ne;padding:0px"><div class=3D"gmail_default" style=3D"font-family:monospace=
"><blockquote style=3D"margin:0 0 0 40px;border:none;padding:0px"><div clas=
s=3D"gmail_default" style=3D"font-family:monospace">[dmarc-sep dmarc-percen=
t]</div></blockquote></div><div class=3D"gmail_default" style=3D"font-famil=
y:monospace"><blockquote style=3D"margin:0 0 0 40px;border:none;padding:0px=
"><div class=3D"gmail_default" style=3D"font-family:monospace"><div class=
=3D"gmail_default">[dmarc-sep dmarc-nprequest]</div></div></blockquote></di=
v><div class=3D"gmail_default" style=3D""><blockquote style=3D"font-family:=
monospace;margin:0px 0px 0px 40px;border:none;padding:0px"><div class=3D"gm=
ail_default" style=3D"font-family:monospace"><div class=3D"gmail_default">[=
dmarc-sep]<br><br></div></div></blockquote></div></blockquote><div class=3D=
"gmail_default" style=3D""><font face=3D"monospace"><br></font></div><div c=
lass=3D"gmail_default" style=3D""><font face=3D"monospace">My first instinc=
t is some sort of diff type output, but that isn&#39;t right.</font></div><=
div class=3D"gmail_default" style=3D""><font face=3D"monospace"><br></font>=
</div><div class=3D"gmail_default" style=3D""><font face=3D"monospace">tim<=
/font></div><div class=3D"gmail_default" style=3D""><font face=3D"monospace=
"><br></font></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Mon, Jun 7, 2021 at 6:26 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.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <div>On 6/7/2021 3:10 PM, Tim Wicinski
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div class=3D"gmail_default" style=3D"font-family:monospace">=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0
        =C2=A0 =C2=A0 =C2=A0dmarc-nprequest =3D =C2=A0&quot;np&quot; *WSP &=
quot;=3D&quot; *WSP</div>
      <div class=3D"gmail_default" style=3D"font-family:monospace">=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0
        =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0( &quot;none&quot; / &quot;quaran=
tine&quot; / &quot;reject&quot; )</div>
    </blockquote>
    <p>I suggest adding a comment that makes the linkage of &#39;nprequest&=
#39;
      to the prose text explicit.</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
Information &amp; Planning Coordinator
American Red Cross
<a href=3D"mailto:dave.crocker2@redcross.org" target=3D"_blank">dave.crocke=
r2@redcross.org</a></pre>
  </div>

</blockquote></div>

--00000000000071422d05c4417d9c--


From nobody Tue Jun  8 08:10:30 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 253AF3A339D for <dmarc@ietfa.amsl.com>; Tue,  8 Jun 2021 08:10:28 -0700 (PDT)
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 (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 pcLnoJ22M1XC for <dmarc@ietfa.amsl.com>; Tue,  8 Jun 2021 08:10:21 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C1993A3397 for <dmarc@ietf.org>; Tue,  8 Jun 2021 08:10:20 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id l17so11371135qtq.12 for <dmarc@ietf.org>; Tue, 08 Jun 2021 08:10:20 -0700 (PDT)
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=I2I89pnyAJM5HHJWwz+h/HGO2RIc4lfpoyc/m2Tm6mA=; b=TpsD0uqIMwm0t9p7YcCf5OSJQOscf+YiJVwZa3JIXxDlBMwJsBW/aMHky1FTFQlfuD FC1Yc4avpmS/EzqHq4TLO6Qf5kxgzwq/vS/OfOfY/jbjt/r6POWFQykQLbUyzMJq7v60 52X8pDZ0ZjOAFn/TdT6mHNQo3sAq0KWlg+ny1DOQ5RDAgd4cHMzwCSiQMlbeoHXzb0Mm SMY0piRgdKUSIhWFgzmRKrQBOuqt2TLA6qXaIlhUfbsHbsraLIp9x8CDqe/j297nL9pa INnOmqXqKuQgRsD0bRnSSAhls5w3M+VXOj5pUSENmASyzeoC87qWYPxhb230Zt8aGGmS Zy+Q==
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=I2I89pnyAJM5HHJWwz+h/HGO2RIc4lfpoyc/m2Tm6mA=; b=egs+D/WX1+zFgVDFUe6u0Slqa1Lq+cvO8fj+UI0ymTb87pY9Tl7A0WyF7LS73EFkJY H9w61jRbWaszIJYa5L1rZEY3DHrTbQyPc+DAy1qVXWFnhZm3ufX9OcvS9CfcLWK1ycCI KzGdIRsAgRlmMVJHQE+3bgwpmbBHQq4jzvhAbac+fefxiFOsnOL6dBPR4eFPqMO83WUh P67fE2v+ds1wokVpNajy9E2FPhY2WjuHyfoo2DNfoPSygBqAYBEgqQLeNvo13VjFcarp 30W3s/bbqLJaGqgyURq/D/p1ifi3p2kD5oPqaYMW/leyo0w37upWUxaslzvMvuYIezBl ZEJg==
X-Gm-Message-State: AOAM5316zWSALArRxnS7txbadBRHLkgFXPljHUr+ROfvLpl1YyABMdeL aKdSBlHyt/SUOvAUTqdHGMCCyDER3DAygURGXhcok1o6EgkXag==
X-Google-Smtp-Source: ABdhPJyxmD0sLi2NV1bcnCfujGktlKewPSq/7M7jbJzJ9B9tdzTae2nfqwKLx/PKRoxT3AZYq4cF/XUr+OMApnezgsk=
X-Received: by 2002:a05:622a:104b:: with SMTP id f11mr5314136qte.220.1623165019279;  Tue, 08 Jun 2021 08:10:19 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8mU58N60MLmc4qRrUPjfUojxxv8MFzkwSZRSk5uCE8o6A@mail.gmail.com> <06fd0594-e86f-ddd4-10bc-165852932479@gmail.com>
In-Reply-To: <06fd0594-e86f-ddd4-10bc-165852932479@gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 8 Jun 2021 11:10:03 -0400
Message-ID: <CAHej_8nBnTuJP1GdA8eN4xQjoHAtCd=NMwgpY=i99PGwgf1dYw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000062e6bd05c4428e7a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QtpG782t3G5oGEwuoyzYLSA8AG4>
Subject: Re: [dmarc-ietf] Ticket #113 - DMARCbis -01 Introduction Section
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 08 Jun 2021 15:10:28 -0000

--00000000000062e6bd05c4428e7a
Content-Type: text/plain; charset="UTF-8"

On Thu, Jun 3, 2021 at 8:27 PM Dave Crocker <dcrocker@gmail.com> wrote:

> On 5/5/2021 11:48 AM, Todd Herr wrote:
>
>
> We would like to achieve rough consensus on this section of text by
> Friday, May 21.
>
> Apologies.  I've only just been able to review this text.  Attached are
> suggested changes, done as a Word document with revision tracking turned on.
>
> It might appear that the edits effect major substance changes to the
> Introduction, but I believe they do not; the intent was to retain the same
> goals for the Introduction.
>
> Changes were driven by:
>
>    - Providing better lead-in for readers with less background on the
>    document's topic
>    - Eliminating detail that is not need in an introduction
>    - Minimizing PSO text, since I belive the covered domains have Domain
>    Owners whether they are PSOs or not; hence the fact of being a PSO has
>    minimal import in the Introduction
>    - General wordsmithing, to tighten things up
>
>
> Taking most of Dave's input into account results in an Introduction
section that will read as follows:

------------------------------------begin current proposed text
-----------------------------------
1. Introduction

   Abusive email often includes unauthorized and deceptive use of a

   domain name in the RFC5322.From header field.  The domain typically

   belongs to an organization expected to be known to - and presumably

   trusted by - the recipient.  The Sender Policy Framework ([RFC7208])

   and DomainKeys Identified Mail ([RFC6376]) protocols provide domain-

   level authentication but are not directly associated with the

   RFC5322.From domain.  DMARC leverages them, so that Domain Owners

   publish a DNS record indicating their RFC5322.From field:


   *  Email authentication policies


   *  Level of concern for mail that fails authentication checks


   *  Desire for reports about email use of the domain name



   DMARC can cover non-existent sub-domains, below the "Organizational

   Domain", as well as domains at the top of the name hierarchy,

   controlled by Public Suffix Operators (PSOs).


   As with SPF and DKIM, DMARC classes results as "pass" or "fail".  A

   pass from either SPF or DKIM is required.  Also the passed domain

   must be "aligned" with the RFC5322.From domain.  Domains are said to

   be "in alignment" if they have the same Organizational Domain, which

   is at the top of the domain hierarchy, while having the same

   administrative authority as the RFC5322.From domain.


   A DMARC pass indicates only that the RFC5322.From domain has been

   authenticated for that message.  Of course, authentication does not

   carry an explicit or implicit value assertion about that message or

   about the Domain Owner.  Indeed, a mail-receiving organization that

   performing DMARC validation can choose to follow the Domain Owner's

   requested disposition for authentication failures, and to inform the

   Domain Owner of the mail handling decision for that message.  It also

   might choose different actions.


   For a mail-receiving organization supporting DMARC, a message that

   passes validation is part of a message stream that is reliably

   associated with the RFC5322.From field Domain Owner.  Therefore,

   reputation assessment of that stream by the mail-receiving

   organization is not encumbered by accounting for unauthorized use of

   that domain in the RFC5322.From field.  A message that fails this

   validation is not necessarily associated with the Domain Owner's

   domain and its reputation.


   DMARC, in the associated [DMARC-Aggregate-Reporting] and

   [DMARC-Failure-Reporting] documents, also specifies a reporting

   framework.  Using it, a mail-receiving domain can generate regular

   reports about messages that claim to be from a domain publishing

   DMARC policies, sending those reports to the addresses specified by

   the Domain Owner.


   Use of DMARC creates some interoperability challenges that require

   due consideration before deployment, particularly with configurations

   that can cause mail to be rejected.  These are discussed in
   Section 9.
-------------------------------------end current proposed text
-----------------------------------

I expect that discussion of this topic will continue for some time.

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*m:* 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.

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

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:tahoma,sans-serif"><span style=3D"font-family:Arial,Helvetica,sans=
-serif">On Thu, Jun 3, 2021 at 8:27 PM Dave Crocker &lt;<a href=3D"mailto:d=
crocker@gmail.com">dcrocker@gmail.com</a>&gt; wrote:</span><br></div></div>=
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
 =20
   =20
 =20
  <div>
    <div>On 5/5/2021 11:48 AM, Todd Herr wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px"=
>
        <div><font face=3D"tahoma,
            sans-serif"><br>
          </font></div>
      </blockquote>
      <font face=3D"tahoma, sans-serif"><span class=3D"gmail_default" style=
=3D"font-family:tahoma,sans-serif">We would like to achieve
          rough consensus on this section of text by Friday, May 21.</span>=
</font></blockquote>
    <p>Apologies.=C2=A0 I&#39;ve only just been able to review this text.=
=C2=A0
      Attached are suggested changes, done as a Word document with
      revision tracking turned on.</p>
    <p>It might appear that the edits effect major substance changes to
      the Introduction, but I believe they do not; the intent was to
      retain the same goals for the Introduction.</p>
    <p>Changes were driven by:</p>
    <ul>
      <li>Providing better lead-in for readers with less background on
        the document&#39;s topic<br>
      </li>
      <li>Eliminating detail that is not need in an introduction</li>
      <li>Minimizing PSO text, since I belive the covered domains have
        Domain Owners whether they are PSOs or not; hence the fact of
        being a PSO has minimal import in the Introduction</li>
      <li>General wordsmithing, to tighten things up</li>
    </ul>
    <p><br></p></div></blockquote><div><span class=3D"gmail_default" style=
=3D"font-family:tahoma,sans-serif">Taking most of Dave&#39;s input into acc=
ount results in an Introduction section that will read as follows:</span></=
div><div><span class=3D"gmail_default" style=3D"font-family:tahoma,sans-ser=
if"><br></span></div><div><span class=3D"gmail_default" style=3D"font-famil=
y:tahoma,sans-serif"><div class=3D"gmail_default">-------------------------=
-----------begin current proposed text -----------------------------------<=
/div><div class=3D"gmail_default">1. Introduction</div><div class=3D"gmail_=
default"><br></div></span></div>





<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0 =C2=A0</span>Abusive email often includes unauthorized =
and deceptive use of a</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>domain name in the RFC5322.From header fie=
ld.<span class=3D"gmail-Apple-converted-space">=C2=A0 </span>The domain typ=
ically</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>belongs to an organization expected to be =
known to - and presumably</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>trusted by - the recipient.<span class=3D"=
gmail-Apple-converted-space">=C2=A0 </span>The Sender Policy Framework ([RF=
C7208])</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>and DomainKeys Identified Mail ([RFC6376])=
 protocols provide domain-</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>level authentication but are not directly =
associated with the</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>RFC5322.From domain.<span class=3D"gmail-A=
pple-converted-space">=C2=A0 </span>DMARC leverages them, so that Domain Ow=
ners</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>publish a DNS record indicating their RFC5=
322.From field:</span></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gma=
il-s1" style=3D"font-variant-ligatures:no-common-ligatures"></span><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>*<span class=3D"gmail-Apple-converted-spac=
e">=C2=A0 </span>Email authentication policies</span></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gma=
il-s1" style=3D"font-variant-ligatures:no-common-ligatures"></span><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>*<span class=3D"gmail-Apple-converted-spac=
e">=C2=A0 </span>Level of concern for mail that fails authentication checks=
</span></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gma=
il-s1" style=3D"font-variant-ligatures:no-common-ligatures"></span><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>*<span class=3D"gmail-Apple-converted-spac=
e">=C2=A0 </span>Desire for reports about email use of the domain name</spa=
n></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gma=
il-s1" style=3D"font-variant-ligatures:no-common-ligatures"></span><br></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gma=
il-s1" style=3D"font-variant-ligatures:no-common-ligatures"></span><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>DMARC can cover non-existent sub-domains, =
below the &quot;Organizational</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>Domain&quot;, as well as domains at the to=
p of the name hierarchy,</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>controlled by Public Suffix Operators (PSO=
s).</span></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gma=
il-s1" style=3D"font-variant-ligatures:no-common-ligatures"></span><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>As with SPF and DKIM, DMARC classes result=
<span class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">s</sp=
an> as &quot;pass&quot; or &quot;fail&quot;.<span class=3D"gmail-Apple-conv=
erted-space">=C2=A0 </span>A</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>pass from either SPF or DKIM is required.<=
span class=3D"gmail-Apple-converted-space">=C2=A0 </span>Also the passed do=
main</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>must be &quot;aligned&quot; with the RFC53=
22.From domain.<span class=3D"gmail-Apple-converted-space">=C2=A0 </span>Do=
mains are said to</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>be &quot;in alignment&quot; if they have t=
he same Organizational Domain, which</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>is at the top of the domain hierarchy, whi=
le having the same</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>administrative authority as the RFC5322.Fr=
om domain.</span></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gma=
il-s1" style=3D"font-variant-ligatures:no-common-ligatures"></span><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>A DMARC pass indicates only that the RFC53=
22.From domain has been</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>authenticated for that message.<span class=
=3D"gmail-Apple-converted-space">=C2=A0 </span>Of course, authentication do=
es not</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>carry an explicit or implicit value assert=
ion about that message or</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>about the Domain Owner.<span class=3D"gmai=
l-Apple-converted-space">=C2=A0 </span>Indeed, a mail-receiving organizatio=
n that</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>performing DMARC validation can choose to =
follow the Domain Owner&#39;s</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>requested disposition for authentication f=
ailures, and to inform the</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>Domain Owner of the mail handling decision=
 for that message.<span class=3D"gmail-Apple-converted-space">=C2=A0 </span=
>It also</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>might choose different actions.</span></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gma=
il-s1" style=3D"font-variant-ligatures:no-common-ligatures"></span><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>For a mail-receiving organization supporti=
ng DMARC, a message that</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>passes validation is part of a message str=
eam that is reliably</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>associated with the RFC5322.From field Dom=
ain Owner.<span class=3D"gmail-Apple-converted-space">=C2=A0 </span>Therefo=
re,</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>reputation assessment of that stream by th=
e mail-receiving</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>organization is not encumbered by accounti=
ng for unauthorized use of</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>that domain in the RFC5322.From field.<spa=
n class=3D"gmail-Apple-converted-space">=C2=A0 </span>A message that fails =
this</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>validation is not necessarily associated w=
ith the Domain Owner&#39;s</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>domain and its reputation.</span></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gma=
il-s1" style=3D"font-variant-ligatures:no-common-ligatures"></span><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>DMARC, in the associated [DMARC-Aggregate-=
Reporting] and</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>[DMARC-Failure-Reporting] documents, also =
specifies a reporting</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>framework.<span class=3D"gmail-Apple-conve=
rted-space">=C2=A0 </span>Using it, a mail-receiving domain can generate re=
gular</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>reports about messages that claim to be fr=
om a domain publishing</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>DMARC policies, sending those reports to t=
he addresses specified by</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>the Domain Owner.</span></p>
<p class=3D"gmail-p2" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0);min-height:13px"><span class=3D"gma=
il-s1" style=3D"font-variant-ligatures:no-common-ligatures"></span><br></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>Use of DMARC creates some interoperability=
 challenges that require</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>due consideration before deployment, parti=
cularly with configurations</span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:no=
rmal;font-family:Menlo;color:rgb(0,0,0)"><span class=3D"gmail-s1" style=3D"=
font-variant-ligatures:no-common-ligatures"><span class=3D"gmail-Apple-conv=
erted-space">=C2=A0=C2=A0 </span>that can cause mail to be rejected.<span c=
lass=3D"gmail-Apple-converted-space">=C2=A0 </span>These are discussed in</=
span></p>
<div><span class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">=
<span class=3D"gmail-Apple-converted-space" style=3D"font-variant-ligatures=
:no-common-ligatures;color:rgb(0,0,0);font-family:Menlo;font-size:11px">=C2=
=A0 =C2=A0</span><span style=3D"font-variant-ligatures:no-common-ligatures;=
color:rgb(0,0,0);font-family:Menlo;font-size:11px">Section 9.</span></span>=
=C2=A0</div><div><div><div class=3D"gmail_default" style=3D"font-family:tah=
oma,sans-serif">-------------------------------------end current proposed t=
ext -----------------------------------</div><div class=3D"gmail_default" s=
tyle=3D"font-family:tahoma,sans-serif"></div></div><div><br></div></div><di=
v><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">I ex=
pect that discussion of this topic will continue for some time.</div><br></=
div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><span><p dir=3D=
"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div=
 style=3D"text-align:left"><span style=3D"vertical-align:baseline;white-spa=
ce:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></span><span=
 style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font=
-family:Arial"> | Sr. Technical Program Manager</span></div><span style=3D"=
vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Ar=
ial"><div style=3D"text-align:left"><span style=3D"vertical-align:baseline"=
><b>e:</b></span><span style=3D"vertical-align:baseline"> <a href=3D"mailto=
:todd.herr@valimail.com" target=3D"_blank">todd.herr@valimail.com</a> </spa=
n></div></span><span><div><span><b>m:</b></span><span> 703.220.4153</span><=
span></span></div><div style=3D"text-align:left"><img style=3D"width: 175px=
; height: 43px;" src=3D"https://hosted-packages.s3-us-west-1.amazonaws.com/=
Valimail+Logo.png"></div></span><p dir=3D"ltr" style=3D"background-color:rg=
b(255,255,255);line-height:1.38;margin-top:0pt;margin-bottom:0pt"><font fac=
e=3D"Arial" color=3D"#666666"><span style=3D"font-size:10.6667px;white-spac=
e:pre-wrap">This email and all data transmitted with it contains confidenti=
al and/or proprietary information intended solely for the use of individual=
(s) authorized to receive it. If you are not an intended and authorized rec=
ipient you are hereby notified of any use, disclosure, copying or distribut=
ion of the information included in this transmission is prohibited and may =
be unlawful. Please immediately notify the sender by replying to this email=
 and then delete it from your system.</span></font></p></span></div></div>

--00000000000062e6bd05c4428e7a--


From nobody Sat Jun 12 05:55:50 2021
Return-Path: <dougfoster.emailstandards@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 826DB3A114C for <dmarc@ietfa.amsl.com>; Sat, 12 Jun 2021 05:55:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id twDSv5FX16yI for <dmarc@ietfa.amsl.com>; Sat, 12 Jun 2021 05:55:46 -0700 (PDT)
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 E4C163A114B for <dmarc@ietf.org>; Sat, 12 Jun 2021 05:55:45 -0700 (PDT)
Received: by mail-oi1-x231.google.com with SMTP id r16so8642438oiw.3 for <dmarc@ietf.org>; Sat, 12 Jun 2021 05:55:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=JLZ923bykjec/yJ0cK3D26KiCm/ZXva+wJ3HXJS5D5Y=; b=mB+tSWlEIPU5dL9QYdfmTBtkMbanKWSLFM2MaF9u+JtdXHnSljetbLx/AYKp5ovmFi Xj+ec0nIqCLBKqX2/DlOSifGvQ2OO0dpvsq+Vb48TMsqzYZIxCbFJcmSQcUEAtHRDH5a UCW1UKGP/uRttykvzKe11gQeNVhRYtTEzgmOTJoaJJ/Qs/ZLlrNOhFcieWOjlrZx8mlX YQhg224+BZSwc5WwLEoXwGN28C25Up5e+ARHsRJ1RJ/Nli7+Q2Q/Atp9NRRcIMzpxeXE W3nElVy70LUrMol4aeOt4KuFqUuX3Vd3aaAvB1/W9B8bi3QjWiMDC90ByvsPjvkxt0ES l6JQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=JLZ923bykjec/yJ0cK3D26KiCm/ZXva+wJ3HXJS5D5Y=; b=lDmbI5XAq3JuR3j649gXzqHdarMakxUcO3TgDwCUeEqHZTN8mlHzZfWCI3D94DSMBD b5HO4GEBkHLXJn7n+exnyy1AOo6KYKpIaPEndnPTn4JNCdpoTb/TSsbpeKkyBoazEqPA xag7SYnpkAPrXXs4aPIenHgfAXg22x+Idq9Efx+qRe6Z6FWos5ImA/keJh/suAOijIzM OKNUChcurc+I6sAFqjmfGeWK5Ru//VIJ7fEoRQp5AGyXChJop/yXA10dHi5Km+Na+Jhx l3dpNNNHCMgyvYq/Ibjg9EXDl3wEEYQ5iGNnSImJNO3farkaJzBgT8c2OtXJ2VxXsepW FH5A==
X-Gm-Message-State: AOAM533V3SgwNmRI7/1hYrOPOOj6vnL/jprQDq71pOzLjOfDdSF4WsOt 01y0bCEgfCbZmDgQplJXCC6zmx//39gg4t6iG8nSCQp+EkI=
X-Google-Smtp-Source: ABdhPJw9EytanIjLSk7mtChvmO5ehZGac+/XaQiDXPx79wiBFa8/N3xbkTPN5GiLACdFd8Kei15hpWmuHljVOo4h7FA=
X-Received: by 2002:aca:bd42:: with SMTP id n63mr16367047oif.73.1623502543750;  Sat, 12 Jun 2021 05:55:43 -0700 (PDT)
MIME-Version: 1.0
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 12 Jun 2021 08:55:33 -0400
Message-ID: <CAH48ZfzuM298fkmhoZtH1ZbK=9Ne9EYtyTYNV27PSsPBW=Gq-w@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000698adc05c4912423"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/tiMnEXfVqCKtUYyukwxsCaRXAP4>
Subject: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 12 Jun 2021 12:55:49 -0000

--000000000000698adc05c4912423
Content-Type: text/plain; charset="UTF-8"

Below is my proposed language for dealing with the problems that NP is
intended to address:
- unused DNS names
- non-existent DNS names

It provides supporting rationale, and provides a more complete solution
than anything suggested previously, and ties the design directly to the
mailing list problem.

I have labelled the sections starting with "X," because I am not sure of
the best way to position this text into the flow of the current draft.

Doug Foster

x. Reducing the scope of the SP policy

DMARC introduces a method for the domain owner to state "at time of
transmission, authorized emails will always authenticate using DMARC
criteria".   However,this authentication can be lost in transit if message
modification occurs in transit, as discussed in RFC 7960.  This possibility
can make domain owners reluctant to move beyond sp=none.  This is a
significant loss, because sp=none opens a vast namespace to domain abuse,
including
- names that are DNS domains but are not protected by a domain-level DMARC
policy
- names that are DNS records records rather than DNS names, and cannot be
protected by a domain-level DMARC policy
- names that are not in DNS at all, and therefore cannot be protected by a
domain-level DMARC policy.

To mitigate these impacts, it is useful to distinguish names used as email
domains from names that are not used for email.   Names that are never used
for email are never authorized at time of transmission, and therefore can
be blocked without concern about in-transit modifications.   Several
methods are presented for addressing this objective.


x.1 Implement mail domains as DNS domains with domain-level DMARC policies.

Mail domains are often implemented as DNS domains, but this is not
required.   MX records and SPF policies can be attached to a named resource
record or a wildcard resource record, while DMARC policies can only be
attached to a DNS domain.

Any name that is configured as a DNS resource record can be reconfigured as
a subdomain name supported by resource records which match the subdomain
name, and names that are not in DNS can be added as DNS domain names.  Once
all used mail domain names are configured as DNS domains, they can be
configured with DMARC policies.   Once this is complete, the SP policy will
only apply to unused and non-existent names.  This will permit use of
SP=reject because any such messages will have been unauthenticated at
origin as well as being unauthenticated at reception.   This approach is
fully compatible with RFC 7489 implementations of DMARC.


x.2 Implement an NP policy

The NP policy assumes that names used for mail can be reliably identified,
so that names not used for mail can be categorized as not authorized.  Two
approaches are used:

- For mail domain names that are used with SMTP, the name is assumed to
also be used as an RFC5322.From domain name.   This is indicated by an MX
record which evaluates to an IP address, or an SPF policy which does not
begin with an ALL term.  (RFC 7505 indicates that an MX record which does
not evaluate to an IP address is useful to indicate that a domain does not
accept incoming mail.  Based on RFC 7208, content after an ALL term is
ignored, so a policy of "-ALL" indicates that the name is never used as an
RFC5321.MailFrom domain and an ALL term with any other modifier is a
meaningless policy.)

- For mail domain names that are not used with SMTP, a new TXT record is
defined, with content "DMARCFROMv1".   The presence of this TXT record
indicates that the associated DNS domain, named DNS resource record, or
wildcard DNS record should be considered as potentially in use as an
RFC5322.From domain name.

Names which are identified by MX record, SPF policy, or DMARCFROMv1 TXT
record are considered in use names and are evaluated using the P or SP
policy.   Names which do not match these criteria are evaluated using the
NP policy.   This allows unused and non-existent names to be given a
stricter DMARC policy than used names.

To implement an NP policy, domain owners may need to make DNS changes:
- For used domain names that are only identified by an A or AAAA record, an
MX record or DMARCFROMv1 TXT record is needed to explicitly indicate that
the name is used for mail.
- For used domain names that are not in DNS at all, a DMARCFROMv1 TXT
record is needed to indicate that the name is used for mail.

The NP policy does not require that all mail domains become DNS domains,
but the NP policy will only be understood by evaluators which use this
specification.  Consequently, it is preferable to ensure that all mail
domains are implemented as DNS domains.

x,3 Implement SPF -ALL policies on unused names.

Organizations that have configured SPF to protect their valid
RFC5321.MailFrom domains may not have taken the extra measure of using SPF
to obstruct names that are not used for mail.  While not directly part of
DMARC, an authentication result of "DMARC=NONE SPF=FAIL" is a more
meaningful result than "DMARC=NONE, SPF=NONE".  Consequently, it is
desirable to  ensure SPF=FAIL for any names that are never used as
RFC5321.MailFrom domain names.   Since SPF has no inheritance, this
requires many entries.

To demonstrate, assume that the domain "nomail.example.com" contains only a
webserver at "www.nomail.example.com".   Multiple SPF records are needed to
maximize protection of this subdomain from improper use.   An SPF policy of
"-ALL" is needed on:
- the domain itself, nomail.example.com,
- named resource records, including www.nomail.example.com
- the wildcard resource record, *.example.com.

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

<div dir=3D"ltr">Below is my proposed language for dealing with the problem=
s that NP is intended to address:<div>- unused DNS names</div><div>- non-ex=
istent DNS names</div><div><br></div><div>It provides supporting rationale,=
 and provides a more complete solution than anything suggested previously, =
and ties the design directly to the mailing list problem.</div><div><br></d=
iv><div>I have labelled the sections starting with &quot;X,&quot; because I=
 am not sure of the best way to position this text into the flow of the cur=
rent draft.</div><div><br></div><div>Doug Foster</div><div><br></div><div>x=
. Reducing the scope of the SP policy<br><br>DMARC introduces a method for =
the domain owner to state &quot;at time of transmission, authorized emails =
will always authenticate using DMARC criteria&quot;. =C2=A0 However,this au=
thentication can be lost in transit if message modification occurs in trans=
it, as discussed in RFC 7960.=C2=A0 This possibility can make domain owners=
 reluctant to move beyond sp=3Dnone.=C2=A0 This is a significant loss, beca=
use sp=3Dnone opens a vast namespace to domain abuse, including<br>- names =
that are DNS domains but are not protected by a domain-level DMARC policy<b=
r>- names that are DNS records records rather than DNS names, and cannot be=
 protected by a domain-level DMARC policy<br>- names that are not in DNS at=
 all, and therefore cannot be protected by a domain-level DMARC policy.<br>=
<br>To mitigate these impacts, it is useful to distinguish names used as em=
ail domains from names that are not used for email. =C2=A0 Names that are n=
ever used for email are never authorized at time of transmission, and there=
fore can be blocked without concern about in-transit modifications. =C2=A0 =
Several methods are presented for addressing this objective.<br><br><br>x.1=
 Implement mail domains as DNS domains with domain-level DMARC policies.<br=
><br>Mail domains are often implemented as DNS domains, but this is not req=
uired. =C2=A0 MX records and SPF policies can be attached to a named resour=
ce record or a wildcard resource record, while DMARC policies can only be a=
ttached to a DNS domain. =C2=A0 <br><br>Any name that is configured as a DN=
S resource record can be reconfigured as a subdomain name supported by reso=
urce records which match the subdomain name,=C2=A0and names that are not in=
 DNS can be added as DNS domain names.=C2=A0 Once all used mail domain name=
s are configured as DNS domains, they can be configured with DMARC policies=
.=C2=A0 =C2=A0Once this is complete, the SP policy will only apply to unuse=
d and non-existent names.=C2=A0 This will permit use of SP=3Dreject because=
 any such messages will have been unauthenticated at origin as well as bein=
g unauthenticated at reception. =C2=A0 This approach is fully compatible wi=
th RFC 7489 implementations of DMARC.<br><br><br>x.2 Implement an NP policy=
<br><br>The NP policy assumes that names used for mail can be reliably iden=
tified, so that names not used for mail can be categorized as not authorize=
d.=C2=A0 Two approaches are used:<br><br>- For mail domain names that are u=
sed with SMTP, the name is assumed to also be used as an RFC5322.From domai=
n name. =C2=A0 This is indicated by an MX record which evaluates to an IP a=
ddress, or an SPF policy which does not begin with an ALL term.=C2=A0 (RFC =
7505 indicates that an MX record which does not evaluate to an IP address i=
s useful to indicate that a domain does not accept incoming mail.=C2=A0 Bas=
ed on RFC 7208, content after an ALL term is ignored, so a policy of &quot;=
-ALL&quot; indicates that the name is never used as an RFC5321.MailFrom dom=
ain and an ALL term with any other modifier is a meaningless policy.)<br><b=
r>- For mail domain names that are not used with SMTP, a new TXT record is =
defined, with content &quot;DMARCFROMv1&quot;. =C2=A0 The presence of this =
TXT record indicates that the associated DNS domain, named DNS resource rec=
ord, or wildcard DNS record should be considered as potentially in use as a=
n RFC5322.From domain name.<br><br>Names which are identified by MX record,=
 SPF policy, or DMARCFROMv1 TXT record are considered in use names and are =
evaluated using the P or SP policy. =C2=A0 Names which do not match these c=
riteria are evaluated using the NP policy. =C2=A0 This allows unused and no=
n-existent names to be given a stricter DMARC policy than used names.<br><b=
r>To implement an NP policy, domain owners may need to make DNS changes:<br=
>- For used domain names that are only identified by an A or AAAA record, a=
n MX record or DMARCFROMv1 TXT record is needed to explicitly indicate that=
 the name is used for mail.<br>- For used domain names that are not in DNS =
at all, a DMARCFROMv1 TXT record=C2=A0is needed to indicate that the name i=
s used for mail.<br><br>The NP policy does not require that all mail domain=
s become DNS domains, but the NP policy will only be understood by evaluato=
rs which=C2=A0use this specification.=C2=A0 Consequently, it is preferable =
to ensure that all mail domains are implemented as DNS domains.<br><br>x,3 =
Implement SPF -ALL policies on unused names.<br><br>Organizations that have=
 configured SPF to protect their valid RFC5321.MailFrom domains may not hav=
e taken the extra measure of using SPF to obstruct names that are not used =
for mail.=C2=A0 While not directly part of DMARC, an authentication result =
of &quot;DMARC=3DNONE SPF=3DFAIL&quot; is a more meaningful result than &qu=
ot;DMARC=3DNONE, SPF=3DNONE&quot;.=C2=A0 Consequently, it is desirable to =
=C2=A0ensure SPF=3DFAIL for any names that are never used as RFC5321.MailFr=
om domain names. =C2=A0 Since SPF has no inheritance, this requires many en=
tries.<br><br>To demonstrate, assume that the domain &quot;<a href=3D"http:=
//nomail.example.com">nomail.example.com</a>&quot; contains only a webserve=
r at &quot;<a href=3D"http://www.nomail.example.com">www.nomail.example.com=
</a>&quot;. =C2=A0 Multiple SPF records are needed to maximize protection o=
f this subdomain from improper use. =C2=A0 An SPF policy of &quot;-ALL&quot=
; is needed on:<br>- the domain itself, <a href=3D"http://nomail.example.co=
m">nomail.example.com</a>,<br>- named resource records, including <a href=
=3D"http://www.nomail.example.com">www.nomail.example.com</a><br>- the wild=
card resource record, *.<a href=3D"http://example.com">example.com</a>.<br>=
=C2=A0<br><br></div></div>

--000000000000698adc05c4912423--


From nobody Sat Jun 12 08:09: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 300803A166B for <dmarc@ietfa.amsl.com>; Sat, 12 Jun 2021 08:09:27 -0700 (PDT)
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 tZ7CduBc-k0Z for <dmarc@ietfa.amsl.com>; Sat, 12 Jun 2021 08:09:24 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5351F3A166D for <dmarc@ietf.org>; Sat, 12 Jun 2021 08:09:24 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id c124so34169700qkd.8 for <dmarc@ietf.org>; Sat, 12 Jun 2021 08:09:24 -0700 (PDT)
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=tGs3MD0zuHmPz9ThTo08Vv9ssM9LVmwYIcPQTCJZFhg=; b=rQvDEdytNTUhJLSFk9/+XJ5BUTPlRbFTc6T8keR2Pdil/+nBnlZAMzECSgYJUHb/Oc I5LZ4aACHK61r4t/wY/wpfUOccKqzSowAbjWziPOYvSDfImfSd4qlGVVLECOinBmXf4z +l/8bTpT50Pt7nQJodCyPyzNVgI4O6Qt58v9ssA90Ssyq4kx0LGgq/wJ9XH6i8JhYNXM fuVja5Ipce0c8ihjK9evmP3LXueFOw3BxWQlaUB+ZRIriHl5SJrWgTeqnPdui69HNrot htrCmAwlELq9qOBXZicbweGqDXJdB9HX5eKceC5F9/qruwJibDWBjMbDsr3ffffcpRwl InSw==
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=tGs3MD0zuHmPz9ThTo08Vv9ssM9LVmwYIcPQTCJZFhg=; b=nAZQV6XEMGvyHEt+kGVUklaMTOCEAI4YghUsvKF8zu6AwwJciA5VS8niL3DLBXs9JX 0838OmzLm1XHQVsmvUVUqWPXWoBpeo3Ertzgf+EUf643QENaOCirB6d6DnoaYuqzp8rN dvsTT2SbRUyjyGijoiN7AFN8m8ztSwgvJSL1b85vBYXyyDKxUei8j5Sz9NH18Z3Yf5U9 0uKm/manEmPbqBm0Pv6orJnRL8SJoY7xRBVnEOSBkVFI5acUuHjKofSluJfPWVk6xwv5 L/v5xYVcMrkwG/35qO6UqjUhUwdlD4odrsMGG4OcxwKGGd1Gk6wHFFHQiwihqDUYICtk Lleg==
X-Gm-Message-State: AOAM5306pTT9N5+lUdaPXktJlJcKErO9VQWJBFG9/72TMNd5KP+ZKUZ/ X/2Tco4OrvBLUdJNom6p4ZhlKm9gP6jVLARZ5J4=
X-Google-Smtp-Source: ABdhPJxcOU7fMm+eXABp5Mz4ympsFg/kQttUMJe6X+YDmajoUWrZrfc9QdsrL+zAqY1831nO3ET8zPvfxW0rJcf66m0=
X-Received: by 2002:a37:9381:: with SMTP id v123mr8958199qkd.64.1623510562343;  Sat, 12 Jun 2021 08:09:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAH48ZfzuM298fkmhoZtH1ZbK=9Ne9EYtyTYNV27PSsPBW=Gq-w@mail.gmail.com>
In-Reply-To: <CAH48ZfzuM298fkmhoZtH1ZbK=9Ne9EYtyTYNV27PSsPBW=Gq-w@mail.gmail.com>
From: Dotzero <dotzero@gmail.com>
Date: Sat, 12 Jun 2021 11:09:11 -0400
Message-ID: <CAJ4XoYcs6iAVOPWAyFvf_iwKCVooUFxC=SbT406o1NvQ_RJxPA@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005b904405c49302f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/wEfxMlX06GXhTTASGX1ZqmIpbHk>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 12 Jun 2021 15:09:27 -0000

--0000000000005b904405c49302f0
Content-Type: text/plain; charset="UTF-8"

On Sat, Jun 12, 2021 at 8:56 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> Below is my proposed language for dealing with the problems that NP is
> intended to address:
> - unused DNS names
> - non-existent DNS names
>
> It provides supporting rationale, and provides a more complete solution
> than anything suggested previously, and ties the design directly to the
> mailing list problem.
>
> I have labelled the sections starting with "X," because I am not sure of
> the best way to position this text into the flow of the current draft.
>
> Doug Foster
>
> x. Reducing the scope of the SP policy
>
> DMARC introduces a method for the domain owner to state "at time of
> transmission, authorized emails will always authenticate using DMARC
> criteria".
>

The portion of the above statement is an incorrect assertion and is
meaningless to validators and mailbox receivers. It is well known (at least
to validators and receivers) that there is a significant subset of senders
who publish incorrect SPF records or improperly DKIM sign messages or
improperly publish DKIM in DNS or improperly publish DMARC in DNS. Further,
a validator or mailbox provider can only go by what they see and know at
the time they attempt to determine whether a given message validates or not.


> However,this authentication can be lost in transit if message modification
> occurs in transit, as discussed in RFC 7960.  This possibility can make
> domain owners reluctant to move beyond sp=none.  This is a significant
> loss, because sp=none opens a vast namespace to domain abuse, including
> - names that are DNS domains but are not protected by a domain-level DMARC
> policy
> - names that are DNS records records rather than DNS names, and cannot be
> protected by a domain-level DMARC policy
> - names that are not in DNS at all, and therefore cannot be protected by a
> domain-level DMARC policy.
>

Senders may be reluctant to implement DMARC for any number of reasons. I've
given email authentication training to thousands of people through OTA when
it was around and to/through the U.S. Federal government. Not once has
anyone raised the above as reasons for reluctance to implement DMARC,
either in total or for implementing policy.

>
> To mitigate these impacts, it is useful to distinguish names used as email
> domains from names that are not used for email.   Names that are never used
> for email are never authorized at time of transmission, and therefore can
> be blocked without concern about in-transit modifications.   Several
> methods are presented for addressing this objective.
>

As pointed out above, you are asserting impacts not in evidence when you
state that these impacts are of concern. A difference, in order to be a
difference, must make a difference. You have presented nothing to show that
this is an issue causing senders not to implement DMARC.

>
>
> x.1 Implement mail domains as DNS domains with domain-level DMARC policies.
>
> Mail domains are often implemented as DNS domains, but this is not
> required.   MX records and SPF policies can be attached to a named resource
> record or a wildcard resource record, while DMARC policies can only be
> attached to a DNS domain.
>
> Any name that is configured as a DNS resource record can be reconfigured
> as a subdomain name supported by resource records which match the subdomain
> name, and names that are not in DNS can be added as DNS domain names.  Once
> all used mail domain names are configured as DNS domains, they can be
> configured with DMARC policies.   Once this is complete, the SP policy will
> only apply to unused and non-existent names.  This will permit use of
> SP=reject because any such messages will have been unauthenticated at
> origin as well as being unauthenticated at reception.   This approach is
> fully compatible with RFC 7489 implementations of DMARC.
>
>
> x.2 Implement an NP policy
>
> The NP policy assumes that names used for mail can be reliably identified,
> so that names not used for mail can be categorized as not authorized.  Two
> approaches are used:
>
> - For mail domain names that are used with SMTP, the name is assumed to
> also be used as an RFC5322.From domain name.   This is indicated by an MX
> record which evaluates to an IP address, or an SPF policy which does not
> begin with an ALL term.  (RFC 7505 indicates that an MX record which does
> not evaluate to an IP address is useful to indicate that a domain does not
> accept incoming mail.  Based on RFC 7208, content after an ALL term is
> ignored, so a policy of "-ALL" indicates that the name is never used as an
> RFC5321.MailFrom domain and an ALL term with any other modifier is a
> meaningless policy.)
>
> - For mail domain names that are not used with SMTP, a new TXT record is
> defined, with content "DMARCFROMv1".   The presence of this TXT record
> indicates that the associated DNS domain, named DNS resource record, or
> wildcard DNS record should be considered as potentially in use as an
> RFC5322.From domain name.
>
> Names which are identified by MX record, SPF policy, or DMARCFROMv1 TXT
> record are considered in use names and are evaluated using the P or SP
> policy.   Names which do not match these criteria are evaluated using the
> NP policy.   This allows unused and non-existent names to be given a
> stricter DMARC policy than used names.
>
> To implement an NP policy, domain owners may need to make DNS changes:
> - For used domain names that are only identified by an A or AAAA record,
> an MX record or DMARCFROMv1 TXT record is needed to explicitly indicate
> that the name is used for mail.
> - For used domain names that are not in DNS at all, a DMARCFROMv1 TXT
> record is needed to indicate that the name is used for mail.
>
> The NP policy does not require that all mail domains become DNS domains,
> but the NP policy will only be understood by evaluators which use this
> specification.  Consequently, it is preferable to ensure that all mail
> domains are implemented as DNS domains.
>
> x,3 Implement SPF -ALL policies on unused names.
>
> Organizations that have configured SPF to protect their valid
> RFC5321.MailFrom domains may not have taken the extra measure of using SPF
> to obstruct names that are not used for mail.  While not directly part of
> DMARC, an authentication result of "DMARC=NONE SPF=FAIL" is a more
> meaningful result than "DMARC=NONE, SPF=NONE".  Consequently, it is
> desirable to  ensure SPF=FAIL for any names that are never used as
> RFC5321.MailFrom domain names.   Since SPF has no inheritance, this
> requires many entries.
>

As you state, it is NOT directly part of DMARC.

>
> To demonstrate, assume that the domain "nomail.example.com" contains only
> a webserver at "www.nomail.example.com".   Multiple SPF records are
> needed to maximize protection of this subdomain from improper use.   An SPF
> policy of "-ALL" is needed on:
> - the domain itself, nomail.example.com,
> - named resource records, including www.nomail.example.com
> - the wildcard resource record, *.example.com.
>

Anyone sophisticated enough to be concerned that this is a problem is
sophisticated enough to publish the appropriate DNS records if they choose.
Your proposal adds unnecessary complexity to address something that is
essentially a non-issue in the real world of DMARC and interoperability.
The more complexity that is added reduces the likelihood of implementation
OR if implementation is attempted, correct implementation.

This proposed change should not be considered by the working group.

Michael Hammer

--0000000000005b904405c49302f0
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 Sat, Jun 12, 2021 at 8:56 AM Dougl=
as Foster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com">dougfo=
ster.emailstandards@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr">Below is my proposed language=
 for dealing with the problems that NP is intended to address:<div>- unused=
 DNS names</div><div>- non-existent DNS names</div><div><br></div><div>It p=
rovides supporting rationale, and provides a more complete solution than an=
ything suggested previously, and ties the design directly to the mailing li=
st problem.</div><div><br></div><div>I have labelled the sections starting =
with &quot;X,&quot; because I am not sure of the best way to position this =
text into the flow of the current draft.</div><div><br></div><div>Doug Fost=
er</div><div><br></div><div>x. Reducing the scope of the SP policy<br><br>D=
MARC introduces a method for the domain owner to state &quot;at time of tra=
nsmission, authorized emails will always authenticate using DMARC criteria&=
quot;. =C2=A0 </div></div></blockquote><div><br></div><div>The portion of t=
he above statement is an incorrect assertion and is meaningless to validato=
rs and mailbox receivers. It is well known (at least to validators and rece=
ivers) that there is a significant subset of senders who publish incorrect =
SPF records or improperly DKIM sign messages or improperly publish DKIM in =
DNS or improperly publish DMARC in DNS. Further, a validator or mailbox pro=
vider can only go by what they see and know at the time they attempt to det=
ermine whether a given message validates or not.<br></div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>How=
ever,this authentication can be lost in transit if message modification occ=
urs in transit, as discussed in RFC 7960.=C2=A0 This possibility can make d=
omain owners reluctant to move beyond sp=3Dnone.=C2=A0 This is a significan=
t loss, because sp=3Dnone opens a vast namespace to domain abuse, including=
<br>- names that are DNS domains but are not protected by a domain-level DM=
ARC policy<br>- names that are DNS records records rather than DNS names, a=
nd cannot be protected by a domain-level DMARC policy<br>- names that are n=
ot in DNS at all, and therefore cannot be protected by a domain-level DMARC=
 policy.<br></div></div></blockquote><div><br></div><div>Senders may be rel=
uctant to implement DMARC for any number of reasons. I&#39;ve given email a=
uthentication training to thousands of people through OTA when it was aroun=
d and to/through the U.S. Federal government. Not once has anyone raised th=
e above as reasons for reluctance to implement DMARC, either in total or fo=
r implementing policy.=C2=A0 <br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"ltr"><div><br>To mitigate these impacts, it is us=
eful to distinguish names used as email domains from names that are not use=
d for email. =C2=A0 Names that are never used for email are never authorize=
d at time of transmission, and therefore can be blocked without concern abo=
ut in-transit modifications. =C2=A0 Several methods are presented for addre=
ssing this objective.<br></div></div></blockquote><div><br></div><div>As po=
inted out above, you are asserting impacts not in evidence when you state t=
hat these impacts are of concern. A difference, in order to be a difference=
, must make a difference. You have presented nothing to show that this is a=
n issue causing senders not to implement DMARC.<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><br><br>x.1 Implemen=
t mail domains as DNS domains with domain-level DMARC policies.<br><br>Mail=
 domains are often implemented as DNS domains, but this is not required. =
=C2=A0 MX records and SPF policies can be attached to a named resource reco=
rd or a wildcard resource record, while DMARC policies can only be attached=
 to a DNS domain. =C2=A0 <br><br>Any name that is configured as a DNS resou=
rce record can be reconfigured as a subdomain name supported by resource re=
cords which match the subdomain name,=C2=A0and names that are not in DNS ca=
n be added as DNS domain names.=C2=A0 Once all used mail domain names are c=
onfigured as DNS domains, they can be configured with DMARC policies.=C2=A0=
 =C2=A0Once this is complete, the SP policy will only apply to unused and n=
on-existent names.=C2=A0 This will permit use of SP=3Dreject because any su=
ch messages will have been unauthenticated at origin as well as being unaut=
henticated at reception. =C2=A0 This approach is fully compatible with RFC =
7489 implementations of DMARC.<br><br><br>x.2 Implement an NP policy<br><br=
>The NP policy assumes that names used for mail can be reliably identified,=
 so that names not used for mail can be categorized as not authorized.=C2=
=A0 Two approaches are used:<br><br>- For mail domain names that are used w=
ith SMTP, the name is assumed to also be used as an RFC5322.From domain nam=
e. =C2=A0 This is indicated by an MX record which evaluates to an IP addres=
s, or an SPF policy which does not begin with an ALL term.=C2=A0 (RFC 7505 =
indicates that an MX record which does not evaluate to an IP address is use=
ful to indicate that a domain does not accept incoming mail.=C2=A0 Based on=
 RFC 7208, content after an ALL term is ignored, so a policy of &quot;-ALL&=
quot; indicates that the name is never used as an RFC5321.MailFrom domain a=
nd an ALL term with any other modifier is a meaningless policy.)<br><br>- F=
or mail domain names that are not used with SMTP, a new TXT record is defin=
ed, with content &quot;DMARCFROMv1&quot;. =C2=A0 The presence of this TXT r=
ecord indicates that the associated DNS domain, named DNS resource record, =
or wildcard DNS record should be considered as potentially in use as an RFC=
5322.From domain name.<br><br>Names which are identified by MX record, SPF =
policy, or DMARCFROMv1 TXT record are considered in use names and are evalu=
ated using the P or SP policy. =C2=A0 Names which do not match these criter=
ia are evaluated using the NP policy. =C2=A0 This allows unused and non-exi=
stent names to be given a stricter DMARC policy than used names.<br><br>To =
implement an NP policy, domain owners may need to make DNS changes:<br>- Fo=
r used domain names that are only identified by an A or AAAA record, an MX =
record or DMARCFROMv1 TXT record is needed to explicitly indicate that the =
name is used for mail.<br>- For used domain names that are not in DNS at al=
l, a DMARCFROMv1 TXT record=C2=A0is needed to indicate that the name is use=
d for mail.<br><br>The NP policy does not require that all mail domains bec=
ome DNS domains, but the NP policy will only be understood by evaluators wh=
ich=C2=A0use this specification.=C2=A0 Consequently, it is preferable to en=
sure that all mail domains are implemented as DNS domains.<br><br>x,3 Imple=
ment SPF -ALL policies on unused names.<br><br>Organizations that have conf=
igured SPF to protect their valid RFC5321.MailFrom domains may not have tak=
en the extra measure of using SPF to obstruct names that are not used for m=
ail.=C2=A0 While not directly part of DMARC, an authentication result of &q=
uot;DMARC=3DNONE SPF=3DFAIL&quot; is a more meaningful result than &quot;DM=
ARC=3DNONE, SPF=3DNONE&quot;.=C2=A0 Consequently, it is desirable to =C2=A0=
ensure SPF=3DFAIL for any names that are never used as RFC5321.MailFrom dom=
ain names. =C2=A0 Since SPF has no inheritance, this requires many entries.=
<br></div></div></blockquote><div><br></div><div>As you state, it is NOT di=
rectly part of DMARC. <br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><div dir=3D"ltr"><div><br>To demonstrate, assume that the domain &qu=
ot;<a href=3D"http://nomail.example.com" target=3D"_blank">nomail.example.c=
om</a>&quot; contains only a webserver at &quot;<a href=3D"http://www.nomai=
l.example.com" target=3D"_blank">www.nomail.example.com</a>&quot;. =C2=A0 M=
ultiple SPF records are needed to maximize protection of this subdomain fro=
m improper use. =C2=A0 An SPF policy of &quot;-ALL&quot; is needed on:<br>-=
 the domain itself, <a href=3D"http://nomail.example.com" target=3D"_blank"=
>nomail.example.com</a>,<br>- named resource records, including <a href=3D"=
http://www.nomail.example.com" target=3D"_blank">www.nomail.example.com</a>=
<br>- the wildcard resource record, *.<a href=3D"http://example.com" target=
=3D"_blank">example.com</a>.<br></div></div></blockquote><div><br></div><di=
v>Anyone sophisticated enough to be concerned that this is a problem is sop=
histicated enough to publish the appropriate DNS records if they choose. Yo=
ur proposal adds unnecessary complexity to address something that is essent=
ially a non-issue in the real world of DMARC and interoperability. The more=
 complexity that is added reduces the likelihood of implementation OR if im=
plementation is attempted, correct implementation.</div><div><br></div><div=
>This proposed change should not be considered by the working group.</div><=
div><br></div><div>Michael Hammer<br></div><div><br></div><div><br></div></=
div></div>

--0000000000005b904405c49302f0--


From nobody Sat Jun 12 11:48:42 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 233F83A1D12 for <dmarc@ietfa.amsl.com>; Sat, 12 Jun 2021 11:48:40 -0700 (PDT)
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 wBC2LGdJnJtu for <dmarc@ietfa.amsl.com>; Sat, 12 Jun 2021 11:48:38 -0700 (PDT)
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 405EB3A1D10 for <dmarc@ietf.org>; Sat, 12 Jun 2021 11:48:38 -0700 (PDT)
Received: by mail-oi1-x229.google.com with SMTP id t40so9669739oiw.8 for <dmarc@ietf.org>; Sat, 12 Jun 2021 11:48:38 -0700 (PDT)
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=D4s5qnEZexHQe5SY/+8mNPflOlf6GXm3leq+qp3vZiE=; b=VYIn3FospulIgRxbGaIjXP8pMK5xakYHEAf9XaTJWZQaHFXCM6anhaS3sC073T7Ztw /qRiqKZq5p3U+AxPkF7dd/MPi4vtq4WzZ2Q1xJSQa4KzpAonrJ0sJRZaf7IZEGyEgHFB EmKhSbXl+y6SDCNtloIUcVLfTA4DFPhZsSWpf0MMahD4n7BhQmDy+aNDshxrLNBZwGfe OR89uyZG/Yq/51oVCSYpCdgdZrrV81plGtNy9BeF8dkV0LaKwHYH88hghQqq8mpJ5r3t ROWtOk1beSq8WwGZfC2zLyf34gojWxWdQa7gDo0qXtpkafaUwIgxl71YGBiALiXwrWO3 HFgw==
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=D4s5qnEZexHQe5SY/+8mNPflOlf6GXm3leq+qp3vZiE=; b=teMOt7Xy+81IdOBrmHaHccg63/4h5X4PC0rd8BOfqXwm3PV75ayh9DE6qGdl4MP/3k //VgQVdpIkkPMVJNVhapsHo8XHD4E9Oaq1ULN9bo9Tzj1COGgku8IyotIrIIZYxPE7JP DGYez09PDoih7Id/an9J1KtslITmghpxyR6rqyWuqN7LY7F03dbo0aYHhUDOJR5JvUK/ INYH7gL88bbzv+IYsWejsBnD1XPiOW2Dx5R3zkpx6QC7MEqGsUzLowWWp+Phw7waCkx1 7VThFI/mx+tdHLaAX17D+vSvPtiF6+ENPH9npTFG0Njl/Z6HPY7/5V3GzTnYKTXXXgts drkQ==
X-Gm-Message-State: AOAM532wsnNjlHx034gplKgCt19TyEPlU5uJjPdJJIrR5AkCgGxayAEn kpO9ofNXc4sA6/R6VKYKBJcSAW1u4ZBtViTfAUo=
X-Google-Smtp-Source: ABdhPJxHDBtno3vAwqDhkkAL82fVV8/QqBgdM0tPffBeM3krFFIWmyFD+IcPJX1TbH2QOMKfUYlggJcYLl4ieR37JC4=
X-Received: by 2002:aca:bd42:: with SMTP id n63mr17143289oif.73.1623523715567;  Sat, 12 Jun 2021 11:48:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAH48ZfzuM298fkmhoZtH1ZbK=9Ne9EYtyTYNV27PSsPBW=Gq-w@mail.gmail.com> <CAJ4XoYcs6iAVOPWAyFvf_iwKCVooUFxC=SbT406o1NvQ_RJxPA@mail.gmail.com>
In-Reply-To: <CAJ4XoYcs6iAVOPWAyFvf_iwKCVooUFxC=SbT406o1NvQ_RJxPA@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 12 Jun 2021 14:48:25 -0400
Message-ID: <CAH48Zfz1Be3JGL9=UPy2zcsgQW4A-0gBNAqioqK64GhQx4VPew@mail.gmail.com>
To: Dotzero <dotzero@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000059d47905c4961235"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/tiU1Dr57OpFPLMCB-pcnBgQ_a74>
Subject: Re: [dmarc-ietf] Ticket #111 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 12 Jun 2021 18:48:40 -0000

--00000000000059d47905c4961235
Content-Type: text/plain; charset="UTF-8"

(Subject ticket number corrected.)

Michael, I am surprised and disappointed by the severity of your critique.

NP Policy
-------------
The NP policy is upon us.   PSD for DMARC demonstrated the need.    The
problem is that their definition of NP, which the current DMARCbis draft
inherits, is a pre-SPF test for an invalid SMTP MailFrom address.   It is a
bizarre stretch to apply that test to the RFC5322.From address.    The
current test is insufficiently defined, undefended, and indefensible.  It
must be fixed.   The focus of this draft is a proposed fix, because there
have been no other fixes offered.

The key insight behind the NP policy idea is that some domain abuse can be
detected and rejected without depending on the attributes which create the
mailing list problem.  The best boundary for the NP policy is between those
names that are used as FROM address and those that are not.   Domain owners
currently lack sufficient mechanism to signal that condition correctly.

I evaluated options based on NXDOMAIN, but rejected them.  Even when done
perfectly, NXDOMAIN excludes a smaller set of unauthorized names than this
approach, and seems more difficult to implement.  NXDOMAIN has some nuances
which I found problematic.  This proposal introduces relatively low
compliance measures for those domain owners that wish to implement NP.

The Introduction
----------------------
As to the introduction, I think the relationship between SP=NONE and the
mailing list problem has been well elucidated.    Nor do I think that an
introductory sentence needs to enumerate all possible reasons for SP=NONE.
 But if you prefer to simply say "some domain owners have difficulty moving
beyond SP=NONE,", without any additional comment, I can accept a change
along those lines.   Getting the correct definition of NP is my priority,
not the opening sentence.

Validate vs Reject
------------------------
Sender authentication involves two partially independent goals:  proving
that a message is definitely authorized, and proving that a message is
definitely not authenticated.   Proving authorization is only relevant for
names that are used as email addresses.   Proving non-authorization has a
much larger scope, because it involves all possible names, not merely
in-use names.

RFC 7489 attempted to prove non-authentication based on domains achieving
SP=REJECT and messages being delivered without in-transit loss of
credentials.   This has not worked out well in practice.   NP defines
non-authentication based on attributes which are not dependent on transit,
and therefore it is a very powerful idea.

Level of Detail
-------------------
I could be convinced to move some of this content into a Best Practices
document.,   But my target audience is not limited to the big organizations
that can build custom code and spend a large amount of money on
consultants.   I am equally concerned about the smaller players who are
dependent on off-the-shelf products available from vendors, and the
developers witin those vendors who often implement to the specification
rather than to the security problem.   So yes, I favor laying things out
clearly, rather than assuming that sophisticated people will be able to
read between the lines.

If you have a different definition of NP, let's hear the proposal and its
defense.

Doug Foster

>
>

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

<div dir=3D"ltr"><div>(Subject ticket number corrected.)</div><div><br></di=
v><div dir=3D"ltr">Michael, I am surprised and disappointed by the severity=
 of your critique.<div><br></div><div>NP Policy</div><div>-------------</di=
v><div>The NP policy is upon us.=C2=A0 =C2=A0PSD for DMARC demonstrated the=
 need.=C2=A0 =C2=A0 The problem is that their definition=C2=A0of NP, which =
the current DMARCbis draft inherits, is a pre-SPF test for an invalid SMTP =
MailFrom address.=C2=A0 =C2=A0It is a bizarre stretch to apply that test to=
 the RFC5322.From address.=C2=A0 =C2=A0 The current test is insufficiently =
defined, undefended, and indefensible.=C2=A0 It must be fixed.=C2=A0 =C2=A0=
The focus of this draft is a proposed fix, because there have been no other=
 fixes offered.</div><div><br></div><div>The key insight=C2=A0behind the NP=
 policy idea is that some domain abuse can be detected and rejected without=
 depending on the attributes which create the mailing list problem.=C2=A0 T=
he best boundary for the NP policy is between those names that are used as =
FROM address and those that are not.=C2=A0 =C2=A0Domain owners currently la=
ck sufficient mechanism=C2=A0to signal that condition correctly.</div><div>=
<br></div><div>I evaluated=C2=A0options=C2=A0based on NXDOMAIN, but rejecte=
d them.=C2=A0 Even when done perfectly, NXDOMAIN excludes a smaller set of =
unauthorized names than this approach, and seems more difficult to implemen=
t.=C2=A0 NXDOMAIN has=C2=A0some nuances which I found problematic.=C2=A0 Th=
is proposal introduces relatively low compliance measures for those domain =
owners that wish to implement NP.</div><div><br></div><div>The Introduction=
</div><div>----------------------</div><div>As to the introduction, I think=
 the relationship between SP=3DNONE and the mailing=C2=A0list problem has b=
een well elucidated.=C2=A0 =C2=A0 Nor do I think that an introductory sente=
nce needs to enumerate all possible reasons for SP=3DNONE.=C2=A0 =C2=A0But =
if you prefer to simply say &quot;some domain owners have difficulty moving=
 beyond SP=3DNONE,&quot;, without any additional comment, I can accept a ch=
ange along those lines.=C2=A0 =C2=A0Getting the correct definition of NP is=
 my priority, not the opening sentence.</div><div><br></div><div>Validate v=
s Reject</div><div>------------------------</div><div>Sender authentication=
 involves two partially independent goals:=C2=A0 proving that a message is =
definitely authorized, and proving that a message is definitely not authent=
icated.=C2=A0 =C2=A0Proving authorization is only relevant for names that a=
re used as email addresses.=C2=A0 =C2=A0Proving non-authorization has a muc=
h larger scope, because it involves all possible names, not merely in-use n=
ames.=C2=A0 =C2=A0</div><div><br></div><div>RFC 7489=C2=A0attempted to prov=
e non-authentication based on domains achieving SP=3DREJECT and messages be=
ing delivered without in-transit loss of credentials.=C2=A0 =C2=A0This has =
not worked out well in practice.=C2=A0 =C2=A0NP defines non-authentication =
based on attributes which are not dependent on transit, and therefore it is=
 a very powerful idea.</div><div><br></div><div>Level of Detail</div><div>-=
------------------</div><div>I could be convinced to move some of this cont=
ent into a Best Practices document.,=C2=A0 =C2=A0But my target audience is =
not limited to the big organizations that can build custom code and spend a=
 large amount of money on consultants.=C2=A0 =C2=A0I am equally concerned a=
bout the smaller players who are dependent on off-the-shelf products availa=
ble from vendors, and the developers witin those vendors who often implemen=
t to the specification rather than to the security problem.=C2=A0 =C2=A0So =
yes, I favor laying things out clearly, rather than assuming that sophistic=
ated people will be able to read between the lines.</div><div><br></div><di=
v>If you have a different definition=C2=A0of NP, let&#39;s hear the=C2=A0pr=
oposal and its defense.</div><div><br></div><div>Doug Foster</div></div><di=
v class=3D"gmail_quote"><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 class=3D"gmail_quote"><div><br></div></div></div>
</blockquote></div></div>

--00000000000059d47905c4961235--


From nobody Sun Jun 13 03:00:20 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 C5AED3A139A for <dmarc@ietfa.amsl.com>; Sun, 13 Jun 2021 03:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 csiQsos2MiPg for <dmarc@ietfa.amsl.com>; Sun, 13 Jun 2021 03:00:07 -0700 (PDT)
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 9F1343A139B for <dmarc@ietf.org>; Sun, 13 Jun 2021 03:00:07 -0700 (PDT)
Received: (qmail 11309 invoked by uid 100); 13 Jun 2021 10:00:06 -0000
Date: 13 Jun 2021 09:59:44 -0000
Message-ID: <20210613095944.11308.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/qS_iSbHLnznfUKSnVYls1BbvQVE>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Jun 13 06:00:06 2021
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jun 2021 10:00:14 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
 13 ( 100%) | 152271 ( 100%) | Total
  3 (23.1%) |  20086 (13.2%) | Dave Crocker <dcrocker@gmail.com>
  2 (15.4%) |  46619 (30.6%) | Todd Herr <todd.herr@valimail.com>
  2 (15.4%) |  29035 (19.1%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  2 (15.4%) |  19108 (12.5%) | Tim Wicinski <tjw.ietf@gmail.com>
  1 ( 7.7%) |  22119 (14.5%) | Dotzero <dotzero@gmail.com>
  1 ( 7.7%) |   6131 ( 4.0%) | Alessandro Vesely <vesely@tana.it>
  1 ( 7.7%) |   6130 ( 4.0%) | Steven M Jones <smj@crash.com>
  1 ( 7.7%) |   3043 ( 2.0%) | John Levine <johnl@taugh.com>


From nobody Mon Jun 14 04:12: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 2D15A3A207E for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 04:12:13 -0700 (PDT)
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 1lYRfxYVoWpe for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 04:12:07 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 373B93A207A for <dmarc@ietf.org>; Mon, 14 Jun 2021 04:12:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1623669122; bh=m0kgNG3k/FtI8PHvVoUpQr2zIMZqKXTqFDag1+sU2gY=; l=4568; h=To:References:From:Date:In-Reply-To; b=CEs+4JMBJ4xG9cWWyxj6TXng1a6Q+iJAojF3bKPGdylqN/JDFkUtIr11R0k0x7oVn 8Gj5rQ4I1bBfe3C7pPeJ87EGJQRNCU700Ts9UhJVUulda+OI+QyT7z4JIYFktsRvUC Fvex/6RyDDqRS7F22TubJTWKW1TbfuqBqEmVUqYg4y3Eoz/c1bJJrnlYR+HSk
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.0000000060C73982.00001265; Mon, 14 Jun 2021 13:12:02 +0200
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <CAH48ZfzuM298fkmhoZtH1ZbK=9Ne9EYtyTYNV27PSsPBW=Gq-w@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <1a666b47-d556-e758-f4ce-05de79c449d1@tana.it>
Date: Mon, 14 Jun 2021 13:12:01 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfzuM298fkmhoZtH1ZbK=9Ne9EYtyTYNV27PSsPBW=Gq-w@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/1mYubgeHr3QfqDqyMFqEmh_4--E>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 14 Jun 2021 11:12:13 -0000

Doug,

maybe it's me, but I have problems understanding your proposal.  Let me quote 
what seems to hamper my comprehension.

Besides, #11 in the Subject: is obviously a typo.


On Sat 12/Jun/2021 14:55:33 +0200 Douglas Foster wrote:
> ties the design directly to the mailing list problem.


I couldn't see where mailing lists are taken into account.


>    However,this authentication can be lost in transit if message modification 
> occurs in transit, as discussed in RFC 7960.  This possibility can make domain 
> owners reluctant to move beyond sp=none.


Why do you consider SP irrespective of P?  Actually, SP could be used by 
"simple" mail sites, those which make no use of subdomains for email.  In such 
cases, setting sp=reject can safely prevent generic abuses even for domains 
having p=none.  It sounds similar to null SPF records for non-mail hosts.


> x.1 Implement mail domains as DNS domains with domain-level DMARC policies.
> 
> Mail domains are often implemented as DNS domains, but this is not required.


Please, stick to well established jargon.  Tim made a good synthesis in section 
2.2 and ensuing ones.  A /DNS domain/ is defined by RFC 1034:

     A domain is identified by a domain name, and consists of that part of
     the domain name space that is at or below the domain name which
     specifies the domain.

In this sense, the concept of non-existing domain names that are legitimately 
used sounds like a contradiction in terms.


> Once all used mail domain names are configured as DNS domains, they can be
> configured with DMARC policies.

AFAICS, a /used mail domain name/ which is not a DNS name is a /non-existent 
domain/ found in some (forged) email addresses.  I agree that such practice 
should be discouraged.  Yet, that doesn't seem to be the point here...

BTW, are there organizations that use non-existent (sub) domains during the 
delivery of legitimate messages?  Years ago I saw sporadic mailing list authors 
forged like john.doe@NOSPAMexample.com.  Is that what you're talking about?


> - For mail domain names that are not used with SMTP, a new TXT record is 
> defined, with content "DMARCFROMv1".   The presence of this TXT record 
> indicates that the associated DNS domain, named DNS resource record, or 
> wildcard DNS record should be considered as potentially in use as an 
> RFC5322.From domain name.


Ok, that is clear, but, IMHO, won't work.  Working MXes or IP addresses are a 
necessary condition to receive mail.  Thus, a purist receiver has to accept 
such domains as valid.  Therefore traditionalist domain operators will not see 
a compelling need to define any auxiliary TXT records.  A new RR type of this 
kind would most probably be going to characterize mass mailers who hasten to 
adopt any new trick that seems to offer a chance to increase deliverability. 
Undoubtedly, someone would be tempted to discard senders based on that (as it 
happened to DKIM...)

An organization which wants to say sp=reject but does use some email subdomains 
had better define plain DMARC records for them.  Records can be easily 
duplicated by CNAMEs.  If we needed to vary some parts but not others, for 
example a different policy but the same aggregate reporting address, we should 
define something equivalent to SPF's include.


> - For used domain names that are not in DNS at all, a DMARCFROMv1 TXT record
> is needed to indicate that the name is used for mail.

Actually, /any/ record definition will turn a domain into an existing one. 
However, by Section 2.7 of PSD, which defines the MX/A/AAAA test, such domain 
would still be non-existing.  In that sense, DMARCFROMv1 conflicts with PSD.


> x,3 Implement SPF -ALL policies on unused names.
> 
> Organizations that have configured SPF to protect their valid RFC5321.MailFrom 
> domains may not have taken the extra measure of using SPF to obstruct names 
> that are not used for mail.  While not directly part of DMARC, an 
> authentication result of "DMARC=NONE SPF=FAIL" is a more meaningful result than 
> "DMARC=NONE, SPF=NONE".  Consequently, it is desirable to  ensure SPF=FAIL for 
> any names that are never used as RFC5321.MailFrom domain names.   Since SPF has 
> no inheritance, this requires many entries.


That's a well known SPF issue:
http://www.open-spf.org/FAQ/Common_mistakes/#all-domains

There used to circulate scripts to generate null SPF records.  It would help if 
DNS hosting services implemented a checkbox to carry out such task.  But this 
if far OT.


Best
Ale
-- 

























From nobody Mon Jun 14 05:42:19 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 DF2773A2303; Mon, 14 Jun 2021 05:42:17 -0700 (PDT)
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, 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=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 pEXR_KjmMRXb; Mon, 14 Jun 2021 05:42:12 -0700 (PDT)
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 AC4FD3A2301; Mon, 14 Jun 2021 05:42:09 -0700 (PDT)
Received: from pps.filterd (m0184890.ppops.net [127.0.0.1]) by mx0b-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 15ECfLkn016284; Mon, 14 Jun 2021 08:42:08 -0400
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=m6tEp6A1Iqi1GDU8XYlCQW7cJGtMQg+PeTEW+qKBlUo=; b=Acj1UhVlJ2HIZoyMkQlvhhUs/WqM3R2rTsb05lDXkuRMfabQVcMR4N5abvvq+wZsW+Zx lddss2hYasNxQi6MAk6hRw+KaE+08iZ/U0nu+qbLH7u26e66aUBGdSFsDkAXccbamltP tD8tmjitEc4lsevG29W33tbGz2G0tG1XAWCpK4+3T1k/RrvENi0F14ri50CuLGYhx5sb zFAlRMmjho6JEtKpBw9I0b6d6eafLg+FIOsVo0Peojvir8tJC+eDlkgTsQreqNMzkYzz eZ7itJTueOfxU0SYr+ZpHdUZ/eHJisjXI75ozCcD8vcjx3YBh9Qq4YQDEoKiz4fxHG/Z nA== 
Received: from copdcexc35.cable.comcast.com (dlppfpt-po-1p.slb.comcast.com [96.99.226.137]) by mx0b-00143702.pphosted.com with ESMTP id 396601rgpm-20 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 14 Jun 2021 08:42:08 -0400
Received: from copdcexc33.cable.comcast.com (147.191.125.132) by COPDCEXC35.cable.comcast.com (147.191.125.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2242.10; Mon, 14 Jun 2021 06:42:02 -0600
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.2242.10 via Frontend Transport; Mon, 14 Jun 2021 06:42:02 -0600
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (104.47.58.106) by webmail.comcast.com (96.114.158.213) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Mon, 14 Jun 2021 06:41:51 -0600
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by MN2PR11MB4599.namprd11.prod.outlook.com (2603:10b6:208:26d::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4219.20; Mon, 14 Jun 2021 12:41:44 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::cddd:25b1:344d:8818]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::cddd:25b1:344d:8818%5]) with mapi id 15.20.4219.025; Mon, 14 Jun 2021 12:41:44 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: =?utf-8?B?TWF0dGjDpHVzIFdhbmRlcg==?= <mail=40wander.science@dmarc.ietf.org>, "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
Thread-Index: AddYdpfWt/LpopsnRqmW8ZVx8+CfOwArR8sAADeC8QABxdTBMA==
Date: Mon, 14 Jun 2021 12:41:44 +0000
Message-ID: <MN2PR11MB4351B731B053D51E093BBE51F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
References: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@MN2PR11MB4351.namprd11.prod.outlook.com> <f04b1dfa-2707-a67e-4df8-bf82d637f4f8@tana.it> <e213afa6-c777-d0a6-48ac-43965ff264cd@wander.science>
In-Reply-To: <e213afa6-c777-d0a6-48ac-43965ff264cd@wander.science>
Accept-Language: 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=comcast.com; 
x-originating-ip: [2601:43:103:e60:9e7:3126:fd:f039]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 902068c6-dcc1-4feb-ad37-08d92f31c461
x-ms-traffictypediagnostic: MN2PR11MB4599:
x-microsoft-antispam-prvs: <MN2PR11MB4599BB729EA8F1C5110BCEB0F7319@MN2PR11MB4599.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: D6qw9Obu+yyC+427po7nI7lncuZAdUr2IT+gxQoTZ4eiMigcxX+tXElQ8qY7X/sQWQBAKNCUh09RPKqjvl3LF44DukQYmP4LZV1QLGMQ9CYnqGR7sBwUJnRneXkuYDPP5314Z2sgw3MXJe+EJ6imIQRYclBuTNERi4jUONg2aLCnCtQ07ccDRxpNQfezoN4bd8HFggnS6tfGdAMdBYI7NhQL7eFSMKTCF32kGKSi2hJH8FR/hiVAyZOQUel/wqoIp1JWuBDqdHbkGZ2TvrsqwtQQA+dXqMaI3vFwbo9OjbdwIGbWpKofnuR6DyrzzMpmWXuV99qyXBpfx3iKfnE0giqhhMnfC+/QcpABTuUTdjWBvasT/IgGx/mnkAKlO8YB5UyJo84bqbGjqSQIQi4sUUXdgltkuFHMgosvo3Ph4gpSG+l2CtcoIhSz+UzPsMyIObqEaqSXWlVY3NdA/j/HK+r6JMwOW+QVVtlAsMdI8NHeaQbFj0dH4TyOMt0uQiOEZ1A9lPdPRLK3wSMCtieIspQWUD5v7NtNmUbt3mwGyDg7gFc0cmxX/c9FZcX1quLyuyGwrKurcjlvy6YNoBvwx7tNFrBv2QLFuCrZl1ejHeXf/Y8BivPQFHn4J7QajLdlgdzzS0TdJlHXJX2w3C35W6mmqBXXA3bTEwyHK0GJhBMs/JmseaNjpX+T+sc1XFWdwPutHlb5pFhHDpr3FIGv/w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4351.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(366004)(376002)(346002)(136003)(396003)(8936002)(2906002)(83380400001)(52536014)(33656002)(66446008)(66946007)(64756008)(66556008)(66476007)(55016002)(9686003)(86362001)(8676002)(110136005)(186003)(478600001)(76116006)(6506007)(53546011)(122000001)(38100700002)(5660300002)(7696005)(316002)(71200400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?utf-8?B?VUVGTHlUamlSTTZMaFl2R01zQVQ2QVp5OSt6TlFEc041dW15bmYvdW5GU1h2?= =?utf-8?B?Z3FBVVI2NjFPSUtVbXNRVUdxU0NHSTAyZFhNZGJvbm5KRzBiTkRhSkdFTVJI?= =?utf-8?B?TzE4RXliODJTUHdITjR3M2ZTWW1JdmRjOFR3dWhpdVBWaWVrTFZWNmdmc2ZB?= =?utf-8?B?NzlvSTFGcE54bDAxQ3J6SnNuUlR5cWVFSUJCK205QU5idkhTQWRvMTFTalJt?= =?utf-8?B?bWFxQTZQbEcvWis3M3pNRzRVRitNZ2tXNGtRWld4MDYwTGwrOFkrYllsbXFo?= =?utf-8?B?b0UwSkdaTVBqWmM0RW05YTJ3ckN4NHpyZm1XcHB1OUcrUnM3dSsrR3J2TWJD?= =?utf-8?B?a3NnYkRiVk4rV3k4bWlkRVRnc0hwS2pmeWVPbWphNERMQTJVeHRwcnRUTVpO?= =?utf-8?B?UkJuT1d6Rk5oWE5wbE11V29nYllVekthVUl6SWZ2aW00TEwzZFF5TmcwaC9j?= =?utf-8?B?OVV0OXQxSVNpUjhYYnpaRnZodjFNQ0VGam5zT0MxYkZoZ08rN283bkE5K3Fa?= =?utf-8?B?TUxrMmxPbTVWalJjZzNpY2NBTzJwb1l2Qm9MZnd5S1cxUXZGYjUvWElHQStj?= =?utf-8?B?dDlKcWVackcwTW90NWEvZ3o3YThuMU1yZXZESnB2MS80V1cwR0pGRG0wWitz?= =?utf-8?B?TnRueStuL0YzMlVBVWhMVGVQQlh2Qk41ZkplSlc2SnpGMzUrK2FNWVVjSVZG?= =?utf-8?B?cDZmQXdTc1RmQi9TaDVNc21jZGR4aTFLOVpsRnRKWVJOT1hJUWdIV1h5dGh6?= =?utf-8?B?ZU0rUW42RHY3SHd3VWVFRXRFMm9wNGNRZCs2UkdSS2J0OGZmYTVKeURhTjVj?= =?utf-8?B?V2JRc1A3bGhxZ0tEMnNEWXVGZVJqZmxESWpNaURmNTFkV1ExQ2kxN2k4alIv?= =?utf-8?B?a2ZNZ2dnd2xZWjFtOENlSUV5cE1mSkhkUkNONGxVQ0d1Mll0bGl1ZkoxTUxp?= =?utf-8?B?RStXTHU5eForamlyeThEN1NuVC9QRHhlK2dDbS9jeTlRRHRQNmpEQUlBYmMv?= =?utf-8?B?NUxuSWg0NWFCeFJOc3VjOXc0T3FsTmlkZlBRRHFSRUN4V2RvRmJaRFIxN0Zj?= =?utf-8?B?VDVvRkpMZlNobkhqS2dUWE12MGt4NVNxVUhDOEpSS21ackRNMzBNZ00yNzZl?= =?utf-8?B?bDVGZEFnUG1EZVBZRGpJVUw3cm9IRWVnMVZOMVJiVWlsdXpiR2FZQnZKTWQy?= =?utf-8?B?MGdhaXdNQUY4U2xoSEYybHJKRWNRQ3JIbWp6QVJLbDBxakFMUGRxazI2V3Nl?= =?utf-8?B?S2NkUzFaSGJVMVZ0OXR0RXdoMzZDajJDTVpxUW5uWUhab3M3YW5kR0FRRndB?= =?utf-8?B?ay9wV3VXaU1WZTh5TytKY1g0Z2ZBU2JVYitKeW5BY3dFVndqQ0dwOHdvVjF3?= =?utf-8?B?VU9KZE9GS0RqWS94TmVkeVZrVnFkU3FaVW5QZk9aQTRyUm1ja3pBdm5XckNk?= =?utf-8?B?QThlS0VLMzVWcU9DblVPSk1OU1lHbnJYME9Oa0pKZnhwOVBEOUhidHlZcmxo?= =?utf-8?B?YjEvQ2o2RkZOclYvQy9NMVg2Y2tGWmUrdTZKY3JpTUFjRDZkZXpjNVpvUVpE?= =?utf-8?B?bml0SysxaVRYcVZJMzduUEdlRTJjUFRycmlYSi9qbjJ4bGs4VXpHWndGRzBG?= =?utf-8?B?bGxSaTd4d0pGdkJBMUFzYkZIOU83cXhKRm10UmFIZHErMFpIRElFWFZmbTY4?= =?utf-8?B?Y1kyWGMzeFhpcXVUZWNVclQ5MmZpZGlQL29OWUtWYjJDdFZMU0g2amQyK2Q2?= =?utf-8?B?UVU0SGVETmk3Z2VZOS9JVHovdU5SdmZ5NXJBUUFzNmVqc2MxemRUNTFXdGRH?= =?utf-8?Q?fk71s5SAuwbkeqHpvNZaMrzfR/BXEXFmsaLSc=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PgqYlvZPSCWaTIWpAnH5X8tH1V8OHQyGY6RMn8bRHIx1Ox9JYx2CyOtUczAVQShfMhkDWcmWwZ61fEj+IlEvEbuSyV7fd3Q8ywD63jj6qP6AOc544qn+Dnvgbqw/vXrB7UnE8v59nyzaSUasekARgdToWugotJVp099rS8WqA3Fj6ckeHtRvR7k1Ulb21DImGQz8ZF+ANJ/MDVSvM9a065XvKQ4DE1uA1BComB11fKNu57siAYlVANCM4QpVlx9mGMLYL9lAz1UN5rlDgtsTXP9I4BB/wIFBduxXbhWyw+kCpuURBZnfwdKjjQbmvPjsTRzlbST2yJvUlksSruw1vg==
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=zbQPOEpAq2/FSYlDUCCy5D3G3P2XseeYswuuGVkGeqM=; b=A8qK6riQWi/ug6NZcdu+/zPxU1oxBBOjhq4fhjwIXpWx2047soKnbHNbuLslebV+Z7vSOrzGYh7gxurvBdzfSehOQ2/bms+WTgIQb3hk0LkcCk+rHTIyt7z+Wf9VZ9Z9YfiEu/4K8wF2dN7tM/qkt+kZt//UbFiQ0ddNEvOkBQCi4eq8Hn2Kpia1I8IXPVmxFJDSbD/yZlsVW2ZZH57cvktayseYZXEsLBsNqsN/jLCneS4dobeFTTnf2YBs7OZxf+VhJhe3wrm17sAWJgnnJ5ddoR7TSClhQV6Y2xhLc11hE+3PFNxcJVRIi6R3AcDMRv8unrwcGSYhscxp8OJagQ==
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: 902068c6-dcc1-4feb-ad37-08d92f31c461
x-ms-exchange-crosstenant-originalarrivaltime: 14 Jun 2021 12:41:44.2675 (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: Nz2O2KWzBkLemOQQIP0J8+daf+uassnapwIXXG6WXRXUCO2xsrdJpsBwCm6lZqb9bXMzaTGxpIG0gYz/X/Ne8rwIsPLBEQzaLox7G26Bd24=
x-ms-exchange-transport-crosstenantheadersstamped: MN2PR11MB4599
x-originatororg: comcast.com
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWT
X-Proofpoint-ORIG-GUID: xmjHGHKYLHIc0u1mtc0L6LCFnpEObh9M
X-Proofpoint-GUID: xmjHGHKYLHIc0u1mtc0L6LCFnpEObh9M
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-06-14_07:2021-06-14, 2021-06-14 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YpfLUI1ABKpd7h7vcImM13fAshw>
Subject: Re: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 14 Jun 2021 12:42:18 -0000

VG8gc3VtbWFyaXplLA0KDQpXZSdkIGxpa2UgdG8gc2VlIGV4dGVuc2lvbnMgYXZhaWxhYmxlIGJv
dGggYmVsb3cgdGhlICJmZWVkYmFjayIgYW5kICJyZWNvcmQiIGVsZW1lbnRzLiAgVGhlIC0wMiBk
cmFmdCBvbmx5IGhhcyBpdCBiZWxvdyB0aGUgImZlZWRiYWNrIiBlbGVtZW50LiAgSSBhZ3JlZSB0
aGF0IGFsbCBlbGVtZW50cywgZWFjaCB0aW1lIHRoZXkgYXJlIHV0aWxpemVkLCBzaG91bGQgbWVu
dGlvbiBhIHJlZmVyZW5jZSBhcyB0byBob3cgdGhleSBhcmUgdG8gYmUgdXRpbGl6ZWQuDQoNCldl
J2QgYWxzbyBsaWtlIHRvIGhhdmUgZXh0ZW5zaW9ucyBnbyB0aHJvdWdoIGFuIElFVEYgcHJvY2Vz
cywgaG93ZXZlciwgd2UgYWxzbyB1bmRlcnN0YW5kIHRoYXQgd2UgY2Fubm90IGV4Y2x1ZGUgdGhp
cmQgcGFydGllcyBmcm9tIGRlZmluaW5nL2RlcGxveWluZyB0aGVpciBvd24gZXh0ZW5zaW9ucy4g
IEkgc3VwcG9zZSB3ZSBjb3VsZCB0ZWxsIHJlcG9ydCByZWNlaXZlcnMgdGhleSAiTVVTVCIgaWdu
b3JlIGFueSBleHRlbnNpb25zIHdoaWNoIGFyZSBub3QgSUVURi1hcHByb3ZlZCwgdGhvdWdoIHRo
YXQgc2VlbXMgYSBiaXQgaGVhdnktaGFuZGVkLg0KDQpTbywgYSBzYW1wbGUgcmVwb3J0IG1heSBs
b29rIHNvbWV0aGluZyBsaWtlOg0KDQogICA8ZmVlZGJhY2s+DQogICAgIDx2ZXJzaW9uPjIuMDwv
dmVyc2lvbj4NCiAgICAgPHJlcG9ydF9tZXRhZGF0YT4NCiAgICAgICA8dmVyc2lvbj4yPC92ZXJz
aW9uPg0KICAgICAgIDxvcmdfbmFtZT5TYW1wbGUgUmVwb3J0ZXI8L29yZ19uYW1lPg0KICAgICAg
IDxlbWFpbD5yZXBvcnRfc2VuZGVyQGV4YW1wbGUtcmVwb3J0ZXIuY29tPC9lbWFpbD4NCiAgICAg
ICA8ZXh0cmFfY29udGFjdF9pbmZvPi4uLjwvZXhwb3J0X2NvbnRhY3RfaW5mbz4NCiAgICAgICA8
cmVwb3J0X2lkPjN2OThhYmJwOHlhOW4zdmE4eXI4b2EzeWE8L3JlcG9ydF9pZD4NCiAgICAgICA8
ZGF0ZV9yYW5nZT4NCiAgICAgICAgIDxiZWdpbj4xNjEyMTI0MTU8L2JlZ2luPg0KICAgICAgICAg
PGVuZD4xNjEyMjE1MTE8L2VuZD4NCiAgICAgICA8L2RhdGVfcmFuZ2U+DQogICAgIDwvcmVwb3J0
X21ldGFkYXRhPg0KICAgICA8cG9saWN5X3B1Ymxpc2hlZD4NCiAgICAgICA8ZG9tYWluPmV4YW1w
bGUuY29tPC9kb21haW4+DQogICAgICAgPHA+cXVhcmFudGluZTwvcD4NCiAgICAgICA8c3A+bm9u
ZTwvc3A+DQogICAgICAgPHBjdD4xMDA8L3BjdD4NCiAgICAgPC9wb2xpY3lfcHVibGlzaGVkPg0K
ICAgICA8cmVjb3JkPg0KICAgICAgIDxyb3c+DQogICAgICAgICA8c291cmNlX2lwPjE5Mi4xNjgu
NC40PC9zb3VyY2VfaXA+DQogICAgICAgICA8Y291bnQ+MTIzPC9jb3VudD4NCiAgICAgICAgIDxw
b2xpY3lfZXZhbHVhdGVkPg0KICAgICAgICAgICA8ZGlzcG9zaXRpb24+cXVhcmFudGluZTwvZGlz
cG9zaXRpb24+DQogICAgICAgICAgIDxka2ltPnBhc3M8L2RraW0+DQogICAgICAgICAgIDxzcGY+
ZmFpbDwvc3BmPg0KICAgICAgICAgPC9wb2xpY3lfZXZhbHVhdGVkPg0KICAgICAgIDwvcm93Pg0K
ICAgICAgIDxpZGVudGlmaWVycz4NCiAgICAgICAgIDxoZWFkZXJfZnJvbT5leGFtcGxlLmNvbTwv
aGVhZGVyX2Zyb20+DQogICAgICAgPC9pZGVudGlmaWVycz4NCiAgICAgICA8YXV0aF9yZXN1bHRz
Pg0KICAgICAgICAgPGRraW0+DQogICAgICAgICAgIDxkb21haW4+ZXhhbXBsZS5jb208L2RvbWFp
bj4NCiAgICAgICAgICAgPHJlc3VsdD5wYXNzPC9yZXN1bHQ+DQogICAgICAgICAgIDxzZWxlY3Rv
cj5hYmMxMjM8L3NlbGVjdG9yPg0KICAgICAgICAgPC9ka2ltPg0KICAgICAgICAgPHNwZj4NCiAg
ICAgICAgICAgPGRvbWFpbj5leGFtcGxlLmNvbT4NCiAgICAgICAgICAgPHJlc3VsdD5mYWlsPC9y
ZXN1bHQ+DQogICAgICAgICA8L3NwZj4NCiAgICAgICA8L2F1dGhfcmVzdWx0cz4NCiAgICAgICAg
PGV4dGVuc2lvbnM+DQogICAgICAgICAgPGV4dGVuc2lvbl9uYW1lIGRlZmluaXRpb249InVybCI+
DQogICAgICAgICAgICAgLi4uLi4uLi4uDQogICAgICAgICAgPC9leHRlbnNpb25fbmFtZT4NCiAg
ICAgICA8L2V4dGVuc2lvbnM+DQogICAgIDwvcmVjb3JkPg0KICAgIDxleHRlbnNpb25zPg0KICAg
ICAgIDxleHRlbnNpb25fbmFtZSBkZWZpbml0aW9uPSJ1cmwiPg0KICAgICAgICAuLi4uDQogICAg
ICAgPC9leHRlbnNpb25fbmFtZT4NCiAgICA8L2V4dGVuc2lvbnM+DQogICA8L2ZlZWRiYWNrPg0K
DQpUaGUgZ29hbCBiZWluZyB0byBhbGxvdyBleHRlbnNpb25zIHRvIGxpdmUgZWl0aGVyIGF0IHRo
ZSByZXBvcnRlZC1JUCBsZXZlbCwgb3IgYXQgdGhlIGRvbWFpbiBsZXZlbC4NCg0KRG9lcyB0aGlz
IHNlZW0gcmVhc29uYWJsZT8NCg0KLS0NCkFsZXggQnJvdG1hbg0KU3IuIEVuZ2luZWVyLCBBbnRp
LUFidXNlICYgTWVzc2FnaW5nIFBvbGljeQ0KQ29tY2FzdA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+IEZyb206IGRtYXJjIDxkbWFyYy1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhh
bGYgT2YgTWF0dGjDpHVzIFdhbmRlcg0KPiBTZW50OiBTYXR1cmRheSwgSnVuZSA1LCAyMDIxIDc6
NTYgQU0NCj4gVG86IGRtYXJjQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbZG1hcmMtaWV0Zl0g
RXh0ZW5zaW9ucyBpbiBBZ2dyZWdhdGUgUmVwb3J0aW5nIC0gRmVlZGJhY2sNCj4gUmVxdWVzdGVk
DQo+DQo+IEFsZXNzYW5kcm8gVmVzZWx5IHdyb3RlIG9uIDIwMjEtMDYtMDQgMTE6MjY6DQo+ID4g
U2Vjb25kLCBJJ20gbm90IHN1cmUgd2UgbmVlZCBhbiA8ZXh0ZW5zaW9ucz4gY29udGFpbmVyLg0K
PiA+IEknZCBnbyBmb3IgYW4gZXhhbXBsZSBsaWtlLCBzYXksIHNvOg0KPiA+DQo+ID4gWy4uLl0N
Cj4gPiAgICAgPGV4dGVuc2lvbl9tZXRhZGF0YSBuYW1lPSJiaW1pIg0KPiA+IHhtbG5zPSJodHRw
Oi8vaWV0Zi5vcmcveG1sLW5hbWVzYXBhY2VzL2JpbWkteG1sPy8xLjAiPg0KPiAgPiBbLi4uXQ0K
PiA+ICAgICAgICA8ZXh0ZW5zaW9uIG5hbWU9ImJpbWkiDQo+ID4geG1sbnM9Imh0dHA6Ly9pZXRm
Lm9yZy94bWwtbmFtZXNhcGFjZXMvYmltaS14bWw/Py8xLjAiPg0KPg0KPiBJZiB3ZSB1c2UgYW4g
YXR0cmlidXRlIGZvciB0aGUgZXh0ZW5zaW9uIG5hbWUsIHRoZW4gd2UgZG9uJ3QgdGhlIGNvbnRh
aW5lcg0KPiBzZWN0aW9uLg0KPiBBcyB0aGUgY3VycmVudCBzY2hlbWEgZG9lcyBub3QgdXNlIGF0
dHJpYnV0ZXMgYXQgYWxsLCBJJ20gbW9yZSBpbmNsaW5lZCB0byBkZWZpbmUNCj4gdGhlIGV4dGVu
c2lvbiBuYW1lIGluIGEgZGlmZmVyZW50IHdheSBmb3IgY29uc2lzdGVudCBub24tdXNlIG9mIGF0
dHJpYnV0ZXMuIEJ1dA0KPiB0aGF0J3MgYSBtaW5vciBkZXRhaWwuDQo+DQo+ID4+IDEpIEV4dGVu
c2lvbnMgaW4gdGhlaXIgb3duIHNlY3Rpb24gKGFzIGl0IGlzIG5vdykgb3Igd2l0aGluIGVhY2gN
Cj4gPj4gPHJvdz4gZWxlbWVudA0KPiA+DQo+ID4NCj4gPiBCb3RoLCBhbmQgYm90aCBvcHRpb25h
bC4gIEFuIGV4dGVuc2lvbiBjYW4gaGF2ZSBzb21lIGRhdGEgdG8gYWRkIGluDQo+ID4gc29tZSA8
cmVjb3JkPiwgYnV0IG5vdCBuZWNlc3NhcmlseSBpbiBhbGwgb2YgdGhlbS4NCj4NCj4gKzENCj4N
Cj4gUmVnYXJkcywNCj4gTWF0dA0KDQo=


From nobody Mon Jun 14 08:35:15 2021
Return-Path: <tadams@proofpoint.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA08F3A283E; Mon, 14 Jun 2021 08:35:13 -0700 (PDT)
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, 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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=proofpoint.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6FfQQdXbSDt; Mon, 14 Jun 2021 08:35:08 -0700 (PDT)
Received: from mx0a-00148503.pphosted.com (mx0b-00148503.pphosted.com [148.163.159.21]) (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 905C73A283C; Mon, 14 Jun 2021 08:35:07 -0700 (PDT)
Received: from pps.filterd (m0086146.ppops.net [127.0.0.1]) by mx0b-00148503.pphosted.com (8.16.1.2/8.16.1.2) with SMTP id 15EEcSKq017310;  Mon, 14 Jun 2021 08:35:05 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proofpoint.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=corp-2019-08-07; bh=Zqof0BgJYe/aJ3eIIvH0nyReBrGh72gsHmtGlxEKaAI=; b=K6bjzRLlPmoKw06zI8fsAxmvFj4Nwvjdp+Aj6qwkrV5Sa4tOQMhsGyKkN7j59V/NB6IU Q43qN/L/E5kGjK8ygaiBAMWOR57b40WV1B4rzYjceqXzO26UB+9gF1AxO+gq+w0FVIfz ZDKvorGSYwQJF4zdAX05TcUg6fNSU17IXBEdBOh3rjbx6acfQ5A9xq+bvi7OymJ6dQ4g SSxATNQ6rMitnyMzpfN1XKHtc7hNV6cJ8g+HrdSAmJ8YGcFep5UYz86IzAZtZxqmt8/s ezzjQTbxvjC4+IXfjBZD9UzVFOTMhEt/rTO/NcMwL2Fc2GBcVbeqJFdj1k/XnRzIKjN/ Wg== 
Received: from lv-exch03.corp.proofpoint.com (spf-mailers.proofpoint.com [136.179.16.100]) by mx0b-00148503.pphosted.com with ESMTP id 394t090s05-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 14 Jun 2021 08:35:04 -0700
Received: from lv-exch01.corp.proofpoint.com (10.94.30.37) by lv-exch03.corp.proofpoint.com (10.19.10.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.2176.2; Mon, 14 Jun 2021 08:35:03 -0700
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (10.19.16.20) by lv-exch01.corp.proofpoint.com (10.94.30.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.2176.2 via Frontend Transport; Mon, 14 Jun 2021 08:35:03 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LV3uXbGEGvFoeXYj90YcCOwJTRuEY8GxrkJNAv4QhFl1VFcvnMmMtwNDFQ+Oo1QBWQPcXl98ZOtNoN6yZiJA6+whnmEf64Oy04YJ/gWd4tBnrjlnmIfRX7VHp7jBxYRq3whav9+TYtUmShhy+gzDeeSqO/j529I2ukt2bTJ8ppRjKwnvTh3F6YkxcBwnvPYHuHUCU/bGHvdskJN9JFMEHsRPWYaupX/QsWFc+bQr+Ymdq3oaBf2eZnDH2jQ6b2kH7BojGKO9q0d7I1WaziEK4bxNsudhE4vjsovcbU4Ad2CHdA4Q8NumhCiDQBh3l1n1s23eci4c3HYCjBNZF52hew==
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=Zqof0BgJYe/aJ3eIIvH0nyReBrGh72gsHmtGlxEKaAI=; b=cx0f4TliJ7eRNqB+ZnyBocsFLVdf00ooyIRXzpx1Kmx+s88MlW+X2qwPmyJDId9KoJBIj8a1wM2j/4BP638ngTOtXtji5ZRpr7u1I7xjE2+amsYw0QxgXGhTYckdexcAaYMTsluV88Fo+A5uhmY6Ou7r8uFfEJWs/GYXnM1rhcmnGkC5cXYzoHYbt5nXl3C7Lu3L+hf5SxTYGmwIa/yx63qzeGi0dQzXL7J7pmbdAh0Kjk4lwq3nNcRwXfd3EpxhphtvHxnU2fb/jkyuiZpRO6ohLYCwNKgVd4qfb2ukHcMOqn6sMMFQQu0n0Y5HUFDJ/E6bMn8gCMV/tAxzfomATQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=proofpoint.com; dmarc=pass action=none header.from=proofpoint.com; dkim=pass header.d=proofpoint.com; arc=none
Received: from CY4PR12MB1782.namprd12.prod.outlook.com (2603:10b6:903:123::21) by CY4PR12MB1349.namprd12.prod.outlook.com (2603:10b6:903:40::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4219.21; Mon, 14 Jun 2021 15:35:01 +0000
Received: from CY4PR12MB1782.namprd12.prod.outlook.com ([fe80::85c3:daa0:5f10:2fc5]) by CY4PR12MB1782.namprd12.prod.outlook.com ([fe80::85c3:daa0:5f10:2fc5%7]) with mapi id 15.20.4219.025; Mon, 14 Jun 2021 15:35:01 +0000
From: Trent Adams <tadams@proofpoint.com>
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>, =?utf-8?B?TWF0dGjDpHVzIFdhbmRlcg==?= <mail=40wander.science@dmarc.ietf.org>, "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
Thread-Index: AddYdpfWt/LpopsnRqmW8ZVx8+CfOwArR8sAADeC8QABxdTBMP//zusA
Date: Mon, 14 Jun 2021 15:35:01 +0000
Message-ID: <703C70FE-5FD0-4B16-84D4-E8C654B6E018@proofpoint.com>
References: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@MN2PR11MB4351.namprd11.prod.outlook.com> <f04b1dfa-2707-a67e-4df8-bf82d637f4f8@tana.it> <e213afa6-c777-d0a6-48ac-43965ff264cd@wander.science> <MN2PR11MB4351B731B053D51E093BBE51F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB4351B731B053D51E093BBE51F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.49.21050901
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=proofpoint.com;
x-originating-ip: [2601:283:4700:8dc0:a152:4d70:c03f:6e8d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0fdc7d66-a053-420d-96ec-08d92f49f968
x-ms-traffictypediagnostic: CY4PR12MB1349:
x-microsoft-antispam-prvs: <CY4PR12MB134904A8B009387C97B85EAFB3319@CY4PR12MB1349.namprd12.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: JjDmH5npgE2rKnDYkpikZQjukqWkIkDRpSI1uhm2dkihLHAU81fSRLZZMn3q7CcjNSegcLrXG57Uhv5h5/UR5RcB3ox2xnopibO9WypsoIrQkyJM5B3DqPTHSYBY6cYIe5z/yJQuAQQsIVPtDm3B7rVUETb6ZQLQshRPa7v+mmqVzuSTugiVBgPbmgtxqCxfZ2W+qT63jGWy7zO2ETKsGWIM32LdL0edH7ardGaeYSizoJXcrKADsgiK9thhbqBUbkN/8wKc/qTGe6sI71ts9p6eLaiyZZC9B/+P28zDA4DHR1DBIHHlldANkCsvUD1tK/9D55kgVkHV9XsgrHcFVlkpcSAl59hTC4qHpBTKRnoTlEhMKEnBMV8L39Qy2NcYIx/5icZ51s549DXkmw4UX9Pr9tU1ByXY8KONH3DJpHvkLUrU6cn3b+VXYeVvXD4ARNllgqaKGNIzU7Qh5c3Fndp+J7HCQNV2xBrh0lj7pxmGtjPbmnmFSypCx0EtmYiV7CuxkhAy4faWxCVOe7Y/wkczgmre51nsTm/UfbOYszoGgVvz0+e92w6m4qVsWW5SII19/5kiD2goUwo415rW19ChasdTQX6F3EZ2U0IQxqYuycY6Wp6rqiRJvozKPZ5iIEPjcRmCsge0DtB39PTOaJbvME0fKSTBkcttexdVgtRsaxPdkoVjoyuGN5H0PqQ654ewBeNsL2LNtanZQ0LXUzdPWByBhOmkbD2WXQJSBQcfIyIJKGu0fUsCqeKuF/VtRyKItMfd/An/TVbfoc/OCw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CY4PR12MB1782.namprd12.prod.outlook.com; PTR:; CAT:NONE;  SFS:(39860400002)(136003)(396003)(346002)(376002)(366004)(6506007)(66556008)(122000001)(66446008)(186003)(110136005)(66476007)(8676002)(36756003)(966005)(8936002)(2906002)(64756008)(316002)(2616005)(86362001)(66946007)(33656002)(38100700002)(6512007)(53546011)(478600001)(71200400001)(76116006)(83380400001)(6486002)(5660300002)(45980500001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?utf-8?B?cmtzQ2Q3ajVBV2MwL2g1V3cyYTFtWEw0a2dxWXdoblI4OC8vMzA5bnRwc3JD?= =?utf-8?B?OW10QXBGWlY1M3cwLzNCNmtnSU9veVJYWlkzRWJVeHdTWFM1S3ZiQXNoUHpq?= =?utf-8?B?TFdLMlNTL1hpSTdRVFk5eXVyRUFSZ0VCcFNBQUhsNThRTUtvdE1rMTlWYmNy?= =?utf-8?B?amFCTzFuTjFQUFVKVHI0SWY4QUd6T2FFem5nQy9qY1kzR3FVemQ4ZHhPZE1N?= =?utf-8?B?SmNFMGRlRnFWS0ZsS3pVZ0tJeHZaMHJRNTJKYU8zU1g0Uko4OS9mUWt0RDhz?= =?utf-8?B?aGg2MFVDbnFLTGdrZ09vM0hROEx5djdXa3NhbGZNOXNnNVZJblFVbmI0YjZi?= =?utf-8?B?K0dZTkxpZTZHRjAycmkrUE15OUtvRFcremNPSWtvbUE2YXpRNlU1RUdESE9K?= =?utf-8?B?SWNGV2gvNUxkY1FiT2ZNUjBJTGdoOFZIYU5MMnQvVmdUS2pkMlpKOExPSW93?= =?utf-8?B?VDJhbGp4T2VIREkxTW8yRThDWnVCZ0MrYldXWVE1T1kralpIdkowQVZZNVll?= =?utf-8?B?c0JlTjh4cmxvYXEycHRTTTZxNVdZYTNJTEdvN3dKWEswaTVLa1hPNWFYMUNG?= =?utf-8?B?RmIrcjVSWCtOUUUvQ0JzT1Y1bWgvUi92S1p3YVViV1RaZ0hJL0ZqTFNqemRy?= =?utf-8?B?c2VJTW41Nm1DRlEvWUgxNmFHVTBTL25Uc0xuT1lYcG91aExUR3NQR3MxQ2lv?= =?utf-8?B?Z0JYdGh4SXBEeWk1SXdMcFdUQUJkUjVrdHRySjVnYlhCd2hEMTd3K0lKMGlt?= =?utf-8?B?MUFHQkR6NkxOWFN3QjRHL2FHSVUwRmpvK3BjUlp6bE00eXBXT3NhekZvOHZU?= =?utf-8?B?Z3BvcTQ1SDlZM050K24xYWFmVkZWRWtFSnFsanB5a1R3MmhuSEZDbGFmUUVi?= =?utf-8?B?cVZkRFBQdlJEclVEMlRNWnpKTlgyT0JlYnBiS0tyeVAveTl1cjRrRHpaOFM5?= =?utf-8?B?cDA1c0JveTBFU05XMGpzY2xxUkNob0xSVlFWY25EYkI4ZU1WTzI3YXBzVGtz?= =?utf-8?B?MjR6bWhjL0RQai9UVDJpc3hqTUprRHJSNzRCbEFTcmpnZmt1WXRoT3hhOVFy?= =?utf-8?B?eHAvc0ZUNmVNcnQ4Qkd1cU82bHRucEhtV2tUNDQ2ek9Kck4rTWFveUZQUHBy?= =?utf-8?B?dVlva3dwR3RlcTZjekhBWDZvdGNTdjhuWEdQUWZBOHVRbzFiR1NsWXZwUzE1?= =?utf-8?B?c0twTHNrR0h0Qk5mZG1vbXgraTB0NTdiZVRWN2M2UmJwWjdDTkl4N0o5QnU2?= =?utf-8?B?T3VrSXRvUzM1enRRdS9BMFE3cC9UN2JlaUFTNG9UcERHVG5BdGkzbm45ZHp1?= =?utf-8?B?SStBNHd1YWVsUnNWbmtMM082VCtrdG5aRTh6SW1YWXNHSnZabStNZ0RXeHhZ?= =?utf-8?B?K3JMckJLSjBuSnlZNkl3MmplQ2haODRxZ2x1bDFpU01ZVENQdkRnSlRBRWFt?= =?utf-8?B?RkJudUtGYTVqSkpCY21wUUYvNXVSM0plOW14ak5ZQTZySEtVY1pPVlFOYndO?= =?utf-8?B?MWdmNW5mQlE2S0YzWExCTkt1MVpPY1lYVmc0eEUxUjFPd2FTRlJJdTBkQ1Zw?= =?utf-8?B?b3ZqZVc3Q1U4ZDBFaktEQ3dpZ1c5RU13cG96Ryt1aXVQSkxHOWpNeXlOVWdi?= =?utf-8?B?RDhTN3JpSE1OUytzSFlObjBEMlFZY09WNFdtU0RISUo0YmxnQ2lLVHlnSzFT?= =?utf-8?B?Y2l2VUlHa2lDM2hKd1hhZWhNQWVoRkNOa1ZVdnkvVjZLdVJNRmhPNG40S1hF?= =?utf-8?B?dVd5djI4SVdBMkZxMmF2YnRFMnJGN0FsbHoyTlFkVDBHbkRheWZhUU5FNFdU?= =?utf-8?B?LzRaKzhoOUlobHhBUHlqR1NMSytrTXZ6V1VVRVFJRVMrYUFRM0NqbFJNeElD?= =?utf-8?B?ODhMUzJqZ21LS0xZM0c1UEtRNWZWYzY1RGw5M09KWVdFZ3c9PQ==?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <ECE0D34E8755374A9F25C7CCB4FFAE2C@namprd12.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CY4PR12MB1782.namprd12.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0fdc7d66-a053-420d-96ec-08d92f49f968
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jun 2021 15:35:01.1165 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 46785c73-1c32-414b-86bc-fae0377cab01
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: qa3DP8l492bRFzjMtC4oKXT6N/ep4rPlyTg5yIztC2AgAVqObILSDi1qJ2tzVBVBs3mUoRAdw3AifffdYHP0hQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR12MB1349
X-OriginatorOrg: proofpoint.com
X-PassedThroughOnPremises: Yes
X-Proofpoint-GUID: xV70cFsvne3mU-HvtK6G9q4UHYHOp-dl
X-Proofpoint-ORIG-GUID: xV70cFsvne3mU-HvtK6G9q4UHYHOp-dl
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.182.1,Aquarius:18.0.761,Hydra:6.0.391,FMLib:17.0.607.475 definitions=2021-06-14_09,2021-06-14_01,2020-04-07_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 malwarescore=0 clxscore=1011 lowpriorityscore=0 suspectscore=0 spamscore=0 bulkscore=0 adultscore=0 mlxscore=0 priorityscore=1501 mlxlogscore=999 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104190000 definitions=main-2106140099
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/UPvUKtxoNCgyWG2kOg0LXtcTdwc>
Subject: Re: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 14 Jun 2021 15:35:14 -0000

DQorMQ0KDQoNCu+7v09uIDYvMTQvMjEsIDY6NDIgQU0sICJkbWFyYyBvbiBiZWhhbGYgb2YgQnJv
dG1hbiwgQWxleCIgPGRtYXJjLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIEFsZXhfQnJv
dG1hbj00MGNvbWNhc3QuY29tQGRtYXJjLmlldGYub3JnPiB3cm90ZToNCg0KICAgIFRvIHN1bW1h
cml6ZSwNCg0KICAgIFdlJ2QgbGlrZSB0byBzZWUgZXh0ZW5zaW9ucyBhdmFpbGFibGUgYm90aCBi
ZWxvdyB0aGUgImZlZWRiYWNrIiBhbmQgInJlY29yZCIgZWxlbWVudHMuICBUaGUgLTAyIGRyYWZ0
IG9ubHkgaGFzIGl0IGJlbG93IHRoZSAiZmVlZGJhY2siIGVsZW1lbnQuICBJIGFncmVlIHRoYXQg
YWxsIGVsZW1lbnRzLCBlYWNoIHRpbWUgdGhleSBhcmUgdXRpbGl6ZWQsIHNob3VsZCBtZW50aW9u
IGEgcmVmZXJlbmNlIGFzIHRvIGhvdyB0aGV5IGFyZSB0byBiZSB1dGlsaXplZC4NCg0KICAgIFdl
J2QgYWxzbyBsaWtlIHRvIGhhdmUgZXh0ZW5zaW9ucyBnbyB0aHJvdWdoIGFuIElFVEYgcHJvY2Vz
cywgaG93ZXZlciwgd2UgYWxzbyB1bmRlcnN0YW5kIHRoYXQgd2UgY2Fubm90IGV4Y2x1ZGUgdGhp
cmQgcGFydGllcyBmcm9tIGRlZmluaW5nL2RlcGxveWluZyB0aGVpciBvd24gZXh0ZW5zaW9ucy4g
IEkgc3VwcG9zZSB3ZSBjb3VsZCB0ZWxsIHJlcG9ydCByZWNlaXZlcnMgdGhleSAiTVVTVCIgaWdu
b3JlIGFueSBleHRlbnNpb25zIHdoaWNoIGFyZSBub3QgSUVURi1hcHByb3ZlZCwgdGhvdWdoIHRo
YXQgc2VlbXMgYSBiaXQgaGVhdnktaGFuZGVkLg0KDQogICAgU28sIGEgc2FtcGxlIHJlcG9ydCBt
YXkgbG9vayBzb21ldGhpbmcgbGlrZToNCg0KICAgICAgIDxmZWVkYmFjaz4NCiAgICAgICAgIDx2
ZXJzaW9uPjIuMDwvdmVyc2lvbj4NCiAgICAgICAgIDxyZXBvcnRfbWV0YWRhdGE+DQogICAgICAg
ICAgIDx2ZXJzaW9uPjI8L3ZlcnNpb24+DQogICAgICAgICAgIDxvcmdfbmFtZT5TYW1wbGUgUmVw
b3J0ZXI8L29yZ19uYW1lPg0KICAgICAgICAgICA8ZW1haWw+cmVwb3J0X3NlbmRlckBleGFtcGxl
LXJlcG9ydGVyLmNvbTwvZW1haWw+DQogICAgICAgICAgIDxleHRyYV9jb250YWN0X2luZm8+Li4u
PC9leHBvcnRfY29udGFjdF9pbmZvPg0KICAgICAgICAgICA8cmVwb3J0X2lkPjN2OThhYmJwOHlh
OW4zdmE4eXI4b2EzeWE8L3JlcG9ydF9pZD4NCiAgICAgICAgICAgPGRhdGVfcmFuZ2U+DQogICAg
ICAgICAgICAgPGJlZ2luPjE2MTIxMjQxNTwvYmVnaW4+DQogICAgICAgICAgICAgPGVuZD4xNjEy
MjE1MTE8L2VuZD4NCiAgICAgICAgICAgPC9kYXRlX3JhbmdlPg0KICAgICAgICAgPC9yZXBvcnRf
bWV0YWRhdGE+DQogICAgICAgICA8cG9saWN5X3B1Ymxpc2hlZD4NCiAgICAgICAgICAgPGRvbWFp
bj5leGFtcGxlLmNvbTwvZG9tYWluPg0KICAgICAgICAgICA8cD5xdWFyYW50aW5lPC9wPg0KICAg
ICAgICAgICA8c3A+bm9uZTwvc3A+DQogICAgICAgICAgIDxwY3Q+MTAwPC9wY3Q+DQogICAgICAg
ICA8L3BvbGljeV9wdWJsaXNoZWQ+DQogICAgICAgICA8cmVjb3JkPg0KICAgICAgICAgICA8cm93
Pg0KICAgICAgICAgICAgIDxzb3VyY2VfaXA+MTkyLjE2OC40LjQ8L3NvdXJjZV9pcD4NCiAgICAg
ICAgICAgICA8Y291bnQ+MTIzPC9jb3VudD4NCiAgICAgICAgICAgICA8cG9saWN5X2V2YWx1YXRl
ZD4NCiAgICAgICAgICAgICAgIDxkaXNwb3NpdGlvbj5xdWFyYW50aW5lPC9kaXNwb3NpdGlvbj4N
CiAgICAgICAgICAgICAgIDxka2ltPnBhc3M8L2RraW0+DQogICAgICAgICAgICAgICA8c3BmPmZh
aWw8L3NwZj4NCiAgICAgICAgICAgICA8L3BvbGljeV9ldmFsdWF0ZWQ+DQogICAgICAgICAgIDwv
cm93Pg0KICAgICAgICAgICA8aWRlbnRpZmllcnM+DQogICAgICAgICAgICAgPGhlYWRlcl9mcm9t
PmV4YW1wbGUuY29tPC9oZWFkZXJfZnJvbT4NCiAgICAgICAgICAgPC9pZGVudGlmaWVycz4NCiAg
ICAgICAgICAgPGF1dGhfcmVzdWx0cz4NCiAgICAgICAgICAgICA8ZGtpbT4NCiAgICAgICAgICAg
ICAgIDxkb21haW4+ZXhhbXBsZS5jb208L2RvbWFpbj4NCiAgICAgICAgICAgICAgIDxyZXN1bHQ+
cGFzczwvcmVzdWx0Pg0KICAgICAgICAgICAgICAgPHNlbGVjdG9yPmFiYzEyMzwvc2VsZWN0b3I+
DQogICAgICAgICAgICAgPC9ka2ltPg0KICAgICAgICAgICAgIDxzcGY+DQogICAgICAgICAgICAg
ICA8ZG9tYWluPmV4YW1wbGUuY29tPg0KICAgICAgICAgICAgICAgPHJlc3VsdD5mYWlsPC9yZXN1
bHQ+DQogICAgICAgICAgICAgPC9zcGY+DQogICAgICAgICAgIDwvYXV0aF9yZXN1bHRzPg0KICAg
ICAgICAgICAgPGV4dGVuc2lvbnM+DQogICAgICAgICAgICAgIDxleHRlbnNpb25fbmFtZSBkZWZp
bml0aW9uPSJ1cmwiPg0KICAgICAgICAgICAgICAgICAuLi4uLi4uLi4NCiAgICAgICAgICAgICAg
PC9leHRlbnNpb25fbmFtZT4NCiAgICAgICAgICAgPC9leHRlbnNpb25zPg0KICAgICAgICAgPC9y
ZWNvcmQ+DQogICAgICAgIDxleHRlbnNpb25zPg0KICAgICAgICAgICA8ZXh0ZW5zaW9uX25hbWUg
ZGVmaW5pdGlvbj0idXJsIj4NCiAgICAgICAgICAgIC4uLi4NCiAgICAgICAgICAgPC9leHRlbnNp
b25fbmFtZT4NCiAgICAgICAgPC9leHRlbnNpb25zPg0KICAgICAgIDwvZmVlZGJhY2s+DQoNCiAg
ICBUaGUgZ29hbCBiZWluZyB0byBhbGxvdyBleHRlbnNpb25zIHRvIGxpdmUgZWl0aGVyIGF0IHRo
ZSByZXBvcnRlZC1JUCBsZXZlbCwgb3IgYXQgdGhlIGRvbWFpbiBsZXZlbC4NCg0KICAgIERvZXMg
dGhpcyBzZWVtIHJlYXNvbmFibGU/DQoNCiAgICAtLQ0KICAgIEFsZXggQnJvdG1hbg0KICAgIFNy
LiBFbmdpbmVlciwgQW50aS1BYnVzZSAmIE1lc3NhZ2luZyBQb2xpY3kNCiAgICBDb21jYXN0DQoN
CiAgICA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQogICAgPiBGcm9tOiBkbWFyYyA8ZG1h
cmMtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIE1hdHRow6R1cyBXYW5kZXINCiAgICA+
IFNlbnQ6IFNhdHVyZGF5LCBKdW5lIDUsIDIwMjEgNzo1NiBBTQ0KICAgID4gVG86IGRtYXJjQGll
dGYub3JnDQogICAgPiBTdWJqZWN0OiBSZTogW2RtYXJjLWlldGZdIEV4dGVuc2lvbnMgaW4gQWdn
cmVnYXRlIFJlcG9ydGluZyAtIEZlZWRiYWNrDQogICAgPiBSZXF1ZXN0ZWQNCiAgICA+DQogICAg
PiBBbGVzc2FuZHJvIFZlc2VseSB3cm90ZSBvbiAyMDIxLTA2LTA0IDExOjI2Og0KICAgID4gPiBT
ZWNvbmQsIEknbSBub3Qgc3VyZSB3ZSBuZWVkIGFuIDxleHRlbnNpb25zPiBjb250YWluZXIuDQog
ICAgPiA+IEknZCBnbyBmb3IgYW4gZXhhbXBsZSBsaWtlLCBzYXksIHNvOg0KICAgID4gPg0KICAg
ID4gPiBbLi4uXQ0KICAgID4gPiAgICAgPGV4dGVuc2lvbl9tZXRhZGF0YSBuYW1lPSJiaW1pIg0K
ICAgID4gPiB4bWxucz0iaHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0dHA6Ly9pZXRmLm9y
Zy94bWwtbmFtZXNhcGFjZXMvYmltaS14bWw/KjEuMF9fO0x3ISFPUmdFZkNCc3IyODJGdyE1alBz
TkR4bllvYWVvX0hDVERIWk9TczVNY1NLVWlrNWZydGdkRnhIQl93TDlPNlZEeXdyWmhva0xPd3Vz
SU5VJCAiPg0KICAgID4gID4gWy4uLl0NCiAgICA+ID4gICAgICAgIDxleHRlbnNpb24gbmFtZT0i
YmltaSINCiAgICA+ID4geG1sbnM9Imh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwOi8v
aWV0Zi5vcmcveG1sLW5hbWVzYXBhY2VzL2JpbWkteG1sPyoqQTEuMF9fO1B5OCEhT1JnRWZDQnNy
MjgyRnchNWpQc05EeG5Zb2Flb19IQ1RESFpPU3M1TWNTS1VpazVmcnRnZEZ4SEJfd0w5TzZWRHl3
clpob2tMTmVtS05GViQgIj4NCiAgICA+DQogICAgPiBJZiB3ZSB1c2UgYW4gYXR0cmlidXRlIGZv
ciB0aGUgZXh0ZW5zaW9uIG5hbWUsIHRoZW4gd2UgZG9uJ3QgdGhlIGNvbnRhaW5lcg0KICAgID4g
c2VjdGlvbi4NCiAgICA+IEFzIHRoZSBjdXJyZW50IHNjaGVtYSBkb2VzIG5vdCB1c2UgYXR0cmli
dXRlcyBhdCBhbGwsIEknbSBtb3JlIGluY2xpbmVkIHRvIGRlZmluZQ0KICAgID4gdGhlIGV4dGVu
c2lvbiBuYW1lIGluIGEgZGlmZmVyZW50IHdheSBmb3IgY29uc2lzdGVudCBub24tdXNlIG9mIGF0
dHJpYnV0ZXMuIEJ1dA0KICAgID4gdGhhdCdzIGEgbWlub3IgZGV0YWlsLg0KICAgID4NCiAgICA+
ID4+IDEpIEV4dGVuc2lvbnMgaW4gdGhlaXIgb3duIHNlY3Rpb24gKGFzIGl0IGlzIG5vdykgb3Ig
d2l0aGluIGVhY2gNCiAgICA+ID4+IDxyb3c+IGVsZW1lbnQNCiAgICA+ID4NCiAgICA+ID4NCiAg
ICA+ID4gQm90aCwgYW5kIGJvdGggb3B0aW9uYWwuICBBbiBleHRlbnNpb24gY2FuIGhhdmUgc29t
ZSBkYXRhIHRvIGFkZCBpbg0KICAgID4gPiBzb21lIDxyZWNvcmQ+LCBidXQgbm90IG5lY2Vzc2Fy
aWx5IGluIGFsbCBvZiB0aGVtLg0KICAgID4NCiAgICA+ICsxDQogICAgPg0KICAgID4gUmVnYXJk
cywNCiAgICA+IE1hdHQNCg0KICAgIF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQogICAgZG1hcmMgbWFpbGluZyBsaXN0DQogICAgZG1hcmNAaWV0Zi5vcmcN
CiAgICBodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9kbWFyY19fOyEhT1JnRWZDQnNyMjgyRnchNWpQc05EeG5Zb2Flb19IQ1RE
SFpPU3M1TWNTS1VpazVmcnRnZEZ4SEJfd0w5TzZWRHl3clpob2tMSWNJclEtbyQgDQoNCg==


From nobody Mon Jun 14 09:28:08 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A7013A29D4 for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 09:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DytTbpGYkojb for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 09:28:01 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5314E3A29D3 for <dmarc@ietf.org>; Mon, 14 Jun 2021 09:28:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1623688076; bh=oyD6iyRO797hSwZbW254rMObRGBH2yaLFbKgbUQd0lE=; l=1387; h=To:References:From:Date:In-Reply-To; b=CD1cS3FevQdlLoaSMHP9Mz5zwa0PwBp/5DmkMj5cXraNbOtyWBZR9EIFYQUgnNxrI ELKR4Hr4N39rfdCj8szZgS4d66DmSIeYp9uwjJj9+e3ycqKX8f5zpclt1OrFg/Kfkm OZiJFDW0fNVDY7bToa/kIDevfkWf+uGmUtGnFioO5RsqzCSniNsVkEwJilbMw
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.0000000060C7838C.00003727; Mon, 14 Jun 2021 18:27:56 +0200
To: dmarc@ietf.org
References: <MN2PR11MB4351A6C5A477DB006CB6DD72F73C9@MN2PR11MB4351.namprd11.prod.outlook.com> <f04b1dfa-2707-a67e-4df8-bf82d637f4f8@tana.it> <e213afa6-c777-d0a6-48ac-43965ff264cd@wander.science> <MN2PR11MB4351B731B053D51E093BBE51F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <90a281ff-5d3c-7a6f-e162-bab8e654fbf1@tana.it>
Date: Mon, 14 Jun 2021 18:27:54 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB4351B731B053D51E093BBE51F7319@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/1YbB_NaM_ccZ0D-AyB0QJxgxlgU>
Subject: Re: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 14 Jun 2021 16:28:07 -0000

On Mon 14/Jun/2021 14:41:44 +0200 Brotman, Alex wrote:
> 
> I agree that all elements, each time they are utilized, should mention a reference as to how they are to be utilized.
> 
> [...]
> 
> So, a sample report may look something like:
> 
>     <feedback>
>       <version>2.0</version>
>       <report_metadata>
>         <version>2</version>


So why doesn't <feedback> mention a reference to how it is utilized?

About that overabundance of <version>'s, the 1st entry, right below <feedback>, is the aggregate report version.  Thus far, we agreed that it is useless as a grammar indication if <feedback> contains its namespace declaration.  However, Matt noted that there may be parsers that consider reports to be pre-IETF drafts if they miss the <version> element.  In this case, it makes sense to keep <version>1.0</version> for backward compatibility, especially if we try not to break existing parsers.

The second <version> entry, inside <report_metadata>, had better wear a different name, to avoid confusion.  I assume it's meant to be the report reference version.  A couple of alternative examples:

     <report_metadata>
       <generator>https://github.com/trusteddomainproject/OpenDMARC/releases/tag/rel-opendmarc-1-4-1</generator>

or

     <report_metadata>
       <generator>
         <url>http://www.trusteddomain.org/opendmarc/</url>
         <version>1.4.1</version>
       </generator>


Best
Ale
-- 

























From nobody Mon Jun 14 10:09:54 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 4FECC3A2B35 for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 10:09:52 -0700 (PDT)
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, RCVD_IN_DNSWL_BLOCKED=0.001, 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=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 CI9CcK8WaIy8 for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 10:09:48 -0700 (PDT)
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 102123A2B33 for <dmarc@ietf.org>; Mon, 14 Jun 2021 10:09:47 -0700 (PDT)
Received: from pps.filterd (m0156891.ppops.net [127.0.0.1]) by mx0a-00143702.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 15EH1YoN002202 for <dmarc@ietf.org>; Mon, 14 Jun 2021 13:09:47 -0400
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=3oI+EbBxMWihQn5gtQbnO28p+228WUbH8uo8UYHcu/I=; b=Pn3+IQV++ZWIqQJROzMrkFpY+fP939v7XYpG6wdpXwtsJj7P7OL6kJspqbfKzcjWJqlY di1t923MhWQcTT6MQwlzd6azlwDNLDlemO0pPTSmCp4MQNhzFdBHibXpGb4Z6/dTsyTj 9v7rkqHgGNA8tSM1W76K+vIfsOc+JZF6i9fWBH7ASYVm1YL5XflWVR1DeRwolJ/7AEmW pWMHLUjTuQoQoqyRBlNIsj+iGlgFtAJsGDYajADHAoP0wpSPoKG0aqo8o/bmTDFjugYW Ansan7M5HDHzkZgGUcf2Wtt2hmI/+WjG6cJc7Me+cnC8R+45JoqXfkomkbjBXtkgk1Xa HQ== 
Received: from copdcexc37.cable.comcast.com (dlppfpt-po-1p.slb.comcast.com [96.99.226.137]) by mx0a-00143702.pphosted.com with ESMTP id 39675kafax-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Mon, 14 Jun 2021 13:09:47 -0400
Received: from copdcexc33.cable.comcast.com (147.191.125.132) by COPDCEXC37.cable.comcast.com (147.191.125.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2242.10; Mon, 14 Jun 2021 11:09:45 -0600
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.2242.10 via Frontend Transport; Mon, 14 Jun 2021 11:09:45 -0600
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (104.47.59.172) by webmail.comcast.com (96.114.158.213) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Mon, 14 Jun 2021 11:09:39 -0600
Received: from MN2PR11MB4351.namprd11.prod.outlook.com (2603:10b6:208:193::31) by BL0PR11MB2913.namprd11.prod.outlook.com (2603:10b6:208:79::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4219.23; Mon, 14 Jun 2021 17:09:38 +0000
Received: from MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::cddd:25b1:344d:8818]) by MN2PR11MB4351.namprd11.prod.outlook.com ([fe80::cddd:25b1:344d:8818%5]) with mapi id 15.20.4219.025; Mon, 14 Jun 2021 17:09:38 +0000
From: "Brotman, Alex" <Alex_Brotman@comcast.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: Sender-supplied decision matrix for passing DMARC
Thread-Index: AddhPDwbCzQ9bLtKT5O2BtOM1Kt/Jw==
Date: Mon, 14 Jun 2021 17:09:38 +0000
Message-ID: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@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:103:e60:9e7:3126:fd:f039]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c959ef3e-042d-46cb-3817-08d92f57314b
x-ms-traffictypediagnostic: BL0PR11MB2913:
x-microsoft-antispam-prvs: <BL0PR11MB2913EF294E0F1B0482BB46ECF7319@BL0PR11MB2913.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: 6lvnl3KvaqzcS1bs+C0Jh6dnXjVNjJnV8x4DTAHvITNhB8BZUprYWP4BfO5Ewx7GjvMdptHIUw16BOxVNMMJHIqnOzNElEmc8CQJ+UCUS4v+cCYddyeTGC0G7p+gYtcFxus+XeCsTW8Ugg3vZmnVucdFBWxdp7kta+Ys3SutZGRJ0SducOlAXtFgHunYwDfft+Kd5wO2g1maZzmnFsnKQFO+DkOUPDGecIrh2oxOyjjcP8jbUjjgn174ULgpwc6IL48u/mtl86dmq747WkYopdf/or03cnpVnpNqAZqdSeeQdmP1T94o0QKEXXm8N3PEhjnTCWofwOVSxj43W5+DDKCABnXIR3cUtx2bzMrFtdDsZJf0hFSnrDVw8iD+ANR717HGngI5jUk53q7E1lSe9aNcSpJcRn+qlOBdY6r0DkzujcbEx/YIHhJivR6A/AXnZFejb9ncXwp2xSxfHECeQS6kT08QbqzJU0Q7EAJRdXOqStdyaxdPv0SqcBKPh5wdtWfMNcMS5VzpoZIguu0TsJhC6PokW4L1KqYOBeGNvLbgIpN75Ax0by3VPGMMgrvol2Ka8ajgcxdCNKZp+pekznx0tJvwduNetD1aJP5T2DA=
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)(396003)(346002)(136003)(39860400002)(366004)(376002)(84050400001)(7696005)(8676002)(122000001)(38100700002)(86362001)(2906002)(316002)(71200400001)(478600001)(9686003)(66946007)(76116006)(66556008)(64756008)(66476007)(66446008)(33656002)(6916009)(8936002)(52536014)(6506007)(186003)(83380400001)(55016002)(5660300002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?r0q+p0cEuJhb+hmnzVmV6RHT8g31jfTzUbHMWXdiBM8Gx1i5oPjG4S5B3aUd?= =?us-ascii?Q?ErTWlFVbIoVix19IuemszUM2xj3pupdQFW4/0VqAHz4IfkXreqz9bPDLSHY2?= =?us-ascii?Q?c7a5XF7FjvAPSV+xDTmQrgzSDXIuHvTp8fjvfTmclpDCXJ4TCsv6B7narwnO?= =?us-ascii?Q?OCPe/lfqt2FEnx9QOWVRVu7z8VHDxtB8igVe2l96kn6gnimXlFgJYgFwXvTQ?= =?us-ascii?Q?5sbu5DG8khtBGp8u7xcOO/3DmJmIHApCZqeq7tpYlf6p441khFxeR0eAxjOX?= =?us-ascii?Q?EIIs4nBClykOmzeq6U3KFU9JmmJ60t+UetQp06Cn4+vpCoNFvxA+i1m85QAy?= =?us-ascii?Q?e8jCY9wSB9C5go6ynlnYsoSlu0YkK1EbV/gni2DYbKUDabMjVC2oeysbQkCy?= =?us-ascii?Q?3qTuBKzTpNn/zmCgs/b4pQjO4HhsioUIUXSyPMa95/kaxxhOqtIqfcsKNYdd?= =?us-ascii?Q?6xOoxzKKd5sk9mnJ4V633B9dl9EI6hAxEG9h5Am6i6kjp7wVtMH2U7LxWgzo?= =?us-ascii?Q?orfTVa/BcRMb5F81vbuW9l6/fWnnnpw01/rcDS5Ls3XB1eh71rkMK7JL2+qO?= =?us-ascii?Q?jay96pzyljDKnVIQtrZnvKkLXuq5qIp7o4Ht6TCXUYMjuzY1xfQzNpnl7Nsk?= =?us-ascii?Q?z0sugsu7EXYsnspYu+qE+M9gh8jCX3uh0wvt1zpLnIufDA1hUvJ1BsFLFx4Y?= =?us-ascii?Q?DRaOS4BVNln1oW84Eb+FlcZ2X9W0Lzhsv3/SkoNLixguSWUOX3JS6sXvZpGu?= =?us-ascii?Q?mYoNhRxCJGJPHU7TScZMwpDSx0A/mshKZVHJuLTUUwfCbV3/wmbyCeYpyCxs?= =?us-ascii?Q?ukm3Kk//pNIsDTdUM6vQsTE/DSDg/ad6zX1nc/243chuvO2ZTI1OPo6iuzIR?= =?us-ascii?Q?qKt98HJ9J+lM0Nz0DXAl3rIb5opTtzqzpzOo0WWEQieEaM5PGJw+XY1vAlFN?= =?us-ascii?Q?yfp7pnMP9TA+KH3lo5sOE1YDv2mKzCDWZAkgtp+Gd6J5A+ZTBcEvF3BdLviQ?= =?us-ascii?Q?8s6LbrW4aNmt9Tm3o1gc5zSDNrOdzriI5pQpbU6wbOQEr43c/47t1Nyt3ArU?= =?us-ascii?Q?T3/dkSZ3re5XSJX/fVtydQgCTCAtvRoZT/ULj2QzX0mYHyJW9tWYZtv/esMo?= =?us-ascii?Q?7rqGMU1oDgbcBeaJne2NNUZT1Oi9PWWH5VQ4HeAJoDLR9wT2x0JHgXvzFU02?= =?us-ascii?Q?RFpcy8M5T7U5AfawQu4QlHJYFb6FmFzF+SThYONAY88i+O0LlToS4w3BEluu?= =?us-ascii?Q?O/GwofybJ83rzw9vbxi5DBo0XNCAxJ/HY74fHCzjBbVtDcmhORvAIcl6lQqm?= =?us-ascii?Q?2jGIYa7CkPjmJ2JafjW+qxcXq3mK+J/mELE5ETgnhg9v/7RlGr1a9SNr85KM?= =?us-ascii?Q?m3XZmcU=3D?=
x-ms-exchange-transport-forked: True
arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PuZc2YtdW7CbnvWfyT7ihRZvSuCaPA/OhWa0rNXc8kEbRp3NuS2dQQHMKMcYfDUfFH+c3cjqkUoPEGla/juII4CM8ssXITCqmJ7vMi37v8oU2usVTTCDtsgirJjsgj3Vq4OU4+7ra/+R2NmL0z1wgRVCm3sd3ORQ3rfSoviQ0q9N2cgvORES3kUxs+LqLw7ZGg/trwgVm5jaEOAjrpU25EK/R5R0VR15EzPTuWoyoJIYY7/9buu4iS6NT5g3c9Xw1HSetAGKDTDImC3N92cKQGbd7UejLjrCEJnNbg88Ql+cKJ0bgY0u22kvzRFzd/UhMMKebFIvP6Mh8hIW7pEP3Q==
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=FbSOZFo9QuK48PVtXsLzD1v/uEpK7YNRfA8M3WV3TCA=; b=l7iJYND7NmjLIcstTKMqundNRzd9ysUOLKvsvUAMKKNyiZ7obq1I2QYTj6NXu+FiQkV6OrhmOysnGsBvL0hTs4gXp2jaF3XF+ezHYEzqBcu0e2dfhhJWeOZ3NEl/chcYuzNQzBvLianx/0nK2OBrbEeRKEGitYulYyYl1odLmhnoKD8Q07S0NdRxDlR3yeQTLO8TQvuFIhB/2RMcGd7L2LHBpPI+vvJ3fbSQIU/olES+bf06899E54rmhLPm4Uv0UqnxDgH3mmJSwatYLPSUrRlQ9LkuIs9gdhhdPufRn6i3qahdGCoiK4z7yMnwHRrhcItWpKyCZcmRZ7lqO+6RMQ==
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: c959ef3e-042d-46cb-3817-08d92f57314b
x-ms-exchange-crosstenant-originalarrivaltime: 14 Jun 2021 17:09:38.4049 (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: RMMNF2r2Izf0zDvhMxI1zgRio04BYRm8QrCt+/IyVfH1B/2W9J0PQXTey+c9zHtkHJ/2+VOqf1S+1T+7eDJ1ir7GF4eRjixIuc42WocqqYQ=
x-ms-exchange-transport-crosstenantheadersstamped: BL0PR11MB2913
x-originatororg: comcast.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward AAETWO
X-Proofpoint-ORIG-GUID: 2gOPxdK9bYABVKhGAhwFU5x7Wyes8e0o
X-Proofpoint-GUID: 2gOPxdK9bYABVKhGAhwFU5x7Wyes8e0o
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.761 definitions=2021-06-14_10:2021-06-14, 2021-06-14 signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VcY1o01uPm3Aj4g2KZLtpKmLB0k>
Subject: [dmarc-ietf] Sender-supplied decision matrix for passing DMARC
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2021 17:09:52 -0000

Hello,

I was talking to some folks about DMARC, and a question came as to suggest =
as the domain holder that your messages should always pass DKIM.  Effective=
ly, the asker wants to say "I intend to deploy SPF and DKIM, but I will *al=
ways* sign my messages with DKIM."  So the obvious answer may be "Just only=
 use DKIM", but I'm not sure that completely answers the question.  While d=
iscussing with someone else, "Tell me when DKIM fails, but SPF is fully ali=
gned".  There was recently an incident at a provider where they were allowi=
ng any sender to send as any domain (and I'm aware that's not specifically =
a DMARC issue).  We all know brands that have just dumped in a pile of "inc=
lude" statements without fully understanding the implications.  In this cas=
e, other users could send as other domains, but perhaps they would not have=
 been DKIM signed.  Should there be a method by which a domain holder can s=
ay "We want all message to have both, or be treated as a failure", or "We'l=
l provide both, but DKIM is a must"?

>From a receiver side, it makes evaluation more complex.  From a sender side=
, it gives them more control over what is considered pass/fail.

How does this look in practice?  Maybe "v=3DDMARC1;p=3Dquarantine;rua=3D...=
;pm=3Ddkim:must,spf:should;"
(pm=3DPolicy Matrix)

Does this make everyone cringe, or perhaps worth a larger discussion?

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


From nobody Mon Jun 14 10:41:30 2021
Return-Path: <zachary.aab@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 55E803A2C07 for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 10:41:28 -0700 (PDT)
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 YXX4K8lAg2hd for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 10:41:23 -0700 (PDT)
Received: from mail-oo1-xc31.google.com (mail-oo1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 203E23A2C08 for <dmarc@ietf.org>; Mon, 14 Jun 2021 10:41:22 -0700 (PDT)
Received: by mail-oo1-xc31.google.com with SMTP id j17-20020a0568200231b029024900620310so2845971oob.7 for <dmarc@ietf.org>; Mon, 14 Jun 2021 10:41:22 -0700 (PDT)
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=eOWDjMkzL+EK1vBKc4sSx42rUgHsIJJ3vzHnHhlcM0I=; b=sDY/f1fB5/tRzCuW9DMH9QGJwhkaKOXC+s6nCffukG43KbQbN19YQstxnXZTQvTTy2 ZVSdBSkr5mNWsIWh/F08vtG5KGV7FV35lkvm9IxG+SjhSgqoWWvEhL9XzPhNAZYKkUFa OQ+Xos7fUh78HMVsDX2GROKX9/5MfVZLgUi9F1pehST6upnSbrV11IeWcQtNJdG7VMqt ZVX68JCF0404GtHwTcO4ZipDz4DMk3paY4VXxe6CldStpMU5ZvT3l7Zs8XXAC0NUVM0f iK8R/ID9dHuNn7zbpiQR+YJXHxnAhvi/nviItQ+E/RXO38hSHaxidNLzabO6/61YxYHF 01dw==
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=eOWDjMkzL+EK1vBKc4sSx42rUgHsIJJ3vzHnHhlcM0I=; b=k2y28+ZtLD5BGtHgTr/SZf6g2Yogu+cGMlBrTSYp4GucPV5L1Lv3pOFg33LD+2Tx3R +LVq0jyUn1mZDYLfWOxOtQFlOEkEzmn+JYAGohNKTU3qyYlsTtaIbUnqU1AwebFptyzC sNPJ9PALEzMSM7RmPyjBVhvb1uJW/Hf/XZQJnpyqCLG2Q5zRCeHJSV+EnSFXfePVnpV3 BktWLwJR5U35SaejHSovQE0EPOAt3u9Tmbr5ljC+Nt5MmXJCf9pdctxc8nxYL2TtGQRR sPnEw6THK0V6IteyHnVvKCJQvFaMio8dh6TedenIs9BRZTRPK4Ku326nCyQcF7KjFUo+ 6ZbQ==
X-Gm-Message-State: AOAM530AWqtJba0PQmdjhBW7ZvNJQD/hLbMtt+yXs2yPql9m6wgtXF2q DrUFGh/Zg4T/m1y6GMnCtE7cqEm3OIFOMKwti6XxdINoj/nd9A==
X-Google-Smtp-Source: ABdhPJxx4+RXSWGL3nguFfha8ydc4fIsutU0onxj8TVcous1CgRv/VM+WRPm4XSGlf/cMWpugk958nbxHlPmeRHDZNc=
X-Received: by 2002:a4a:dd8d:: with SMTP id h13mr13887036oov.84.1623692480660;  Mon, 14 Jun 2021 10:41:20 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Zachary Aab <zachary.aab@gmail.com>
Date: Mon, 14 Jun 2021 13:41:09 -0400
Message-ID: <CAD8zhRdWwZ4tHKNbZvuFHy1seLJ0VqQ7+r-5SowJJ7Hqssm9xQ@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="00000000000088c6f305c4bd5dd9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Y50xZyKSeuOmEIWSXSVLY6J0x9I>
Subject: Re: [dmarc-ietf] Sender-supplied decision matrix for passing DMARC
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2021 17:41:28 -0000

--00000000000088c6f305c4bd5dd9
Content-Type: text/plain; charset="UTF-8"

This rings to me like something that would look like the simple/relaxed
alignment option currently in DMARC.  "Require aligned DKIM" being
something along the lines of "rdkim=y; rspf=n;" with the
not-included/default value being "n."
If you agree that adding it is simple enough, the real question is what
value does this really add to DMARC and/or will it improve DMARC adoption?
Personally, I think it would be generally welcomed among senders who like
really granular control over their authentication or who don't fully
understand DMARC's "defaults" (for example, senders who use "p=reject;
pct=100;").

On Mon, Jun 14, 2021 at 1:10 PM Brotman, Alex <Alex_Brotman=
40comcast.com@dmarc.ietf.org> wrote:

> Hello,
>
> I was talking to some folks about DMARC, and a question came as to suggest
> as the domain holder that your messages should always pass DKIM.
> Effectively, the asker wants to say "I intend to deploy SPF and DKIM, but I
> will *always* sign my messages with DKIM."  So the obvious answer may be
> "Just only use DKIM", but I'm not sure that completely answers the
> question.  While discussing with someone else, "Tell me when DKIM fails,
> but SPF is fully aligned".  There was recently an incident at a provider
> where they were allowing any sender to send as any domain (and I'm aware
> that's not specifically a DMARC issue).  We all know brands that have just
> dumped in a pile of "include" statements without fully understanding the
> implications.  In this case, other users could send as other domains, but
> perhaps they would not have been DKIM signed.  Should there be a method by
> which a domain holder can say "We want all message to have both, or be
> treated as a failure", or "We'll provide both, but DKI
>  M is a must"?
>
> >From a receiver side, it makes evaluation more complex.  From a sender
> side, it gives them more control over what is considered pass/fail.
>
> How does this look in practice?  Maybe
> "v=DMARC1;p=quarantine;rua=...;pm=dkim:must,spf:should;"
> (pm=Policy Matrix)
>
> Does this make everyone cringe, or perhaps worth a larger discussion?
>
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr">This rings to me like something that would look like the s=
imple/relaxed alignment option currently in DMARC.=C2=A0 &quot;Require alig=
ned DKIM&quot; being something along the lines of &quot;rdkim=3Dy; rspf=3Dn=
;&quot; with the not-included/default value being &quot;n.&quot;<div>If you=
 agree that adding it is simple enough, the real question is what value doe=
s this really add to DMARC and/or will it improve DMARC adoption?<div>Perso=
nally, I think it would be generally welcomed among senders who like really=
 granular control over their authentication or who don&#39;t fully understa=
nd DMARC&#39;s &quot;defaults&quot; (for example, senders who use &quot;p=
=3Dreject; pct=3D100;&quot;).</div></div></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jun 14, 2021 at 1:10 PM Br=
otman, Alex &lt;Alex_Brotman=3D<a href=3D"mailto:40comcast.com@dmarc.ietf.o=
rg">40comcast.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">Hello,<br>
<br>
I was talking to some folks about DMARC, and a question came as to suggest =
as the domain holder that your messages should always pass DKIM.=C2=A0 Effe=
ctively, the asker wants to say &quot;I intend to deploy SPF and DKIM, but =
I will *always* sign my messages with DKIM.&quot;=C2=A0 So the obvious answ=
er may be &quot;Just only use DKIM&quot;, but I&#39;m not sure that complet=
ely answers the question.=C2=A0 While discussing with someone else, &quot;T=
ell me when DKIM fails, but SPF is fully aligned&quot;.=C2=A0 There was rec=
ently an incident at a provider where they were allowing any sender to send=
 as any domain (and I&#39;m aware that&#39;s not specifically a DMARC issue=
).=C2=A0 We all know brands that have just dumped in a pile of &quot;includ=
e&quot; statements without fully understanding the implications.=C2=A0 In t=
his case, other users could send as other domains, but perhaps they would n=
ot have been DKIM signed.=C2=A0 Should there be a method by which a domain =
holder can say &quot;We want all message to have both, or be treated as a f=
ailure&quot;, or &quot;We&#39;ll provide both, but DKI<br>
=C2=A0M is a must&quot;?<br>
<br>
&gt;From a receiver side, it makes evaluation more complex.=C2=A0 From a se=
nder side, it gives them more control over what is considered pass/fail.<br=
>
<br>
How does this look in practice?=C2=A0 Maybe &quot;v=3DDMARC1;p=3Dquarantine=
;rua=3D...;pm=3Ddkim:must,spf:should;&quot;<br>
(pm=3DPolicy Matrix)<br>
<br>
Does this make everyone cringe, or perhaps worth a larger discussion?<br>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--00000000000088c6f305c4bd5dd9--


From nobody Mon Jun 14 10:45: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 5B68E3A2C26 for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 10:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vV8DOcfKi_Yp for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 10:45:34 -0700 (PDT)
Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4932D3A2C23 for <dmarc@ietf.org>; Mon, 14 Jun 2021 10:45:34 -0700 (PDT)
Received: by mail-vk1-xa2e.google.com with SMTP id 184so4335295vkz.13 for <dmarc@ietf.org>; Mon, 14 Jun 2021 10:45:34 -0700 (PDT)
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=KzvY503In23kSDrl+9Amv/sjB8SL8z5pHmpfpguPevk=; b=ZLHOG6LFD7d25moEVpIHeawBxNMcmBYlPUZLUrcl8JC3jym1UMsk8tyrzI19tlY+Ue NhvlWg8eK0VbOWzsgyOEPqeRF35UH/hwbXPUTcNWHKXqsCwHLQdDVpJAAPhhfdKR9bmX YKTw12rzf1ZbxYM6O8cOrnnFl0lz6vzR2R9TD4dby841fgMeaUsWs/3eAGNIeB+XHDAa JG81OaE1eZ3aLzq1pmJoEckgp3twGKdi1GaIQGIeBe8v6Hx36niaCb8Cf89J/R7LEUYL 1zXEKHb2HST5qvyIPRyFh2Jd9UH/IDsomAfbz8pNgxGtCsHh5zBDQsEW9JDirLgwwHnA kFyA==
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=KzvY503In23kSDrl+9Amv/sjB8SL8z5pHmpfpguPevk=; b=saxqBAdPnCpEEOWtFLyKa0fNUcLoO0BsYixOcxtHqlytkNpC/0bnuH4cvDTm8qaDxn kICdnvNCwLiCpR3AKcDu45OfVTKZTrimZQeqd0mAUH+qPZinX9arfsctce/K5qdm1uIl m7nX2v5SGZ2IIqHDgpTK/j7oCk78eItsMwChMCaPAEpFnUKapkIV8S/EgjPk4K+gIEYp GjSuqlV2UsQgEPR4AQsUZAmzlQC0sRPfXZfipU6AmDx9pmUlqaEM3zcsZkADp25J3RYy w0+2M7mbU5Rm05DiDWfxxJHo6BfyldjM0ykWSDVMvYN6VhpYNGIBnBL0MggYWn2qd6wH qQFA==
X-Gm-Message-State: AOAM531AnmFRk5jYUnQUItzQFqGbqyftQBTSeDhJTspvmq3dj8lIIY16 WbDEz/jBoBhhDrJGOPo2JAatLeJeAw3HvwbRF88Ttg==
X-Google-Smtp-Source: ABdhPJxshwufMT34X92Aw4wdu/sXFI3+dQ5QHHXYfg2+adtR2xmiCoAMf4WDKUWNeP7v3XCKRNfRaz0Rf8ZbY+veZy4=
X-Received: by 2002:a1f:2e86:: with SMTP id u128mr74673vku.22.1623692731847; Mon, 14 Jun 2021 10:45:31 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Seth Blank <seth@valimail.com>
Date: Mon, 14 Jun 2021 10:45:21 -0700
Message-ID: <CAOZAAfM4w2nNcDcdqXXtDf1_H7Ah1Py1gO0Yjm1byh3eKXzTUQ@mail.gmail.com>
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>,  "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000081a61905c4bd6ca2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Y317Xm8BwGSxZZ_N7dRKej0KoAk>
Subject: Re: [dmarc-ietf] Sender-supplied decision matrix for passing DMARC
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2021 17:45:40 -0000

--00000000000081a61905c4bd6ca2
Content-Type: text/plain; charset="UTF-8"

HUGE cringe ;-) DMARC has an explicit policy that either SPF or DKIM must
pass aligned. This proposal breaks that foundationally.

This is suggested quite frequently, but fails to understand just how few
senders of email actually send with DKIM. Most email is sent from services
that have a core business that's not in email, and when we're lucky, they
manage to publish an SPF record for their customers to use. Only large
volume sophisticated services tend to do DKIM.

A domain owner that requires everything that sends on its behalf to use
DKIM basically shoots itself in the foot, and makes most of the services
they'd need to use unavailable to themselves.

The correct answer is what you said: domain owners who want this should
only authenticate services using DKIM.

Seth


On Mon, Jun 14, 2021 at 10:10 AM Brotman, Alex <Alex_Brotman=
40comcast.com@dmarc.ietf.org> wrote:

> Hello,
>
> I was talking to some folks about DMARC, and a question came as to suggest
> as the domain holder that your messages should always pass DKIM.
> Effectively, the asker wants to say "I intend to deploy SPF and DKIM, but I
> will *always* sign my messages with DKIM."  So the obvious answer may be
> "Just only use DKIM", but I'm not sure that completely answers the
> question.  While discussing with someone else, "Tell me when DKIM fails,
> but SPF is fully aligned".  There was recently an incident at a provider
> where they were allowing any sender to send as any domain (and I'm aware
> that's not specifically a DMARC issue).  We all know brands that have just
> dumped in a pile of "include" statements without fully understanding the
> implications.  In this case, other users could send as other domains, but
> perhaps they would not have been DKIM signed.  Should there be a method by
> which a domain holder can say "We want all message to have both, or be
> treated as a failure", or "We'll provide both, but DKI
>  M is a must"?
>
> >From a receiver side, it makes evaluation more complex.  From a sender
> side, it gives them more control over what is considered pass/fail.
>
> How does this look in practice?  Maybe
> "v=DMARC1;p=quarantine;rua=...;pm=dkim:must,spf:should;"
> (pm=Policy Matrix)
>
> Does this make everyone cringe, or perhaps worth a larger discussion?
>
> --
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy
> Comcast
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Seth Blank* | VP, Product
*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.

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

<div dir=3D"ltr"><div>HUGE cringe ;-) DMARC has an explicit policy that eit=
her SPF or DKIM must pass aligned. This proposal breaks that foundationally=
.</div><div></div><div><br></div><div>This is suggested quite frequently, b=
ut fails to understand just how few senders of email actually send with DKI=
M. Most email is sent from services that have a core business that&#39;s no=
t in email, and when we&#39;re lucky, they manage to publish an SPF record =
for their customers to use. Only large volume sophisticated services tend t=
o do DKIM.</div><div><br></div><div>A domain owner that requires everything=
 that sends on its behalf to use DKIM basically shoots itself in the foot, =
and makes most of the services they&#39;d need to use unavailable to themse=
lves.</div><div><br></div><div>The correct answer is what you said: domain =
owners who want this should only authenticate services using DKIM.</div><di=
v><br></div><div>Seth</div><div><br></div></div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jun 14, 2021 at 10:10 AM =
Brotman, Alex &lt;Alex_Brotman=3D<a href=3D"mailto:40comcast.com@dmarc.ietf=
.org">40comcast.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">Hello,<br>
<br>
I was talking to some folks about DMARC, and a question came as to suggest =
as the domain holder that your messages should always pass DKIM.=C2=A0 Effe=
ctively, the asker wants to say &quot;I intend to deploy SPF and DKIM, but =
I will *always* sign my messages with DKIM.&quot;=C2=A0 So the obvious answ=
er may be &quot;Just only use DKIM&quot;, but I&#39;m not sure that complet=
ely answers the question.=C2=A0 While discussing with someone else, &quot;T=
ell me when DKIM fails, but SPF is fully aligned&quot;.=C2=A0 There was rec=
ently an incident at a provider where they were allowing any sender to send=
 as any domain (and I&#39;m aware that&#39;s not specifically a DMARC issue=
).=C2=A0 We all know brands that have just dumped in a pile of &quot;includ=
e&quot; statements without fully understanding the implications.=C2=A0 In t=
his case, other users could send as other domains, but perhaps they would n=
ot have been DKIM signed.=C2=A0 Should there be a method by which a domain =
holder can say &quot;We want all message to have both, or be treated as a f=
ailure&quot;, or &quot;We&#39;ll provide both, but DKI<br>
=C2=A0M is a must&quot;?<br>
<br>
&gt;From a receiver side, it makes evaluation more complex.=C2=A0 From a se=
nder side, it gives them more control over what is considered pass/fail.<br=
>
<br>
How does this look in practice?=C2=A0 Maybe &quot;v=3DDMARC1;p=3Dquarantine=
;rua=3D...;pm=3Ddkim:must,spf:should;&quot;<br>
(pm=3DPolicy Matrix)<br>
<br>
Does this make everyone cringe, or perhaps worth a larger discussion?<br>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Seth Blank</b></span><span style=3D"vertical-align:baselin=
e;white-space:pre-wrap;font-size:small;font-family:Arial"> | VP, Product</s=
pan></div><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-=
size:small;font-family:Arial"><div style=3D"text-align:left"><span style=3D=
"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:bas=
eline"> <a href=3D"mailto:seth@valimail.com" target=3D"_blank">seth@valimai=
l.com</a></span></div></span><span><div><span><b>p:</b></span><span> 415.27=
3.8818 </span><span></span></div><div style=3D"text-align:left"><img style=
=3D"width: 175px; height: 43px;" src=3D"https://hosted-packages.s3-us-west-=
1.amazonaws.com/Valimail+Logo.png"></div></span><p dir=3D"ltr" style=3D"bac=
kground-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;margin-botto=
m:0pt"><font face=3D"Arial" color=3D"#666666"><span style=3D"font-size:10.6=
667px;white-space:pre-wrap">This email and all data transmitted with it con=
tains confidential and/or proprietary information intended solely for the u=
se of individual(s) authorized to receive it. If you are not an intended an=
d authorized recipient you are hereby notified of any use, disclosure, copy=
ing or distribution of the information included in this transmission is pro=
hibited and may be unlawful. Please immediately notify the sender by replyi=
ng to this email and then delete it from your system.</span></font></p></sp=
an></div>

--00000000000081a61905c4bd6ca2--


From tobias.herkula@1und1.de  Mon Jun 14 10:53:23 2021
Return-Path: <tobias.herkula@1und1.de>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E98733A2C8B; Mon, 14 Jun 2021 10:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level: 
X-Spam-Status: No, score=-2.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, 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=1und1.de
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59y4K4MrNp5g; Mon, 14 Jun 2021 10:53:12 -0700 (PDT)
Received: from moint.1and1.com (moint.1and1.com [212.227.15.7]) (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 605323A2C7D; Mon, 14 Jun 2021 10:53:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=1und1.de; s=corp1; h=MIME-Version:Message-ID:Date:Subject:To:From:cc:sender:reply-to; bh=NjbcBCMAenW5JJEZ+JsOZOCHWPxyhMHWF1V7zS2sEVk=; b=CUoQ/Q4EnuUKf1c1muttn9Lm7 f6qBfZ1cVKK7tbfqOHbjScVc2XcvpVB2wqQ4xDNH2+jBEyQ+9kYiikxwQQHg1xKT3UTk4ZPO/5grM 0ZirhLhsJrzNzXToui9U8LbHXqkn1l35+2tsRtIjQtrQoU8Zo6971aZNkMQqRtVStjwUvlqCdJN1b 4ewaQeu+RJoQmnQOxOOAp6udmfAhpTiiJaSmDSi7DSByq9IHGR/UTN28ZuNY8sllkCGOjIlm6Yj/O xOKfPVmmZE8u3mmOKfeWspi6Gw5SReKJScDMbqRuTM+wt5JcjgCMlkhGoNLZfCQNNQKkTuhzUGMRa uCjYRPzFg==;
Received: from [10.96.4.11] (helo=KAPPEX002.united.domain) by mrint.1and1.com with esmtps (TLS1.2:ECDHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.92) (envelope-from <tobias.herkula@1und1.de>) id 1lsqlq-00052o-HS; Mon, 14 Jun 2021 19:53:10 +0200
Received: from KAPPEX008.united.domain (10.96.4.17) by KAPPEX002.united.domain (10.96.4.11) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Mon, 14 Jun 2021 19:53:09 +0200
Received: from KAPPEX008.united.domain ([fe80::8d8b:cacd:98e8:ec69]) by KAPPEX008.united.domain ([fe80::8d8b:cacd:98e8:ec69%13]) with mapi id 15.00.1497.018; Mon, 14 Jun 2021 19:53:09 +0200
From: Tobias Herkula <tobias.herkula@1und1.de>
To: Seth Blank <seth=40valimail.com@dmarc.ietf.org>, "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>, "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Sender-supplied decision matrix for passing DMARC
Thread-Index: AddhPDwbCzQ9bLtKT5O2BtOM1Kt/J///8BiA///dPFA=
Date: Mon, 14 Jun 2021 17:53:08 +0000
Message-ID: <caa45e567fb844dd8c46a8ccbf4077d6@KAPPEX008.united.domain>
References: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@MN2PR11MB4351.namprd11.prod.outlook.com> <CAOZAAfM4w2nNcDcdqXXtDf1_H7Ah1Py1gO0Yjm1byh3eKXzTUQ@mail.gmail.com>
In-Reply-To: <CAOZAAfM4w2nNcDcdqXXtDf1_H7Ah1Py1gO0Yjm1byh3eKXzTUQ@mail.gmail.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.96.5.20]
Content-Type: multipart/alternative; boundary="_000_caa45e567fb844dd8c46a8ccbf4077d6KAPPEX008uniteddomain_"
MIME-Version: 1.0
X-Virus-Scanned: ClamAV@mvs-ha-bs
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WUp2bmCz-ZqzBArLRGyReh8Bgqs>
Subject: Re: [dmarc-ietf] Sender-supplied decision matrix for passing DMARC
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2021 17:55:03 -0000

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

VGhpcyByaXNrcyBzZW5kYWJpbGl0eSB3aXRoIHRoZSBmYWN0IHRoYXQgdGhlcmUgYXJlIGEgbG9m
IG9mIHJlY2VpdmVycyB0aGF0IHJlcXVpcmUgU1BGLVJScy4gU28gbm90IHByb3ZpZGluZyBTUEYt
UlJzIGFsc28gZmFpbHMgd2l0aCBzdWNoIGFuIHJlcXVpcmVtZW50LiBCZXNpZGVzIHRoYXQgZG9l
cyBTUEYgbm90IGhlbHAgd2l0aCBhbnkga2luZCBvZiA1MzIyLkZyb20gc3Bvb2ZpbmcsIGJ1dCB0
aGlzIGlzdCBoZSBtb3N0IGltcG9ydGFudCBpZGVudGlmaWVyIGZvciBhbiBlbmR1c2VyLg0KDQov
IFRvYmlhcyBIZXJrdWxhDQoNClNlbmlvciBQcm9kdWN0IE93bmVyIE1haWwgU2VjdXJpdHkNCk1h
aWwgQXBwbGljYXRpb24gU2VjdXJpdHkNCg0KMSYxIE1haWwgJiBNZWRpYSBHbWJIIHwgTWl0dGUg
fCAxMDExNSBCZXJsaW4gfCBEZXV0c2NobGFuZA0KRS1NYWlsOiB0b2JpYXMuaGVya3VsYUAxdW5k
MS5kZTxtYWlsdG86dG9iaWFzLmhlcmt1bGFAMXVuZDEuZGU+IHwgV2ViOiB3d3cuMXVuZDEuZGU8
aHR0cDovL3d3dy4xdW5kMS5kZT4NCg0KSGF1cHRzaXR6IE1vbnRhYmF1ciwgQW10c2dlcmljaHQg
TW9udGFiYXVyLCBIUkIgNzY2Ng0KDQpHZXNjaMOkZnRzZsO8aHJlcjogQWxleGFuZGVyIENoYXJs
ZXMsIFRob21hcyBMdWR3aWcsIEphbiBPZXRqZW4sIFNhbmRyYSBWb2xsbWVyDQoNCk1lbWJlciBv
ZiBVbml0ZWQgSW50ZXJuZXQNCg0KRGllc2UgRS1NYWlsIGthbm4gdmVydHJhdWxpY2hlIHVuZC9v
ZGVyIGdlc2V0emxpY2ggZ2VzY2jDvHR6dGUgSW5mb3JtYXRpb25lbiBlbnRoYWx0ZW4uIFdlbm4g
U2llIG5pY2h0IGRlciBiZXN0aW1tdW5nc2dlbcOkw59lIEFkcmVzc2F0IHNpbmQgb2RlciBkaWVz
ZSBFLU1haWwgaXJydMO8bWxpY2ggZXJoYWx0ZW4gaGFiZW4sIHVudGVycmljaHRlbiBTaWUgYml0
dGUgZGVuIEFic2VuZGVyIHVuZCB2ZXJuaWNodGVuIFNpZSBkaWVzZSBFLU1haWwuIEFuZGVyZW4g
YWxzIGRlbSBiZXN0aW1tdW5nc2dlbcOkw59lbiBBZHJlc3NhdGVuIGlzdCB1bnRlcnNhZ3QsIGRp
ZXNlIEUtTWFpbCB6dSBzcGVpY2hlcm4sIHdlaXRlcnp1bGVpdGVuIG9kZXIgaWhyZW4gSW5oYWx0
IGF1ZiB3ZWxjaGUgV2Vpc2UgYXVjaCBpbW1lciB6dSB2ZXJ3ZW5kZW4uDQoNClRoaXMgZS1tYWls
IG1heSBjb250YWluIGNvbmZpZGVudGlhbCBhbmQvb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbi4g
SWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCBvZiB0aGlzIGUtbWFpbCwgeW91
IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhhdCBzYXZpbmcsIGRpc3RyaWJ1dGlvbiBvciB1c2Ugb2Yg
dGhlIGNvbnRlbnQgb2YgdGhpcyBlLW1haWwgaW4gYW55IHdheSBpcyBwcm9oaWJpdGVkLiBJZiB5
b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGUtbWFpbCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUg
c2VuZGVyIGFuZCBkZWxldGUgdGhlIGUtbWFpbC4NCg0KDQoNClZvbjogZG1hcmMgPGRtYXJjLWJv
dW5jZXNAaWV0Zi5vcmc+IEltIEF1ZnRyYWcgdm9uIFNldGggQmxhbmsNCkdlc2VuZGV0OiBNb250
YWcsIDE0LiBKdW5pIDIwMjEgMTk6NDUNCkFuOiBCcm90bWFuLCBBbGV4IDxBbGV4X0Jyb3RtYW49
NDBjb21jYXN0LmNvbUBkbWFyYy5pZXRmLm9yZz47IGRtYXJjQGlldGYub3JnDQpCZXRyZWZmOiBS
ZTogW2RtYXJjLWlldGZdIFNlbmRlci1zdXBwbGllZCBkZWNpc2lvbiBtYXRyaXggZm9yIHBhc3Np
bmcgRE1BUkMNCg0KSFVHRSBjcmluZ2UgOy0pIERNQVJDIGhhcyBhbiBleHBsaWNpdCBwb2xpY3kg
dGhhdCBlaXRoZXIgU1BGIG9yIERLSU0gbXVzdCBwYXNzIGFsaWduZWQuIFRoaXMgcHJvcG9zYWwg
YnJlYWtzIHRoYXQgZm91bmRhdGlvbmFsbHkuDQoNClRoaXMgaXMgc3VnZ2VzdGVkIHF1aXRlIGZy
ZXF1ZW50bHksIGJ1dCBmYWlscyB0byB1bmRlcnN0YW5kIGp1c3QgaG93IGZldyBzZW5kZXJzIG9m
IGVtYWlsIGFjdHVhbGx5IHNlbmQgd2l0aCBES0lNLiBNb3N0IGVtYWlsIGlzIHNlbnQgZnJvbSBz
ZXJ2aWNlcyB0aGF0IGhhdmUgYSBjb3JlIGJ1c2luZXNzIHRoYXQncyBub3QgaW4gZW1haWwsIGFu
ZCB3aGVuIHdlJ3JlIGx1Y2t5LCB0aGV5IG1hbmFnZSB0byBwdWJsaXNoIGFuIFNQRiByZWNvcmQg
Zm9yIHRoZWlyIGN1c3RvbWVycyB0byB1c2UuIE9ubHkgbGFyZ2Ugdm9sdW1lIHNvcGhpc3RpY2F0
ZWQgc2VydmljZXMgdGVuZCB0byBkbyBES0lNLg0KDQpBIGRvbWFpbiBvd25lciB0aGF0IHJlcXVp
cmVzIGV2ZXJ5dGhpbmcgdGhhdCBzZW5kcyBvbiBpdHMgYmVoYWxmIHRvIHVzZSBES0lNIGJhc2lj
YWxseSBzaG9vdHMgaXRzZWxmIGluIHRoZSBmb290LCBhbmQgbWFrZXMgbW9zdCBvZiB0aGUgc2Vy
dmljZXMgdGhleSdkIG5lZWQgdG8gdXNlIHVuYXZhaWxhYmxlIHRvIHRoZW1zZWx2ZXMuDQoNClRo
ZSBjb3JyZWN0IGFuc3dlciBpcyB3aGF0IHlvdSBzYWlkOiBkb21haW4gb3duZXJzIHdobyB3YW50
IHRoaXMgc2hvdWxkIG9ubHkgYXV0aGVudGljYXRlIHNlcnZpY2VzIHVzaW5nIERLSU0uDQoNClNl
dGgNCg0KDQpPbiBNb24sIEp1biAxNCwgMjAyMSBhdCAxMDoxMCBBTSBCcm90bWFuLCBBbGV4IDxB
bGV4X0Jyb3RtYW49NDBjb21jYXN0LmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86NDBjb21jYXN0
LmNvbUBkbWFyYy5pZXRmLm9yZz4+IHdyb3RlOg0KSGVsbG8sDQoNCkkgd2FzIHRhbGtpbmcgdG8g
c29tZSBmb2xrcyBhYm91dCBETUFSQywgYW5kIGEgcXVlc3Rpb24gY2FtZSBhcyB0byBzdWdnZXN0
IGFzIHRoZSBkb21haW4gaG9sZGVyIHRoYXQgeW91ciBtZXNzYWdlcyBzaG91bGQgYWx3YXlzIHBh
c3MgREtJTS4gIEVmZmVjdGl2ZWx5LCB0aGUgYXNrZXIgd2FudHMgdG8gc2F5ICJJIGludGVuZCB0
byBkZXBsb3kgU1BGIGFuZCBES0lNLCBidXQgSSB3aWxsICphbHdheXMqIHNpZ24gbXkgbWVzc2Fn
ZXMgd2l0aCBES0lNLiIgIFNvIHRoZSBvYnZpb3VzIGFuc3dlciBtYXkgYmUgIkp1c3Qgb25seSB1
c2UgREtJTSIsIGJ1dCBJJ20gbm90IHN1cmUgdGhhdCBjb21wbGV0ZWx5IGFuc3dlcnMgdGhlIHF1
ZXN0aW9uLiAgV2hpbGUgZGlzY3Vzc2luZyB3aXRoIHNvbWVvbmUgZWxzZSwgIlRlbGwgbWUgd2hl
biBES0lNIGZhaWxzLCBidXQgU1BGIGlzIGZ1bGx5IGFsaWduZWQiLiAgVGhlcmUgd2FzIHJlY2Vu
dGx5IGFuIGluY2lkZW50IGF0IGEgcHJvdmlkZXIgd2hlcmUgdGhleSB3ZXJlIGFsbG93aW5nIGFu
eSBzZW5kZXIgdG8gc2VuZCBhcyBhbnkgZG9tYWluIChhbmQgSSdtIGF3YXJlIHRoYXQncyBub3Qg
c3BlY2lmaWNhbGx5IGEgRE1BUkMgaXNzdWUpLiAgV2UgYWxsIGtub3cgYnJhbmRzIHRoYXQgaGF2
ZSBqdXN0IGR1bXBlZCBpbiBhIHBpbGUgb2YgImluY2x1ZGUiIHN0YXRlbWVudHMgd2l0aG91dCBm
dWxseSB1bmRlcnN0YW5kaW5nIHRoZSBpbXBsaWNhdGlvbnMuICBJbiB0aGlzIGNhc2UsIG90aGVy
IHVzZXJzIGNvdWxkIHNlbmQgYXMgb3RoZXIgZG9tYWlucywgYnV0IHBlcmhhcHMgdGhleSB3b3Vs
ZCBub3QgaGF2ZSBiZWVuIERLSU0gc2lnbmVkLiAgU2hvdWxkIHRoZXJlIGJlIGEgbWV0aG9kIGJ5
IHdoaWNoIGEgZG9tYWluIGhvbGRlciBjYW4gc2F5ICJXZSB3YW50IGFsbCBtZXNzYWdlIHRvIGhh
dmUgYm90aCwgb3IgYmUgdHJlYXRlZCBhcyBhIGZhaWx1cmUiLCBvciAiV2UnbGwgcHJvdmlkZSBi
b3RoLCBidXQgREtJDQogTSBpcyBhIG11c3QiPw0KDQo+RnJvbSBhIHJlY2VpdmVyIHNpZGUsIGl0
IG1ha2VzIGV2YWx1YXRpb24gbW9yZSBjb21wbGV4LiAgRnJvbSBhIHNlbmRlciBzaWRlLCBpdCBn
aXZlcyB0aGVtIG1vcmUgY29udHJvbCBvdmVyIHdoYXQgaXMgY29uc2lkZXJlZCBwYXNzL2ZhaWwu
DQoNCkhvdyBkb2VzIHRoaXMgbG9vayBpbiBwcmFjdGljZT8gIE1heWJlICJ2PURNQVJDMTtwPXF1
YXJhbnRpbmU7cnVhPS4uLjtwbT1ka2ltOm11c3Qsc3BmOnNob3VsZDsiDQoocG09UG9saWN5IE1h
dHJpeCkNCg0KRG9lcyB0aGlzIG1ha2UgZXZlcnlvbmUgY3JpbmdlLCBvciBwZXJoYXBzIHdvcnRo
IGEgbGFyZ2VyIGRpc2N1c3Npb24/DQoNCi0tDQpBbGV4IEJyb3RtYW4NClNyLiBFbmdpbmVlciwg
QW50aS1BYnVzZSAmIE1lc3NhZ2luZyBQb2xpY3kNCkNvbWNhc3QNCg0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCmRtYXJjIG1haWxpbmcgbGlzdA0KZG1h
cmNAaWV0Zi5vcmc8bWFpbHRvOmRtYXJjQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9kbWFyYw0KDQoNCi0tDQpTZXRoIEJsYW5rIHwgVlAsIFByb2R1Y3QN
CmU6IHNldGhAdmFsaW1haWwuY29tPG1haWx0bzpzZXRoQHZhbGltYWlsLmNvbT4NCnA6IDQxNS4y
NzMuODgxOA0KW2h0dHBzOi8vaG9zdGVkLXBhY2thZ2VzLnMzLXVzLXdlc3QtMS5hbWF6b25hd3Mu
Y29tL1ZhbGltYWlsK0xvZ28ucG5nXQ0KDQpUaGlzIGVtYWlsIGFuZCBhbGwgZGF0YSB0cmFuc21p
dHRlZCB3aXRoIGl0IGNvbnRhaW5zIGNvbmZpZGVudGlhbCBhbmQvb3IgcHJvcHJpZXRhcnkgaW5m
b3JtYXRpb24gaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIGluZGl2aWR1YWwocykgYXV0
aG9yaXplZCB0byByZWNlaXZlIGl0LiBJZiB5b3UgYXJlIG5vdCBhbiBpbnRlbmRlZCBhbmQgYXV0
aG9yaXplZCByZWNpcGllbnQgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQgb2YgYW55IHVzZSwgZGlz
Y2xvc3VyZSwgY29weWluZyBvciBkaXN0cmlidXRpb24gb2YgdGhlIGluZm9ybWF0aW9uIGluY2x1
ZGVkIGluIHRoaXMgdHJhbnNtaXNzaW9uIGlzIHByb2hpYml0ZWQgYW5kIG1heSBiZSB1bmxhd2Z1
bC4gUGxlYXNlIGltbWVkaWF0ZWx5IG5vdGlmeSB0aGUgc2VuZGVyIGJ5IHJlcGx5aW5nIHRvIHRo
aXMgZW1haWwgYW5kIHRoZW4gZGVsZXRlIGl0IGZyb20geW91ciBzeXN0ZW0uDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIg
MTUgNSAyIDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1h
bCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJZm9udC1zaXpl
OjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQphOmxpbmssIHNw
YW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0K
CXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FLU1haWxGb3JtYXR2b3JsYWdlMTkN
Cgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28t
c3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJp
ZjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7
c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcwLjg1cHQgNzAuODVwdCAyLjBjbSA3MC44
NXB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHls
ZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQi
IHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+
PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0
IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFk
Pg0KPGJvZHkgbGFuZz0iREUiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiIHN0eWxlPSJ3b3Jk
LXdyYXA6YnJlYWstd29yZCI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5UaGlz
IHJpc2tzIHNlbmRhYmlsaXR5IHdpdGggdGhlIGZhY3QgdGhhdCB0aGVyZSBhcmUgYSBsb2Ygb2Yg
cmVjZWl2ZXJzIHRoYXQgcmVxdWlyZSBTUEYtUlJzLiBTbyBub3QgcHJvdmlkaW5nIFNQRi1SUnMg
YWxzbyBmYWlscyB3aXRoIHN1Y2ggYW4gcmVxdWlyZW1lbnQuIEJlc2lkZXMgdGhhdCBkb2VzIFNQ
RiBub3QgaGVscCB3aXRoIGFueQ0KIGtpbmQgb2YgNTMyMi5Gcm9tIHNwb29maW5nLCBidXQgdGhp
cyBpc3QgaGUgbW9zdCBpbXBvcnRhbnQgaWRlbnRpZmllciBmb3IgYW4gZW5kdXNlci48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi8gVG9iaWFzIEhlcmt1bGE8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+U2VuaW9yIFByb2R1Y3QgT3duZXIgTWFpbCBTZWN1cml0eTxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TWFpbCBBcHBsaWNhdGlvbiBTZWN1cml0eTxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj4xJmFtcDsxIE1haWwgJmFtcDsgTWVkaWEgR21iSCB8IE1pdHRlIHwg
MTAxMTUgQmVybGluIHwgRGV1dHNjaGxhbmQ8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPkUtTWFpbDogPGEgaHJlZj0ibWFpbHRvOnRvYmlhcy5oZXJrdWxhQDF1bmQxLmRlIj48
c3BhbiBzdHlsZT0iY29sb3I6IzA1NjNDMSI+dG9iaWFzLmhlcmt1bGFAMXVuZDEuZGU8L3NwYW4+
PC9hPiB8IFdlYjoNCjxhIGhyZWY9Imh0dHA6Ly93d3cuMXVuZDEuZGUiPjxzcGFuIHN0eWxlPSJj
b2xvcjojMDU2M0MxIj53d3cuMXVuZDEuZGU8L3NwYW4+PC9hPjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5IYXVwdHNpdHogTW9udGFiYXVyLCBBbXRzZ2VyaWNodCBNb250YWJhdXIsIEhSQiA3NjY2
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkdlc2Now6RmdHNmw7xocmVyOiBBbGV4YW5kZXIgQ2hh
cmxlcywgVGhvbWFzIEx1ZHdpZywgSmFuIE9ldGplbiwgU2FuZHJhIFZvbGxtZXI8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+TWVtYmVyIG9mIFVuaXRlZCBJbnRlcm5ldDxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5EaWVzZSBFLU1haWwga2FubiB2ZXJ0cmF1bGljaGUgdW5kL29kZXIgZ2VzZXR6bGlj
aCBnZXNjaMO8dHp0ZSBJbmZvcm1hdGlvbmVuIGVudGhhbHRlbi4gV2VubiBTaWUgbmljaHQgZGVy
IGJlc3RpbW11bmdzZ2Vtw6TDn2UgQWRyZXNzYXQgc2luZCBvZGVyIGRpZXNlIEUtTWFpbCBpcnJ0
w7xtbGljaCBlcmhhbHRlbiBoYWJlbiwgdW50ZXJyaWNodGVuIFNpZSBiaXR0ZSBkZW4gQWJzZW5k
ZXIgdW5kIHZlcm5pY2h0ZW4gU2llDQogZGllc2UgRS1NYWlsLiBBbmRlcmVuIGFscyBkZW0gYmVz
dGltbXVuZ3NnZW3DpMOfZW4gQWRyZXNzYXRlbiBpc3QgdW50ZXJzYWd0LCBkaWVzZSBFLU1haWwg
enUgc3BlaWNoZXJuLCB3ZWl0ZXJ6dWxlaXRlbiBvZGVyIGlocmVuIEluaGFsdCBhdWYgd2VsY2hl
IFdlaXNlIGF1Y2ggaW1tZXIgenUgdmVyd2VuZGVuLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5U
aGlzIGUtbWFpbCBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgYW5kL29yIHByaXZpbGVnZWQgaW5m
b3JtYXRpb24uIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQgb2YgdGhpcyBl
LW1haWwsIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQgc2F2aW5nLCBkaXN0cmlidXRpb24g
b3IgdXNlIG9mIHRoZSBjb250ZW50IG9mIHRoaXMgZS1tYWlsIGluIGFueSB3YXkgaXMgcHJvaGli
aXRlZC4gSWYNCiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGUtbWFpbCBpbiBlcnJvciwgcGxlYXNl
IG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhlIGUtbWFpbC48bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtw
YWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPlZvbjo8
L2I+IGRtYXJjICZsdDtkbWFyYy1ib3VuY2VzQGlldGYub3JnJmd0OyA8Yj5JbSBBdWZ0cmFnIHZv
bg0KPC9iPlNldGggQmxhbms8YnI+DQo8Yj5HZXNlbmRldDo8L2I+IE1vbnRhZywgMTQuIEp1bmkg
MjAyMSAxOTo0NTxicj4NCjxiPkFuOjwvYj4gQnJvdG1hbiwgQWxleCAmbHQ7QWxleF9Ccm90bWFu
PTQwY29tY2FzdC5jb21AZG1hcmMuaWV0Zi5vcmcmZ3Q7OyBkbWFyY0BpZXRmLm9yZzxicj4NCjxi
PkJldHJlZmY6PC9iPiBSZTogW2RtYXJjLWlldGZdIFNlbmRlci1zdXBwbGllZCBkZWNpc2lvbiBt
YXRyaXggZm9yIHBhc3NpbmcgRE1BUkM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkhVR0UgY3JpbmdlIDstKSBETUFSQyBoYXMgYW4gZXhwbGljaXQgcG9saWN5
IHRoYXQgZWl0aGVyIFNQRiBvciBES0lNIG11c3QgcGFzcyBhbGlnbmVkLiBUaGlzIHByb3Bvc2Fs
IGJyZWFrcyB0aGF0IGZvdW5kYXRpb25hbGx5LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIGlzIHN1Z2dlc3RlZCBxdWl0ZSBmcmVxdWVu
dGx5LCBidXQgZmFpbHMgdG8gdW5kZXJzdGFuZCBqdXN0IGhvdyBmZXcgc2VuZGVycyBvZiBlbWFp
bCBhY3R1YWxseSBzZW5kIHdpdGggREtJTS4gTW9zdCBlbWFpbCBpcyBzZW50IGZyb20gc2Vydmlj
ZXMgdGhhdCBoYXZlIGEgY29yZSBidXNpbmVzcyB0aGF0J3Mgbm90IGluIGVtYWlsLCBhbmQgd2hl
biB3ZSdyZSBsdWNreSwgdGhleSBtYW5hZ2UgdG8gcHVibGlzaA0KIGFuIFNQRiByZWNvcmQgZm9y
IHRoZWlyIGN1c3RvbWVycyB0byB1c2UuIE9ubHkgbGFyZ2Ugdm9sdW1lIHNvcGhpc3RpY2F0ZWQg
c2VydmljZXMgdGVuZCB0byBkbyBES0lNLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BIGRvbWFpbiBvd25lciB0aGF0IHJlcXVpcmVzIGV2ZXJ5
dGhpbmcgdGhhdCBzZW5kcyBvbiBpdHMgYmVoYWxmIHRvIHVzZSBES0lNIGJhc2ljYWxseSBzaG9v
dHMgaXRzZWxmIGluIHRoZSBmb290LCBhbmQgbWFrZXMgbW9zdCBvZiB0aGUgc2VydmljZXMgdGhl
eSdkIG5lZWQgdG8gdXNlIHVuYXZhaWxhYmxlIHRvIHRoZW1zZWx2ZXMuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZSBjb3JyZWN0IGFuc3dl
ciBpcyB3aGF0IHlvdSBzYWlkOiBkb21haW4gb3duZXJzIHdobyB3YW50IHRoaXMgc2hvdWxkIG9u
bHkgYXV0aGVudGljYXRlIHNlcnZpY2VzIHVzaW5nIERLSU0uPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNldGg8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBNb24sIEp1biAxNCwgMjAy
MSBhdCAxMDoxMCBBTSBCcm90bWFuLCBBbGV4ICZsdDtBbGV4X0Jyb3RtYW49PGEgaHJlZj0ibWFp
bHRvOjQwY29tY2FzdC5jb21AZG1hcmMuaWV0Zi5vcmciPjQwY29tY2FzdC5jb21AZG1hcmMuaWV0
Zi5vcmc8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGlu
ZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhlbGxvLDxicj4NCjxicj4NCkkgd2FzIHRhbGtpbmcgdG8g
c29tZSBmb2xrcyBhYm91dCBETUFSQywgYW5kIGEgcXVlc3Rpb24gY2FtZSBhcyB0byBzdWdnZXN0
IGFzIHRoZSBkb21haW4gaG9sZGVyIHRoYXQgeW91ciBtZXNzYWdlcyBzaG91bGQgYWx3YXlzIHBh
c3MgREtJTS4mbmJzcDsgRWZmZWN0aXZlbHksIHRoZSBhc2tlciB3YW50cyB0byBzYXkgJnF1b3Q7
SSBpbnRlbmQgdG8gZGVwbG95IFNQRiBhbmQgREtJTSwgYnV0IEkgd2lsbCAqYWx3YXlzKiBzaWdu
IG15IG1lc3NhZ2VzIHdpdGggREtJTS4mcXVvdDsmbmJzcDsNCiBTbyB0aGUgb2J2aW91cyBhbnN3
ZXIgbWF5IGJlICZxdW90O0p1c3Qgb25seSB1c2UgREtJTSZxdW90OywgYnV0IEknbSBub3Qgc3Vy
ZSB0aGF0IGNvbXBsZXRlbHkgYW5zd2VycyB0aGUgcXVlc3Rpb24uJm5ic3A7IFdoaWxlIGRpc2N1
c3Npbmcgd2l0aCBzb21lb25lIGVsc2UsICZxdW90O1RlbGwgbWUgd2hlbiBES0lNIGZhaWxzLCBi
dXQgU1BGIGlzIGZ1bGx5IGFsaWduZWQmcXVvdDsuJm5ic3A7IFRoZXJlIHdhcyByZWNlbnRseSBh
biBpbmNpZGVudCBhdCBhIHByb3ZpZGVyIHdoZXJlIHRoZXkgd2VyZQ0KIGFsbG93aW5nIGFueSBz
ZW5kZXIgdG8gc2VuZCBhcyBhbnkgZG9tYWluIChhbmQgSSdtIGF3YXJlIHRoYXQncyBub3Qgc3Bl
Y2lmaWNhbGx5IGEgRE1BUkMgaXNzdWUpLiZuYnNwOyBXZSBhbGwga25vdyBicmFuZHMgdGhhdCBo
YXZlIGp1c3QgZHVtcGVkIGluIGEgcGlsZSBvZiAmcXVvdDtpbmNsdWRlJnF1b3Q7IHN0YXRlbWVu
dHMgd2l0aG91dCBmdWxseSB1bmRlcnN0YW5kaW5nIHRoZSBpbXBsaWNhdGlvbnMuJm5ic3A7IElu
IHRoaXMgY2FzZSwgb3RoZXIgdXNlcnMgY291bGQgc2VuZA0KIGFzIG90aGVyIGRvbWFpbnMsIGJ1
dCBwZXJoYXBzIHRoZXkgd291bGQgbm90IGhhdmUgYmVlbiBES0lNIHNpZ25lZC4mbmJzcDsgU2hv
dWxkIHRoZXJlIGJlIGEgbWV0aG9kIGJ5IHdoaWNoIGEgZG9tYWluIGhvbGRlciBjYW4gc2F5ICZx
dW90O1dlIHdhbnQgYWxsIG1lc3NhZ2UgdG8gaGF2ZSBib3RoLCBvciBiZSB0cmVhdGVkIGFzIGEg
ZmFpbHVyZSZxdW90Oywgb3IgJnF1b3Q7V2UnbGwgcHJvdmlkZSBib3RoLCBidXQgREtJPGJyPg0K
Jm5ic3A7TSBpcyBhIG11c3QmcXVvdDs/PGJyPg0KPGJyPg0KJmd0O0Zyb20gYSByZWNlaXZlciBz
aWRlLCBpdCBtYWtlcyBldmFsdWF0aW9uIG1vcmUgY29tcGxleC4mbmJzcDsgRnJvbSBhIHNlbmRl
ciBzaWRlLCBpdCBnaXZlcyB0aGVtIG1vcmUgY29udHJvbCBvdmVyIHdoYXQgaXMgY29uc2lkZXJl
ZCBwYXNzL2ZhaWwuPGJyPg0KPGJyPg0KSG93IGRvZXMgdGhpcyBsb29rIGluIHByYWN0aWNlPyZu
YnNwOyBNYXliZSAmcXVvdDt2PURNQVJDMTtwPXF1YXJhbnRpbmU7cnVhPS4uLjtwbT1ka2ltOm11
c3Qsc3BmOnNob3VsZDsmcXVvdDs8YnI+DQoocG09UG9saWN5IE1hdHJpeCk8YnI+DQo8YnI+DQpE
b2VzIHRoaXMgbWFrZSBldmVyeW9uZSBjcmluZ2UsIG9yIHBlcmhhcHMgd29ydGggYSBsYXJnZXIg
ZGlzY3Vzc2lvbj88YnI+DQo8YnI+DQotLTxicj4NCkFsZXggQnJvdG1hbjxicj4NClNyLiBFbmdp
bmVlciwgQW50aS1BYnVzZSAmYW1wOyBNZXNzYWdpbmcgUG9saWN5PGJyPg0KQ29tY2FzdDxicj4N
Cjxicj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJy
Pg0KZG1hcmMgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOmRtYXJjQGlldGYub3Jn
IiB0YXJnZXQ9Il9ibGFuayI+ZG1hcmNAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kbWFyYyIgdGFyZ2V0PSJfYmxhbmsiPmh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZG1hcmM8L2E+PG86cD48L286cD48
L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiciBjbGVh
cj0iYWxsIj4NCjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tLSA8bzpw
PjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
Ij5TZXRoIEJsYW5rPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj4gfCBWUCwgUHJvZHVjdDwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
PmU6PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj4NCjxhIGhyZWY9Im1haWx0bzpzZXRoQHZhbGlt
YWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnNldGhAdmFsaW1haWwuY29tPC9hPjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5wOjwvYj4gNDE1LjI3
My44ODE4IDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48aW1n
IGJvcmRlcj0iMCIgd2lkdGg9IjE3NSIgaGVpZ2h0PSI0MyIgc3R5bGU9IndpZHRoOjEuODIyOWlu
O2hlaWdodDouNDQ3OWluIiBpZD0iX3gwMDAwX2kxMDI1IiBzcmM9Imh0dHBzOi8vaG9zdGVkLXBh
Y2thZ2VzLnMzLXVzLXdlc3QtMS5hbWF6b25hd3MuY29tL1ZhbGltYWlsJiM0MztMb2dvLnBuZyI+
PG86cD48L286cD48L3A+DQo8cCBzdHlsZT0ibWFyZ2luOjBjbTtiYWNrZ3JvdW5kOndoaXRlIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjguMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzY2NjY2NiI+VGhpcyBlbWFpbCBhbmQgYWxsIGRhdGEgdHJhbnNt
aXR0ZWQgd2l0aCBpdCBjb250YWlucyBjb25maWRlbnRpYWwgYW5kL29yIHByb3ByaWV0YXJ5IGlu
Zm9ybWF0aW9uIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiBpbmRpdmlkdWFsKHMpIGF1
dGhvcml6ZWQNCiB0byByZWNlaXZlIGl0LiBJZiB5b3UgYXJlIG5vdCBhbiBpbnRlbmRlZCBhbmQg
YXV0aG9yaXplZCByZWNpcGllbnQgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQgb2YgYW55IHVzZSwg
ZGlzY2xvc3VyZSwgY29weWluZyBvciBkaXN0cmlidXRpb24gb2YgdGhlIGluZm9ybWF0aW9uIGlu
Y2x1ZGVkIGluIHRoaXMgdHJhbnNtaXNzaW9uIGlzIHByb2hpYml0ZWQgYW5kIG1heSBiZSB1bmxh
d2Z1bC4gUGxlYXNlIGltbWVkaWF0ZWx5IG5vdGlmeSB0aGUgc2VuZGVyDQogYnkgcmVwbHlpbmcg
dG8gdGhpcyBlbWFpbCBhbmQgdGhlbiBkZWxldGUgaXQgZnJvbSB5b3VyIHN5c3RlbS48L3NwYW4+
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_caa45e567fb844dd8c46a8ccbf4077d6KAPPEX008uniteddomain_--


From nobody Mon Jun 14 11:08:52 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 71DA33A2CE3; Mon, 14 Jun 2021 11:08:48 -0700 (PDT)
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.32.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dmarc@ietf.org
Message-ID: <162369412839.26775.12999469210702081825@ietfa.amsl.com>
Date: Mon, 14 Jun 2021 11:08:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/RfOJSALRYSS53RfseLhgmaKmyB4>
Subject: [dmarc-ietf] I-D Action: draft-ietf-dmarc-psd-15.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: Mon, 14 Jun 2021 18:08:49 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain-based Message Authentication, Reporting & Conformance WG of the IETF.

        Title           : Experimental DMARC Extension For Public Suffix Domains
        Authors         : Scott Kitterman
                          Tim Wicinski
	Filename        : draft-ietf-dmarc-psd-15.txt
	Pages           : 15
	Date            : 2021-06-14

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

   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.


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

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-psd-15

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


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Jun 14 11:39:48 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 CE3413A2DC2 for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 11:39:46 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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 61woi8_13CcS for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 11:39:41 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70093.outbound.protection.outlook.com [40.107.7.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 6A7063A2DC0 for <dmarc@ietf.org>; Mon, 14 Jun 2021 11:39:41 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iYAPS0qetbCbMw4P+OP978F3B15GoXhw/raMfI+K30ljV5U8o0gyHe/r4MDuffd8tptul1tE6svJ3b9fB6x3YwhCd2T/I+J/EQ3fC2cGJfrIBdOUW8Q1eijqDTIgvcktwsaW7/tv0CAmmBIM3yaziXOQDgrHvG84gAKS9pWbNNQ+2msLWhAZfzG6YYEsU5GHhF14J01TWjmk18EHiK1ygMaVrdP07yVqlCTS2Q9DLwLGa8e5GgXfErFa+n9MBTttkP+XMGpGuXOj6YIr2cC+URlOy+rfNK/refun2Pt/U0VPu1kbrFN+0ZQBqgGPdkCLrQUj8BVDCojr6OYXHybL9g==
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=plPy5e8h55YHLuFKrweN2KgbsmRVCkljki1BgQg5PXw=; b=M1kzJhDNS+vGhfhEM6xpqRuKjLwlMMWpxreMPkEgQwelkwW4C4Eg6vikX5X2VSEeiRjW160jRMM+FCz5IK2cCVgAPeUy9wwlR5FO6qfPU6oL5ofIkd0SkgvnZwUfQmyqQfpbRCOanQAOcOO7piC06MTZN6u+Mf+npU1g/ikR/umOp2/ejbtmMdScegNDeldvndsgFDfL4XEYL4JFbtIK3rvgteavh0qXmYOM61G3XqpOORA3enU3VH17FfZag0g4ddjxA3pfJ6lMMBlItGTdr/U94OAomwaXsW0ww/ogDqLCfDSxbu4V9CObjj4hbQFzyD3WIl8bMnGUb8c55JvUmA==
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=plPy5e8h55YHLuFKrweN2KgbsmRVCkljki1BgQg5PXw=; b=nFc3H6PJ/4Gbh7Pi2Jd9HA1pWWwnWX28aSbwxGO9rlh4Y1VdkTbkHVUL88nXR786974x0K8m0zM+IBqsL+aMyzhy+DovZY5oq25yQ0r14m6OEu5mN6UKuRnfzSokwRglxbHfyccoExy/w2VrJJQfedKZ19VNTsXkz+MZHHqhaQeyiuTQ/auPgbjRsW0J9zWvEFt/vtptFkoLc1RcDoM57TRB1p09uASKh/FYDfaE5Qjc9YS9gRTb35INrbqKeLZ+2QUt57xVQ/kVoTCovnAAHDsW04dII/U1y4wDii/3naao3CgKyVVIylVw3izuE+wMNWuoUcMhOGxOVMZWGAtEDg==
Received: from DBAPR01MB7048.eurprd01.prod.exchangelabs.com (2603:10a6:10:17d::6) by DB8PR01MB6326.eurprd01.prod.exchangelabs.com (2603:10a6:10:159::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4219.21; Mon, 14 Jun 2021 18:39:36 +0000
Received: from DBAPR01MB7048.eurprd01.prod.exchangelabs.com ([fe80::e4bd:eff:a8e7:d4a2]) by DBAPR01MB7048.eurprd01.prod.exchangelabs.com ([fe80::e4bd:eff:a8e7:d4a2%7]) with mapi id 15.20.4219.025; Mon, 14 Jun 2021 18:39:36 +0000
From: Ken O'Driscoll <ken@wemonitoremail.com>
To: "Brotman, Alex" <Alex_Brotman=40comcast.com@dmarc.ietf.org>, "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: Sender-supplied decision matrix for passing DMARC
Thread-Index: AddhPDwbCzQ9bLtKT5O2BtOM1Kt/JwADpzx3
Date: Mon, 14 Jun 2021 18:39:36 +0000
Message-ID: <DBAPR01MB7048EBC9777FED3934872FFEC7319@DBAPR01MB7048.eurprd01.prod.exchangelabs.com>
References: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
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: 8674277c-a0ad-4f98-cc78-08d92f63c2ee
x-ms-traffictypediagnostic: DB8PR01MB6326:
x-microsoft-antispam-prvs: <DB8PR01MB6326C3C1B7A73118C8EB4248C7319@DB8PR01MB6326.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: 8jjJoo/sR8N3F+yz2asUa1Ctqzc3ipN/rwa+1npML0PgVkXz24WLil75PYSYLWAb2Wfha8qc84NsVdKfsbRZSCRSuXZuRSLGpP0/eP/YEhkn+4WNDqpaExxj84QgLP3kesyR1IU4PzgPtjHFuTjC0jbHesOIl11br49DJy8AuK21zeU3URhG/7pO2pjFHwOk0mSA5cwy8NmBzVNb4V3htwYTv4x2CmUDpLdPM4W26uNwSm06dVJ2zGq9grzZJAeazdXqE4C0+oyNb7+/sWMKAesgAFcBQm1cgGzxR6eGH4tgSM3yDGnfHsQZexoyfSGRRNlwBLOqhTklXw1yU8EaQjbnyGTingiLzBtQnWDwc9oSvR4eE2PjIc1xQIjZ+LESHepLji6tW6+Xt+ouCAMJOoCG+e1pgHDicW1TDW3Opz+cn+c80uPNwc2+hBo6xIdyQ6NlMBqnQNGg7qMSTk9wU7xixLmtdLajru2llnuuCrGlo1U/rhjVKogW3Rt9no7atqLwbyvllykT7u2gqUn+dkgItqWZpLzpo//qdIscnQ6ppuPyH2xT1L4ZYz5KvQpBvqT06aHiwV+wgtA5nr1uBdz1eBmqMY6iotki//IIO47Wqq2HpO/X0KmqcNyBBKOIzHHcS8+sK72pyTzSfkme/5F5yjRUPTphIpNKqmlPJWbwhUfmnpTeGS7+44jNn95SPNrImDX0QOoQ6jI09xPNfA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DBAPR01MB7048.eurprd01.prod.exchangelabs.com; PTR:;  CAT:NONE; SFS:(346002)(366004)(5660300002)(8676002)(966005)(9686003)(86362001)(71200400001)(8936002)(33656002)(2906002)(66476007)(64756008)(66556008)(76116006)(66446008)(91956017)(66946007)(52536014)(55016002)(83380400001)(38100700002)(166002)(122000001)(186003)(53546011)(6506007)(7696005)(26005)(478600001)(316002)(110136005); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?DaiTLwj+icGEAczZaVD0RCKO3C+pRSqQs1lZNL3VPZ+t1+vFDl6zBSN8WUYq?= =?us-ascii?Q?eN7j7sGR1w7iAV5JUvtDJfc0Rz+Kt81UKZ3PMWUri4p2WuKi12gEWAqB6TZX?= =?us-ascii?Q?bxVPnwTxatTuuW5iuf5OO7ZQciyB3BrhZDftUEuRq5uS+/8GWMZrxclIYnnE?= =?us-ascii?Q?qj6JrvnqEs+6twsxB3I4mhEobgTh3ylYLlRao4Bp8R8vj859S0Cq3LGrCxsR?= =?us-ascii?Q?LpC+Ytl6G8b9FiSM06k7dt0mOSkgMSN7NwgJbLRbiWtKeVQFFBUAAojOUzr3?= =?us-ascii?Q?dAOngijaZNqESlWOnFbRsDV7DJljJz3Tb6UGQwHjKL/X9FCfpwckDsd1OHNC?= =?us-ascii?Q?XKKXEcuD57stk8zm0Zc4dbx1JmQjG08Vwi5ukiORXehS0EtURO2C5IO+zQh/?= =?us-ascii?Q?gOvbyR7jR8EUM6mEiaMPRDw+U6AkeBYghxE+V/sV4bglYqB9lcKJygs0yICR?= =?us-ascii?Q?vS8q8QnebmTHCRaZpth8iFfyhb6B/bzqV966zKsyQDjbKZU8emxKEuVNpc8G?= =?us-ascii?Q?6pTjNKTqddIFXW1Vi1Fp611T5+PuvCdcB7JWKCrQ8gPv5kMJsAQpsbgCntMb?= =?us-ascii?Q?w5k3/fXjIBLP/mFGXhkbQjPCQz/oo5Pp1/f5VJ62nvllsd2CM3SKvxwK1gR+?= =?us-ascii?Q?6qo8TXjefnCBecaqM3V/F3Q6cloKVIg6rd07MliSnzvUBJgSvrT4oFLsU+Fi?= =?us-ascii?Q?FU1g/L39p1UmO5qoeJVyECPSzeYqjscUiN+TCV15g9AuSLC4vh1k4pGgiSjV?= =?us-ascii?Q?OYMMsIR30FOTkHTSZhNzGg/vOH4V+e+ldd+P4ZTlKkUX3sJoBDcGC5PaVdyz?= =?us-ascii?Q?V8TlbUktCMi5YUDB5wcnlyEbQifiSQFkjtZo3tssXF2WAB7pnmBBXOJeDbNY?= =?us-ascii?Q?j0ahDG9iJv1dYTfn8s/lEfY+iTDHNZMP4KeVJRIEDj54Er22g4NiBkCpd7+Y?= =?us-ascii?Q?84gHMXcyyStHHAMmjgcTWvM+PTPwOSBvkqz7E1KaRTV8VwJnGEeasxab3Hmb?= =?us-ascii?Q?intwHtCCkBqGvaUB1sqybjQUVWslwZHC3cQpn1gAFzfEgT7rMwLpIXr2g4h1?= =?us-ascii?Q?dv5KuVlt8vEjxGFeogx7nxVtgw67iHlIORBfMiBh/h4losdpICMqHqeqWe8F?= =?us-ascii?Q?v4BHy/oVXBeJfi+9brTQD3Ud7eqxdvnJypPDFIugQdlkWVTTYuKmOBxy10xM?= =?us-ascii?Q?eAM5GUzPmRX1DkQ6FFEdGKTYduNN7NXMLmo0twFjPz0FvDx5rGwBO/IZDWL9?= =?us-ascii?Q?j4b9QaW6NG2dma2ewI13ncr9vog4fUB+beSFBWPM5l2KhgW53Dm3SQQj42rZ?= =?us-ascii?Q?YHEDnrIkkBN6gvbsytSQm1PU?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DBAPR01MB7048EBC9777FED3934872FFEC7319DBAPR01MB7048eurp_"
MIME-Version: 1.0
X-OriginatorOrg: wemonitoremail.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DBAPR01MB7048.eurprd01.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8674277c-a0ad-4f98-cc78-08d92f63c2ee
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jun 2021 18:39:36.7576 (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: kGNi7mS+FGNFuzAjtGsc7UfjzJtWKD7l7/9W/SAJBMQRpEPTkQBoISbcssZWiHUStTKjsvNYgRSHGz7dsjPFag==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8PR01MB6326
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/2LNUUTAxFowPX7dC1oo9KPNo1gw>
Subject: Re: [dmarc-ietf] Sender-supplied decision matrix for passing DMARC
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2021 18:39:47 -0000

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

I think this is a bad idea as it adds unnecessary additional complexity. Cu=
rrently, a domain owner can choose to only implement DKIM or SPF on a mail =
stream if they only wish one mechanism to be evaluated.

Further, if there is a (renewed?) desire to apply a policy layer to DKIM si=
gned messages, then isn't that what ADSP (RFC 5617) was intended for?

Ken.

________________________________
From: dmarc <dmarc-bounces@ietf.org> on behalf of Brotman, Alex <Alex_Brotm=
an=3D40comcast.com@dmarc.ietf.org>
Sent: Monday 14 June 2021, 18:10
To: dmarc@ietf.org
Subject: [dmarc-ietf] Sender-supplied decision matrix for passing DMARC

Hello,

I was talking to some folks about DMARC, and a question came as to suggest =
as the domain holder that your messages should always pass DKIM.  Effective=
ly, the asker wants to say "I intend to deploy SPF and DKIM, but I will *al=
ways* sign my messages with DKIM."  So the obvious answer may be "Just only=
 use DKIM", but I'm not sure that completely answers the question.  While d=
iscussing with someone else, "Tell me when DKIM fails, but SPF is fully ali=
gned".  There was recently an incident at a provider where they were allowi=
ng any sender to send as any domain (and I'm aware that's not specifically =
a DMARC issue).  We all know brands that have just dumped in a pile of "inc=
lude" statements without fully understanding the implications.  In this cas=
e, other users could send as other domains, but perhaps they would not have=
 been DKIM signed.  Should there be a method by which a domain holder can s=
ay "We want all message to have both, or be treated as a failure", or "We'l=
l provide both, but DKI
 M is a must"?

>From a receiver side, it makes evaluation more complex.  From a sender sid=
e, it gives them more control over what is considered pass/fail.

How does this look in practice?  Maybe "v=3DDMARC1;p=3Dquarantine;rua=3D...=
;pm=3Ddkim:must,spf:should;"
(pm=3DPolicy Matrix)

Does this make everyone cringe, or perhaps worth a larger discussion?

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

_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body>
<div style=3D"color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);=
" dir=3D"auto">
I think this is a bad idea as it adds unnecessary additional complexity. Cu=
rrently, a domain owner can choose to only implement DKIM or SPF on a mail =
stream if they only wish one mechanism to be evaluated.</div>
<div style=3D"color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);=
" dir=3D"auto">
<br>
</div>
<div style=3D"color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);=
" dir=3D"auto">
Further, if there is a (renewed?) desire to apply a policy layer to DKIM si=
gned messages, then isn't that what ADSP (RFC 5617) was intended for?</div>
<div style=3D"color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);=
" dir=3D"auto">
<br>
</div>
<div id=3D"ms-outlook-mobile-signature">
<div style=3D"color: rgb(33, 33, 33); background-color: rgb(255, 255, 255)"=
 dir=3D"auto">
Ken.</div>
</div>
<div id=3D"id-0533bcc8-1905-4299-9502-0db27d8b2cea" class=3D"ms-outlook-mob=
ile-reference-message">
<div style=3D"font-family: sans-serif; font-size: 12pt; color: rgb(0, 0, 0)=
;"><br>
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg"><strong>From:</strong> dmarc &lt;dmarc-bounces@ie=
tf.org&gt; on behalf of Brotman, Alex &lt;Alex_Brotman=3D40comcast.com@dmar=
c.ietf.org&gt;<br>
<strong>Sent:</strong> Monday 14 June 2021, 18:10<br>
<strong>To:</strong> dmarc@ietf.org<br>
<strong>Subject:</strong> [dmarc-ietf] Sender-supplied decision matrix for =
passing DMARC<br>
</div>
<br>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style><font size=3D"=
2"><span style=3D"font-size:11pt;">
<div class=3D"PlainText">Hello,<br>
<br>
I was talking to some folks about DMARC, and a question came as to suggest =
as the domain holder that your messages should always pass DKIM.&nbsp; Effe=
ctively, the asker wants to say &quot;I intend to deploy SPF and DKIM, but =
I will *always* sign my messages with DKIM.&quot;&nbsp;
 So the obvious answer may be &quot;Just only use DKIM&quot;, but I'm not s=
ure that completely answers the question.&nbsp; While discussing with someo=
ne else, &quot;Tell me when DKIM fails, but SPF is fully aligned&quot;.&nbs=
p; There was recently an incident at a provider where they were
 allowing any sender to send as any domain (and I'm aware that's not specif=
ically a DMARC issue).&nbsp; We all know brands that have just dumped in a =
pile of &quot;include&quot; statements without fully understanding the impl=
ications.&nbsp; In this case, other users could send
 as other domains, but perhaps they would not have been DKIM signed.&nbsp; =
Should there be a method by which a domain holder can say &quot;We want all=
 message to have both, or be treated as a failure&quot;, or &quot;We'll pro=
vide both, but DKI<br>
&nbsp;M is a must&quot;?<br>
<br>
&gt;From a receiver side, it makes evaluation more complex.&nbsp; From a se=
nder side, it gives them more control over what is considered pass/fail.<br=
>
<br>
How does this look in practice?&nbsp; Maybe &quot;v=3DDMARC1;p=3Dquarantine=
;rua=3D...;pm=3Ddkim:must,spf:should;&quot;<br>
(pm=3DPolicy Matrix)<br>
<br>
Does this make everyone cringe, or perhaps worth a larger discussion?<br>
<br>
--<br>
Alex Brotman<br>
Sr. Engineer, Anti-Abuse &amp; Messaging Policy<br>
Comcast<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
dmarc@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc">https://www.ietf.or=
g/mailman/listinfo/dmarc</a><br>
</div>
</span></font><br>
</div>
</body>
</html>

--_000_DBAPR01MB7048EBC9777FED3934872FFEC7319DBAPR01MB7048eurp_--


From nobody Mon Jun 14 12:51:08 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 4C7A13A07DC for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 12:51:04 -0700 (PDT)
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=TZjNlzIL; dkim=pass (2048-bit key) header.d=taugh.com header.b=A29EgKAn
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d29DzJA6Jgvv for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 12:50:58 -0700 (PDT)
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 AEA863A07D4 for <dmarc@ietf.org>; Mon, 14 Jun 2021 12:50:58 -0700 (PDT)
Received: (qmail 58695 invoked from network); 14 Jun 2021 19:50:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=e543.60c7b320.k2106; bh=4I8WWVUj6DvL5Pd8vYJbosuhrLf2WFJQLb6NqN7NNz8=; b=TZjNlzILxGUamTbfr781zJC3MuP/nXMQfZ+T+RnO24xgKjZ9Lyih4MkecoNXnOXOMz9aMHUdU9mmCYP4uLGaZ63vqXtwAG9CSepikNL3b957akIQ9LyxkczmWA/hoa5FuWl6Dfmew0G2sUwvpqaZaqsCwRJk2/Yud98tfDJG4Y/KIh1oqpOOqygEwZx3HqysAZL+FimjpEfrKp0zlCyiCKcIzg/PJKKZO97iXATYWAV5w73D7umHFi5gS0gsaJDGE+2sSNbg8NROZI5gCgU6+PtvrPYOZXsZgN8tyeNyQscxC6HD2JOuT7TjEtDCkZPlu2oUMkq935bLn3YnnfOM/w==
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=e543.60c7b320.k2106; bh=4I8WWVUj6DvL5Pd8vYJbosuhrLf2WFJQLb6NqN7NNz8=; b=A29EgKAnueILL83BJkDQzk0XNFMcK9pwgnCrctiuSn8r0Pf2hlf3eKQsUG1OT6o1bkSAxSWLTZ9EJtj3E6L3qbV9t21Xon37qxcLOEQmUq6DH4TSrmN/jfiQKeDp0CN4SNI8/taXzzRWh3Oh9q49UQeW3kaMCYKbVW0UqxcH02tTtENMYNvnu6zTje9DyR/6kw27umrwUNsyEb1BKuMgXszmZNeCwAEGbOpQcO+CXFHGCGunqq7JyndDtRCTko6ydXQZJmQ2FS3pybniPDRABZLFml9JOiy8B/5gh4I77/FKGGFCWZsP1pv+6U4FazGoiyl1LXH1lD9AIlS95zWkEA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 14 Jun 2021 19:50:56 -0000
Received: by ary.qy (Postfix, from userid 501) id 621FB10CFD51; Mon, 14 Jun 2021 15:50:54 -0400 (EDT)
Date: 14 Jun 2021 15:50:54 -0400
Message-Id: <20210614195054.621FB10CFD51@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: Alex_Brotman@comcast.com
In-Reply-To: <MN2PR11MB4351B731B053D51E093BBE51F7319@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/MmoVD7RQBp94LUkIteaKJKZFqcw>
Subject: Re: [dmarc-ietf] Extensions in Aggregate Reporting - Feedback Requested
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 14 Jun 2021 19:51:05 -0000

It appears that Brotman, Alex <Alex_Brotman@comcast.com> said:
>To summarize,
>
>We'd like to see extensions available both below the "feedback" and "record" elements.  The -02 draft only has it below the "feedback" element.  I agree that all
>elements, each time they are utilized, should mention a reference as to how they are to be utilized.
>
>We'd also like to have extensions go through an IETF process, however, we also understand that we cannot exclude third parties from defining/deploying their own
>extensions.  I suppose we could tell report receivers they "MUST" ignore any extensions which are not IETF-approved, though that seems a bit heavy-handed.

Remember, IETF standards are about how to interoperate.  If people want to interpret private extensions,
that is fine so long as the private ones don't interfere with public ones.

While we would like it if people published the details of their private extensions, just knowing the
names is useful since that keeps names from colliding.  So we should set up a FCFS registry for
extensions, specification would be nice but not required.

R's,
John


From nobody Mon Jun 14 12:53:43 2021
Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9FAE3A083B for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 12:53:39 -0700 (PDT)
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=TB66yqHt; dkim=pass (2048-bit key) header.d=taugh.com header.b=hyzcCUTn
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3LZYFZ7IODYZ for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 12:53:35 -0700 (PDT)
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 458D73A082C for <dmarc@ietf.org>; Mon, 14 Jun 2021 12:53:35 -0700 (PDT)
Received: (qmail 59276 invoked from network); 14 Jun 2021 19:53: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:mime-version:content-type:content-transfer-encoding:cleverness; s=e78a.60c7b3bd.k2106; bh=DHRX9xoTbhAo6LQuQbf0dB71MiY1VNaloP7LnczvDaQ=; b=TB66yqHtDjYnCU+/eiy6HFk0dzyZc1o2BFiYOvQSjc4xJZNLigaW8/6yYSK7R9+hKCo+c55fily2XcWv/pP/GUXJd5N0GK02AocsonrXCxV3jF16BXxNGQCcjyPp0mVGDPyAbRx1VKoSAShzAIu+Rj4OsLUE2XeYroKyGDQX/bE77/+XmOfxHPqzbtn4wY700rRxIDgJC5O/iQq7z2614FIFjkGlyJdv4nT4xbb+YQP1y6KHig4BRRlv2g7/SrZ5GFayP6RrEyLNCismCLtCeNXZUATr9spngV1LRMLuIXsFDQzT3gaKAWI+NhUeqFTE3XqmLiQumNJG+AU21RALAQ==
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=e78a.60c7b3bd.k2106; bh=DHRX9xoTbhAo6LQuQbf0dB71MiY1VNaloP7LnczvDaQ=; b=hyzcCUTnuBrS8GPZzE76VEb0UiUrKAH5WgPBnLbb+Feh4lAjl0CvMwqmeFLTODImwJpmBvuCDNFTiSxn9jELwPh7Qs9we5p5s99+pMG+/yf05up0rfpgL7iJX6zAXjzab3idNMQ1pMLSSMkx6oBEPQViU6aSL5MtfkFrPQFFxP+sIheIURJYV/hVb++qFJu3+AbpXEACZ/bVWGpJTxCH8cS97nHXCaLZojmo096S0Q7oSdlG+Px6GvPpPuhGtuLqec1oxurdZqY6jivUNU8dkGiWDaQD/VL7yc9LaO6t+W5Rc2h41KVmxzOap7+ww8Jqt30KpamCFmqydvvowIEb8g==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 14 Jun 2021 19:53:33 -0000
Received: by ary.qy (Postfix, from userid 501) id 235D510D0492; Mon, 14 Jun 2021 15:53:30 -0400 (EDT)
Date: 14 Jun 2021 15:53:30 -0400
Message-Id: <20210614195331.235D510D0492@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: Alex_Brotman@comcast.com
In-Reply-To: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@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/N9U-PmzuAbdstTFLm0sO2TfgjZM>
Subject: Re: [dmarc-ietf] Sender-supplied decision matrix for passing DMARC
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2021 19:53:40 -0000

It appears that Brotman, Alex <Alex_Brotman@comcast.com> said:
>Does this make everyone cringe, or perhaps worth a larger discussion?

Cringe.  If others have said, if you want DKIM to pass, sign everything with DKIM.  I can promise you
that anyone who says "all of our mail will always pass SPF" doesn't know where his mail is going.

For other reasons it would be a good idea to publish SPF records and have them usually pass, but they don't
have to be the same domain as the DKIM or DMARC.


From nobody Mon Jun 14 16:19:23 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 F3D303A12BD for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 16:19:21 -0700 (PDT)
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 KKoW34TqQMyd for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 16:19:16 -0700 (PDT)
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 217193A12BC for <dmarc@ietf.org>; Mon, 14 Jun 2021 16:19:16 -0700 (PDT)
Received: by mail-oi1-x230.google.com with SMTP id s23so16172227oiw.9 for <dmarc@ietf.org>; Mon, 14 Jun 2021 16:19:15 -0700 (PDT)
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=SNh5Z4OSjvV4hdBmXVqHV8BRhQYRqY6GtyARRhJ6OgY=; b=CSu8t5OOsVMCuuX3zjtg5Q+aIcZioBVSbWDeBYkK+VvA61N/lOzp42w+lq5IIdCJK+ Pc2v6sN4x1B0paJEhWEOVPGm8u5RX4kuFuNokI6/cC0qIfe1mv+pO+DtBjGXpTAVaElm HhcxeHp1ApSQMfUb0RKfMRe54kGoTy1LhpJ6MyjrEVSlEfcQvBDrATTNqxf/xgvI1Xzh mud/HX+e1t7XvQtMLPVoM494Vhv+jIhbqEg8wxuKtrNjuX/WDmm4X50/EUW1e64YSYvB 5pe05U55TBJ9g+LpAxMHt3ZqkKOn6pRVJvMg0E782i/akVU5ZL1wNhV0mFA1FqjFswN0 Ff5g==
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=SNh5Z4OSjvV4hdBmXVqHV8BRhQYRqY6GtyARRhJ6OgY=; b=plpk98Kg3x8nAg+oeyinFXa4W1Ors6TGTM0+2jtGb3WfQC/RRiQMuIfVGd6ZFxmtTC BHm/a27T+kciXyyxSZGwMtTvBbPpq1TXib2b4TfsH+lvj2EBxw3AlfLmIuE5uVmbynlw SDIpqFojYzSWGMfZdfRQNUGp9+iPzFP5ZHsqRUgZ9ER1s4cU9Gvfvx1LstXNWNp7KA63 VagdPeW5ozX3T++QroiMWpPXpm+SzTJg058QbzpQa4VEWYvwuWkZ5Uyhu/cnS9StJBmm 5ydNEIkl4WGC3+IY7o1p0droXiqO4kMx2vFQvXtt1GY1dw2+wcJRShs4V3POjSQsyCrj HRKw==
X-Gm-Message-State: AOAM533gT9Ifbw3zDqjJlKAXd5MSbx4zoIxBett7uhQPF9iHsrefRwlL GQNod83fNbQf1iR9wp+0SwpcKd7wMpozIoimY1maJlj+uWA=
X-Google-Smtp-Source: ABdhPJw1hDJINPKCfvAytQwORgNwlGlU99wuoJirWX0xU0BJ1UOyxpzhxFW5eOd+oddPa2LSlAKcGbzAVP8FAfV2faY=
X-Received: by 2002:aca:c492:: with SMTP id u140mr1048030oif.20.1623712754265;  Mon, 14 Jun 2021 16:19:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAH48ZfzuM298fkmhoZtH1ZbK=9Ne9EYtyTYNV27PSsPBW=Gq-w@mail.gmail.com> <1a666b47-d556-e758-f4ce-05de79c449d1@tana.it>
In-Reply-To: <1a666b47-d556-e758-f4ce-05de79c449d1@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 14 Jun 2021 19:19:03 -0400
Message-ID: <CAH48ZfxxUjvfHsd0QKwXbOqZLyeqhVmzORPekJBoPcwAb8tiiA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ef709805c4c21556"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/H6MiB54jnkZPxSMoWi1GYEjOUe4>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 14 Jun 2021 23:19:22 -0000

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

Thank you for asking.

OK.,  I will use the term "email suffix" for the part of an email address
that follows the @ character,  and "DNS domain" for a name that appears in
DNS as a domain object.

An email suffix can legitimately be associated with an A/AAAA
resource record that is not a DNS domain.   For example, an alarm
monitoring system might send alarms using the server's host name as the
email suffix (e.g. Alarms@MonitorE.xample.Com).   MX and SPF can also be
configured for Monitor.Example.Com even though it is not a  DNS domain.
This is specifically authorized by RFC 5321.

A spoofed email address could use any email suffix, such as
NotSpam@TrickedYou.Example.Com.   Our interest must extend beyond names
that are in DNS.

In my mailstream, most messages sent from mailing services use the mailing
service domain for the SMTP address.  This insures that the message
produces SPF PASS.  It also means that the FROM domain name has no
necessary dependence on any DNS entry.   It took me only one day to find
examples of this;,non-existent subdomains used on legitimate messages sent
by mailing services.  The FROM suffix correctly reflects the parent
organization, but the full email suffix does not appear in DNS.   This
situation means that we cannot distinguish between valid and invalid email
suffixes using DNS alone, we must require domain owner signalling.

How does a domain owner signal that @bounce.e.example.com is valid as a
FROM domain, even though the name is only used for mailing service
messages?    Under the current draft, the domain owner must associate the
name with an IP address using an MX, A, or SPF record, even though the name
has no legitimate connection to the chosen IP address.  I do not consider
this acceptable.   In the real world, I fear that implementing such a
requirement will have unexpected consequences, and network administrators
who share my fear will be reluctant to comply with our draft.

I focused on SP and NP because it is the SP or NP policy which provides
inheritance,  Inheritance has to be the primary way that we defend against
abuse of unused and non-existent email suffixes

You asked a lot of questions.   I think I should stop there and give you a
chance to respond before going further.

Doug Foster


On Mon, Jun 14, 2021 at 7:12 AM Alessandro Vesely <vesely@tana.it> wrote:

> Doug,
>
> maybe it's me, but I have problems understanding your proposal.  Let me
> quote
> what seems to hamper my comprehension.
>
> Besides, #11 in the Subject: is obviously a typo.
>
>
> On Sat 12/Jun/2021 14:55:33 +0200 Douglas Foster wrote:
> > ties the design directly to the mailing list problem.
>
>
> I couldn't see where mailing lists are taken into account.
>
>
> >    However,this authentication can be lost in transit if message
> modification
> > occurs in transit, as discussed in RFC 7960.  This possibility can make
> domain
> > owners reluctant to move beyond sp=none.
>
>
> Why do you consider SP irrespective of P?  Actually, SP could be used by
> "simple" mail sites, those which make no use of subdomains for email.  In
> such
> cases, setting sp=reject can safely prevent generic abuses even for
> domains
> having p=none.  It sounds similar to null SPF records for non-mail hosts.
>
>
> > x.1 Implement mail domains as DNS domains with domain-level DMARC
> policies.
> >
> > Mail domains are often implemented as DNS domains, but this is not
> required.
>
>
> Please, stick to well established jargon.  Tim made a good synthesis in
> section
> 2.2 and ensuing ones.  A /DNS domain/ is defined by RFC 1034:
>
>      A domain is identified by a domain name, and consists of that part of
>      the domain name space that is at or below the domain name which
>      specifies the domain.
>
> In this sense, the concept of non-existing domain names that are
> legitimately
> used sounds like a contradiction in terms.
>
>
> > Once all used mail domain names are configured as DNS domains, they can
> be
> > configured with DMARC policies.
>
> AFAICS, a /used mail domain name/ which is not a DNS name is a
> /non-existent
> domain/ found in some (forged) email addresses.  I agree that such
> practice
> should be discouraged.  Yet, that doesn't seem to be the point here...
>
> BTW, are there organizations that use non-existent (sub) domains during
> the
> delivery of legitimate messages?  Years ago I saw sporadic mailing list
> authors
> forged like john.doe@NOSPAMexample.com.  Is that what you're talking
> about?
>
>
> > - For mail domain names that are not used with SMTP, a new TXT record is
> > defined, with content "DMARCFROMv1".   The presence of this TXT record
> > indicates that the associated DNS domain, named DNS resource record, or
> > wildcard DNS record should be considered as potentially in use as an
> > RFC5322.From domain name.
>
>
> Ok, that is clear, but, IMHO, won't work.  Working MXes or IP addresses
> are a
> necessary condition to receive mail.  Thus, a purist receiver has to
> accept
> such domains as valid.  Therefore traditionalist domain operators will not
> see
> a compelling need to define any auxiliary TXT records.  A new RR type of
> this
> kind would most probably be going to characterize mass mailers who hasten
> to
> adopt any new trick that seems to offer a chance to increase
> deliverability.
> Undoubtedly, someone would be tempted to discard senders based on that (as
> it
> happened to DKIM...)
>
> An organization which wants to say sp=reject but does use some email
> subdomains
> had better define plain DMARC records for them.  Records can be easily
> duplicated by CNAMEs.  If we needed to vary some parts but not others, for
> example a different policy but the same aggregate reporting address, we
> should
> define something equivalent to SPF's include.
>
>
> > - For used domain names that are not in DNS at all, a DMARCFROMv1 TXT
> record
> > is needed to indicate that the name is used for mail.
>
> Actually, /any/ record definition will turn a domain into an existing one.
> However, by Section 2.7 of PSD, which defines the MX/A/AAAA test, such
> domain
> would still be non-existing.  In that sense, DMARCFROMv1 conflicts with
> PSD.
>
>
> > x,3 Implement SPF -ALL policies on unused names.
> >
> > Organizations that have configured SPF to protect their valid
> RFC5321.MailFrom
> > domains may not have taken the extra measure of using SPF to obstruct
> names
> > that are not used for mail.  While not directly part of DMARC, an
> > authentication result of "DMARC=NONE SPF=FAIL" is a more meaningful
> result than
> > "DMARC=NONE, SPF=NONE".  Consequently, it is desirable to  ensure
> SPF=FAIL for
> > any names that are never used as RFC5321.MailFrom domain names.   Since
> SPF has
> > no inheritance, this requires many entries.
>
>
> That's a well known SPF issue:
> http://www.open-spf.org/FAQ/Common_mistakes/#all-domains
>
> There used to circulate scripts to generate null SPF records.  It would
> help if
> DNS hosting services implemented a checkbox to carry out such task.  But
> this
> if far OT.
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

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

<div dir=3D"ltr">Thank you for asking.<div><br></div><div>OK.,=C2=A0 I will=
 use the term &quot;email suffix&quot; for the part of an email address tha=
t follows the=C2=A0@ character,=C2=A0 and &quot;DNS domain&quot; for a name=
 that appears in DNS as a domain object.</div><div><br></div><div>An email =
suffix can legitimately be associated with an A/AAAA resource=C2=A0record t=
hat is not a DNS domain.=C2=A0 =C2=A0For example, an alarm monitoring syste=
m might send alarms using the server&#39;s host name as the email suffix (e=
.g. <a href=3D"mailto:Alarms@MonitorE.xample.Com">Alarms@MonitorE.xample.Co=
m</a>).=C2=A0 =C2=A0MX and SPF can also be configured for <a href=3D"http:/=
/Monitor.Example.Com">Monitor.Example.Com</a> even though it is not a=C2=A0=
 DNS domain.=C2=A0 This is specifically authorized by RFC 5321.</div><div><=
br></div><div>A spoofed email address could use=C2=A0any email suffix, such=
 as <a href=3D"mailto:NotSpam@TrickedYou.Example.Com">NotSpam@TrickedYou.Ex=
ample.Com</a>.=C2=A0 =C2=A0Our interest must extend beyond names that are i=
n DNS.</div><div><br></div><div>In my mailstream, most messages sent from m=
ailing services use the mailing service domain=C2=A0for the SMTP address.=
=C2=A0 This insures that the message produces SPF PASS.=C2=A0 It also means=
=C2=A0that the FROM domain name has no necessary dependence on any DNS entr=
y.=C2=A0 =C2=A0It took me only one day to find examples of this;,non-existe=
nt subdomains used on legitimate messages sent by mailing services.=C2=A0 T=
he FROM suffix correctly reflects the parent organization, but the full ema=
il suffix does not appear in DNS.=C2=A0 =C2=A0This situation means that we =
cannot distinguish between valid and invalid email suffixes using DNS alone=
, we must require domain owner signalling.</div><div><br></div><div>How doe=
s a domain owner signal that @<a href=3D"http://bounce.e.example.com">bounc=
e.e.example.com</a> is valid as a FROM domain, even though the name is only=
 used for mailing service messages?=C2=A0 =C2=A0 Under the current draft, t=
he domain owner must associate the name with an IP address using an MX, A, =
or SPF record, even though the name has no legitimate connection to the cho=
sen IP address.=C2=A0 I do not consider this acceptable.=C2=A0 =C2=A0In the=
 real world, I fear that implementing such a requirement will have unexpect=
ed consequences, and network administrators who share my fear will be reluc=
tant to comply with our draft.</div><div><br></div><div>I focused on SP and=
 NP because it is the SP or NP policy which provides inheritance,=C2=A0 Inh=
eritance has to be the primary way that we defend against abuse of unused a=
nd non-existent email suffixes<br></div><div><br></div><div>You asked a lot=
 of questions.=C2=A0 =C2=A0I think I should stop there and give you a chanc=
e to respond before going further.</div><div><br></div><div>Doug Foster</di=
v><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Mon, Jun 14, 2021 at 7:12 AM Alessandro Vesely &lt;<a h=
ref=3D"mailto:vesely@tana.it">vesely@tana.it</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">Doug,<br>
<br>
maybe it&#39;s me, but I have problems understanding your proposal.=C2=A0 L=
et me quote <br>
what seems to hamper my comprehension.<br>
<br>
Besides, #11 in the Subject: is obviously a typo.<br>
<br>
<br>
On Sat 12/Jun/2021 14:55:33 +0200 Douglas Foster wrote:<br>
&gt; ties the design directly to the mailing list problem.<br>
<br>
<br>
I couldn&#39;t see where mailing lists are taken into account.<br>
<br>
<br>
&gt;=C2=A0 =C2=A0 However,this authentication can be lost in transit if mes=
sage modification <br>
&gt; occurs in transit, as discussed in RFC 7960.=C2=A0 This possibility ca=
n make domain <br>
&gt; owners reluctant to move beyond sp=3Dnone.<br>
<br>
<br>
Why do you consider SP irrespective of P?=C2=A0 Actually, SP could be used =
by <br>
&quot;simple&quot; mail sites, those which make no use of subdomains for em=
ail.=C2=A0 In such <br>
cases, setting sp=3Dreject can safely prevent generic abuses even for domai=
ns <br>
having p=3Dnone.=C2=A0 It sounds similar to null SPF records for non-mail h=
osts.<br>
<br>
<br>
&gt; x.1 Implement mail domains as DNS domains with domain-level DMARC poli=
cies.<br>
&gt; <br>
&gt; Mail domains are often implemented as DNS domains, but this is not req=
uired.<br>
<br>
<br>
Please, stick to well established jargon.=C2=A0 Tim made a good synthesis i=
n section <br>
2.2 and ensuing ones.=C2=A0 A /DNS domain/ is defined by RFC 1034:<br>
<br>
=C2=A0 =C2=A0 =C2=A0A domain is identified by a domain name, and consists o=
f that part of<br>
=C2=A0 =C2=A0 =C2=A0the domain name space that is at or below the domain na=
me which<br>
=C2=A0 =C2=A0 =C2=A0specifies the domain.<br>
<br>
In this sense, the concept of non-existing domain names that are legitimate=
ly <br>
used sounds like a contradiction in terms.<br>
<br>
<br>
&gt; Once all used mail domain names are configured as DNS domains, they ca=
n be<br>
&gt; configured with DMARC policies.<br>
<br>
AFAICS, a /used mail domain name/ which is not a DNS name is a /non-existen=
t <br>
domain/ found in some (forged) email addresses.=C2=A0 I agree that such pra=
ctice <br>
should be discouraged.=C2=A0 Yet, that doesn&#39;t seem to be the point her=
e...<br>
<br>
BTW, are there organizations that use non-existent (sub) domains during the=
 <br>
delivery of legitimate messages?=C2=A0 Years ago I saw sporadic mailing lis=
t authors <br>
forged like john.doe@NOSPAMexample.com.=C2=A0 Is that what you&#39;re talki=
ng about?<br>
<br>
<br>
&gt; - For mail domain names that are not used with SMTP, a new TXT record =
is <br>
&gt; defined, with content &quot;DMARCFROMv1&quot;. =C2=A0 The presence of =
this TXT record <br>
&gt; indicates that the associated DNS domain, named DNS resource record, o=
r <br>
&gt; wildcard DNS record should be considered as potentially in use as an <=
br>
&gt; RFC5322.From domain name.<br>
<br>
<br>
Ok, that is clear, but, IMHO, won&#39;t work.=C2=A0 Working MXes or IP addr=
esses are a <br>
necessary condition to receive mail.=C2=A0 Thus, a purist receiver has to a=
ccept <br>
such domains as valid.=C2=A0 Therefore traditionalist domain operators will=
 not see <br>
a compelling need to define any auxiliary TXT records.=C2=A0 A new RR type =
of this <br>
kind would most probably be going to characterize mass mailers who hasten t=
o <br>
adopt any new trick that seems to offer a chance to increase deliverability=
. <br>
Undoubtedly, someone would be tempted to discard senders based on that (as =
it <br>
happened to DKIM...)<br>
<br>
An organization which wants to say sp=3Dreject but does use some email subd=
omains <br>
had better define plain DMARC records for them.=C2=A0 Records can be easily=
 <br>
duplicated by CNAMEs.=C2=A0 If we needed to vary some parts but not others,=
 for <br>
example a different policy but the same aggregate reporting address, we sho=
uld <br>
define something equivalent to SPF&#39;s include.<br>
<br>
<br>
&gt; - For used domain names that are not in DNS at all, a DMARCFROMv1 TXT =
record<br>
&gt; is needed to indicate that the name is used for mail.<br>
<br>
Actually, /any/ record definition will turn a domain into an existing one. =
<br>
However, by Section 2.7 of PSD, which defines the MX/A/AAAA test, such doma=
in <br>
would still be non-existing.=C2=A0 In that sense, DMARCFROMv1 conflicts wit=
h PSD.<br>
<br>
<br>
&gt; x,3 Implement SPF -ALL policies on unused names.<br>
&gt; <br>
&gt; Organizations that have configured SPF to protect their valid RFC5321.=
MailFrom <br>
&gt; domains may not have taken the extra measure of using SPF to obstruct =
names <br>
&gt; that are not used for mail.=C2=A0 While not directly part of DMARC, an=
 <br>
&gt; authentication result of &quot;DMARC=3DNONE SPF=3DFAIL&quot; is a more=
 meaningful result than <br>
&gt; &quot;DMARC=3DNONE, SPF=3DNONE&quot;.=C2=A0 Consequently, it is desira=
ble to =C2=A0ensure SPF=3DFAIL for <br>
&gt; any names that are never used as RFC5321.MailFrom domain names. =C2=A0=
 Since SPF has <br>
&gt; no inheritance, this requires many entries.<br>
<br>
<br>
That&#39;s a well known SPF issue:<br>
<a href=3D"http://www.open-spf.org/FAQ/Common_mistakes/#all-domains" rel=3D=
"noreferrer" target=3D"_blank">http://www.open-spf.org/FAQ/Common_mistakes/=
#all-domains</a><br>
<br>
There used to circulate scripts to generate null SPF records.=C2=A0 It woul=
d help if <br>
DNS hosting services implemented a checkbox to carry out such task.=C2=A0 B=
ut this <br>
if far OT.<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>
</blockquote></div>

--000000000000ef709805c4c21556--


From nobody Mon Jun 14 19:00:37 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 EF1D03A19C8 for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 19:00:35 -0700 (PDT)
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 lFomTd9MfkxJ for <dmarc@ietfa.amsl.com>; Mon, 14 Jun 2021 19:00:33 -0700 (PDT)
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 AB6B23A19C7 for <dmarc@ietf.org>; Mon, 14 Jun 2021 19:00:33 -0700 (PDT)
Received: from shiny.crash.com (192-184-141-33.fiber.dynamic.sonic.net [192.184.141.33]) (authenticated bits=0) by segv.crash.com (8.15.2/8.15.2/cci-colo-1.16) with ESMTPSA id 15F20LT3063225 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NO) for <dmarc@ietf.org>; Tue, 15 Jun 2021 02:00:30 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 15F20LT3063225
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1623722431; bh=Xu1gn+kMomthUYYjhMGe6hIHH5aKo397uMS1gxHq300=; h=Subject:To:References:From:Date:In-Reply-To; b=VJgkexHCS+9oIjGC0bDLaUHB8QVEUsbvbYSzhFV47m/3aisDCNr3HqaU+ExyJk7b7 ZjjtjDkx2Hd0BKL7SBVjd0pcW4a6zsGIRZxA/hh1w255iS9a4VvatDyFxi2lOt8ZGf BK/XmBR0X0cDGzAjoy6XEuwcQsUpUZAEcuGk5OJ2MHNMDGRphxIRXLTLlEEYqlrcA5 z7EWPGieAv+1PQhUwPit5QSm0AELnMS7PZR+riDjaQC0hPqKlcTsZjAskE17NLVpxS Ks6Lu+05Lei8utGmwnL5arZl71xs/JE01YjA7AQxjN6QCblZu2TMIqP0aQ+WOP5x0K tZVWU6ew/Qseg==
X-Authentication-Warning: segv.crash.com: Host 192-184-141-33.fiber.dynamic.sonic.net [192.184.141.33] claimed to be shiny.crash.com
To: dmarc@ietf.org
References: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Steven M Jones <smj@crash.com>
Message-ID: <9eec190f-c8a6-273e-f7fe-4a25ee057c55@crash.com>
Date: Mon, 14 Jun 2021 19:00:43 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB4351C05DCCFD04F0C7B3F766F7319@MN2PR11MB4351.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Tue, 15 Jun 2021 02:00:30 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QHveeiqIzK6piaDwFWgo2214X2E>
Subject: Re: [dmarc-ietf] Sender-supplied decision matrix for passing DMARC
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jun 2021 02:00:36 -0000

On 6/14/21 10:09, Brotman, Alex wrote:
> Does this make everyone cringe, or perhaps worth a larger discussion?


This was considered (repeatedly) during the original DMARC work, and I
believe again while it was being put into RFC7489 form.

It was rejected because it increased the likelihood of broken/invalid
records for the overwhelming majority, while providing complexity that
relatively few senders wanted. And they could usually get what they
wanted by other means.

I would not be in favor of adding more complex policy expressions.

--S.




From nobody Wed Jun 16 04:34:06 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41A883A129D for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 04:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VOpJKEB5Cq09 for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 04:33:59 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B89E3A1295 for <dmarc@ietf.org>; Wed, 16 Jun 2021 04:33:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1623843234; bh=nfHaKFUm0jgg10hEvG/oBuK+bud9J0WJ8XGYJILfnVA=; l=1044; h=To:References:From:Date:In-Reply-To; b=BgXH6XXVUlnGhIWwuERc17CzFdJYB0jWM70B8dqPp265ZLFkBJ2LnekHP0goxMvoD ZcJMMXMqnenvIbETDczQgfiKz2nnO1Fey1RZUlupbH3DOcIy5qtxVYB7j8AJg5hHYd Y/EqylTeM8iKnedOI9HkKdarwhDpWrPiRHcs/Bv7kdt2vopvQ4ny9maFl5vCt
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 00000000005DC03D.0000000060C9E1A2.0000478A; Wed, 16 Jun 2021 13:33:54 +0200
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <CAH48ZfzuM298fkmhoZtH1ZbK=9Ne9EYtyTYNV27PSsPBW=Gq-w@mail.gmail.com> <1a666b47-d556-e758-f4ce-05de79c449d1@tana.it> <CAH48ZfxxUjvfHsd0QKwXbOqZLyeqhVmzORPekJBoPcwAb8tiiA@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <05352758-3a50-2ba1-e6a9-f31174a32bc4@tana.it>
Date: Wed, 16 Jun 2021 13:33:53 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfxxUjvfHsd0QKwXbOqZLyeqhVmzORPekJBoPcwAb8tiiA@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/N0wvLYfnpgAWP-XVs5YyrkBXpYE>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jun 2021 11:34:04 -0000

On Tue 15/Jun/2021 01:19:03 +0200 Douglas Foster wrote:
> It took me only one day to find examples of this;,non-existent subdomains used 
> on legitimate messages sent by mailing services.  The FROM suffix correctly 
> reflects the parent organization, but the full email suffix does not appear in 
> DNS.


Me too.  I reviewed my logs for 2021 and got this:

88 NXDOMAIN found out of 160,473 messages:
35 bounces (empty mailfrom),
26 not found host in an existing suffix,
27 totally astray.

Except for bounces, which just reflect a poorly configured server, I wouldn't 
swear to their legitimacy.  For the few samples of which I still have the 
score, it was high.

However, to reject based just on NXDOMAIN is too harsh.


> This situation means that we cannot distinguish between valid and invalid
> email suffixes using DNS alone, we must require domain owner signalling.

I'd agree, but the idea of suggesting to signal such lack of registration over 
the DNS is to diabolically persist on an error.


Best
Ale
-- 


















From nobody Wed Jun 16 09:01:21 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 D15A93A1D96 for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 09:01:18 -0700 (PDT)
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=HU3B79m+; dkim=pass (2048-bit key) header.d=taugh.com header.b=kMw07kju
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J3MS37L41pKs for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 09:01:13 -0700 (PDT)
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 3D5DC3A1D9E for <dmarc@ietf.org>; Wed, 16 Jun 2021 09:01:13 -0700 (PDT)
Received: (qmail 22504 invoked from network); 16 Jun 2021 16:01:11 -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=57e6.60ca2047.k2106; bh=6kHafs7kiUa0aoNWBg2N7VRL+kFEPAaR/1Ql/y+cgEY=; b=HU3B79m+wjTheAYGSfAXyS7c3eu6d84Tcxbw3LixaKWBaBusp9l4pD1/b2MalowQYu3LQLqGzu3AE56GgSIc/+kGamUB6jste08safU/oKkxKs7S/UwPWBda1lCn2vdbBjAmo/h0NbJIr87WBrghleHxxiSIwep1W996NJFd6XlGRh3Itkhr3UGbUT871plqZIkcBf2QTUQTUsnCwzmDW9qRzfGMl6AnvHIsV2tCRYEvnqVL3rRvOYP7MZczIoMQdNyVBJJTARYc9xBAP8ZFLK5JPGyUY5WAsxxPIrou+A/gdcpE2/gSYdiS1ocEJZjoYatzzDWS/jdCfmN+uZS67A==
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=57e6.60ca2047.k2106; bh=6kHafs7kiUa0aoNWBg2N7VRL+kFEPAaR/1Ql/y+cgEY=; b=kMw07kjuSkMEcixleL2SRbuIZUAG/hoi7xMY33mfOMwAu446hB5oBXxgS64e5PFXIlQN7lm7iCSjrCcPYsDykItBRilWjwns9p+F8m0keIoJbcIfQyy05PEGk8cXbx7HCk5dGyhn72y5SVpOWWHo9irvWCmomMGcqY7D2P5gqoQ7+HMLiCbGMZPp1eBtr0w9plFziaP2ce3LLFvC2GTcgreO3xZXxdf04HomRcnXCuB7gWwZzYPpa66RLf/z6JQQ1yejmHgtQimt+1FPWNJsN10G5olMyJffNqIFFtwJ+wuIC6tYbYTvKxa/ge/h2fFiGajsrIkk3trGi0VuJFS09g==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 16 Jun 2021 16:01:10 -0000
Received: by ary.qy (Postfix, from userid 501) id 09D6011E70FD; Wed, 16 Jun 2021 12:01:08 -0400 (EDT)
Date: 16 Jun 2021 12:01:08 -0400
Message-Id: <20210616160110.09D6011E70FD@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <05352758-3a50-2ba1-e6a9-f31174a32bc4@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/bnZSznRXHuCJgYGOEx3LgaDpb3o>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jun 2021 16:01:19 -0000

It appears that Alessandro Vesely  <vesely@tana.it> said:
>However, to reject based just on NXDOMAIN is too harsh.

I dunno, in my experience it's quite common, and if you do, the chances of losing a message you care
about are negligible.

In any event, this has nothing to do with DMARC.  If for some reason you want to do a DMARC evaluation
of a non-existent domain, you can use the organizational domain or I suppose PSD.

R's,
John


From nobody Wed Jun 16 10:51:25 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 741473A20E5 for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 10:51:23 -0700 (PDT)
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 1vXNybjLS5cx for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 10:51:18 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90AB53A20E4 for <dmarc@ietf.org>; Wed, 16 Jun 2021 10:51:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1623865870; bh=iTC4Mz5QojbG3ZdWHHg/hvW3baueCKKD6CnMAReo4Ac=; l=1056; h=To:References:From:Date:In-Reply-To; b=BM12dZUHZMVaTVFZaldKP9dU0AWy1KZrirx7CcQ8aLviA/noClDsi/U7tE/EfVq7x qu5yCGl1E1V5C93eOtndzcSLLm9OEB2ByvUHl1ldhawan1nLzF7y+zhhrhcoJn9B4K mRf5Fhvwt0qfHxWMYT9rBU0hhlYpWE1PiCuO2zgSpYJjbnziXq4LvWY37j4ek
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 00000000005DC03D.0000000060CA3A0E.0000712D; Wed, 16 Jun 2021 19:51:10 +0200
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210616160110.09D6011E70FD@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <71e61630-0bc8-c9f1-6e7c-5267889c15af@tana.it>
Date: Wed, 16 Jun 2021 19:51:09 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <20210616160110.09D6011E70FD@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/zWQdfLnl14LCxBeEcq48ApPuXzQ>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jun 2021 17:51:24 -0000

On Wed 16/Jun/2021 18:01:08 +0200 John Levine wrote:
> It appears that Alessandro Vesely  <vesely@tana.it> said:
>>However, to reject based just on NXDOMAIN is too harsh.
> 
> I dunno, in my experience it's quite common, and if you do, the chances of losing a message you care
> about are negligible.


It's been customary to reject NXDOMAIN in smtp.mailfrom since when I recall it. 
  To reject NXDOMAIN in header.from is (was) an ADSP feature which doesn't seem 
to be very widespread.  DMARC dropped it a long time ago.


> In any event, this has nothing to do with DMARC.  If for some reason you want to do a DMARC evaluation
> of a non-existent domain, you can use the organizational domain or I suppose PSD.


It might make sense to reject that ~30% which doesn't even have an 
organizational domain (dubbed totally astray in my previous post).  But I still 
receive From: <please.post@publicly.invalid> on a mailing list.  Rejecting that 
risks getting unsubscribed.  Perhaps mailing lists deserve a special permission...


Best
Ale
-- 
















From nobody Wed Jun 16 11:02:31 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 476993A212D for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 11:02:30 -0700 (PDT)
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=DF5qclqs; dkim=pass (2048-bit key) header.d=taugh.com header.b=HN7xkhgt
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96Tp8G6hYjZA for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 11:02:25 -0700 (PDT)
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 392AC3A212A for <dmarc@ietf.org>; Wed, 16 Jun 2021 11:02:25 -0700 (PDT)
Received: (qmail 62959 invoked from network); 16 Jun 2021 18:02:23 -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=f5ed.60ca3caf.k2106; bh=BLJMvBAjukk/yLTjunXjxlIsj6spZ6S2qA9pMEYLz1s=; b=DF5qclqsnG0gwkrz0/5WTSJhPpuOFWbMe0HcxaDupK37HPrEVNiaaem08CGwaby9hq6q/B7x0ZbwpOTOQ35OaB7nmjyI8ci1o0SnXcbqgqWak8IdPuxNseykUQepMehe7J5TvAN9UlBBfanuF6x8Sy5mxz9UN9lW0C81UPaV9RQr8mTMycHkca7x3UR97pbSjzSCj2qjN1NAlOJNiN0c6zxFrX7xwr2k/9Vr7jPUSCXxc3nFBYiba9TviXHUi+5R0UtsHAU4Yz7767aGK/2vRomAjonVmoWl7j0dY9A8ncJaucoSKyhSadUekru/RMRNvcth9dz8UoWJDl7T5/HOBQ==
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=f5ed.60ca3caf.k2106; bh=BLJMvBAjukk/yLTjunXjxlIsj6spZ6S2qA9pMEYLz1s=; b=HN7xkhgtj+/51oJglyy8z3wC4Pix3Rl8nCqEI4C7gwffwWXqH2PmlAdvVanr2eOe17ME+CUTgwgi1TpT4B5CXS8mlI/OL9XCLbRz1gfxp+LpesiAlmWMhgJ/V0/B4TyADikoe4lltqTIDZV1P8g5WKsnpnLVVcwp8Ap0YZ2Mz15s3CxeU2m3jToKxDRSwi99JNFMCzSyxFcEzmhJbNkWJvq+Sveolmhik+6cjAxs8iaupe9H1UucTCJ1xsGiF87OLULs8X0jT5qpqCEjSgfzSEMX8Umdp7TXjLNxvtmXKLKIL2bckIZ9wAA0SW4+ChCfoVo5ogY/z8NvJnUGdzPqkQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 16 Jun 2021 18:02:23 -0000
Received: by ary.qy (Postfix, from userid 501) id 53DC311FBCDC; Wed, 16 Jun 2021 14:02:21 -0400 (EDT)
Date: 16 Jun 2021 14:02:21 -0400
Message-Id: <20210616180222.53DC311FBCDC@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <71e61630-0bc8-c9f1-6e7c-5267889c15af@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/88X_01-UUxG_fnwBItgB4Zv7i4E>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jun 2021 18:02:31 -0000

It appears that Alessandro Vesely  <vesely@tana.it> said:
>It might make sense to reject that ~30% which doesn't even have an 
>organizational domain (dubbed totally astray in my previous post).  But I still 
>receive From: <please.post@publicly.invalid> on a mailing list.  Rejecting that 
>risks getting unsubscribed.  Perhaps mailing lists deserve a special permission...

Or perhaps mailing lists should refrain from forwarding messages from cowards who
use fake addresses and don't sign their mail.

Either way, I still don't see what this has to do with DMARC.  Let's close ticket #112 and stop.

R's,
John


From nobody Wed Jun 16 11:28:42 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 CA28D3A2204 for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 11:28:39 -0700 (PDT)
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 s3_Vz8mQlnD4 for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 11:28:34 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AAB53A21BD for <dmarc@ietf.org>; Wed, 16 Jun 2021 11:28:34 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id u20so2670978qtx.1 for <dmarc@ietf.org>; Wed, 16 Jun 2021 11:28:34 -0700 (PDT)
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=YX92Xi2oAkIPHZb+Qh5B5pordt7Q1QE1L/3WZfaG4O4=; b=QU97IFXRPNne3+V6j+yOOiKl6nd8FHVJJ68MOMBnxEDod3KhanVHubH3O0XLaYuzoN QB/YQBKxHdKiP31gF0RtsTOkiLzE0GXZSBubYyJGxT+aswCDhhNlJ7iPnTROUb5rpZyn SimCd0N68Yk1m1Fin61z/qVkxbjdifEgR0t5YhKeSHjUPiLLYyAp8+IXc28s4sfUTZ1s bHfcndixNfGychIF9+B4iTNQH1Ff9epT/7lOSn4B79PwGLqeUsrDhxPTGZ1SOXLvQu/v k2UoIdXZ+crp0zFaEqmA754cYMScHFbJJOVOfstxtwtI21SDqhHCo4SS9cEffa9OxbFc Qpvg==
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=YX92Xi2oAkIPHZb+Qh5B5pordt7Q1QE1L/3WZfaG4O4=; b=gpb5Pj80mydVIYdWcTpreG8Lo5Z5TfX0fr/43tfOCKzekgMzNb4dFX/wxcJ2v2pM05 ZhrGEBvdSwkxt8qGKZueZq1xg3ae3D4nC8saz1tW41tP+l8dZFs4aSoxTYDplaWBRVZ9 qBiR2OSKLl1D8FCF3+Z4FrsLZ/Gc3hkHaKcBTd9qCaSTbIuZswLs6nUz8hN8bpd3UC/t XbhqlO/UP2+MzYlPJfW9m9pqrxTdqGDsI3HlEVXADDLtzTjdrwoVaFULBxH8TuyK/e0P Hf1Qj1n+n0wk2OUwNSzqFKnf4ZBgYZgvmNN5yzSE4qz6ggRzY9Iav1CmYSNWJ17qcVQg U84g==
X-Gm-Message-State: AOAM533FNU4BOpJ/7a1L2r+7ChC1LW7XnSdabCdavxFd8qaKt/uXPs0c vxDRYDFzAiVsI7XAk4OTQfeWvONbudR0D1sv6CqbpSao
X-Google-Smtp-Source: ABdhPJz76sYpTZTH9+sAXXH57bQ5+l8jPPlNsKb5LGL8iQU3CtVw2hBkoJRfqlB/VMq3/Lb8RjtPFX1RT6aXrg5L3ms=
X-Received: by 2002:ac8:1098:: with SMTP id a24mr1204909qtj.34.1623868112983;  Wed, 16 Jun 2021 11:28:32 -0700 (PDT)
MIME-Version: 1.0
References: <71e61630-0bc8-c9f1-6e7c-5267889c15af@tana.it> <20210616180222.53DC311FBCDC@ary.qy>
In-Reply-To: <20210616180222.53DC311FBCDC@ary.qy>
From: Dotzero <dotzero@gmail.com>
Date: Wed, 16 Jun 2021 14:28:22 -0400
Message-ID: <CAJ4XoYeBDekxPzPsjxpt-MC2Jt-bk0TLyiTWuP+XXNB+YYyD7w@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="000000000000095b0805c4e642bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/FYLGYBkmzhfkcQVPirxRS768hZ4>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jun 2021 18:28:40 -0000

--000000000000095b0805c4e642bf
Content-Type: text/plain; charset="UTF-8"

On Wed, Jun 16, 2021 at 2:02 PM John Levine <johnl@taugh.com> wrote:

> It appears that Alessandro Vesely  <vesely@tana.it> said:
> >It might make sense to reject that ~30% which doesn't even have an
> >organizational domain (dubbed totally astray in my previous post).  But I
> still
> >receive From: <please.post@publicly.invalid> on a mailing list.
> Rejecting that
> >risks getting unsubscribed.  Perhaps mailing lists deserve a special
> permission...
>
> Or perhaps mailing lists should refrain from forwarding messages from
> cowards who
> use fake addresses and don't sign their mail.
>
> Either way, I still don't see what this has to do with DMARC.  Let's close
> ticket #112 and stop.
>
> R's,
> John
>

+1

Michael Hammer

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jun 16, 2021 at 2: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">It appears tha=
t Alessandro Vesely=C2=A0 &lt;<a href=3D"mailto:vesely@tana.it" target=3D"_=
blank">vesely@tana.it</a>&gt; said:<br>
&gt;It might make sense to reject that ~30% which doesn&#39;t even have an =
<br>
&gt;organizational domain (dubbed totally astray in my previous post).=C2=
=A0 But I still <br>
&gt;receive From: &lt;please.post@publicly.invalid&gt; on a mailing list.=
=C2=A0 Rejecting that <br>
&gt;risks getting unsubscribed.=C2=A0 Perhaps mailing lists deserve a speci=
al permission...<br>
<br>
Or perhaps mailing lists should refrain from forwarding messages from cowar=
ds who<br>
use fake addresses and don&#39;t sign their mail.<br>
<br>
Either way, I still don&#39;t see what this has to do with DMARC.=C2=A0 Let=
&#39;s close ticket #112 and stop.<br>
<br>
R&#39;s,<br>
John<br></blockquote><div><br></div><div>+1</div><div><br></div><div>Michae=
l Hammer<br></div></div></div>

--000000000000095b0805c4e642bf--


From nobody Wed Jun 16 12:41:46 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 6440D3A2453 for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 12:41:44 -0700 (PDT)
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 E9PaAY2J9l0i for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 12:41:39 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2134.outbound.protection.outlook.com [40.107.22.134]) (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 464483A2450 for <dmarc@ietf.org>; Wed, 16 Jun 2021 12:41:39 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=f8mV/7pWASO3/2JpqfeuKE/l5pE+btUy8x8LPtnDXwSynkaPEy/dsy5UKBpYTQHkqG1aqi+CDDs2T3xWgOc5Pscccz88q4BxiILPlTldK2U4GaBa697XcQy4RRVWF5VC/dxiSgOQj6sJMNKXy/465AHCtpfmsBcvPbWTpWKHeBUc8+GQA4lRakatakM6aDs+NJpjyayjo01npcxi8jB0yKQibsm0syQ8b9HEe+daKXYunq4zv/HrGVzw+xqm1dhMge5YB+RyuDIB4Xq55bhSJPuPgat4dvyDynSy9huGxCD7kR/Mzjt2+AE3559kY6/V+lIZkwMZBbhVxkBE/RFu7g==
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=h4+WwiW/9gDacUdlVg0uoT+vDMwa7cg24SXSQLWXnrs=; b=j1D3xwhYzgpbwKI5CzVC3PVp0xo6GAqALYkSnoRNZFiwmRVs6E8u3itjcg8E6/3EyuUpe9sNqQFPTmInncuz2jpyakGGXdxzGbj2KoCE3sso/IVLZMIlFmRhOSY1zqJzIFQl4fw1fE1bxdpQuHQVpru7Qw9flnmscLTtJzYEtYoxhOfU0Ju+PsmE0E08B5MDFtQw9EkCXB9bSWYJNgdEF4/vBfXU705XOzLJExPOu606hn3TNUnVah/ZdFEAdj6cdoHvu0fO3La13yJJUk/VNbCFiXETnmW3AKGfrkZhLuT0LBBnaAV/rQy/JyDDlQBYPtVSyPtmnHB51GjAVshZTw==
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=h4+WwiW/9gDacUdlVg0uoT+vDMwa7cg24SXSQLWXnrs=; b=QIRl1EFZnpXoXu3TIXpl7W6jokoB9QjP8nx5RPn0h8rJ8UcYhS4Ei5ZX7ytL6R395z4Vi4/g2d8kCyjKUVfG/GwgPY5eJKcHPKR0nF2SbbFQCgMX4u2gNZ9OIh5ZyCwSIb0GigrRf79t8tATr5VPThbN0jUTuaskQgK9hQ+FPx8GL+5CBMIgcZ8Ztrx25G0UaAZgDs2fZYBoKhqeEH9Rk2DE/jFW0lylBiO8+eWcKLFm50pcnMvA8eVlHWyFP0cN9v2INQa8d1eNFE/mvqZx4k2fSpxlnP8WcDQAaDLDQXLRO+IvAE9e8WLZoan2dl8gz+8Ux4V5vVDf4l9+xuclDQ==
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.4219.25; Wed, 16 Jun 2021 19:41:35 +0000
Received: from VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::d066:24d0:78c4:f187]) by VI1PR01MB7053.eurprd01.prod.exchangelabs.com ([fe80::d066:24d0:78c4:f187%4]) with mapi id 15.20.4242.018; Wed, 16 Jun 2021 19:41:35 +0000
From: Ken O'Driscoll <ken@wemonitoremail.com>
To: John Levine <johnl@taugh.com>, "dmarc@ietf.org" <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
Thread-Index: AQHXX4pPIJTr6GcxlUGz7qrJbCn59asTXR2AgADLIoCAAl+kgIAASqsAgAAevYCAAAMhgIAAG2yv
Date: Wed, 16 Jun 2021 19:41:35 +0000
Message-ID: <VI1PR01MB7053BE4BBE929FEB7432C7E7C70F9@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>
References: <71e61630-0bc8-c9f1-6e7c-5267889c15af@tana.it>, <20210616180222.53DC311FBCDC@ary.qy>
In-Reply-To: <20210616180222.53DC311FBCDC@ary.qy>
Accept-Language: en-GB, en-US
Content-Language: en-GB
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=wemonitoremail.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8df656c7-bc90-415d-51d6-08d930fec03a
x-ms-traffictypediagnostic: VI1PR01MB4270:
x-microsoft-antispam-prvs: <VI1PR01MB427025DE0D0A96392EF4C4E2C70F9@VI1PR01MB4270.eurprd01.prod.exchangelabs.com>
x-ms-oob-tlc-oobclassifiers: OLM:191;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: lMTMuxDp2bREJsmty5EQB5bnSaLJtdBDpWPVbYKuEhnSK9rp97nHiDm7yUYjRb7dzvsIfrDHKV699J/w5SQLDXnUT/Y8DOLd9kRb8sEaxE0bEfjfKCAYBf2Hx1Uy6iSY72PaoESIbmlT06UjvQ5ElcrqTK4nyGEwJyft56XcUPsL0n9P4ukZ0KWpL38ocZd2eX87YIG/UDy0s92I21yKQ31u1U8odS+AyiYeSolw4XmQqi3nZWuEORpjk+T04vawsNa0tWn28b+4FWF2CFQtsdX1gTFlNnz/oqh5uX+5kOsLSL3ZrFrodhJD+Xp29iYvLwEDXCvGKLQfk+LxAhBqCVU1Gtph5+m/m38ZJuz8ZnWuzba1LqxpSfUmgIVJGIAfPIsn55s/BgqrhndrKuWrTfZFWMe8N59FlhtcImPiHqmGEagkVvk8EwkmocMMVSNhVCFFid24QcSTDMdi1FHH8uD2lKBq6qDuzjVzYhuDWX7PfsbkDpHrI5DXUG2mRDhKGV+3fJzUNKjxwJV9KHmzQz5/AhWxqYTGAJjbFbXs3rB8Q9xDcH9R36aESD2IN0CJRhkvoGNgBSjg3hWU+VcqunstY3ad6Jwa3aooTTwmr9nuZ30gYlt3BT08/rfwufyRHYg1PSDonBU1PQFRfN64ReugiKLtERD9ldyXZVnSXIEhqmARU5jxUkPjjtYsA6V1QGwQDeKrz9fhJiz3cEMzRg==
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:(396003)(376002)(366004)(346002)(136003)(39830400003)(9686003)(186003)(53546011)(33656002)(966005)(478600001)(4744005)(86362001)(5660300002)(55016002)(26005)(2906002)(8936002)(6506007)(66446008)(83380400001)(66476007)(71200400001)(91956017)(66556008)(38100700002)(76116006)(8676002)(7696005)(122000001)(52536014)(110136005)(316002)(64756008)(66946007)(166002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?1+j1tJvMVmon1sfAZbr2xA5DrZPOtqw7AIWfeVyUGDIGfYK7iJPuKkZhRZ+u?= =?us-ascii?Q?dLDO62lMj2PBT9RC4v6ZdDOXjSC18B7DDWcFROp4KFBWi1483x+GnnskUqxm?= =?us-ascii?Q?haBB6yaOZeENzl7sJvJSDG/u/gIYfniz1XK9FCZa9rtiL5eP/yy5GCDmkilD?= =?us-ascii?Q?DKs/uZTIW4UofsATVujkwXORD/GQZTIivXBdiBTRWfu1tLQnpDHwuFGtcQgr?= =?us-ascii?Q?W+rgTSOEcP44xdUNJ3KeH5xR4k2NEjj9/RjSiWvjKj2QtvoHsow6ju9oX399?= =?us-ascii?Q?jozpGzJgeSlKmKFJlCmvwZO0rfSsZWPItaCjg29gVJaJ9Gf3RDsos5cGI1a4?= =?us-ascii?Q?3qultzhknwC01h7G8iWXtuu4ysk+lym54TGKmtTq+o/dhqMO5PimAoziekjJ?= =?us-ascii?Q?i9sxZr8RQcDDN6xmCaTH5Y0bfmQ2+6/4/Mt5fEJYBGinBskJayWtFecV7iUk?= =?us-ascii?Q?zWj/9BeNnIb5vtjPtPhfyCt/ROlmhPOibhuWfbrZNfj/a/Wjnb4UxgjNTwHg?= =?us-ascii?Q?nNj1rz0hMayIHvxtx7ZAThp8xlEgkvFi5f7uPnyA+7Xu/RQ8laBa7fdIR7+x?= =?us-ascii?Q?n0gjBWlAT7YpIrVrnS8ZjWgdvnFEtOR791vnfgRIUZhwh/Mk7UKuekvM5K9T?= =?us-ascii?Q?HF3fuM4SdHsLoLQjusaIuZR/SwnR6wOsXcCPGuiozZsPMdi5dBVCGtT62sIQ?= =?us-ascii?Q?lIcX2NXrM6hbzXGOVqwE5uSrwpNc9BPL671/DA4GG4h8W92Yj4tmKiP6xEZU?= =?us-ascii?Q?EYf1uSBfDw+L/xwcCLQqMTIvnLwginBQuWAtOf+z37iM8e4ayttV6WPy5Qbu?= =?us-ascii?Q?A2OO9c0pr0D/cxNRx6jwcFAXc4j4G2vtBNzBSr4UaNuGW1OOCreVQkuH1hwE?= =?us-ascii?Q?B6IMkmm1OnOS05MysaRcrB3AopCX0iPuOU3jVKulG/kSJhx9BfsXfkSH/+ej?= =?us-ascii?Q?eRfAw9MOGjl+spVUZdzILEwTI5Za8ecInZke8+4Gm5/r4LaQvSXGyJ60xEHI?= =?us-ascii?Q?Hwre0N+7NEtvjWahQzvb9JHy2As3kbYOsXx7/oTCB8KQ6QV3YwUXuuQGMG/J?= =?us-ascii?Q?zWxO3GrpU7omaGGpy//bHgeaqQzWp+PMup8ubx1HMV9r/Ck3vFKc0heRdioi?= =?us-ascii?Q?tX0GOxLf+mQMcUJVBNsXj97S1+pKIAGX5gkG7CcMXWoleI4mKRirK/1zD+nj?= =?us-ascii?Q?+5shNrOTTiMBeP1jCpDda2l3oILzsx0XC8kHRrz+z3sJ2Q5zsDp3vH1q+KZi?= =?us-ascii?Q?kOBR72Zk8JRZkQg+662cTQKSTsg1r/qEjpe6T/fUycuzrH7VjNQowUyhqpFM?= =?us-ascii?Q?h6+qW+A8skq0U5LE9yrZsVPYkblrGW+GEILneGa4ksrqZQ=3D=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_VI1PR01MB7053BE4BBE929FEB7432C7E7C70F9VI1PR01MB7053eurp_"
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: 8df656c7-bc90-415d-51d6-08d930fec03a
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Jun 2021 19:41:35.3315 (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: zhE/lVhVhRbt0QWc9lMf1ktIGhc8wd2hyTCtdbMl9YT6XP65uBybkiHLFiEmrPEUT6YTLyn4DTatHFFrTOxGSw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR01MB4270
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9FR--wuAThhQKa12M6XkfIVj2_8>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jun 2021 19:41:45 -0000

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

+1

Ken.

________________________________
From: dmarc <dmarc-bounces@ietf.org> on behalf of John Levine <johnl@taugh.=
com>
Sent: Wednesday, 16 June 2021, 19:02
To: dmarc@ietf.org
Cc: vesely@tana.it
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language

It appears that Alessandro Vesely  <vesely@tana.it> said:
>It might make sense to reject that ~30% which doesn't even have an
>organizational domain (dubbed totally astray in my previous post).  But I =
still
>receive From: <please.post@publicly.invalid> on a mailing list.  Rejecting=
 that
>risks getting unsubscribed.  Perhaps mailing lists deserve a special permi=
ssion...

Or perhaps mailing lists should refrain from forwarding messages from cowar=
ds who
use fake addresses and don't sign their mail.

Either way, I still don't see what this has to do with DMARC.  Let's close =
ticket #112 and stop.

R's,
John

_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body>
<div style=3D"color: rgb(33, 33, 33); background-color: rgb(255, 255, 255);=
" dir=3D"auto">
+1</div>
<div id=3D"ms-outlook-mobile-signature">
<div><br>
</div>
<div>Ken.</div>
</div>
<div id=3D"id-4582805f-6694-41c7-a9a3-8e83c34b4f79" class=3D"ms-outlook-mob=
ile-reference-message">
<div style=3D"font-family: sans-serif; font-size: 12pt; color: rgb(0, 0, 0)=
;"><br>
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg"><strong>From:</strong> dmarc &lt;dmarc-bounces@ie=
tf.org&gt; on behalf of John Levine &lt;johnl@taugh.com&gt;<br>
<strong>Sent:</strong> Wednesday, 16 June 2021, 19:02<br>
<strong>To:</strong> dmarc@ietf.org<br>
<strong>Cc:</strong> vesely@tana.it<br>
<strong>Subject:</strong> Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed=
 language<br>
</div>
<br>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style><font size=3D"=
2"><span style=3D"font-size:11pt;">
<div class=3D"PlainText">It appears that Alessandro Vesely&nbsp; &lt;vesely=
@tana.it&gt; said:<br>
&gt;It might make sense to reject that ~30% which doesn't even have an <br>
&gt;organizational domain (dubbed totally astray in my previous post).&nbsp=
; But I still <br>
&gt;receive From: &lt;please.post@publicly.invalid&gt; on a mailing list.&n=
bsp; Rejecting that <br>
&gt;risks getting unsubscribed.&nbsp; Perhaps mailing lists deserve a speci=
al permission...<br>
<br>
Or perhaps mailing lists should refrain from forwarding messages from cowar=
ds who<br>
use fake addresses and don't sign their mail.<br>
<br>
Either way, I still don't see what this has to do with DMARC.&nbsp; Let's c=
lose ticket #112 and stop.<br>
<br>
R's,<br>
John<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
dmarc@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc">https://www.ietf.or=
g/mailman/listinfo/dmarc</a><br>
</div>
</span></font><br>
</div>
</body>
</html>

--_000_VI1PR01MB7053BE4BBE929FEB7432C7E7C70F9VI1PR01MB7053eurp_--


From nobody Wed Jun 16 14:43: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 2AB7B3A27CF for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 14:43:25 -0700 (PDT)
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 AM-xpg7e-UVT for <dmarc@ietfa.amsl.com>; Wed, 16 Jun 2021 14:43:20 -0700 (PDT)
Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6A5C3A27AC for <dmarc@ietf.org>; Wed, 16 Jun 2021 14:43:20 -0700 (PDT)
Received: by mail-oi1-x234.google.com with SMTP id d19so4091571oic.7 for <dmarc@ietf.org>; Wed, 16 Jun 2021 14:43:20 -0700 (PDT)
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=BF0Ov+kMRb425eTO5JJkTKHmLogyd65SCvbGqjSae6g=; b=eOqpqwkvkhqMrxo06XW6AAW0mpQ6wVJ0w3/a2+pjb4nvHm18HqolD/mu1x25UG55If CTSpHpjcu0sGWKAspSetcpGUM2Qm41PcSA0Lo0THThharHaq07Qvx3uMiZpLgFV5wxVU ctMmD3/VJIPGg1r7QRD1OSX8cMcWqhfXLmXbjsZDTCydfw/y1f6yaYZQ+DkQCE7elgzy L3JPom3yfXL1doa7KDjxt4Umyu8WpUigYAfVkvNCxqB6YBtuz7wTD1MbBHoGFri6KM4J efygd+cBfD0JBFuz/7cktBIvp6Cjk3wyKSGZEWuokD0GFGZfW5zlA3MBV3OeXGVEygI+ ulig==
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=BF0Ov+kMRb425eTO5JJkTKHmLogyd65SCvbGqjSae6g=; b=huJTia/9WPsbqxdRHyKGkIhCcNi1M1JHZn6aV0LF9YnO/v9FF5qtkFQaEQXVmrIKqe t1YbXRsjptcG+cBD4t4lC8HyUIto0LY/s8GcKkaSkx3JQ6G7WsHkyZa/7haV3AGWkCTz wjPNBmFefG7hDuattNXQO3r3tB5mjGhzqUxnRuM8kccFv0vU6AUW1Od/EHCuHiQMaIPM W70VIf3orM941Rpol3Ojph0kk5wHrw7POpPuNnrjJ1lQIJK6qYn/3Ku+2h+h0WFljyeY 4tgr6bskisC8LAjG4+E7wX7/9aDV1laANaBejL2jJ0QcWORcTiCy8tIwPsjtQBA5ozA3 dB8g==
X-Gm-Message-State: AOAM530FG3VUybEU1ToUJ3DQReBsZANVp7+awzpuKFurACXK7IlQcsbP LBklqpfrc9Ho8g8+L/kvZBbluisFS9o/awhSwEdXmRPdi6M=
X-Google-Smtp-Source: ABdhPJzVa+wT8tKajVI8+ZI5kb7/dKbOxtnhtuVJ9U36cOL1iZfIteA67FzR08dIcfqQ6IT/TWosIajLQyjtWivwl6c=
X-Received: by 2002:a05:6808:130d:: with SMTP id y13mr2048047oiv.146.1623879799502;  Wed, 16 Jun 2021 14:43:19 -0700 (PDT)
MIME-Version: 1.0
References: <20210616160110.09D6011E70FD@ary.qy> <71e61630-0bc8-c9f1-6e7c-5267889c15af@tana.it>
In-Reply-To: <71e61630-0bc8-c9f1-6e7c-5267889c15af@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 16 Jun 2021 17:43:08 -0400
Message-ID: <CAH48ZfyYSW5003cxgP0r_skzSdfNvV9FL=sY_32PwQ1dWXxFCg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009b7cdf05c4e8fa59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VuI3fKBcSBXMGpVOb37W6GiYu08>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jun 2021 21:43:25 -0000

--0000000000009b7cdf05c4e8fa59
Content-Type: text/plain; charset="UTF-8"

You or the others seem to be confusing NXDOMAIN on RFC5321.MailFrom lookup
with NXDOMAIN on RFC5322.FROM.  The issues are very different.

NXDomain on the MailFrom lookup says neither the SPF policy nor the SMTP
domain exist, and therefore there is no reverse path.   Rejecting such
messages makes a lot of sense and, as has been said, has nothing to do with
DMARC.

NXDomain on RFC5322.From is a completely different issue.    It means that
the name is only used for service provider messaging, and is therefore not
linked to any IP address or other physical infrastructure.  It affects the
ability to define a meaningful NP test.   The issue becomes irrelevant to
DMARC if and only if we drop the NP policy idea completely.

The proposed MX/A/AAAA/SPF test has two significant problems:
- It incorrectly classifies some names as NP because they do not need
MX/A/AAAA/SPF records because they are not tied to an IP address, and we
have provided a very poor mechanism for a domain owner to come into
compliance.
- It incorrectly classifies some names that are not used for email as not
NP, simply because they have an A/AAAA record.   It provides no method for
the domain owner to signal that the name is not used for email and
therefore should be treated as NP.

With the expectation of significant errors in both directions, we do not
have a usable definition of NP.

Doug Foster



On Wed, Jun 16, 2021 at 1:51 PM Alessandro Vesely <vesely@tana.it> wrote:

> On Wed 16/Jun/2021 18:01:08 +0200 John Levine wrote:
> > It appears that Alessandro Vesely  <vesely@tana.it> said:
> >>However, to reject based just on NXDOMAIN is too harsh.
> >
> > I dunno, in my experience it's quite common, and if you do, the chances
> of losing a message you care
> > about are negligible.
>
>
> It's been customary to reject NXDOMAIN in smtp.mailfrom since when I
> recall it.
>   To reject NXDOMAIN in header.from is (was) an ADSP feature which doesn't
> seem
> to be very widespread.  DMARC dropped it a long time ago.
>
>
> > In any event, this has nothing to do with DMARC.  If for some reason you
> want to do a DMARC evaluation
> > of a non-existent domain, you can use the organizational domain or I
> suppose PSD.
>
>
> It might make sense to reject that ~30% which doesn't even have an
> organizational domain (dubbed totally astray in my previous post).  But I
> still
> receive From: <please.post@publicly.invalid> on a mailing list.
> Rejecting that
> risks getting unsubscribed.  Perhaps mailing lists deserve a special
> permission...
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr">You or the others seem to be confusing NXDOMAIN=C2=A0on RF=
C5321.MailFrom lookup with NXDOMAIN on RFC5322.FROM.=C2=A0 The issues are v=
ery different.<div><br></div><div>NXDomain on the MailFrom lookup says neit=
her the SPF policy nor the SMTP domain exist, and therefore there is no rev=
erse path.=C2=A0 =C2=A0Rejecting such messages makes a lot of sense and, as=
 has been said, has nothing to do with DMARC.</div><div><br></div><div>NXDo=
main on RFC5322.From is a completely different issue.=C2=A0 =C2=A0 It means=
 that the name is only used for service provider messaging, and is therefor=
e not linked to any IP address or other physical infrastructure.=C2=A0 It a=
ffects the ability to define a meaningful NP test.=C2=A0 =C2=A0The issue be=
comes irrelevant to DMARC if and only if we drop the NP policy idea complet=
ely.</div><div><br></div><div>The proposed MX/A/AAAA/SPF test has two signi=
ficant problems:</div><div>- It incorrectly classifies some names as NP bec=
ause they do not need MX/A/AAAA/SPF records because they are not tied to an=
 IP address, and we have provided a very poor mechanism for a domain owner =
to come into compliance.</div><div>- It incorrectly classifies some names t=
hat are not used for email as not NP, simply because they have an A/AAAA re=
cord.=C2=A0 =C2=A0It provides no method for the domain owner to signal that=
 the name is not used for email and therefore should be treated as NP.</div=
><div><br></div><div>With the expectation of significant errors in both dir=
ections, we do not have a usable definition of NP.</div><div><br></div><div=
>Doug Foster</div><div><br></div><div><br></div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jun 16, 2021 at 1:5=
1 PM Alessandro Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
On Wed 16/Jun/2021 18:01:08 +0200 John Levine wrote:<br>
&gt; It appears that Alessandro Vesely=C2=A0 &lt;<a href=3D"mailto:vesely@t=
ana.it" target=3D"_blank">vesely@tana.it</a>&gt; said:<br>
&gt;&gt;However, to reject based just on NXDOMAIN is too harsh.<br>
&gt; <br>
&gt; I dunno, in my experience it&#39;s quite common, and if you do, the ch=
ances of losing a message you care<br>
&gt; about are negligible.<br>
<br>
<br>
It&#39;s been customary to reject NXDOMAIN in smtp.mailfrom since when I re=
call it. <br>
=C2=A0 To reject NXDOMAIN in header.from is (was) an ADSP feature which doe=
sn&#39;t seem <br>
to be very widespread.=C2=A0 DMARC dropped it a long time ago.<br>
<br>
<br>
&gt; In any event, this has nothing to do with DMARC.=C2=A0 If for some rea=
son you want to do a DMARC evaluation<br>
&gt; of a non-existent domain, you can use the organizational domain or I s=
uppose PSD.<br>
<br>
<br>
It might make sense to reject that ~30% which doesn&#39;t even have an <br>
organizational domain (dubbed totally astray in my previous post).=C2=A0 Bu=
t I still <br>
receive From: &lt;please.post@publicly.invalid&gt; on a mailing list.=C2=A0=
 Rejecting that <br>
risks getting unsubscribed.=C2=A0 Perhaps mailing lists deserve a special p=
ermission...<br>
<br>
<br>
Best<br>
Ale<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>

--0000000000009b7cdf05c4e8fa59--


From nobody Thu Jun 17 00:57:06 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 C09373A11D6 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 00:57:04 -0700 (PDT)
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 cY9Yrkx54qgc for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 00:57:03 -0700 (PDT)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37D363A11D5 for <dmarc@ietf.org>; Thu, 17 Jun 2021 00:57:03 -0700 (PDT)
Received: by mail-vs1-xe36.google.com with SMTP id x8so2510440vso.5 for <dmarc@ietf.org>; Thu, 17 Jun 2021 00:57:03 -0700 (PDT)
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=hNMTATexqciUGoDrdpp9cjA+OXqs1zeBd8tbCaRWeMY=; b=LkDP7qtKdTj1nvUC3Oe0oyL6Rt6u0KZ3ABy6LQfSvj71NlJeWI5IbKUxMwMi/KTeAb OTXdiymiXGzn24dwsLNsUrWp5ehUqVp88Ki9dFpXh/9jvub/vJKuv11bcAxVXSF5qCvH YuuJZygJSJIPHEqGQztmqu1f7SyT3aQjb5Vd5AniFYDTrvIzCUsEFbk0AE2NicnzC8yX S3oy+ENh+V3+x0WlFeHdlYVveHZiIhUl7ZU/R7A+wtof6dDOjj3GTz6MqWMHOMBnwUcb 7qM9bjVpGgQzshNvAZdmENMX5tDAWIzD7NaoJeHLYivaGD/K2NJXtYEYpF3HeQjKC3/s mB3Q==
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=hNMTATexqciUGoDrdpp9cjA+OXqs1zeBd8tbCaRWeMY=; b=OGoaCbHL69PkAih5v8Ae99HLSGCMusXoDKa+13ttVjzkpt4Zbk88ol4PPtKANdjIsU Z0fjMwOZ7/OjlJ0fHb9bFzGxIoIgjijS6E3cVvWCZ3u2PZnTHOSjbR+WoKi360hThZuw 2bztCtXGh10EsHodYfaxQA/wqn1S8bILeCYHdp/tpbklotsjNBk091YbvZNF54uUjAIe ayCL2zQ76kFRp4fWjb1BsdpR3u7Juw05MuIqr8TK9msA9LZgcOQozJwC8zLnrXFoUM8k MEptbyefuUaFcJtZslFJsMIuyjAvavVHci6NxyX2KBZ7hClw0Ev2rcJLxZCHLJYkfVeD woig==
X-Gm-Message-State: AOAM5320/vMqvgRyJO/TIt7nKhibv3NELGwPgFMwDV8PjvJrTttSL7v6 Puddmsg+7ZiPVkRNf8IImThO65+WN8yjqKQKjTA=
X-Google-Smtp-Source: ABdhPJzfj4adii76BoXh/s1Fpd/xvLccsgMKKpIPtd3QPjQzDfVjad4tzINKIMirNjVrUaXSWyHyjeak6gaA6bQYKgM=
X-Received: by 2002:a67:1a45:: with SMTP id a66mr3093916vsa.15.1623916621359;  Thu, 17 Jun 2021 00:57:01 -0700 (PDT)
MIME-Version: 1.0
References: <20210616160110.09D6011E70FD@ary.qy> <71e61630-0bc8-c9f1-6e7c-5267889c15af@tana.it> <CAH48ZfyYSW5003cxgP0r_skzSdfNvV9FL=sY_32PwQ1dWXxFCg@mail.gmail.com>
In-Reply-To: <CAH48ZfyYSW5003cxgP0r_skzSdfNvV9FL=sY_32PwQ1dWXxFCg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 17 Jun 2021 00:56:50 -0700
Message-ID: <CAL0qLwYsTgRJ8PnjG7nAdTJJ54ww2HWtvOGp2EeMqNStjD6X8A@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005c6d4305c4f18d16"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Vnc_HPXIxKF7w1Zq8TiYEtiQrxs>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 07:57:05 -0000

--0000000000005c6d4305c4f18d16
Content-Type: text/plain; charset="UTF-8"

I continue to not understand the defect you're highlighting here.

I think you've expressed yourself primarily in the abstract.  Could you
craft a sample message, sample envelope, and sample DNS context that
highlights the problem you're talking about?  Maybe then it'll snap into
focus.

On Wed, Jun 16, 2021 at 2:43 PM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> NXDomain on RFC5322.From is a completely different issue.    It means that
> the name is only used for service provider messaging, and is therefore not
> linked to any IP address or other physical infrastructure.  It affects the
> ability to define a meaningful NP test.   The issue becomes irrelevant to
> DMARC if and only if we drop the NP policy idea completely.
>
> The proposed MX/A/AAAA/SPF test has two significant problems:
> - It incorrectly classifies some names as NP because they do not need
> MX/A/AAAA/SPF records because they are not tied to an IP address, and we
> have provided a very poor mechanism for a domain owner to come into
> compliance.
>

There's a workaround here: If I want to use a name that is not represented
in the DNS according to that test, all I need to do is DKIM sign with my
parent domain.  That makes "p" apply because now you have an aligned
"pass", which presumably trumps any "np" that's set.

If you aren't signing with DKIM in that scenario, and you obviously can't
pass SPF either, then you can't possibly hope to pass DMARC irrespective of
any test being done on the name's validity.

- It incorrectly classifies some names that are not used for email as not
> NP, simply because they have an A/AAAA record.   It provides no method for
> the domain owner to signal that the name is not used for email and
> therefore should be treated as NP.
>

If they're not used for email, then they're not in DMARC's problem space.

At any rate, since PSD has been approved, I'm hoping the experiment is
underway, or will be soon, and then we might have some actual data about
the severity of this defect and thus also possibly some hints about ways it
can be mitigated.

-MSK

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

<div dir=3D"ltr"><div>I continue to not understand the defect you&#39;re hi=
ghlighting here.</div><div><br></div><div>I think you&#39;ve expressed your=
self primarily in the abstract.=C2=A0 Could you craft a sample message, sam=
ple envelope, and sample DNS context that highlights the problem you&#39;re=
 talking about?=C2=A0 Maybe then it&#39;ll snap into focus.<br></div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jun =
16, 2021 at 2:43 PM Douglas Foster &lt;<a href=3D"mailto:dougfoster.emailst=
andards@gmail.com">dougfoster.emailstandards@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"><div dir=3D"ltr">NXDo=
main on RFC5322.From is a completely different issue.=C2=A0 =C2=A0 It means=
 that the name is only used for service provider messaging, and is therefor=
e not linked to any IP address or other physical infrastructure.=C2=A0 It a=
ffects the ability to define a meaningful NP test.=C2=A0 =C2=A0The issue be=
comes irrelevant to DMARC if and only if we drop the NP policy idea complet=
ely.<div><br></div><div>The proposed MX/A/AAAA/SPF test has two significant=
 problems:</div><div>- It incorrectly classifies some names as NP because t=
hey do not need MX/A/AAAA/SPF records because they are not tied to an IP ad=
dress, and we have provided a very poor mechanism for a domain owner to com=
e into compliance.</div></div></blockquote><div><br></div><div>There&#39;s =
a workaround here: If I want to use a name that is not represented in the D=
NS according to that test, all I need to do is DKIM sign with my parent dom=
ain.=C2=A0 That makes &quot;p&quot; apply because now you have an aligned &=
quot;pass&quot;, which presumably trumps any &quot;np&quot; that&#39;s set.=
<br></div><div><br> </div><div>If you aren&#39;t signing with DKIM in that =
scenario, and you obviously can&#39;t pass SPF either, then you can&#39;t p=
ossibly hope to pass DMARC irrespective of any test being done on the name&=
#39;s validity.<br></div><div><br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div dir=3D"ltr"><div>- It incorrectly classifies some names=
 that are not used for email as not NP, simply because they have an A/AAAA =
record.=C2=A0 =C2=A0It provides no method for the domain owner to signal th=
at the name is not used for email and therefore should be treated as NP.</d=
iv></div></blockquote><div><br></div><div>If they&#39;re not used for email=
, then they&#39;re not in DMARC&#39;s problem space.</div></div><div class=
=3D"gmail_quote"><br></div><div class=3D"gmail_quote">At any rate, since PS=
D has been approved, I&#39;m hoping the experiment is underway, or will be =
soon, and then we might have some actual data about the severity of this de=
fect and thus also possibly some hints about ways it can be mitigated.</div=
><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">-MSK<br></=
div></div>

--0000000000005c6d4305c4f18d16--


From nobody Thu Jun 17 04:13:03 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E68313A1B02 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 04:13:01 -0700 (PDT)
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 mWvyLT8HtTP6 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 04:12:57 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DB8F3A1B75 for <dmarc@ietf.org>; Thu, 17 Jun 2021 04:12:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1623928365; bh=WV44Xj19AAS0Bg1cHa7NmyUFj0Im7n6p6uOtwe2FXg0=; l=968; h=To:References:From:Date:In-Reply-To; b=BTRnPu/tvl6VASUWhoEYeNSZRRbOGaLNcD6YtPkgPgi/V2hvXAkD8RcSuEpmi+QmL wp5NzFuUCHwvL4q7AFACfWS7Nsx1hbu3abxSQchEuSbJBV2vntqAtjHMNuaLSPQfUF 3S9mqKkCgsoHYo8qSEy792QuqfuRubsofLM8M7stGEf4OJlYjj5pF2IyoedQA
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 00000000005DC03D.0000000060CB2E2C.00003C69; Thu, 17 Jun 2021 13:12:44 +0200
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210616180222.53DC311FBCDC@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <6e76e4af-e592-0103-33dc-4cda6b129071@tana.it>
Date: Thu, 17 Jun 2021 13:12:44 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <20210616180222.53DC311FBCDC@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/HxdtMlUkmgmJRJ_qF3jmBXGoLig>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 11:13:02 -0000

On Wed 16/Jun/2021 20:02:21 +0200 John Levine wrote:
> Let's close ticket #112 and stop.


I agree that the definition given in the PSD is clear enough:

    For DMARC purposes, a non-existent domain is a domain for which there
    is an NXDOMAIN or NODATA response for A, AAAA, and MX records.  This
    is a broader definition than that in [RFC8020].

However, by that definition a domain with a Null MX [RFC7505] is an existent 
domain for DMARC purposes.  Perhaps this apparent contradiction could be noted 
by adding a sentence somewhere, for example:

    Even though the bare existence of a domain does not entail that it can send
    or receive email, the presence or absence of the relevant DNS RRs determines
    which policy between sp= and np= is applicable.  If a DMARC record is found
    for a domain that would be non-existent by the above definition, the p=
    policy defined there is still the one to be applied.

Would that add clarity?


Best
Ale
-- 


























From nobody Thu Jun 17 06:36:00 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 DA4703A1FF3 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:35:57 -0700 (PDT)
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, 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=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 3mu6d6mC-A1y for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:35:51 -0700 (PDT)
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 5A3FA3A1FEA for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:35:51 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id o19so4688378qtp.5 for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:35:51 -0700 (PDT)
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=ZsNRkUVcyq+jVpWXGqNMSfcaayANJpzgDoO+QvZ5xSo=; b=MCe3Ypn2IsgO7gNB+thlBZUWls4yzbUGUBIXugACYkqOsGFHvNmlg7yRcySO73q3La QrRul6RRvl+fEhz2S6s0wFEy3Vp3To9XfUCT+tJ7fyva/9DKYd/Gh1JkBDuNWnEbQVBO 7VBYoxfYDXvYWAJ13iKTAXc7dtxjJ1XER8/fkdMjak32dygKqHe3lqC9zmjEXh6z4RIN NFi7FaaJFUPsPH3YTIaVdApmqpee7s8OqIR2nfns27G3GhuYGsUYUiNZLYqMiixPLLMP rTjUCdcC1QGzi0ZFd3eo4/U/9d9IiTDNfd4N05WilvqaGSohc0uX0osySN2kn1gOza3Y 1Dsg==
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=ZsNRkUVcyq+jVpWXGqNMSfcaayANJpzgDoO+QvZ5xSo=; b=CZ1gHb/owcdC2mD9MiIGKOW7FgAsZWD3XW3i58Ld+J/Fh057LmCU1ADbUw39gzfFf/ I1xTViF37iuZ1cdsKBkI6a27p08sqeRQPKdkC3E6pxRXeRIOxyB7WJc0n8Qyex8oZ34D LJubEcBUWTwRN5269artozF3elVg99uBnlw8Jq58XqJE/ytBIh4rLEI+Mq68Gdp/mHX8 ZNIG7HUJFS8oItKi/74Zwp06ePYYB2L6W1kRbtv0lBx6J3//3BI+wwY4BF075O9oRUEe 8ac1maCAPlur56bHrHtO3AB25LXeScSxKZjoTXll/fsyDkQzV4/ASN8rY24h24HUOAn0 cA4Q==
X-Gm-Message-State: AOAM532jhfkwZmgnll1JaznYWQzJr+2kcbS8gUoobmYOWU12D4LJDdCs jxXQyhNvszuWVZRkSeO1Ya5cLS8xE213fPb/3tANjWRHOoSHfg==
X-Google-Smtp-Source: ABdhPJzeyR3LTQ774QHUiOCOImR1XITsJAtIeM199BnQ+9WVjNRj8bARcqQ0LTWocvlSLi0X1eyr+5GeZlCGgrATlvI=
X-Received: by 2002:ac8:5f93:: with SMTP id j19mr5188077qta.298.1623936949222;  Thu, 17 Jun 2021 06:35:49 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8mp7KtnqaH8fEAHTjoeN63tm_QL_L8b3oS4qbLBh-Zv0A@mail.gmail.com> <e01d76ea-449a-8a59-f5a5-5aeaabf7e2d8@crash.com>
In-Reply-To: <e01d76ea-449a-8a59-f5a5-5aeaabf7e2d8@crash.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Thu, 17 Jun 2021 09:35:33 -0400
Message-ID: <CAHej_8mjK7sARFQhYnONqbzRxjh=GZx1n1xm2ccfd39kdP+Bsw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ff1d5d05c4f648f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/yyd99XoLsKRI8QuYrhx2e2CNsWw>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #4 (Definition of "fo" parameter) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 13:35:58 -0000

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

I have closed the subject ticket and incorporated relevant text
changes in draft-ietf-dmarc-dmarcbis-02,
which will be published on Datatracker as soon as the chairs have a chance
to do so.

On Fri, May 28, 2021 at 8:29 PM Steven M Jones <smj@crash.com> wrote:

> On 5/28/21 08:43, Todd Herr wrote:
>
>
> Consensus on Ticket #4 <https://trac.ietf.org/trac/dmarc/ticket/4>(Definition
> of "fo" parameter) was reached during the May 27 DMARC Interim to update
> the definition of the "fo" parameter with the following sentence, as shown
> in dmarcbis-01:
>
> The value of this tag is either "0", "1", or a colon-separated list of the
> options represented by alphabetic characters.
>
>
> It is understood from the discussion that ABNF for the "fo" tag will have
> to be updated, and this update will happen in the next version of dmarcbis,
> scheduled for release in the next few weeks.
>
>
> I support the proposed change.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Todd Herr* | Technical Director, Standards and Ecosystem
*e:* todd.herr@valimail.com
*m:* 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.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D""><font face=3D"taho=
ma, sans-serif">I have closed the subject ticket and incorporated relevant =
text changes in=C2=A0</font><span style=3D"font-variant-ligatures:no-common=
-ligatures;color:rgb(0,0,0)"><font face=3D"tahoma, sans-serif" style=3D"">d=
raft-ietf-dmarc-dmarcbis-02, which will be published on Datatracker as soon=
 as the chairs have a chance to do so.</font></span></div>





</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Fri, May 28, 2021 at 8:29 PM Steven M Jones &lt;<a href=3D"mailto:smj@cr=
ash.com">smj@crash.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <div>On 5/28/21 08:43, Todd Herr wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif=
"><br>
        </div>
        <div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif=
">Consensus
          on <a href=3D"https://trac.ietf.org/trac/dmarc/ticket/4" target=
=3D"_blank">Ticket #4 </a>(Definition
          of &quot;fo&quot; parameter) was reached during the May 27 DMARC =
Interim
          to update the definition of the &quot;fo&quot; parameter with the
          following sentence, as shown in dmarcbis-01:</div>
        <div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif=
"><br>
        </div>
        <div class=3D"gmail_default">
          <blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:=
0px">
            <div class=3D"gmail_default"><font face=3D"tahoma, sans-serif">=
<span>The
                  value of this tag is either &quot;0&quot;, &quot;1&quot;,=
 or a
                  colon-separated list of the options represented by
                  alphabetic characters.</span><br>
              </font></div>
          </blockquote>
        </div>
        <div><br>
        </div>
        <div>
          <div class=3D"gmail_default" style=3D"font-family:tahoma,sans-ser=
if">It is understood from
            the discussion that ABNF for the &quot;fo&quot; tag will have t=
o be
            updated, and this update will happen in the next version of
            dmarcbis, scheduled for release in the next few weeks.</div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>I support the proposed change.<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><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baseline=
;white-space:pre-wrap;font-size:small;font-family:Arial"> | Technical Direc=
tor, Standards and Ecosystem</span></div><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"=
text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><s=
pan style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail=
.com" target=3D"_blank">todd.herr@valimail.com</a> </span></div></span><spa=
n><div><span><b>m:</b></span><span> 703.220.4153</span><span></span></div><=
div style=3D"text-align:left"><img style=3D"width: 175px; height: 43px;" sr=
c=3D"https://hosted-packages.s3-us-west-1.amazonaws.com/Valimail+Logo.png">=
</div></span><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 all data transmitted with it contains confidential and/or proprie=
tary information intended solely for the use of individual(s) authorized to=
 receive it. If you are not an intended and authorized recipient you are he=
reby notified of any use, disclosure, copying or distribution of the inform=
ation included in this transmission is prohibited and may be unlawful. Plea=
se immediately notify the sender by replying to this email and then delete =
it from your system.</span></font></p></span></div>

--000000000000ff1d5d05c4f648f9--


From nobody Thu Jun 17 06:38:36 2021
Return-Path: <todd.herr@valimail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73BA53A2034 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:38:25 -0700 (PDT)
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, 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=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 sBuQ7YsINUTb for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:38:20 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FCC03A2028 for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:38:20 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id a15so4661995qtx.13 for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:38:20 -0700 (PDT)
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=ht75SK1CUxphgS2rr/GFjWCEbKy/zdu1EVIBKWcLmpc=; b=LEPdIazGVAoq+EFvLmVbMz59H7Ifvp1l1mpa4NXC1bfdmtMWS9JalvbyDvUiIJ8cGl X34nNLfr4hTAMAprngsDRQ3IoXvXBksqlMR2fzGzD+8/Yovb1jCbms4/KF0iQ2WtG7vu V5OkiMdYny4KeUUUiDj/11yFiZbL2xszY/UczSJtyNliAFnDhnr85on1zm5J/NmKxYX3 tFChqvKREbgSPVpzOEm3NkvK2XgYKLvthLIjCu5kxuhLupWU/+22yjQ42MvK/YiQk2cd kkdoR4qCLcnObXCYd8PoHI+BvH2h/lCZODybm7Ijvh/zi44ypahNNT4QTMKBLnoFNjWR guwA==
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=ht75SK1CUxphgS2rr/GFjWCEbKy/zdu1EVIBKWcLmpc=; b=L7EG6qwilozMlhevd56vFPrvCc2SpUjjRI0i1fkHUYVs5lfzApbBgX1lf/kr98pJfN 6vvuXXqv8VrcZ3aAZyLKh0LyKagBsf41t/fM5xygcRI3haYQ69FOgNrZlDXpvkz4Xllx RKrug/4sOSAOF6IjR1M6bdXJ6tQDvtdN1LOe8oV185uazCjXAmZLSf56kmetPV3yVuvF RdVkG1idmIma2LPmEdT9xYnoiaEXBTEHyo30b3Dss9ZWXlfToK7RPj3icTtQOlS+yq0D ZSqKGGdqZYbwcGqGGbUqyw96gp6bb7GyDluKK6mkGFyZgBUoTF2rXsrDLNy6PUncrnPB oTNQ==
X-Gm-Message-State: AOAM531cf78fKx13sAhimARRHTIc1pjkeY7yW0jO2YCt8tjC6TA7W0KY d6JgNQQo5Q1wBbx97H5QcKoRhYQnQVQ678sK8XqfCuqVLGVo+A==
X-Google-Smtp-Source: ABdhPJwnYfAb+gpDK41uKApjWjtBv08XWCbNYACUJ8s+IN3NY+8eyGDBcC1YC0a3MgBYIBd2jekx8fk1GhjDqraDriE=
X-Received: by 2002:a05:622a:ca:: with SMTP id p10mr5313498qtw.83.1623937098093;  Thu, 17 Jun 2021 06:38:18 -0700 (PDT)
MIME-Version: 1.0
References: <e6403b99-dcc2-1507-4187-a7586c9f5eea@tana.it> <20210603221737.C8146B6B7BB@ary.qy> <CAJ4XoYcek=dW6Q75CTzQzB+9szUWreC8D8_he0SiLw-7m_25UQ@mail.gmail.com> <CADyWQ+HDHatO8XTzpPZXWL0+BzgJ5=JjAQDoWPi=rFLTO2V=cw@mail.gmail.com>
In-Reply-To: <CADyWQ+HDHatO8XTzpPZXWL0+BzgJ5=JjAQDoWPi=rFLTO2V=cw@mail.gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Thu, 17 Jun 2021 09:38:02 -0400
Message-ID: <CAHej_8k-8LGG=fOj+UOrtr7-x0af_MwH-MjwY07WK-OEpo2pCw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dea91f05c4f651ec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VOSNa8KaDMjaB9QOUVPilChStCQ>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #47 (Removal of "pct" tag) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 13:38:35 -0000

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

I have closed the subject ticket and incorporated relevant text
changes in draft-ietf-dmarc-dmarcbis-02,
which will be published on Datatracker as soon as the chairs have a chance
to do so.

The relevant text changes here include clarification of the meaning of the
pct tag as well as a much longer discussion of message sampling and the
limitations inherent in the application of the pct tag.

The text changes all fall under the umbrella of "proposed text", and I
expect there will be further discussion of the topic.


On Fri, Jun 4, 2021 at 4:00 PM Tim Wicinski <tjw.ietf@gmail.com> wrote:

> +1 With Mr Levine's line of thinking.
>
> I also agree with keeping pct= tag.
>
> tim
>
>
> On Thu, Jun 3, 2021 at 7:16 PM Dotzero <dotzero@gmail.com> wrote:
>
>>
>>
>> On Thu, Jun 3, 2021 at 6:17 PM John Levine <johnl@taugh.com> wrote:
>>
>>> It appears that Alessandro Vesely  <vesely@tana.it> said:
>>> >On Thu 03/Jun/2021 05:45:33 +0200 Murray S. Kucherawy wrote:
>>> >> I don't understand what "demeaning a domain's policy" means.
>>> >
>>> >I meant to say that p=quarantine; pct=0 is to be considered a strict
>>> policy to
>>> >all effects.  Saying so should prevent reasoning something like "Oh,
>>> they said
>>> >quarantine, but since pct=0 it is somewhat faked, so I'll skip X",
>>> where X
>>> >could be rewriting From:, displaying a BIMI image, record aggregate
>>> data, or
>>> >any other action that might depend on the policy.  That is to say pct=0
>>> does
>>> >not alter the value of p=, otherwise testing becomes a nightmare.
>>>
>>> If we agree that's what we mean, that's what we should say, e.g., add
>>> something
>>> like this:
>>>
>>>  Senders may use pct=0 to signal an intention to apply a stricter
>>>  DMARC policy in the future, and to request receivers that do special
>>>  processing based on DMARC policy to do that processing. Examples of
>>>  special processing might include mailing list software rewriting
>>>  addresses in From headers.
>>>
>>
>> As long as we get the wording right, I agree with your line of thinking
>> John. Again, we don't have insight as to the extent that receivers will
>> honor the request.
>>
>> Michael Hammer
>> _______________________________________________
>> 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
>


-- 

*Todd Herr* | Technical Director, Standards and Ecosystem
*e:* todd.herr@valimail.com
*m:* 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.

--000000000000dea91f05c4f651ec
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:tahoma,s=
ans-serif"><font face=3D"tahoma, sans-serif">I have closed the subject tick=
et and incorporated relevant text changes in=C2=A0</font><span style=3D"fon=
t-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)"><font face=3D"tah=
oma, sans-serif">draft-ietf-dmarc-dmarcbis-02, which will be published on D=
atatracker as soon as the chairs have a chance to do so.</font></span><br><=
/div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><=
span style=3D"font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)">=
<font face=3D"tahoma, sans-serif"><br></font></span></div><div class=3D"gma=
il_default" style=3D"font-family:tahoma,sans-serif"><span style=3D"font-var=
iant-ligatures:no-common-ligatures;color:rgb(0,0,0)"><font face=3D"tahoma, =
sans-serif">The relevant text changes here include clarification of the mea=
ning of the pct tag as well as a much longer discussion of message sampling=
 and the limitations inherent in the application of the pct tag.</font></sp=
an></div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-seri=
f"><span style=3D"font-variant-ligatures:no-common-ligatures;color:rgb(0,0,=
0)"><font face=3D"tahoma, sans-serif"><br></font></span></div><div class=3D=
"gmail_default" style=3D"font-family:tahoma,sans-serif"><span style=3D"font=
-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)"><font face=3D"taho=
ma, sans-serif">The text changes all fall under the umbrella of &quot;propo=
sed text&quot;, and I expect there will be further discussion of the topic.=
</font></span></div><div class=3D"gmail_default" style=3D"font-family:tahom=
a,sans-serif"><span style=3D"font-variant-ligatures:no-common-ligatures;col=
or:rgb(0,0,0)"><font face=3D"tahoma, sans-serif"><br></font></span></div></=
div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On=
 Fri, Jun 4, 2021 at 4:00 PM Tim Wicinski &lt;<a href=3D"mailto:tjw.ietf@gm=
ail.com">tjw.ietf@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_default" st=
yle=3D"font-family:monospace">+1 With Mr Levine&#39;s line of thinking.=C2=
=A0=C2=A0<br></div><div class=3D"gmail_default" style=3D"font-family:monosp=
ace"><br></div><div class=3D"gmail_default" style=3D"font-family:monospace"=
>I also agree with keeping pct=3D tag.=C2=A0</div><div class=3D"gmail_defau=
lt" style=3D"font-family:monospace"><br></div><div class=3D"gmail_default" =
style=3D"font-family:monospace">tim</div><div class=3D"gmail_default" style=
=3D"font-family:monospace"><br></div></div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jun 3, 2021 at 7:16 PM Dotzero=
 &lt;<a href=3D"mailto:dotzero@gmail.com" target=3D"_blank">dotzero@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=
"><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, Jun 3, 2021 at 6:17 PM John=
 Levine &lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@taug=
h.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">It appears that Alessandro Vesely=C2=A0 &lt;<a href=3D"mailto:vesely@t=
ana.it" target=3D"_blank">vesely@tana.it</a>&gt; said:<br>
&gt;On Thu 03/Jun/2021 05:45:33 +0200 Murray S. Kucherawy wrote:<br>
&gt;&gt; I don&#39;t understand what &quot;demeaning a domain&#39;s policy&=
quot; means.<br>
&gt;<br>
&gt;I meant to say that p=3Dquarantine; pct=3D0 is to be considered a stric=
t policy to <br>
&gt;all effects.=C2=A0 Saying so should prevent reasoning something like &q=
uot;Oh, they said <br>
&gt;quarantine, but since pct=3D0 it is somewhat faked, so I&#39;ll skip X&=
quot;, where X <br>
&gt;could be rewriting From:, displaying a BIMI image, record aggregate dat=
a, or <br>
&gt;any other action that might depend on the policy.=C2=A0 That is to say =
pct=3D0 does <br>
&gt;not alter the value of p=3D, otherwise testing becomes a nightmare.<br>
<br>
If we agree that&#39;s what we mean, that&#39;s what we should say, e.g., a=
dd something<br>
like this:<br>
<br>
=C2=A0Senders may use pct=3D0 to signal an intention to apply a stricter<br=
>
=C2=A0DMARC policy in the future, and to request receivers that do special<=
br>
=C2=A0processing based on DMARC policy to do that processing. Examples of<b=
r>
=C2=A0special processing might include mailing list software rewriting<br>
=C2=A0addresses in From headers.<br></blockquote><div><br></div><div>As lon=
g as we get the wording right, I agree with your line of thinking John. Aga=
in, we don&#39;t have insight as to the extent that receivers will honor th=
e request.</div><div><br></div><div>Michael Hammer<br></div></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baseline=
;white-space:pre-wrap;font-size:small;font-family:Arial"> | Technical Direc=
tor, Standards and Ecosystem</span></div><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"=
text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><s=
pan style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail=
.com" target=3D"_blank">todd.herr@valimail.com</a> </span></div></span><spa=
n><div><span><b>m:</b></span><span> 703.220.4153</span><span></span></div><=
div style=3D"text-align:left"><img style=3D"width: 175px; height: 43px;" sr=
c=3D"https://hosted-packages.s3-us-west-1.amazonaws.com/Valimail+Logo.png">=
</div></span><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 all data transmitted with it contains confidential and/or proprie=
tary information intended solely for the use of individual(s) authorized to=
 receive it. If you are not an intended and authorized recipient you are he=
reby notified of any use, disclosure, copying or distribution of the inform=
ation included in this transmission is prohibited and may be unlawful. Plea=
se immediately notify the sender by replying to this email and then delete =
it from your system.</span></font></p></span></div>

--000000000000dea91f05c4f651ec--


From nobody Thu Jun 17 06:39:11 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 651EC3A2036 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:38:58 -0700 (PDT)
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, 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=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 J5ct8CJcU0Qi for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:38:53 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 926073A2013 for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:38:53 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id u20so4728882qtx.1 for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:38:53 -0700 (PDT)
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=YLX8SIF1SQIaVs6/aRZO2FncGj1giGgpo3zCzMi+hl4=; b=Ri/MgwAP15VMfeOeXBNXSbE9kebeI6H6NKkka4Mg/agSBHnzSR/lblUNV4oZ9LkZ8F LyGR0ZXyInAAfoV1+hwGC0U2dJ7ZVt0A3rmsv5uld9Xes90vWfTaCGtew5TxhpaTJGj6 fyGiY/sWXLIsIuLkO6uHQFVY7CkFGHZvgHonG7CpoMAjXAFv1cvz947V5u0oCM0tzhfs 6Yg9f5lXCZTZG+MXpyGuxmP72ok4AktTpFa37mJ1WQ6v8OWIHb8hRk7UdYlX+RqFhgif f+bFTpudVgo2K5EKs26ZUslknXj864BOS1CKoj+Pl0H0m/7R/hj10a7qM0F4EiCQF/VB EhVg==
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=YLX8SIF1SQIaVs6/aRZO2FncGj1giGgpo3zCzMi+hl4=; b=GUEFU+eCRBsbNpXmKQMsWItsgg8SLOCXyXGN6HO2/XZ8O8TsnIre8J8rx+OxNfsi48 u8R14y6JfKrH+Kil2aKvnqVVlXySMaKPaiCVC+tEHkHA3EfGcuuIZwlrZ24OLmI8Cvio /YEvYgpw8iiMlX4THl7G11X3lkTFU255WJ9xj2xOYDOiGvpNtHiKwDACKbfn6ZgkTsEB eDwad440zC6lnor3JrFYqitCCxi15kqCT2aVYLFR9jgsCOpXR4g07rW+VaX+xSFErNEB +AA4sfNN8G6fzUDiigx2GrvXR95a0TO9HLCEzyprP29dkouYrRXW+GbK18/CwnePgGol PhDQ==
X-Gm-Message-State: AOAM532TbjxYl6oLteGqiqqAcEBipYu6a1gn3AUqe5/YKmmQKC6c5zMu 5wWEsiLPgn9/I3XNeatX4KuyCHon7BR37hVs71cJ0mFrMeVFBg==
X-Google-Smtp-Source: ABdhPJyyT70z0gJB5aFtqdS/3LGocaz635DYsXLe5/NuEhTDiV8SJ+8Wjj5A7JMwqkEcWjJCWhDVFKbqdLq7FYEsqAw=
X-Received: by 2002:ac8:74d3:: with SMTP id j19mr5228417qtr.208.1623937131876;  Thu, 17 Jun 2021 06:38:51 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8kfk=-RT0bgsiRqoEJNXXzqSYvxgfBwqYnXxGUquisyjw@mail.gmail.com> <ee3d7541-db25-e3d6-be79-434b2f8c2244@crash.com>
In-Reply-To: <ee3d7541-db25-e3d6-be79-434b2f8c2244@crash.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Thu, 17 Jun 2021 09:38:36 -0400
Message-ID: <CAHej_8kJ6Artj0rb+kabnC3j8ChQQeckW5pDsAdKtyoyu-gnpA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e2387505c4f653af"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/sp8NDGkxFDINoPx7Ylq2Uw2HnAc>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #50 (Remove ri= tag) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 13:39:09 -0000

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

I have closed the subject ticket and incorporated relevant text
changes in draft-ietf-dmarc-dmarcbis-02,
which will be published on Datatracker as soon as the chairs have a chance
to do so.

On Fri, May 28, 2021 at 8:30 PM Steven M Jones <smj@crash.com> wrote:

> On 5/28/21 08:43, Todd Herr wrote:
>
>
> Consensus on Ticket #50 <https://trac.ietf.org/trac/dmarc/ticket/50>
> (Remove ri= tag) was reached during the May 27 DMARC Interim to remove the
> tag and update the IANA registry to reflect its removal.
>
>
> I support removing the tag from the specification, but following TIm
> Wisnewski suggestion to mark the tag as "historic" in the IANA registry.
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Todd Herr* | Technical Director, Standards and Ecosystem
*e:* todd.herr@valimail.com
*m:* 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.

--000000000000e2387505c4f653af
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:tahoma,s=
ans-serif"><font face=3D"tahoma, sans-serif">I have closed the subject tick=
et and incorporated relevant text changes in=C2=A0</font><span style=3D"fon=
t-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)"><font face=3D"tah=
oma, sans-serif">draft-ietf-dmarc-dmarcbis-02, which will be published on D=
atatracker as soon as the chairs have a chance to do so.</font></span><br><=
/div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Fri, May 28, 2021 at 8:30 PM Steven M Jones &lt;<a href=3D"mailto:s=
mj@crash.com">smj@crash.com</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <div>On 5/28/21 08:43, Todd Herr wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif=
"><br>
        </div>
        <div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif=
">Consensus
          on <a href=3D"https://trac.ietf.org/trac/dmarc/ticket/50" target=
=3D"_blank">Ticket #50</a>
          (Remove ri=3D tag) was reached during the May 27 DMARC Interim
          to remove the tag and update the IANA registry to reflect its
          removal.</div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>I support removing the tag from the specification, but following
      TIm Wisnewski suggestion to mark the tag as &quot;historic&quot; in t=
he IANA
      registry.</p>
    <p><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><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baseline=
;white-space:pre-wrap;font-size:small;font-family:Arial"> | Technical Direc=
tor, Standards and Ecosystem</span></div><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"=
text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><s=
pan style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail=
.com" target=3D"_blank">todd.herr@valimail.com</a> </span></div></span><spa=
n><div><span><b>m:</b></span><span> 703.220.4153</span><span></span></div><=
div style=3D"text-align:left"><img style=3D"width: 175px; height: 43px;" sr=
c=3D"https://hosted-packages.s3-us-west-1.amazonaws.com/Valimail+Logo.png">=
</div></span><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 all data transmitted with it contains confidential and/or proprie=
tary information intended solely for the use of individual(s) authorized to=
 receive it. If you are not an intended and authorized recipient you are he=
reby notified of any use, disclosure, copying or distribution of the inform=
ation included in this transmission is prohibited and may be unlawful. Plea=
se immediately notify the sender by replying to this email and then delete =
it from your system.</span></font></p></span></div>

--000000000000e2387505c4f653af--


From nobody Thu Jun 17 06:40:37 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 2B33D3A2000 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:40:36 -0700 (PDT)
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 (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 4_kQ02KEWbKR for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:40:31 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 096083A1FFA for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:40:30 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id t9so4698776qtw.7 for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:40:30 -0700 (PDT)
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=nm/bXWRus8qs3WpuXvE+Dov217ns/aZW0pPe2mPjOz8=; b=WI6m2n//kJcdDwDuSrFsL0wo02nVFSZI6RzFeshaQVvOx+Lsz7+88F73bNm3yd0Xjj 3jQPwzAmXaeYRTPUkbwK1tFm7E/qmmZxrFSDD18m9mfQae82Hv57/oH6PutI+kjG0s9a s+bd8ymcIC9H4rWwlfMyAA28SP6BG/uSyhnlauS9Ae0MML4CtyZwhxrgJtPJy2xD5RqU Z1hS/Wp+Qx7uSHcapyB1UCilY5xLn5hPkHbhO+vM8CCyQw9wbZCsvrFnHJt9+iQDUnA+ oKVe0FXs60C1hYcfAaOcuSG6GkAcbDsC6gWUskisqy/0DRfBWvyMyh/lXvofLdMEFias AB+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=nm/bXWRus8qs3WpuXvE+Dov217ns/aZW0pPe2mPjOz8=; b=gsp/jhF33auGvDA8YwV1FbnsWFnQa+gWarf6gzUNqeMT+A+eP+xoFHNrvbxAAMfYvc kapc5ypzqPeVuJRLSClRQmsjgTQGdQVQ5M8kPsHdaxUKC5V6vzgsQrSFCp0L4hr3nnpB YanauZ7MmaCu+spxq2c/e1+CKRr6V2qvtMDoQCSB1s1R2Pu8VJlUxI+ACou+RbA4nokI oskPsJOenLS9FLzhDSD7CoDAA/qTckDBrfsEdXf6DtL9POSdKWfC4LzJ+CotFK8XcxeF wYhnm800HqCw9bqc4qZ90bgwTPL9rTnhs/W5Od+HOS3Vlrz/ns725uQ7rpkVPaCVH2ro X4rQ==
X-Gm-Message-State: AOAM533vrVw0h2UUi6jZbMNYUOk6x0rCi4cJQgK6Wsgf6naXXv9CMFhU C+gOjevWmd+xEWFhOKO/Hn7sKbM+BM1ly9h5KX8UUP2V18POQg==
X-Google-Smtp-Source: ABdhPJzY+EONkRLSqSFdNY+Bho70nGnw4BsQST7usl0hmjUukyWV4ICvtKA8/zouuzUZYVUO/iVoQpTW2iAaEbT8IVg=
X-Received: by 2002:ac8:5f93:: with SMTP id j19mr5208165qta.298.1623937227192;  Thu, 17 Jun 2021 06:40:27 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8npHwekgJDLOV=hVPdd0OFoMumJCKL5Yitz5oWrhkQdNg@mail.gmail.com> <a8ef636c-815a-6b40-a955-b7049afba82f@crash.com> <a7fc5ba7-e17b-72b5-e81a-1dd0ac6cb418@tana.it> <CALaySJ+FGMBA2AuNzwUOyA5eccUkQ399Kc3c-oj99oZRov8oPQ@mail.gmail.com> <88957ada-7514-f664-6269-88503c1a81fd@tana.it> <fc795d67-1003-32cd-d99a-fa9256a802a1@crash.com> <c2ae5c84-53fa-8d5e-b912-8433d5798698@crash.com> <8f57f42c-735e-0bb3-98a7-06514687342f@tana.it>
In-Reply-To: <8f57f42c-735e-0bb3-98a7-06514687342f@tana.it>
From: Todd Herr <todd.herr@valimail.com>
Date: Thu, 17 Jun 2021 09:40:11 -0400
Message-ID: <CAHej_8=YCF6vKMF38rjFqT6c9nsBfkm0ScV6+S7AF=LByAtzrw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000908cf705c4f6594f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/emmXHSCeo-8Hm4eHSuArRu9TV_w>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #53 (Remove reporting message size chunking) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 13:40:36 -0000

--000000000000908cf705c4f6594f
Content-Type: text/plain; charset="UTF-8"

I have closed the subject ticket and incorporated relevant text
changes in draft-ietf-dmarc-dmarcbis-02,
which will be published on Datatracker as soon as the chairs have a chance
to do so.

On Tue, Jun 8, 2021 at 4:32 AM Alessandro Vesely <vesely@tana.it> wrote:

> Thank you Steve, this confirms size limits are a useless encumbrance on
> reporting.
>
> Best
> Ale
>
>
> On Tue 08/Jun/2021 01:20:55 +0200 Steven M Jones wrote:
> > On 5/31/21 15:49, Steven M Jones wrote:
> >> I think we can get the input needed to resolve this by Todd's requested
> >> deadline, and be able to show we did the due diligence to back up the
> >> decision.
> >
> >
> > I got three responses - unfortunately I discovered I don't have as many
> > of these contacts as I used to. So it's still anecdotal, but it includes
> > two of the (I don't know) dozen top mailbox providers in the world - for
> > whatever positive or negative weighting that may carry with you.
> >
> > I'm about to add the following comment to the TRAC ticket:
> >
> >
> >
> > I offered to try and get information on the frequency of use of this
> > feature from mailbox providers/report generators. I received three
> > responses, which I will rephrase to protect the sources. They can speak
> > up if they wish to go on the record.
> >
> > 1. Global mailbox provider A: Our code doesn't handle the syntax, and
> > will try to send to the address including the size specification. So if
> > you use that in your domain's RUA tag, our reports to you are probably
> > bouncing. There's a bug filed to fix it, but no commitment to do so.
> >
> > 2. Global mailbox provider B: We had the same bug, but fixed it - so
> > reports will be sent to the correct address. But regarding the limit, we
> > checked to see if anybody who specified a limit was receiving reports
> > large enough to trigger it, and nobody was. Large operators who might
> > actually trigger it, didn't specify a size. So we never implemented it.
> >
> > 3. National mailbox provider: I wrote code to implement it, but to my
> > knowledge it has never been triggered. Maybe our operation isn't big
> > enough. But implementing it was painful - guessing what the compressed
> > size would be, how to trim or truncate the report to fit the limit, who
> > to notify in the event of truncation and how... I would prefer removal,
> > but failing that please simplify it. [I can share the suggestions if we
> > go that way. --S.]
> >
> >
> >
> > --Steve.
> >
> >
> > _______________________________________________
> > 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
>


-- 

*Todd Herr* | Technical Director, Standards and Ecosystem
*e:* todd.herr@valimail.com
*m:* 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.

--000000000000908cf705c4f6594f
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:tahoma,s=
ans-serif"><font face=3D"tahoma, sans-serif">I have closed the subject tick=
et and incorporated relevant text changes in=C2=A0</font><span style=3D"fon=
t-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)"><font face=3D"tah=
oma, sans-serif">draft-ietf-dmarc-dmarcbis-02, which will be published on D=
atatracker as soon as the chairs have a chance to do so.</font></span><br><=
/div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Tue, Jun 8, 2021 at 4:32 AM Alessandro Vesely &lt;<a href=3D"mailto=
:vesely@tana.it">vesely@tana.it</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">Thank you Steve, this confirms size limits=
 are a useless encumbrance on reporting.<br>
<br>
Best<br>
Ale<br>
<br>
<br>
On Tue 08/Jun/2021 01:20:55 +0200 Steven M Jones wrote:<br>
&gt; On 5/31/21 15:49, Steven M Jones wrote:<br>
&gt;&gt; I think we can get the input needed to resolve this by Todd&#39;s =
requested<br>
&gt;&gt; deadline, and be able to show we did the due diligence to back up =
the<br>
&gt;&gt; decision.<br>
&gt; <br>
&gt; <br>
&gt; I got three responses - unfortunately I discovered I don&#39;t have as=
 many<br>
&gt; of these contacts as I used to. So it&#39;s still anecdotal, but it in=
cludes<br>
&gt; two of the (I don&#39;t know) dozen top mailbox providers in the world=
 - for<br>
&gt; whatever positive or negative weighting that may carry with you.<br>
&gt; <br>
&gt; I&#39;m about to add the following comment to the TRAC ticket:<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; I offered to try and get information on the frequency of use of this<b=
r>
&gt; feature from mailbox providers/report generators. I received three<br>
&gt; responses, which I will rephrase to protect the sources. They can spea=
k<br>
&gt; up if they wish to go on the record.<br>
&gt; <br>
&gt; 1. Global mailbox provider A: Our code doesn&#39;t handle the syntax, =
and<br>
&gt; will try to send to the address including the size specification. So i=
f<br>
&gt; you use that in your domain&#39;s RUA tag, our reports to you are prob=
ably<br>
&gt; bouncing. There&#39;s a bug filed to fix it, but no commitment to do s=
o.<br>
&gt; <br>
&gt; 2. Global mailbox provider B: We had the same bug, but fixed it - so<b=
r>
&gt; reports will be sent to the correct address. But regarding the limit, =
we<br>
&gt; checked to see if anybody who specified a limit was receiving reports<=
br>
&gt; large enough to trigger it, and nobody was. Large operators who might<=
br>
&gt; actually trigger it, didn&#39;t specify a size. So we never implemente=
d it.<br>
&gt; <br>
&gt; 3. National mailbox provider: I wrote code to implement it, but to my<=
br>
&gt; knowledge it has never been triggered. Maybe our operation isn&#39;t b=
ig<br>
&gt; enough. But implementing it was painful - guessing what the compressed=
<br>
&gt; size would be, how to trim or truncate the report to fit the limit, wh=
o<br>
&gt; to notify in the event of truncation and how... I would prefer removal=
,<br>
&gt; but failing that please simplify it. [I can share the suggestions if w=
e<br>
&gt; go that way. --S.]<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; --Steve.<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://www.ietf.org/mailman/listinfo/dmarc" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><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>Todd Herr</b></span><span style=3D"vertical-align:baseline=
;white-space:pre-wrap;font-size:small;font-family:Arial"> | Technical Direc=
tor, Standards and Ecosystem</span></div><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"=
text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><s=
pan style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail=
.com" target=3D"_blank">todd.herr@valimail.com</a> </span></div></span><spa=
n><div><span><b>m:</b></span><span> 703.220.4153</span><span></span></div><=
div style=3D"text-align:left"><img style=3D"width: 175px; height: 43px;" sr=
c=3D"https://hosted-packages.s3-us-west-1.amazonaws.com/Valimail+Logo.png">=
</div></span><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 all data transmitted with it contains confidential and/or proprie=
tary information intended solely for the use of individual(s) authorized to=
 receive it. If you are not an intended and authorized recipient you are he=
reby notified of any use, disclosure, copying or distribution of the inform=
ation included in this transmission is prohibited and may be unlawful. Plea=
se immediately notify the sender by replying to this email and then delete =
it from your system.</span></font></p></span></div>

--000000000000908cf705c4f6594f--


From nobody Thu Jun 17 06:43:27 2021
Return-Path: <todd.herr@valimail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCF6E3A2046 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:43:21 -0700 (PDT)
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 (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 2MepHWeu5LO8 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:43:16 -0700 (PDT)
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 2D7863A2025 for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:43:15 -0700 (PDT)
Received: by mail-qv1-xf2f.google.com with SMTP id f5so1646896qvu.8 for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:43:15 -0700 (PDT)
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=kQD+vV1q5z7Xgz24A3caCYHlYDue7ytUreY7/guOf2Y=; b=G9cEBtoeDqUuNfvkKp3PKM11UPwK3Y6//I20i9iXfPz4PymrgBkKZqA93yQAy1miXW HXBD+rZs6SU2LnfGN7qIHXdgFErn6j0BomWXW8wgmPdcnjWlFM+Vr1BIYqtcCWn/xa4M 93hOkhGFW9lGs3DQUaCZCQ7vo+BzvTaFA41cX+vKREXAW1r69+4ks3FEu81aqUt7R5+M xbA+DE31whw6NZezZXMLyAGvlikbuCdYURYuuwMYeA/dYemvr34NYueei0rZtQRp3Zyz LgAixGO4UjaX7rIXLxugYsSbp+Dwt8EA/ls+zdvFApXFClbSQUMz/1C+53gpZrE2wBZd v87Q==
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=kQD+vV1q5z7Xgz24A3caCYHlYDue7ytUreY7/guOf2Y=; b=npzalFcO0pspKCoUG+iaR3/6qVlfVb/lnDRl1VW9tXgs90j1Pho4QfwR14KoP5uc04 ON/VdOVPrMXPyJMSS8UkTeIPYMt81MraT4+G3gIKU+GETs/ny7SW4EKTIMOvEUdDhwbR WRUStAxBeMQiLImD0v+JUJmxdIYOoq09pOSeG28X/nj6GXHNFNCxSxZ7Agqq6QRd5rc1 vxe2d2xbJDJWeOPgElxeUl7BjJQFqZJNjUUyZIZXVvf0UPofMkFmimB+gZSierH2BFQG pdqtH1fBuUmbarxMFDrWDwJp6J/H4O23AMxFxC/DZnvIkDc7MaDc3XzdvqFBr8x9UM61 1rAg==
X-Gm-Message-State: AOAM533LIm0uy1sPNIPQT0sWOMydD3H3C/deoUYYIhsrJEshFBmdfeOb biIPpi68WfR1ISvNWEh38+FYg6lsy0BYtGgNMhH7u5/3WKIKvg==
X-Google-Smtp-Source: ABdhPJw5MTpDEwceT54juUUUIix6kwDG6Zr8h0jM/zgqp6I4GME0IKLdJD9IT8+0xFOIM14BL/5qi+2/6t4F7zFMPnI=
X-Received: by 2002:ad4:45a6:: with SMTP id y6mr6087254qvu.54.1623937394341; Thu, 17 Jun 2021 06:43:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8nmJCVwaTxVHdFL8j65ZcWd6B5f7qKQsvfY4eUoe_exrA@mail.gmail.com> <a17a4c1e-a66e-e7f0-ef81-98e2947df6f9@crash.com>
In-Reply-To: <a17a4c1e-a66e-e7f0-ef81-98e2947df6f9@crash.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Thu, 17 Jun 2021 09:42:58 -0400
Message-ID: <CAHej_8mqa_rFc5F-4dJLxNK-fwE4r3-BGh3XydwZii7NaT4dPQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000870ddb05c4f663c2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/drS3n-YJhkynyo5uLZkih-Ef3bc>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #54 (Limits on recipients per report) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 13:43:26 -0000

--000000000000870ddb05c4f663c2
Content-Type: text/plain; charset="UTF-8"

I have closed the subject ticket and incorporated relevant text
changes in draft-ietf-dmarc-dmarcbis-02,
which will be published on Datatracker as soon as the chairs have a chance
to do so.

On Fri, May 28, 2021 at 8:59 PM Steven M Jones <smj@crash.com> wrote:

> On 5/28/21 08:46, Todd Herr wrote:
>
>
> Consensus on Ticket #54 <https://trac.ietf.org/trac/dmarc/ticket/54>
> (Remove or expand limits on number of recipients per report) was reached
> during the May 27 DMARC Interim to update the text in the DMARC URIs
> section to read:
>
> The place such URIs are specified (see Section 6.3
> <https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-01.html#general-record-format>)
> allows a list of these to be provided. The list of URIs is separated by
> commas (ASCII 0x2c). A report SHOULD be sent to each listed URI provided in
> the DMARC record.
>
> This proposed change will be made in the next version of dmarcbis,
> scheduled for release in the next few weeks.
>
>
> I support the change.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Todd Herr* | Technical Director, Standards and Ecosystem
*e:* todd.herr@valimail.com
*m:* 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.

--000000000000870ddb05c4f663c2
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:tahoma,s=
ans-serif"><font face=3D"tahoma, sans-serif">I have closed the subject tick=
et and incorporated relevant text changes in=C2=A0</font><span style=3D"fon=
t-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)"><font face=3D"tah=
oma, sans-serif">draft-ietf-dmarc-dmarcbis-02, which will be published on D=
atatracker as soon as the chairs have a chance to do so.</font></span><br><=
/div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Fri, May 28, 2021 at 8:59 PM Steven M Jones &lt;<a href=3D"mailto:s=
mj@crash.com">smj@crash.com</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <div>On 5/28/21 08:46, Todd Herr wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr"><br>
        <div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif=
">Consensus
          on <a href=3D"https://trac.ietf.org/trac/dmarc/ticket/54" target=
=3D"_blank">Ticket #54</a>
          (Remove or expand limits on number of recipients per report)
          was reached during the May 27 DMARC Interim to update the text
          in the DMARC URIs section to read:</div>
        <div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif=
"><br>
        </div>
        <blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0p=
x">
          <div class=3D"gmail_default"><font face=3D"tahoma, sans-serif">Th=
e
              place such URIs are specified (see=C2=A0<a href=3D"https://ww=
w.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-01.html#general-record-form=
at" style=3D"text-decoration-line:none;color:rgb(34,34,238)" target=3D"_bla=
nk">Section 6.3</a>)
              allows a list of these to be provided. The list of URIs is
              separated by commas (ASCII 0x2c). A report SHOULD be sent
              to each listed URI provided in the DMARC record.</font></div>
          <div class=3D"gmail_default"><font face=3D"tahoma, sans-serif"><b=
r>
            </font></div>
        </blockquote>
        <div>
          <div class=3D"gmail_default" style=3D"font-family:tahoma,sans-ser=
if">This proposed change
            will be made in the next version of dmarcbis, scheduled for
            release in the next few weeks.</div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>I support the change.<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><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baseline=
;white-space:pre-wrap;font-size:small;font-family:Arial"> | Technical Direc=
tor, Standards and Ecosystem</span></div><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"=
text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><s=
pan style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail=
.com" target=3D"_blank">todd.herr@valimail.com</a> </span></div></span><spa=
n><div><span><b>m:</b></span><span> 703.220.4153</span><span></span></div><=
div style=3D"text-align:left"><img style=3D"width: 175px; height: 43px;" sr=
c=3D"https://hosted-packages.s3-us-west-1.amazonaws.com/Valimail+Logo.png">=
</div></span><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 all data transmitted with it contains confidential and/or proprie=
tary information intended solely for the use of individual(s) authorized to=
 receive it. If you are not an intended and authorized recipient you are he=
reby notified of any use, disclosure, copying or distribution of the inform=
ation included in this transmission is prohibited and may be unlawful. Plea=
se immediately notify the sender by replying to this email and then delete =
it from your system.</span></font></p></span></div>

--000000000000870ddb05c4f663c2--


From nobody Thu Jun 17 06:44:15 2021
Return-Path: <todd.herr@valimail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1740C3A2060 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:44:05 -0700 (PDT)
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, 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=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 1NrxvKcGFjU3 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:44:01 -0700 (PDT)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF34A3A2044 for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:44:00 -0700 (PDT)
Received: by mail-qk1-x72b.google.com with SMTP id u30so3124317qke.7 for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:44:00 -0700 (PDT)
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=bYBjvGKOLzu4445joVG3CC6z65E6nN3ZTfVZ1FiQ0ME=; b=fTCr1LgoH3MP4I5YqAPOsRF6dGEmdDLioqVPoEfVFQNYTuR1or6/ZHLgyPylRNr6PV ew4l8s1j+p7zglRupiBdVfeYwkWEn24UzBRovZKXuDIKDmN/kpxaatAlJVJ/eB7/6nHY YeCKD12XqvAVf5BBG9dc5TbEb1yVa4fsUnVGSkaBB3xjjMC/y5ml8SSgfQtMJtleMLoC 78lqDd4d9Vnqoh/turjU3FtJDBqeoRKa71Z5e6ZoQuELZUKDLq2fJyDZe6cvy/OlgHJS A1hRcfurQOxqU7LvPBbwsYKSace2U1Av78fcy+W6FnN31UId6e1IAMhZjXdCjUyodLbf +Dww==
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=bYBjvGKOLzu4445joVG3CC6z65E6nN3ZTfVZ1FiQ0ME=; b=GLZ/sv7jOH/8FqnGlL9J8zmbZ/5JITBqWqU1HTWrKmK/2u0vxlRVB+kWIYiiMCrK7Y xa3vFi/44PwsxYQ2lgI5gXtTHk20/l6lAUNQf4nFoXhw9ndVOo/xs+ytzl9BcYqJXLz3 QFdEReZbr8HwH9disBiXVW9dV+a0jGB6Ih7onT3aLuTFpnusSEpfnMIsYNS5CNLJmSwf 3DNvN2jAG+7bBGL/6+YyaSy0Y6CXEYCWb85YA4LJjxK8QqkWLkaMleJIZUKSiifwozvU f3n/1L+Hc2UvtrsXWYh6SEbNPY5038DcuDT82nHx/EKHNtnNG8F/DdpVhArEBYU/E8Rz a3Bg==
X-Gm-Message-State: AOAM532Hh4jBPzY7d7Xt5VB41G5OZ2C5Im/K+8uFcAxme/8zcQru0o56 U/7OWmxkYg2P1+5ZbmFxuhpnolVruWPgQuIPnULUXZH8mSgBWg==
X-Google-Smtp-Source: ABdhPJw24/U9/72KINoPZIur9I0dnUc4Wha9PKJbpjQBCm4Jv02lGShhaGSNgUCx33VdvUv/Q4RjTLH7/YIeorSs2E0=
X-Received: by 2002:a37:b205:: with SMTP id b5mr3973616qkf.208.1623937438863;  Thu, 17 Jun 2021 06:43:58 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8kt3Z2FgDAaZQdfsTqv0V0nMNW68ZSj9CPd+7wkuT3Ozw@mail.gmail.com> <059a9372-b5c7-096e-73d6-2c1b85b3f7f2@crash.com>
In-Reply-To: <059a9372-b5c7-096e-73d6-2c1b85b3f7f2@crash.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Thu, 17 Jun 2021 09:43:43 -0400
Message-ID: <CAHej_8=y5XQbyEhEcqMwMO923RoeH28UqbM8Qzn4Tjr3evW6yg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002e667005c4f666ab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PKz6HNy1B1v-ORuEhznG-wHHhV0>
Subject: Re: [dmarc-ietf] Consensus Sought - Ticket #82 (Deprecate rf= and maybe fo= tag) - With Interim Notes
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 13:44:14 -0000

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

I have closed the subject ticket and incorporated relevant text
changes in draft-ietf-dmarc-dmarcbis-02,
which will be published on Datatracker as soon as the chairs have a chance
to do so.

On Fri, May 28, 2021 at 8:32 PM Steven M Jones <smj@crash.com> wrote:

> On 5/28/21 08:47, Todd Herr wrote:
>
>
> Consensus on Ticket #82 <https://trac.ietf.org/trac/dmarc/ticket/82>
> (Deprecate rf= and maybe fo= tag) was reached during the May 27 DMARC
> Interim to remove the "rf" tag from the core spec and allow for the
> possibility that it could potentially be reintroduced, if needed, in the
> separate failure reporting spec. (The fo tag was not discussed during this
> part of the Interim).
>
>
> I support moving the tag to either of the associated reporting documents,
> if it is included anywhere.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*Todd Herr* | Technical Director, Standards and Ecosystem
*e:* todd.herr@valimail.com
*m:* 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.

--0000000000002e667005c4f666ab
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:tahoma,s=
ans-serif"><font face=3D"tahoma, sans-serif">I have closed the subject tick=
et and incorporated relevant text changes in=C2=A0</font><span style=3D"fon=
t-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)"><font face=3D"tah=
oma, sans-serif">draft-ietf-dmarc-dmarcbis-02, which will be published on D=
atatracker as soon as the chairs have a chance to do so.</font></span><br><=
/div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Fri, May 28, 2021 at 8:32 PM Steven M Jones &lt;<a href=3D"mailto:s=
mj@crash.com">smj@crash.com</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <div>On 5/28/21 08:47, Todd Herr wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr"><br>
        <div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif=
">Consensus
          on <a href=3D"https://trac.ietf.org/trac/dmarc/ticket/82" target=
=3D"_blank">Ticket #82</a> (Deprecate rf=3D and
          maybe fo=3D tag) was reached during the May 27 DMARC Interim to
          remove the &quot;rf&quot; tag from the core spec and allow for th=
e
          possibility that it could potentially be reintroduced, if
          needed, in the separate failure reporting spec. (The fo tag
          was not discussed during this part of the Interim).</div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>I support moving the tag to either of the associated reporting
      documents, if it is included anywhere.<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><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;=
margin-top:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span =
style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-=
family:Arial"><b>Todd Herr</b></span><span style=3D"vertical-align:baseline=
;white-space:pre-wrap;font-size:small;font-family:Arial"> | Technical Direc=
tor, Standards and Ecosystem</span></div><span style=3D"vertical-align:base=
line;white-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"=
text-align:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><s=
pan style=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail=
.com" target=3D"_blank">todd.herr@valimail.com</a> </span></div></span><spa=
n><div><span><b>m:</b></span><span> 703.220.4153</span><span></span></div><=
div style=3D"text-align:left"><img style=3D"width: 175px; height: 43px;" sr=
c=3D"https://hosted-packages.s3-us-west-1.amazonaws.com/Valimail+Logo.png">=
</div></span><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 all data transmitted with it contains confidential and/or proprie=
tary information intended solely for the use of individual(s) authorized to=
 receive it. If you are not an intended and authorized recipient you are he=
reby notified of any use, disclosure, copying or distribution of the inform=
ation included in this transmission is prohibited and may be unlawful. Plea=
se immediately notify the sender by replying to this email and then delete =
it from your system.</span></font></p></span></div>

--0000000000002e667005c4f666ab--


From nobody Thu Jun 17 06:55:28 2021
Return-Path: <johnl@taugh.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D39E23A2090 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=zT/q7HAM; dkim=pass (2048-bit key) header.d=taugh.com header.b=aG3wyesH
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPC1_JgtEqiM for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 06:55:20 -0700 (PDT)
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 D83EE3A208F for <dmarc@ietf.org>; Thu, 17 Jun 2021 06:55:19 -0700 (PDT)
Received: (qmail 27076 invoked from network); 17 Jun 2021 13:55:18 -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=69c1.60cb5446.k2106; bh=MsXd1SZYYhBF2hprjbXT6K0R6VkfgiywwC6OkpPFlXc=; b=zT/q7HAMc2On3S0WJqgOsl/I67/4Zo9kdOYqrKAcjj7vscyzBjCIOmggtcQnRvJOopKPNzsC/iLCfD3il5hTNJL8kpbFGOpO6KAmLPD/NO29GE9HIXEjDRa+kr8gFc68vqXgX5f9KBL4sAr4ihilDNnala2XoD3bI3r8cR+NzszNTrttg8OppUvJxis3VCFne2qtb6NL3ZSnJ7Nyc5YgiJ6mzSrcVBNKanxPJmuCe5479xVvWWyJ401CRuG4pztIxhTO1sYP4FUxzS/hhXKX9mHpRfaTrxf1G8SLGpk6040pKCCjk1djrWkx4S0GIEy9abHOZTlaJA9sG604zC3ZhA==
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=69c1.60cb5446.k2106; bh=MsXd1SZYYhBF2hprjbXT6K0R6VkfgiywwC6OkpPFlXc=; b=aG3wyesHpi44fJ4XfFWMse2tFcGFv0Dx+q4VLTnMbqiXLsuFYyI8Ft1Jwy+4pVaoZw6rDHf8dZCYY9EWzwAklK/5padPchE7ypBT3VbfzA0LftIclwPFn1DKZ3sZx+uXSwmZDs3V9OXD43cK3MyO/+7/QFLOljtRC9I6MMRHzfnkPIOznkRfUvCynbANQeHcCnhRD0tmWh3S0daRjeRqHlqMYv8fuPSyyU66nTyxe9H9YRNmw+7Bkd1R3TlRndJniW4gAbkdc0fcJyDRhuT8L8uRRYbWOy+lutdKUzLi3sZQaiqyNHFi8Z6zD2LOpLvSF4XqI1nFxcUulDkwHHhnzA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 17 Jun 2021 13:55:17 -0000
Received: by ary.qy (Postfix, from userid 501) id 41A3412ABDEF; Thu, 17 Jun 2021 09:55:17 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 190B012ABDCC; Thu, 17 Jun 2021 09:55:17 -0400 (EDT)
Date: 17 Jun 2021 09:55:17 -0400
Message-ID: <9d22cfaa-b27d-4c7b-61b5-947fd7a7567@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Alessandro Vesely" <vesely@tana.it>, dmarc@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <6e76e4af-e592-0103-33dc-4cda6b129071@tana.it>
References: <20210616180222.53DC311FBCDC@ary.qy> <6e76e4af-e592-0103-33dc-4cda6b129071@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9YdZD43FgKfAaYZbkJOP5mh0vN8>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 13:55:26 -0000

> However, by that definition a domain with a Null MX [RFC7505] is an existent 
> domain for DMARC purposes.

True, but so what?  If you want to do a DMARC alignment check, you do it 
the same way as for any other domain.  For the umpteenth time, DMARC is 
not the magic anti-spam bullet, and you continue to use whatever other 
filtering methods you use.

> Would that add clarity?

No.  Let's close #112 and talk about something else.

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


From nobody Thu Jun 17 09:18: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 BBC973A25A3 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 09:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJ-DNi1UDOy3 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 09:18:01 -0700 (PDT)
Received: from mail-oo1-xc32.google.com (mail-oo1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4DC03A25A6 for <dmarc@ietf.org>; Thu, 17 Jun 2021 09:18:00 -0700 (PDT)
Received: by mail-oo1-xc32.google.com with SMTP id o5-20020a4a2c050000b0290245d6c7b555so1701111ooo.11 for <dmarc@ietf.org>; Thu, 17 Jun 2021 09:18:00 -0700 (PDT)
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=9oWlyDRDcqWcqLrO/leOAvqg6IpMBjFlaPB0nptWj7w=; b=Xd+BC/OnZe+DGrMb4lKa1BfkNdiCh2Olcs0w/YYJl+bFNm4lOX1/v7TXyH+JsDy3nG HRfcl1iksCD9liGelsDsXy1ooCjK68FaTOxD5sYTUTLBy6IWxPhK2HzoxvEE2zNf0Wq9 cifVd3I4eRuMvfsNgdL/AXFNsNPRw6QV4Pl7lzUCz6SBZRs848a0Pl3mzv5v4S21/ZXL 913lVn2tb3aN41mW5A2ooaBqYVaQPmcAbmgqulIzKd3xzp3SfjQQUh3HpXVZuql9zv+z s0NYeB248dRlUZc88guBlOy05vTHt2QVBgujr0g7UV1SRePKNs8fcTsD1GdUqlCmTZRs y+xQ==
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=9oWlyDRDcqWcqLrO/leOAvqg6IpMBjFlaPB0nptWj7w=; b=VWV2Mof5jU/TtfvBP63X5Wxv9t7068/Cx5yZjWly9FynMrlftR/QV0lFaIJIbgn6L2 0Erzis3ODmn4iE3ZfW4kD3UYvCe/Cqy7ZG7ek6J7zrIV+o17MA+BzxxtpI5ydZBwBtdc QOIKrHsMVneJRzagA93/xq5WrLPzB+EWLOk1mpYtzhS6w3NxoytO0ttgkdTLqxCC2wNh T0usgQO8RKuWHPCSKI8e8sU1cFEx2N177pYIorPhQ7HuRkwkFahwIjy6wqGnmTYh3BQk BrgNtnZwF0Kwk/LuRF+LtSx+WwHaA92KMdynNIyCGkYQB2xWQ9qmInLMLy2EYeMTEqoN YaPw==
X-Gm-Message-State: AOAM532Ws2mB7Xb3quUfiPi5+X8R/aXB+T8v8ofcZcO2fvhOeoEl9lXx 6Q5mKcTLiyvjLLkr9n7Ag2C9K7W04PJSzZMBwVKxLCS8CGU=
X-Google-Smtp-Source: ABdhPJzhIrzG3FW1HYjdYE1/4MsmSYydpsiRfb2v8bduuzyLR/nmeUDD/e1uKCnc3A4iH+Rjli+dJL9y0qJLik3n2sY=
X-Received: by 2002:a4a:d456:: with SMTP id p22mr1710543oos.13.1623946679036;  Thu, 17 Jun 2021 09:17:59 -0700 (PDT)
MIME-Version: 1.0
References: <20210616160110.09D6011E70FD@ary.qy> <71e61630-0bc8-c9f1-6e7c-5267889c15af@tana.it> <CAH48ZfyYSW5003cxgP0r_skzSdfNvV9FL=sY_32PwQ1dWXxFCg@mail.gmail.com> <CAL0qLwYsTgRJ8PnjG7nAdTJJ54ww2HWtvOGp2EeMqNStjD6X8A@mail.gmail.com>
In-Reply-To: <CAL0qLwYsTgRJ8PnjG7nAdTJJ54ww2HWtvOGp2EeMqNStjD6X8A@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Thu, 17 Jun 2021 12:17:48 -0400
Message-ID: <CAH48ZfzddEUcph74bZLoPnx5Ri9sEh31Ni8+BuAkPaRkXOuw9g@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f02d1c05c4f88c56"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4lB4KKpL-ITTaLyJ9y3KhEm1W9c>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 16:18:05 -0000

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

This is frustrating.   NP is a new design and the design issues should
have been discussed before we got to this point.   I don't know why so many
people are eager to not define the new technology.

There seems to be an unwillingness to acknowledge the current state of the
email ecosystem.  There seems to be a mythology that any email suffix used
with a mailing service must also exist elsewhere in the ecosystem as an
SMTP sender and receiver.   The MX/A/AAAA/.SPF seems to be based on this
myth.  There is no such necessity in the real world.

For a legitimate message, where a mailing service uses its own identity for
MailFrom and the client's identity for the From, the From address has very
few constraints:
- IETF format rules
- DMARC policy if present
- Mailing service business practices

On mailing service business practices:
I find that the major mailing services can be trusted to correctly present
the client organization.  But that does not include a requirement that the
email suffix has a separate identity as an SMTP sender and receiver.   My
data indicates that they will be happy to let @Example.Com send a message
from @EasterSale.Marketing.Example.com.

On DMARC policy
NP is only relevant if:
- The message does not authenticate.  DMARC PASS continues to be a final
result.
- A domain P policy does not apply.   P policies override SP and NP
policies.
- The SP policy is NONE and the NP policy is QUARANTINE or REJECT.   (If
the NP policy is the same as the SP policy, the result will be equivalent
to RFC7489 SP without NP.  If the NP policy is weaker than the SP policy,
the configuration is simply stupid.)

NP is an effort to partition the RFC 7489 SP=NONE result set, so that a
subset of all SP results can be blocked on some additional criteria.
This additional criterion could be based on non-existent as indicated by
NXDOMAIN, or it could be based on "not used for email" based on a criterion
to be defined.   Either approach needs to have a mechanism for
non-compliant names to be made compliant.   I believe that this should
involve a DNS entry, but the compliance measure should be specific to the
NP test.   Requiring that every FROM address be linked to an IP address
does not meet that requirement.

Doug Foster

Doug Foster


On Thu, Jun 17, 2021 at 3:57 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> I continue to not understand the defect you're highlighting here.
>
> I think you've expressed yourself primarily in the abstract.  Could you
> craft a sample message, sample envelope, and sample DNS context that
> highlights the problem you're talking about?  Maybe then it'll snap into
> focus.
>
> On Wed, Jun 16, 2021 at 2:43 PM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> NXDomain on RFC5322.From is a completely different issue.    It means
>> that the name is only used for service provider messaging, and is therefore
>> not linked to any IP address or other physical infrastructure.  It affects
>> the ability to define a meaningful NP test.   The issue becomes irrelevant
>> to DMARC if and only if we drop the NP policy idea completely.
>>
>> The proposed MX/A/AAAA/SPF test has two significant problems:
>> - It incorrectly classifies some names as NP because they do not need
>> MX/A/AAAA/SPF records because they are not tied to an IP address, and we
>> have provided a very poor mechanism for a domain owner to come into
>> compliance.
>>
>
> There's a workaround here: If I want to use a name that is not represented
> in the DNS according to that test, all I need to do is DKIM sign with my
> parent domain.  That makes "p" apply because now you have an aligned
> "pass", which presumably trumps any "np" that's set.
>
> If you aren't signing with DKIM in that scenario, and you obviously can't
> pass SPF either, then you can't possibly hope to pass DMARC irrespective of
> any test being done on the name's validity.
>
> - It incorrectly classifies some names that are not used for email as not
>> NP, simply because they have an A/AAAA record.   It provides no method for
>> the domain owner to signal that the name is not used for email and
>> therefore should be treated as NP.
>>
>
> If they're not used for email, then they're not in DMARC's problem space.
>
> At any rate, since PSD has been approved, I'm hoping the experiment is
> underway, or will be soon, and then we might have some actual data about
> the severity of this defect and thus also possibly some hints about ways it
> can be mitigated.
>
> -MSK
>

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

<div dir=3D"ltr">This is frustrating.=C2=A0 =C2=A0NP is a new design and th=
e design issues should have=C2=A0been discussed before we got to this point=
.=C2=A0 =C2=A0I don&#39;t know why so many people are eager to not define t=
he new technology.<div><div><br></div></div><div>There seems to be an unwil=
lingness to acknowledge the current=C2=A0state of the email ecosystem.=C2=
=A0 There seems to be a mythology that any email suffix used with a mailing=
 service must also exist elsewhere in the ecosystem as an SMTP sender and r=
eceiver.=C2=A0 =C2=A0The MX/A/AAAA/.SPF seems to be based on this myth.=C2=
=A0 There is no such necessity in the real world.</div><div></div><div><br>=
</div><div>For a legitimate message, where a mailing service uses its own i=
dentity for MailFrom and the client&#39;s identity for the From, the From a=
ddress has very few constraints:</div><div>- IETF format rules</div><div>- =
DMARC policy if present</div><div>- Mailing service business practices</div=
><div><br></div><div>On mailing service business practices:<br></div><div>I=
 find that the major mailing services can be trusted to correctly present t=
he client organization.=C2=A0 But that does not include a requirement that =
the email suffix has a separate identity as an SMTP sender and receiver.=C2=
=A0 =C2=A0My data indicates that they will be happy to let @Example.Com sen=
d a message from=C2=A0@<a href=3D"http://EasterSale.Marketing.Example.com">=
EasterSale.Marketing.Example.com</a>.</div><div><br></div><div>On DMARC pol=
icy</div><div>NP is only relevant if:</div><div>- The message does not auth=
enticate.=C2=A0 DMARC PASS continues to be a final result.</div><div>- A do=
main P policy does not apply.=C2=A0 =C2=A0P policies override SP and NP pol=
icies.</div><div>- The SP policy is NONE and the NP policy is QUARANTINE or=
 REJECT.=C2=A0 =C2=A0(If the NP policy is the same as the SP policy, the re=
sult will be equivalent to RFC7489 SP without NP.=C2=A0 If the NP policy is=
 weaker than the SP policy, the configuration is simply stupid.)</div><div>=
<br></div><div>NP is an effort to partition the RFC 7489 SP=3DNONE result s=
et, so that a subset of all SP results can be blocked on some additional cr=
iteria.=C2=A0 =C2=A0 This additional criterion could be based on non-existe=
nt as indicated by NXDOMAIN, or it could be based on &quot;not used for ema=
il&quot; based on a criterion to be defined.=C2=A0 =C2=A0Either approach ne=
eds to have a mechanism for non-compliant names to be made compliant.=C2=A0=
 =C2=A0I believe that this should involve a DNS entry, but the compliance m=
easure should be specific to the NP test.=C2=A0 =C2=A0Requiring that every =
FROM address be linked to an IP address does not meet that requirement.</di=
v><div><br></div><div>Doug Foster</div><div><br></div><div>Doug Foster</div=
><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Thu, Jun 17, 2021 at 3:57 AM Murray S. Kucherawy &lt;<a =
href=3D"mailto:superuser@gmail.com" target=3D"_blank">superuser@gmail.com</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div>I continue to not understand the defect you&#39;re high=
lighting here.</div><div><br></div><div>I think you&#39;ve expressed yourse=
lf primarily in the abstract.=C2=A0 Could you craft a sample message, sampl=
e envelope, and sample DNS context that highlights the problem you&#39;re t=
alking about?=C2=A0 Maybe then it&#39;ll snap into focus.<br></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jun 16=
, 2021 at 2:43 PM Douglas Foster &lt;<a href=3D"mailto:dougfoster.emailstan=
dards@gmail.com" target=3D"_blank">dougfoster.emailstandards@gmail.com</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div =
dir=3D"ltr">NXDomain on RFC5322.From is a completely different issue.=C2=A0=
 =C2=A0 It means that the name is only used for service provider messaging,=
 and is therefore not linked to any IP address or other physical infrastruc=
ture.=C2=A0 It affects the ability to define a meaningful NP test.=C2=A0 =
=C2=A0The issue becomes irrelevant to DMARC if and only if we drop the NP p=
olicy idea completely.<div><br></div><div>The proposed MX/A/AAAA/SPF test h=
as two significant problems:</div><div>- It incorrectly classifies some nam=
es as NP because they do not need MX/A/AAAA/SPF records because they are no=
t tied to an IP address, and we have provided a very poor mechanism for a d=
omain owner to come into compliance.</div></div></blockquote><div><br></div=
><div>There&#39;s a workaround here: If I want to use a name that is not re=
presented in the DNS according to that test, all I need to do is DKIM sign =
with my parent domain.=C2=A0 That makes &quot;p&quot; apply because now you=
 have an aligned &quot;pass&quot;, which presumably trumps any &quot;np&quo=
t; that&#39;s set.<br></div><div><br> </div><div>If you aren&#39;t signing =
with DKIM in that scenario, and you obviously can&#39;t pass SPF either, th=
en you can&#39;t possibly hope to pass DMARC irrespective of any test being=
 done on the name&#39;s validity.<br></div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>- It incorrectly cla=
ssifies some names that are not used for email as not NP, simply because th=
ey have an A/AAAA record.=C2=A0 =C2=A0It provides no method for the domain =
owner to signal that the name is not used for email and therefore should be=
 treated as NP.</div></div></blockquote><div><br></div><div>If they&#39;re =
not used for email, then they&#39;re not in DMARC&#39;s problem space.</div=
></div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">At a=
ny rate, since PSD has been approved, I&#39;m hoping the experiment is unde=
rway, or will be soon, and then we might have some actual data about the se=
verity of this defect and thus also possibly some hints about ways it can b=
e mitigated.</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_=
quote">-MSK<br></div></div>
</blockquote></div>

--000000000000f02d1c05c4f88c56--


From nobody Thu Jun 17 09:25:10 2021
Return-Path: <dougfoster.emailstandards@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E72D13A25D3 for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 09:25:07 -0700 (PDT)
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 DZj_0tNbNM0M for <dmarc@ietfa.amsl.com>; Thu, 17 Jun 2021 09:25:03 -0700 (PDT)
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 174353A25D2 for <dmarc@ietf.org>; Thu, 17 Jun 2021 09:25:02 -0700 (PDT)
Received: by mail-oi1-x230.google.com with SMTP id x196so7106154oif.10 for <dmarc@ietf.org>; Thu, 17 Jun 2021 09:25:02 -0700 (PDT)
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=D+uOdT0RFO49uKJevEB89XBqe2HYe5pTjoXFc/mDKpw=; b=CseXqQnBufELCvWtbBpvTREJfYUw2bG2TnJxcNgiqvoNB+Cl4BKVsIR+IaeZ8tGH+p LUgEOl0v52Qv1c1GR+c3GBWCx862nC5bPMe0en4yonHH5x5JBDSftXZHZblpD2ZDbxUt V25SErVPbBTNGFEQjDjaRPsOa1XvHaPWcwQR9Fd/9kLjs8S1+l8j86H5kE7Oh0ZPMDUq 1+YBQlhrAHhtxteF4ImjlEMM+E2egLC1FJoatgM9STS5I1dl/jwaem3ncT7K2DlIWQHj 0fcei9Jj7B/WLilu3+v68Xyl+6fUHjHmh7VARCemhJkISMjzpcKpsAchmgvuoONLUieJ uvGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=D+uOdT0RFO49uKJevEB89XBqe2HYe5pTjoXFc/mDKpw=; b=LvQWToI/D9WOnDFEZcRvOmj5Mc89NFoq8OI5TtWIUV1hFIDjARnzM/2cj3L7Ac/WvB 6WZ4d2S/V9XPfW4pNoHIhfPfiSw4aH0iwryljOshctMqYiMe8QWIASD2qiajJcD4aQyY SW+M/DfcdI2lztDN3ui+g+LRmyquGnpad0AAM8IhAe9z6ZQ0WwXD63ZpACv+AFg/O3O5 A6ZWpwbS+QwNlI0gpGIv48XSXx06Bxn53ah2Fu4w17PRzlG325I2IBe/VeEop+G+XpxR 5uk+/FfrS6AmEtq/YuNjDiQfP7OGmM7G6RxOTHBAXCvKv6lNMYsZo3+5aNECqi7dMZGR 0D0g==
X-Gm-Message-State: AOAM5339s2gvlrUJNh9sHQGJ8E8USv8O2XxA6Xgq/9bT5lLcNSO6E5Gp hHmqvHv/azf8CBot0DoF9RQdnmk5s4Y2IdJuLLzATp0b
X-Google-Smtp-Source: ABdhPJyIy+Vcmugxo/mynBGQxM8Vu186vQQNsqZ+mVkNm6ACTu6waowJKR5cdHuqjAMIZJpBpxzNN+gBcnoNdBPzBFs=
X-Received: by 2002:aca:1802:: with SMTP id h2mr1929299oih.146.1623947101422;  Thu, 17 Jun 2021 09:25:01 -0700 (PDT)
MIME-Version: 1.0
References: <20210616180222.53DC311FBCDC@ary.qy> <6e76e4af-e592-0103-33dc-4cda6b129071@tana.it>
In-Reply-To: <6e76e4af-e592-0103-33dc-4cda6b129071@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Thu, 17 Jun 2021 12:24:51 -0400
Message-ID: <CAH48Zfw+KEvAuZ6qPhFNhVdJg3TJR7ZBX-FCAMHezf22sbEs_g@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001d488905c4f8a6d7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Yv04RXJDeE-kPkfRlSuN_9RpqaM>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jun 2021 16:25:08 -0000

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

Yes, The test should most certainly define how MX="." and SPF="-ALL"
affect the test.  This is why I said that the test needs a more complete
definition, but many were unwilling to even address that part of the
problem.

Even with those modifications, the test is only applicable for names that
are also used for SMTP MAILFROM.   This does not cover all names that are
used for FROM.

I infer that the A/AAAA component is included in the test definition
because these might indicate an implicit MX.   The use of implicit MX is
unnecessary, and I suspect unlikely to be in use by DMARC-publishing
domains.    It would a minor compliance step to require domain owners to
replace implicit MX with explicit MX, so that the test will accurately
indicate names that are used for SMTP purposes.

Doug Foster



On Thu, Jun 17, 2021 at 7:13 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Wed 16/Jun/2021 20:02:21 +0200 John Levine wrote:
> > Let's close ticket #112 and stop.
>
>
> I agree that the definition given in the PSD is clear enough:
>
>     For DMARC purposes, a non-existent domain is a domain for which there
>     is an NXDOMAIN or NODATA response for A, AAAA, and MX records.  This
>     is a broader definition than that in [RFC8020].
>
> However, by that definition a domain with a Null MX [RFC7505] is an
> existent
> domain for DMARC purposes.  Perhaps this apparent contradiction could be
> noted
> by adding a sentence somewhere, for example:
>
>     Even though the bare existence of a domain does not entail that it can
> send
>     or receive email, the presence or absence of the relevant DNS RRs
> determines
>     which policy between sp= and np= is applicable.  If a DMARC record is
> found
>     for a domain that would be non-existent by the above definition, the p=
>     policy defined there is still the one to be applied.
>
> Would that add clarity?
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr"><div dir=3D"ltr">Yes, The test should most certainly defin=
e how MX=3D&quot;.&quot; and SPF=3D&quot;-ALL&quot; affect=C2=A0the test.=
=C2=A0 This is why I said that the test needs a more complete definition, b=
ut many were unwilling to even address that part of the problem.<div><div><=
br></div><div>Even with those modifications, the test is only applicable fo=
r names that are also used for SMTP MAILFROM.=C2=A0 =C2=A0This does not cov=
er all names that are used for FROM.<br></div><div><br></div><div>I infer t=
hat the A/AAAA component is included in the test definition because these m=
ight indicate an implicit MX.=C2=A0 =C2=A0The use of implicit MX is unneces=
sary, and I suspect unlikely to be in use by DMARC-publishing domains.=C2=
=A0 =C2=A0 It would a minor compliance step to require domain owners to rep=
lace implicit MX with explicit MX, so that the test will accurately indicat=
e names that are used for SMTP purposes.=C2=A0</div><div><br></div><div>Dou=
g Foster</div><div><br><br></div></div></div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jun 17, 2021 at 7:13 AM Ales=
sandro Vesely &lt;<a href=3D"mailto:vesely@tana.it">vesely@tana.it</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed 16=
/Jun/2021 20:02:21 +0200 John Levine wrote:<br>
&gt; Let&#39;s close ticket #112 and stop.<br>
<br>
<br>
I agree that the definition given in the PSD is clear enough:<br>
<br>
=C2=A0 =C2=A0 For DMARC purposes, a non-existent domain is a domain for whi=
ch there<br>
=C2=A0 =C2=A0 is an NXDOMAIN or NODATA response for A, AAAA, and MX records=
.=C2=A0 This<br>
=C2=A0 =C2=A0 is a broader definition than that in [RFC8020].<br>
<br>
However, by that definition a domain with a Null MX [RFC7505] is an existen=
t <br>
domain for DMARC purposes.=C2=A0 Perhaps this apparent contradiction could =
be noted <br>
by adding a sentence somewhere, for example:<br>
<br>
=C2=A0 =C2=A0 Even though the bare existence of a domain does not entail th=
at it can send<br>
=C2=A0 =C2=A0 or receive email, the presence or absence of the relevant DNS=
 RRs determines<br>
=C2=A0 =C2=A0 which policy between sp=3D and np=3D is applicable.=C2=A0 If =
a DMARC record is found<br>
=C2=A0 =C2=A0 for a domain that would be non-existent by the above definiti=
on, the p=3D<br>
=C2=A0 =C2=A0 policy defined there is still the one to be applied.<br>
<br>
Would that add clarity?<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>
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>

--0000000000001d488905c4f8a6d7--


From nobody Fri Jun 18 00:01:57 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 8E2A03A3FBF for <dmarc@ietfa.amsl.com>; Fri, 18 Jun 2021 00:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HaVdoi0IN9jf for <dmarc@ietfa.amsl.com>; Fri, 18 Jun 2021 00:01:53 -0700 (PDT)
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 B0BEF3A3FBE for <dmarc@ietf.org>; Fri, 18 Jun 2021 00:01:53 -0700 (PDT)
Received: by mail-vs1-xe32.google.com with SMTP id 68so4417101vsu.6 for <dmarc@ietf.org>; Fri, 18 Jun 2021 00:01:53 -0700 (PDT)
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=rRzsxjjsVTBUGuTXvs4AFvXn48A+kLcLGCzXGyVHDlw=; b=BJqJToKVnQadM/3CEO27zPf5fMxDyB0hqsEA92ovcJI/Y6AtSzmFUx1sa+ZD2XU4nJ qw+U+N/WtAVqGQGqyusQk1sK1Jy63NbbFFinpQB6S43Gzzm1mxhTH19agIF9uusSCbJ1 llw3ukTn/tLUeiw3pTmiuRxh8hPRdSP1fAbQ9uzoT/0RrGuHRw1RzWS9Epe6yrN8TtEq jHgtFO1qmb5jlETBA+xzcdj+LAJcLL9UvHxpS2j+hqZRnKNI/WmnSQqP5YLHGC4eaVr3 SQb358dg7Hsb6ASfm3oRn1fmSl7cz6Q/1xByBjvpWlhHZIu9B7O9lLaZuwgXmyI7dHRZ Bcsg==
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=rRzsxjjsVTBUGuTXvs4AFvXn48A+kLcLGCzXGyVHDlw=; b=XRgDfAa1wH53EHsr9K5fUo9boDpOYQ8jEniEI8839+xMJp0idUsHp/l/0+6sZFQXbc NACUCc17n9NOoeqNOV45m9CJQxCLE1YD3gNbAfbJ2qH0E6u5BLfjhvhYy/Tdcqa/9jCq V90nKV1aoHyAOxh7ZxVQFKdVyvTMTxQ4Ee6eY9zxJyPfqMc2euKsqACLUoX8aiH+laCy wQlWoC9IUgiWi05GglEAOVIcd2Iv28L+CUNzpGVbbhpC/PJhC9d183EP2QNYUu97qR3c HeSz0DfOf3USxaEw2DJYHAr9SuD/wFOV6BF+TjltI1lCeLVkVp2CtXNDfCjMZYhlDZbk 31fg==
X-Gm-Message-State: AOAM530flkiF+x9kzXnKR4G8mLcDIWQOjyKghoRtpG+C7uUuJkYcXmgU T4bm7TftQjUIsybApGRwTrUVovaNoO3aOCoVhgo=
X-Google-Smtp-Source: ABdhPJwZw2DQBrtzp9/t+6fm5tTG+AjSDgVZbtfgsYQmk0Itsej1V4b+xIVXKaerYfoFF8csmRTdjLhFJiFrvfoHYyc=
X-Received: by 2002:a67:ef82:: with SMTP id r2mr5274345vsp.0.1623999710663; Fri, 18 Jun 2021 00:01:50 -0700 (PDT)
MIME-Version: 1.0
References: <20210616160110.09D6011E70FD@ary.qy> <71e61630-0bc8-c9f1-6e7c-5267889c15af@tana.it> <CAH48ZfyYSW5003cxgP0r_skzSdfNvV9FL=sY_32PwQ1dWXxFCg@mail.gmail.com> <CAL0qLwYsTgRJ8PnjG7nAdTJJ54ww2HWtvOGp2EeMqNStjD6X8A@mail.gmail.com> <CAH48ZfzddEUcph74bZLoPnx5Ri9sEh31Ni8+BuAkPaRkXOuw9g@mail.gmail.com>
In-Reply-To: <CAH48ZfzddEUcph74bZLoPnx5Ri9sEh31Ni8+BuAkPaRkXOuw9g@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 18 Jun 2021 00:01:39 -0700
Message-ID: <CAL0qLwa6Z8Q-Amt4cQ3WcfE8ia6NqqD6JL4u1ydJ=B2WiG3qHA@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000de992405c504e564"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/2feLm-iBBsREqhuzwJTYk9fQ55Q>
Subject: Re: [dmarc-ietf] Ticket #11 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 18 Jun 2021 07:01:56 -0000

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

On Thu, Jun 17, 2021 at 9:18 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> This is frustrating.   NP is a new design and the design issues should
> have been discussed before we got to this point.   I don't know why so many
> people are eager to not define the new technology.
>

Please don't conflate "I still don't understand what you're talking about"
with "I am eager not to define NP" or "I am unwilling to acknowledge
(something)".  They're not the same thing, and only the former is true.

Your message continues to assert something abstract.  I'll repeat my
previous request:

Could you craft a sample message (including DKIM details), sample envelope,
and sample DNS context (including A, AAAA, MX, and SPF details) that
highlights the problem you're talking about?  Maybe then it'll snap into
focus.

NP is an effort to partition the RFC 7489 SP=NONE result set, so that a
> subset of all SP results can be blocked on some additional criteria.
> This additional criterion could be based on non-existent as indicated by
> NXDOMAIN, or it could be based on "not used for email" based on a criterion
> to be defined.   Either approach needs to have a mechanism for
> non-compliant names to be made compliant.   I believe that this should
> involve a DNS entry, but the compliance measure should be specific to the
> NP test.   Requiring that every FROM address be linked to an IP address
> does not meet that requirement.
>

If I squint at this, maybe I can see what you're trying to argue: "
example.com" can't publish an "np" policy if they use a subdomain of "
example.com" that has no representation of any kind in the DNS.  Is that
correct?  If so, do you find this to be a defect, or simply a limitation to
be documented?  If you think it's a defect, why is that so?

-MSK

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

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jun 17, 2021 at 9:18 AM Douglas F=
oster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com">dougfoster=
.emailstandards@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">This i=
s frustrating.=C2=A0 =C2=A0NP is a new design and the design issues should =
have=C2=A0been discussed before we got to this point.=C2=A0 =C2=A0I don&#39=
;t know why so many people are eager to not define the new technology.</div=
></blockquote><div><br></div><div>Please don&#39;t conflate &quot;I still d=
on&#39;t understand what you&#39;re talking about&quot; with &quot;I am eag=
er not to define NP&quot; or &quot;I am unwilling to acknowledge (something=
)&quot;.=C2=A0 They&#39;re not the same thing, and only the former is true.=
<br></div><div><br></div><div>Your message continues to assert something ab=
stract.=C2=A0 I&#39;ll repeat my previous request:</div><div><br></div><div=
><div>Could you craft a sample message (including DKIM details), sample env=
elope, and sample DNS=20
context (including A, AAAA, MX, and SPF details) that highlights the proble=
m you&#39;re talking about?=C2=A0 Maybe then=20
it&#39;ll snap into focus.<br></div></div><div> <br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div></div>NP is an effor=
t to partition the RFC 7489 SP=3DNONE result set, so that a subset of all S=
P results can be blocked on some additional criteria.=C2=A0 =C2=A0 This add=
itional criterion could be based on non-existent as indicated by NXDOMAIN, =
or it could be based on &quot;not used for email&quot; based on a criterion=
 to be defined.=C2=A0 =C2=A0Either approach needs to have a mechanism for n=
on-compliant names to be made compliant.=C2=A0 =C2=A0I believe that this sh=
ould involve a DNS entry, but the compliance measure should be specific to =
the NP test.=C2=A0 =C2=A0Requiring that every FROM address be linked to an =
IP address does not meet that requirement.<br></div></blockquote><div>=C2=
=A0</div><div>If I squint at this, maybe I can see what you&#39;re trying t=
o argue: &quot;<a href=3D"http://example.com">example.com</a>&quot; can&#39=
;t publish an &quot;np&quot; policy if they use a subdomain of &quot;<a hre=
f=3D"http://example.com">example.com</a>&quot; that has no representation o=
f any kind in the DNS.=C2=A0 Is that correct?=C2=A0 If so, do you find this=
 to be a defect, or simply a limitation to be documented?=C2=A0 If you thin=
k it&#39;s a defect, why is that so?<br></div><div><br></div><div>-MSK<br><=
/div></div></div>

--000000000000de992405c504e564--


From nobody Sun Jun 20 03:00:18 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 19A763A0B22 for <dmarc@ietfa.amsl.com>; Sun, 20 Jun 2021 03:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 BA7-6I1hYUhM for <dmarc@ietfa.amsl.com>; Sun, 20 Jun 2021 03:00:08 -0700 (PDT)
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 E3BF93A0B28 for <dmarc@ietf.org>; Sun, 20 Jun 2021 03:00:07 -0700 (PDT)
Received: (qmail 3619 invoked by uid 100); 20 Jun 2021 10:00:07 -0000
Date: 20 Jun 2021 09:59:45 -0000
Message-ID: <20210620095945.3618.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/4yNRUY4Wh5Dy_6jdOWHDfLbZRKg>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Jun 20 06:00:06 2021
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Jun 2021 10:00:13 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
 34 ( 100%) | 344046 ( 100%) | Total
  6 (17.6%) |  71897 (20.9%) | Todd Herr <todd.herr@valimail.com>
  6 (17.6%) |  27299 ( 7.9%) | John Levine <johnl@taugh.com>
  5 (14.7%) |  27070 ( 7.9%) | Alessandro Vesely <vesely@tana.it>
  4 (11.8%) |  57847 (16.8%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  2 ( 5.9%) |  29813 ( 8.7%) | Ken O'Driscoll <ken@wemonitoremail.com>
  2 ( 5.9%) |  29281 ( 8.5%) | Brotman, Alex <alex_brotman@comcast.com>
  2 ( 5.9%) |  19392 ( 5.6%) | Murray S. Kucherawy <superuser@gmail.com>
  1 ( 2.9%) |  25145 ( 7.3%) | Tobias Herkula <tobias.herkula@1und1.de>
  1 ( 2.9%) |  18845 ( 5.5%) | Trent Adams <tadams@proofpoint.com>
  1 ( 2.9%) |  12891 ( 3.7%) | Seth Blank <seth@valimail.com>
  1 ( 2.9%) |  10193 ( 3.0%) | Zachary Aab <zachary.aab@gmail.com>
  1 ( 2.9%) |   6648 ( 1.9%) | Dotzero <dotzero@gmail.com>
  1 ( 2.9%) |   4492 ( 1.3%) | Steven M Jones <smj@crash.com>
  1 ( 2.9%) |   3233 ( 0.9%) |  <internet-drafts@ietf.org>


From nobody Mon Jun 21 06:36:36 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 3E8003A0F0E; Mon, 21 Jun 2021 06:36:31 -0700 (PDT)
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.32.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dmarc@ietf.org
Message-ID: <162428259119.8045.17042995497056731302@ietfa.amsl.com>
Date: Mon, 21 Jun 2021 06:36:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/S4h2nwWHomY03a2b4K7t3dcLFX8>
Subject: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dmarcbis-02.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: Mon, 21 Jun 2021 13:36:31 -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)
        Authors         : Todd M. Herr
                          John Levine
	Filename        : draft-ietf-dmarc-dmarcbis-02.txt
	Pages           : 69
	Date            : 2021-06-21

Abstract:
   This document describes the Domain-based Message Authentication,
   Reporting, and Conformance (DMARC) protocol.

   DMARC permits the owner of an email author's domain name to enable
   validation of the domain's use, to indicate the Domain Owner's or
   Public Suffix Operator's severity of concern regarding failed
   validation, and to request reports about use of the domain name.
   Mail receiving organizations can use this information when evaluating
   handling choices for incoming mail.

   This document obsoletes RFC 7489.


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

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

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


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Jun 21 21:17:51 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 0B2E93A116C for <dmarc@ietfa.amsl.com>; Mon, 21 Jun 2021 21:17:50 -0700 (PDT)
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 xG6XH6Y-cbcH for <dmarc@ietfa.amsl.com>; Mon, 21 Jun 2021 21:17:45 -0700 (PDT)
Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F111B3A1168 for <dmarc@ietf.org>; Mon, 21 Jun 2021 21:17:44 -0700 (PDT)
Received: by mail-ot1-x331.google.com with SMTP id i10-20020a9d68ca0000b029045d4c970c96so1218294oto.6 for <dmarc@ietf.org>; Mon, 21 Jun 2021 21:17:44 -0700 (PDT)
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=zWUoiygmNhiI9n1zu94AJUCaWb4tuq1dAv7BrRX2uAk=; b=s237JIlEfs20ara7EykOhPH0qWil/QZlZLi7Xjdz3yaWg1IHNmcl9cOSeOvg02aXKP jAhMULkyeYR7HMjfHXLydkrDRoqJDNXOwiiiGIV3bjulUtcYjhtFZBLDhfRtgQeSOAuv RBpqy5jegmCfv1CSLlcnUpbQ0q0Cdfzrzv+kDN9W/bWpP6Fo8k5NORiydOvFijVuyXQz iGtJFyAzsq46DnPBYlOlEwpy52M8uNR9V0X42asviNF6o7utEeZU/GA3SmBZ0+bjFc2o pTTFd+yIYykTBGRmUNyxBus4M3HnkvoMjGbeM9yQH5KQaGazFS/WMrTLfKoFn1iKQSEY sGXQ==
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=zWUoiygmNhiI9n1zu94AJUCaWb4tuq1dAv7BrRX2uAk=; b=KvgMULWmvZrDcMj7kRL9IZHVWtgs/bBJqCPzlQUv732FX77tIPpXmjXXOQJMAbOd7u Q6qJopgFWD+p7IbERW1WRPD/uXj6j7i1YJzmEEL927D4CFsxmQJY/etOQq2sAQHsvs5l VoYly/Yusu//QO8cHH19qEYCbC06lFu6aD+GlpqstywZzuIOV5OqyCuRAtnyv4NZ+KBv OQCOIFEWEhMtBy3Nwv+YpA/9DaWCOPLPfjAd2QpW9d2t9F5GXFDoncMiKl2+FilVTKIU k8VPItfX2gwDQ+3wgHJZdJZY98sbO4AzXedKN7NdcZ4wyREw15xnfYkiFTI0jY6SQch3 WAEA==
X-Gm-Message-State: AOAM530XPg75dcfsM+LfWcXNHgZZDa5SlqDk0HvYlZhCJQI7KMz7cskw 5G7Ou9u16HpXzpA/PEyHKGXsDFDqMeDZMkt+Sl4=
X-Google-Smtp-Source: ABdhPJxn7NBKSSnXoh89qECgTHoX3NTp6hg2U34ffmFJaZ68ISfVFR9GZQnvw8e8bJx5ityCznAJVjGWR372Ejb/TMQ=
X-Received: by 2002:a05:6830:1102:: with SMTP id w2mr1198037otq.298.1624335463193;  Mon, 21 Jun 2021 21:17:43 -0700 (PDT)
MIME-Version: 1.0
References: <20210616160110.09D6011E70FD@ary.qy> <71e61630-0bc8-c9f1-6e7c-5267889c15af@tana.it> <CAH48ZfyYSW5003cxgP0r_skzSdfNvV9FL=sY_32PwQ1dWXxFCg@mail.gmail.com> <CAL0qLwYsTgRJ8PnjG7nAdTJJ54ww2HWtvOGp2EeMqNStjD6X8A@mail.gmail.com>
In-Reply-To: <CAL0qLwYsTgRJ8PnjG7nAdTJJ54ww2HWtvOGp2EeMqNStjD6X8A@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 22 Jun 2021 00:17:33 -0400
Message-ID: <CAH48Zfz6tMw_RSPn-U1Jce1tsGur6mqjXgZpqUVAwP0mT4BfVA@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000047c20505c55312c4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/RrQij0q80phZsVfunTINuQ8QQ4A>
Subject: Re: [dmarc-ietf] Ticket #111 (and #112) - Proposed language
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 22 Jun 2021 04:17:50 -0000

--00000000000047c20505c55312c4
Content-Type: text/plain; charset="UTF-8"

I am providing two types of examples:
1) A legitimate sender using a non-existent name,
2) An impersonating sender using undefended non-domain names.


Valid Message Example
===================

MailFrom:  info99@service.govdelivery.com
From:         updates@secure.hiltonheadislandsc.gov
Signature: None
DMARC Policy:   Not currently configured.
SPF Status:   PASS
FROM Status:  NXDOMAIN

What happens when they implement DMARC?

One possibility is that they create a DKIM signature for
"scope1._domainkey. secure.hiltonheadislandsc.gov"   This ensures DMARC
PASS as long as the signature validates.

But if the message is modified in transit, the signature will no longer
validate.   Which policy should apply?   If the public key was successfully
retrieved, then the name certainly exists, and is used for DKIM signing, so
it should be SP.   But it does not yet meet the MX/A/AAAA/SPF test, so our
draft calls for it to be evaluated as NP.

To meet the MX/A/AAAA/SPF tests, the sender must create one of those four
DNS records.   But which one is relevant?   None of them.


Attack Scenario Examples
====================

Assume:  Example.com has DMARC policy of "p=reject, sp=none, np=none"

Also assume that "spammer.tld" decides it will be profitable to impersonate
example.com, and begins this data collection:

Research:
1. Spammer scans the example.com website, collecting host names.
2. Spammer performs MX and SPF lookups to collect additional host names.
3. Spammer performs DNS lookup on some other commonly-used names to see if
they exist.
4. Spammer notes that while "example.com" is protected by SPF and DMARC
p=reject, individual hosts do not have an SPF policy.

Strategy
Spammer does not want to risk being blocked by DMARC p=reject, so he will
not use "example.com" directly.
Spammer does not want to be blocked by SPF NXDOMAIN, so he will not use a
non-existent MAILFROM domain.
Spammer choses "mail.example.com" as the preferred impersonation domain.


Attack Scenario 1:  Spammer gets lucky, because the MX for "example.com" is
the host "mail.example.com".   Spammer has these options;

a) Pretend to be a mailing service, using spammer.tld as the SPF context:
MAILFROM=user@spammer.tld
FROM=user@mail.example.com
Sender authentication evaluates to SPF=PASS and DMARC policy SP applies.

Example.com has these sender-authentication defense options for this attack:
- Changing mail.example.com to a subdomain and creating a subdomain DMARC
P=reject/quarantine policy, or
- Changing the organization policy to sp=reject/quarantine


b) Pretend to be a direct message
MAILFROM=user@mail.example.com
FROM=user@mail.example.com
Sender authentication evaluates to SPF=NONE and DMARC policy SP applies.

Example.com has these sender-authentication defense options for this attack:
- Create an SPF "-ALL" policy for "mail.example.com"
- Changing mail.example.com to a subdomain and creating a subdomain DMARC
P=reject/quarantine policy, or
- Changing the organization policy to sp=reject/quarantine


================

Scenario 2:  Spammer notes that "mail.example.com" is not a defined host.
 Spammer has these options:

a) Pretend to be a mailing service, using spammer.tld as the SPF context:
MAILFROM=user@spammer.tld
FROM=user@mail.example.com
Sender authentication evaluates to SPF=PASS and DMARC policy NP applies.

Example.com has these sender-authentication defense options for this attack:
- Changing mail.example.com to a subdomain and creating a subdomain DMARC
P=reject/quarantine policy, or
- Changing the organization policy to sp=reject/quarantine


b) Pretend to be a mailing service, sent by a host in the target domain:
MAILFROM=user@www.example.com
FROM=user@mail.example.com
Sender authentication evaluates to SPF=NONE and DMARC policy NP applies.

Example.com has these sender-authentication defense options for this attack:
- Create an SPF "-ALL" policy for "www.example.com", or
- Changing mail.example.com to a subdomain and creating a subdomain DMARC
P=reject/quarantine policy, or
- Changing the organization policy to sp=reject/quarantine, or
- Changing the organization policy to np=reject/quarantine




On Thu, Jun 17, 2021 at 3:57 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> I continue to not understand the defect you're highlighting here.
>
> I think you've expressed yourself primarily in the abstract.  Could you
> craft a sample message, sample envelope, and sample DNS context that
> highlights the problem you're talking about?  Maybe then it'll snap into
> focus.
>
> On Wed, Jun 16, 2021 at 2:43 PM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> NXDomain on RFC5322.From is a completely different issue.    It means
>> that the name is only used for service provider messaging, and is therefore
>> not linked to any IP address or other physical infrastructure.  It affects
>> the ability to define a meaningful NP test.   The issue becomes irrelevant
>> to DMARC if and only if we drop the NP policy idea completely.
>>
>> The proposed MX/A/AAAA/SPF test has two significant problems:
>> - It incorrectly classifies some names as NP because they do not need
>> MX/A/AAAA/SPF records because they are not tied to an IP address, and we
>> have provided a very poor mechanism for a domain owner to come into
>> compliance.
>>
>
> There's a workaround here: If I want to use a name that is not represented
> in the DNS according to that test, all I need to do is DKIM sign with my
> parent domain.  That makes "p" apply because now you have an aligned
> "pass", which presumably trumps any "np" that's set.
>
> If you aren't signing with DKIM in that scenario, and you obviously can't
> pass SPF either, then you can't possibly hope to pass DMARC irrespective of
> any test being done on the name's validity.
>
> - It incorrectly classifies some names that are not used for email as not
>> NP, simply because they have an A/AAAA record.   It provides no method for
>> the domain owner to signal that the name is not used for email and
>> therefore should be treated as NP.
>>
>
> If they're not used for email, then they're not in DMARC's problem space.
>
> At any rate, since PSD has been approved, I'm hoping the experiment is
> underway, or will be soon, and then we might have some actual data about
> the severity of this defect and thus also possibly some hints about ways it
> can be mitigated.
>
> -MSK
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div>I am providing two types of examples=
:=C2=A0 =C2=A0</div><div>1) A legitimate sender using a non-existent name,=
=C2=A0</div><div>2) An impersonating=C2=A0sender using undefended non-domai=
n names.</div><div><br></div><div><br></div><div>Valid Message Example</div=
><div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div><div><=
br></div><div>MailFrom:=C2=A0 <a href=3D"mailto:info99@service.govdelivery.=
com">info99@service.govdelivery.com</a><br style=3D"box-sizing:border-box">=
From:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:updates@secure.hil=
tonheadislandsc.gov">updates@secure.hiltonheadislandsc.gov</a><br></div><di=
v>Signature: None</div><div>DMARC Policy:=C2=A0 =C2=A0Not currently configu=
red.</div><div>SPF Status:=C2=A0 =C2=A0PASS</div><div>FROM Status:=C2=A0 NX=
DOMAIN</div><div><br></div><div>What happens when they implement DMARC?</di=
v><div><br></div><div>One possibility is that they create a DKIM signature =
for &quot;scope1._domainkey.

<a href=3D"http://secure.hiltonheadislandsc.gov">secure.hiltonheadislandsc.=
gov</a>&quot;=C2=A0 =C2=A0This ensures DMARC PASS as long as the signature =
validates.</div><div><br></div><div>But if the message is modified in trans=
it, the signature will no longer validate.=C2=A0 =C2=A0Which policy should =
apply?=C2=A0 =C2=A0If the public key was successfully retrieved, then the n=
ame certainly exists, and is used for DKIM signing, so it should be SP.=C2=
=A0 =C2=A0But it does not yet meet the MX/A/AAAA/SPF test, so our draft cal=
ls for it to be evaluated as NP.</div><div><br></div><div>To meet the MX/A/=
AAAA/SPF tests, the sender must create one of those four DNS records.=C2=A0=
 =C2=A0But which one is relevant?=C2=A0 =C2=A0None of them.</div><div><br><=
/div><div><br></div><div>Attack Scenario Examples</div><div>=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div><div><br></div><div>Assu=
me:=C2=A0 Example.com has DMARC policy of &quot;p=3Dreject, sp=3Dnone, np=
=3Dnone&quot;</div><div><br></div><div>Also assume that &quot;spammer.tld&q=
uot; decides it will be profitable to impersonate <a href=3D"http://example=
.com">example.com</a>, and begins this data collection:</div><div><br></div=
><div>Research:</div><div>1. Spammer scans the <a href=3D"http://example.co=
m">example.com</a> website, collecting=C2=A0host names.<br></div><div>2. Sp=
ammer performs MX and SPF lookups to collect additional host names.</div><d=
iv>3. Spammer performs=C2=A0DNS lookup on some other commonly-used names to=
 see if they exist.</div><div><div>4. Spammer notes that while &quot;<a hre=
f=3D"http://example.com">example.com</a>&quot; is protected by SPF and DMAR=
C p=3Dreject, individual=C2=A0hosts do not have an=C2=A0SPF policy.</div><d=
iv></div></div><div><br></div><div>Strategy</div><div>Spammer does not want=
 to risk being blocked by DMARC p=3Dreject, so he will not use &quot;<a hre=
f=3D"http://example.com">example.com</a>&quot; directly.</div><div>Spammer=
=C2=A0does not want to be blocked by SPF NXDOMAIN, so he will not use a non=
-existent MAILFROM domain.</div><div>Spammer choses &quot;<a href=3D"http:/=
/mail.example.com">mail.example.com</a>&quot; as the preferred impersonatio=
n domain.</div><div><br></div><div><br></div><div>Attack Scenario 1:=C2=A0 =
Spammer gets lucky, because the MX for &quot;<a href=3D"http://example.com"=
>example.com</a>&quot; is the host &quot;<a href=3D"http://mail.example.com=
">mail.example.com</a>&quot;.=C2=A0 =C2=A0Spammer has these options;<br><br=
></div><div>a) Pretend to be a mailing service, using spammer.tld as the SP=
F context:</div><div>MAILFROM=3Duser@spammer.tld</div><div>FROM=3D<a href=
=3D"mailto:user@mail.example.com">user@mail.example.com</a></div><div>Sende=
r authentication evaluates to SPF=3DPASS and DMARC policy SP applies.</div>=
<div><br></div><blockquote style=3D"margin:0 0 0 40px;border:none;padding:0=
px"><div>Example.com has these sender-authentication defense options for th=
is attack:</div><div><div><div>-=20

Changing <a href=3D"http://mail.example.com">mail.example.com</a> to a subd=
omain and creating a subdomain DMARC P=3Dreject/quarantine policy, or</div>=
</div></div><div>- Changing the organization policy to sp=3Dreject/quaranti=
ne</div></blockquote><div><br></div><div>b) Pretend to be a direct message<=
/div><div><div><div>MAILFROM=3D<a href=3D"mailto:user@mail.example.com">use=
r@mail.example.com</a></div><div></div></div><div></div><div>FROM=3D<a href=
=3D"mailto:user@mail.example.com">user@mail.example.com</a><br></div><div><=
/div></div><div><div>Sender authentication evaluates to SPF=3DNONE and DMAR=
C policy SP applies.</div><div></div></div><div><br></div><blockquote style=
=3D"margin:0 0 0 40px;border:none;padding:0px"><div><div>Example.com has th=
ese sender-authentication defense options for this attack:</div></div><div>=
<div>- Create an SPF &quot;-ALL&quot; policy for &quot;<a href=3D"http://ma=
il.example.com">mail.example.com</a>&quot;</div></div><div><div>-=20

Changing <a href=3D"http://mail.example.com">mail.example.com</a> to a subd=
omain and creating a subdomain DMARC P=3Dreject/quarantine policy, or</div>=
<div><div><div></div></div></div></div><div><div>- Changing the organizatio=
n policy to sp=3Dreject/quarantine</div></div></blockquote><div><div></div>=
</div><div><div><br></div><div></div></div><div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D</div><div><br></div><div><div>Scenario 2:=C2=A0 Spamm=
er notes that &quot;<a href=3D"http://mail.example.com">mail.example.com</a=
>&quot; is not a defined host.=C2=A0 =C2=A0Spammer has these options:<br><b=
r></div><div></div></div><div><div>a) Pretend to be a mailing service, usin=
g spammer.tld as the SPF context:</div><div></div><div>MAILFROM=3Duser@spam=
mer.tld<br></div><div>FROM=3D<a href=3D"mailto:user@mail.example.com">user@=
mail.example.com</a></div><div>Sender authentication evaluates to SPF=3DPAS=
S and DMARC policy NP applies.</div><div><br></div></div><blockquote style=
=3D"margin:0 0 0 40px;border:none;padding:0px"><div><div><div>Example.com h=
as these sender-authentication defense options for this attack:</div></div>=
</div><div><div><div>-=20

Changing <a href=3D"http://mail.example.com">mail.example.com</a> to a subd=
omain and creating a subdomain DMARC P=3Dreject/quarantine policy, or</div>=
</div></div><div><div><div>- Changing the organization policy to sp=3Drejec=
t/quarantine</div></div></div></blockquote><div><div><div></div></div></div=
><div><div><div></div></div><div><br></div><div><div>b) Pretend to be a mai=
ling service, sent by a host in the target domain:</div><div></div></div><d=
iv><div><div><div><div>MAILFROM=3D<a href=3D"mailto:user@www.example.com">u=
ser@www.example.com</a></div><div></div></div><div></div><div>FROM=3D<a hre=
f=3D"mailto:user@mail.example.com">user@mail.example.com</a><br></div><div>=
</div></div><div><div>Sender authentication evaluates to SPF=3DNONE and DMA=
RC policy NP applies.</div><div></div></div><div></div></div><div><br></div=
></div></div><blockquote style=3D"margin:0 0 0 40px;border:none;padding:0px=
"><div><div><div><div><div>Example.com has these sender-authentication defe=
nse options for this attack:</div></div></div></div></div><div><div><div><d=
iv><div>- Create an SPF &quot;-ALL&quot; policy for &quot;<a href=3D"http:/=
/www.example.com">www.example.com</a>&quot;, or</div></div></div></div></di=
v><div><div><div><div><div>- Changing <a href=3D"http://mail.example.com">m=
ail.example.com</a> to a subdomain and creating a subdomain DMARC P=3Drejec=
t/quarantine policy, or</div></div></div></div></div><div><div><div><div>- =
Changing the organization policy to sp=3Dreject/quarantine, or</div></div><=
/div></div><div><div><div><div><div>- Changing the organization policy to n=
p=3Dreject/quarantine</div></div></div></div></div></blockquote><div><div><=
div><div><div></div></div></div></div></div><div><div><div><div></div></div=
></div></div><div><div><div><div><div><br></div><div></div></div><div></div=
></div><div></div></div><div><br></div></div></div><br><div class=3D"gmail_=
quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jun 17, 2021 at 3:57 A=
M Murray S. Kucherawy &lt;<a href=3D"mailto:superuser@gmail.com">superuser@=
gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><div>I continue to not understand the defect yo=
u&#39;re highlighting here.</div><div><br></div><div>I think you&#39;ve exp=
ressed yourself primarily in the abstract.=C2=A0 Could you craft a sample m=
essage, sample envelope, and sample DNS context that highlights the problem=
 you&#39;re talking about?=C2=A0 Maybe then it&#39;ll snap into focus.<br><=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Wed, Jun 16, 2021 at 2:43 PM Douglas Foster &lt;<a href=3D"mailto:dougfos=
ter.emailstandards@gmail.com" target=3D"_blank">dougfoster.emailstandards@g=
mail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div dir=3D"ltr">NXDomain on RFC5322.From is a completely different=
 issue.=C2=A0 =C2=A0 It means that the name is only used for service provid=
er messaging, and is therefore not linked to any IP address or other physic=
al infrastructure.=C2=A0 It affects the ability to define a meaningful NP t=
est.=C2=A0 =C2=A0The issue becomes irrelevant to DMARC if and only if we dr=
op the NP policy idea completely.<div><br></div><div>The proposed MX/A/AAAA=
/SPF test has two significant problems:</div><div>- It incorrectly classifi=
es some names as NP because they do not need MX/A/AAAA/SPF records because =
they are not tied to an IP address, and we have provided a very poor mechan=
ism for a domain owner to come into compliance.</div></div></blockquote><di=
v><br></div><div>There&#39;s a workaround here: If I want to use a name tha=
t is not represented in the DNS according to that test, all I need to do is=
 DKIM sign with my parent domain.=C2=A0 That makes &quot;p&quot; apply beca=
use now you have an aligned &quot;pass&quot;, which presumably trumps any &=
quot;np&quot; that&#39;s set.<br></div><div><br> </div><div>If you aren&#39=
;t signing with DKIM in that scenario, and you obviously can&#39;t pass SPF=
 either, then you can&#39;t possibly hope to pass DMARC irrespective of any=
 test being done on the name&#39;s validity.<br></div><div><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>- It inco=
rrectly classifies some names that are not used for email as not NP, simply=
 because they have an A/AAAA record.=C2=A0 =C2=A0It provides no method for =
the domain owner to signal that the name is not used for email and therefor=
e should be treated as NP.</div></div></blockquote><div><br></div><div>If t=
hey&#39;re not used for email, then they&#39;re not in DMARC&#39;s problem =
space.</div></div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_=
quote">At any rate, since PSD has been approved, I&#39;m hoping the experim=
ent is underway, or will be soon, and then we might have some actual data a=
bout the severity of this defect and thus also possibly some hints about wa=
ys it can be mitigated.</div><div class=3D"gmail_quote"><br></div><div clas=
s=3D"gmail_quote">-MSK<br></div></div>
</blockquote></div></div>

--00000000000047c20505c55312c4--


From nobody Sat Jun 26 09:35:54 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 6AFE93A1C04 for <dmarc@ietfa.amsl.com>; Sat, 26 Jun 2021 09:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.005
X-Spam-Level: 
X-Spam-Status: No, score=-2.005 tagged_above=-999 required=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, HTML_OBFUSCATE_10_20=0.093, SPF_HELO_NONE=0.001, SPF_PASS=-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 x92Gjdj61sC7 for <dmarc@ietfa.amsl.com>; Sat, 26 Jun 2021 09:35:50 -0700 (PDT)
Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9DC63A1C02 for <dmarc@ietf.org>; Sat, 26 Jun 2021 09:35:49 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id i12-20020a05683033ecb02903346fa0f74dso12943996otu.10 for <dmarc@ietf.org>; Sat, 26 Jun 2021 09:35:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=27oiyWle/so9VlXzPL8rwyKXFzQzCRhPL7Zb7bJpbVk=; b=XYPfm1SlZpfDXVXCMydiGa0zGfwtwRQMrgcFIKIMo3QvtKvIcuOPqicAudSTdI/J3N 1s1+8IITmWABBpovtiktyNqiWm40sCdDLnvJ8vE/BEWOEK6ME3Dai5B39YTHGK2Efm8n Arb8iMujo9FSSY2s+9x+lPgqlNI04vRXsgDK5szldKGpsniR94/WippuiM/Bd2dwyqF8 4mAKtc21EbRpy6SHIjwfB7WEsI/x1D1TuTCqTIfztzGVu2vwnBBVV4+XS6TPKVTEwpgn 33EahzabQ70dsr4nUG1pEO9GyapdyTIYYuW0hNZmr0DcONcPaNUFLKKMXFwOKOg84OrW 2d7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=27oiyWle/so9VlXzPL8rwyKXFzQzCRhPL7Zb7bJpbVk=; b=O1yyCrXEYxk2gWbRoJrtAGPuLjrYphFxyh61XPGn4LeBKuvdzzTY5c30B3pCx62ObE XsM2umgvxlYRP8fy8P+yXMxCTtYnfukYeTb0vf8GFzzBz87WImtLSr9Bhx4vMKmXHE5D lppaRLPRzRgwzcuo6vbv3wpKglYvvPkL9McTMI/2cTFQMKFWASzWGpY6Y52gSGYMVxQy JfFzhITvarNz2mGACbMWPtbkC3JKudSM/EgWiWRZx9D4cc8pqx54XwrAzsx62oynf//f h61bnhfwKjq3nc7/uz11nJynfQHixUsWHOthdkznvAtIrdBapqlEDommeaKWpuD6h49H qzig==
X-Gm-Message-State: AOAM5308kcJWoeHdt1dQqpoeexFJiDjgAMNqxMoSieLfu7c4CBlvpab4 MTr83NQHo3VDqwkgGIapEuWMi5CmxMLmWetli/M+5J2x1k4=
X-Google-Smtp-Source: ABdhPJxA+RBSK6//MROV6Hg/tRpCY/oosmcMcFYbHaWKjNT+GthhaKmq8WBoZOyJrUsi6utkQf0eExWomjQvNl2HKMk=
X-Received: by 2002:a9d:7d05:: with SMTP id v5mr15434491otn.240.1624725348199;  Sat, 26 Jun 2021 09:35:48 -0700 (PDT)
MIME-Version: 1.0
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 26 Jun 2021 12:35:38 -0400
Message-ID: <CAH48Zfyai_qZzMt5VDhpWj5wHrYAyLA5hEssvKXwXn9v006XDg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003cb1a705c5add974"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/TJ8shuX6x_na991rGjJS_h4LNlo>
Subject: [dmarc-ietf] Ticket #112 - Authentication vs. Repudiation.
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Jun 2021 16:35:53 -0000

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

DMARC is very effective for message authentication.  DMARC PASS allows
preferred handling to be applied without fear of spoofing.  For example:

If DMARC=3DPASS
and RFC5322.FROM ends with =E2=80=9CEXAMPLE.COM=E2=80=9D
they Bypass Tests ( =E2=80=9CSpam Scoring=E2=80=9D,  =E2=80=9CAttachment Re=
strictions=E2=80=9D )

(Curiously, I had trouble finding products which could implement this type
of rule, suggesting that we need more best practice documentation.)

However, DMARC has proven to be ineffective as a tool for message
repudiation.    DMARC FAIL does not necessarily mean spoofed content, it
can mean many things:

=C2=B7         If the message contains a DKIM signature that does not verif=
y:

o   the message was forwarded with modifications

o   the signature hash was computed incorrectly at creation

o   the signature hash was computed incorrectly at reception

o   the signature and the message are fraudulent

=C2=B7         If the message does not contain a DKIM signature at all:

o   the SPF policy has an omission

o   the SPF policy has a PERMERROR mistake

o   the message was forwarded

o   the message is from a tolerated and non-malicious impersonator

o   the message is fraudulent

Given these diverse possibilities, DMARC FAIL is not a reliable indication
that the message should be blocked, whatever the sender policy.
Quarantining might be the best response, if evaluators have the human
resources with sufficient skills to evaluate each such message, so that a
determinative policy can be created.

Overall, Sender Authentication meets the primary needs of message
senders:   their messages can be verified with SPF or DKIM in the hope that
their messages will be more likely to be given preferred handling.

Message receivers are very concerned about malicious messages being
accepted, so repudiation has a high interest level, and these interests are
not satisfied with an Authentication-Only result.   Some vendor products
and some system managers have responded to this need by treating an
authentication failure as if it provides confirmed repudiation.  Such
behavior is not justified and has created all of the problems documented by
RFC 7960.

The notion of an NP policy reverses this situation.  NP has no ability to
provide authentication, and is only evaluated when authentication fails.
But it can provide confirmed repudiation for a subset of the organization
or PSD name space, specifically the names which are never used for a
particular purpose.

The PSD proposal defined a two-way split:   names which are plausibly used
for SMTP are considered valid, and names which are not plausibly used for
SMTP are considered invalid.   As I have discussed elsewhere, this creates
errors because it involves guessing the sender=E2=80=99s intention and it e=
xcludes
certain name usage scenarios.

Given that we have two usage states (valid or invalid) and two usage
locations (RFC5321.MailFrom and RFC5322.From), we have four possibilities
for any specific name:

1.       Name used by domain owner for both MailFrom and From.   A message
which uses this name is not repudiated.

2.       Name used by domain owner for MailFrom only.   A message which
uses this name in the From header is repudiated.

3.       Name used by domain owner for From only.  A message which uses
this name in the MailFrom address is repudiated.

4.       Name used by domain owner for neither MailFrom nor From.  A
message which uses this name is repudiated.

How to document and evaluate these categories:

We have the available tools to distinguish the SMTP portion of this problem=
:

=C2=B7         An SPF policy which evaluates to at least one IP address
indicates that the message is used for SMTP, and the message must be in
categories 1 or 2.

=C2=B7         An SPF policy of "-ALL" indicates that the name is never use=
d for
SMTP.   The message must be in category 3 or 4.

=C2=B7         An SPF policy lookup which returns NXDOMAIN indicates that t=
he
name is not defined in DNS, and therefore has no return path.   For
purposes of NP processing, it is appropriate to treat this result as
equivalent to a policy of =E2=80=9C-ALL=E2=80=9D.   The message must be in =
category 3 or 4.

=C2=B7         A message which does not have an SPF policy is ambiguous, bu=
t if
the domain owner has published an NP policy of reject or quarantine, the
absence of an SPF policy should be treated as equivalent to rejection
(=E2=80=9C-All=E2=80=9D).

What we lack is an equivalent mechanism for indicating whether a name is
used in an RFC5322.From header.   I have proposed that this be implemented
as a TXT record, because it must be possible to assign the signal to any
possible DNS name.  To handle all four categories, we need both a positive
signal (name is used for From) and a negative signal (name is never used
for From).

We can assume that in the absence of a signal, the From signal matches the
MailFrom signal.  This minimizes the number of DNS entries required, and
simplifies the conformance effort for domain owners who wish to utilize the
NP policy.

=C2=B7         When SPF evaluation indicates that the name is valid for SMT=
P,
then

o   If the DMARC signal is present and positive, the signal is redundant
and category 1 applies.

o   If the DMARC signal is absent, positive is assumed and category 1
applies.

o   If the DMARC signal is negative, category 2 applies.

=C2=B7         When SPF evaluation indicates that the name is not valid for
SMTP, then

o   If the DMARC signal is present and positive, category 3 applies

o   If the DMARC signal is absent, negative is assumed and category 4
applies.

o   If the DMARC signal is negative, category 4 applies.

Application of the NP policy

If the NP policy is NONE or not published, the domain owner has not
indicated compliance with this mechanism, and the SP policy is applied.

If the NP policy evaluates to =E2=80=9Cnot repudiated=E2=80=9D, then the SP=
 policy applies.

If both NP and SP are set to reject or quarantine, then all unauthenticated
messages will be rejected by one or the other of the policies.   Messages
rejected because of NP have a higher level of certainty because they are
verifiably repudiated.

Notes about the NP approach:

=C2=B7         NP does not protect all names; it only protects unused names=
.
For example, it does not solve the problem of messages that are processed
through a content-altering mailing list.   However, the mailing list
problem only applies to names that are valid, so a message with a
repudiated name is reliably not affected by the mailing list problem.  The
universe of unused names is very large, so blocking such usage is a
significant benefit to mail evaluators.

=C2=B7         Some DMARC failures are caused by non-malicious impersonatio=
n by
trusted senders, and these can be wanted messages which will be given a
DMARC exception.   Operational experience indicates that these senders only
impersonate existing names that they have obtained through legitimate
interactions, so they will not be using invalid names and will be
unaffected by the NP policy.

Conformance effort for domain owners:

=C2=B7         Determine all used names and how they are used.

=C2=B7         Add DMARC positive DNS entries as needed to indicate names i=
n 3.

=C2=B7         If desired, add DMARC negative DNS entries to distinguish
category 2 from category 1 for improved enforcement.  In the absence of a
negative signal, category 2 messages will be handled as category 1 and
never repudiated.

=C2=B7         When ready, publish a NP policy of quarantine or reject.


Doug Foster

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

<div dir=3D"ltr"><p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-he=
ight:107%;font-size:11pt;font-family:Calibri,sans-serif"><span style=3D"fon=
t-size:11pt">DMARC is very effective for message authentication.=C2=A0 DMAR=
C PASS allows preferred handling to be
applied without fear of spoofing.=C2=A0 For
example:</span><br></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt 0.5in;line-height:107%;f=
ont-size:11pt;font-family:Calibri,sans-serif">If DMARC=3DPASS <br>
and RFC5322.FROM ends with =E2=80=9C<a href=3D"http://EXAMPLE.COM">EXAMPLE.=
COM</a>=E2=80=9D <br>
they Bypass Tests ( =E2=80=9CSpam Scoring=E2=80=9D, =C2=A0=E2=80=9CAttachme=
nt
Restrictions=E2=80=9D )</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">(Curiously, I had trouble finding p=
roducts which could implement
this type of rule, suggesting that we need more best practice documentation=
.)</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">However, DMARC has proven to be ine=
ffective as a tool for
message repudiation.=C2=A0=C2=A0=C2=A0 DMARC FAIL does
not necessarily mean spoofed content, it can mean many things:</p>

<p class=3D"gmail-MsoListParagraphCxSpFirst" style=3D"margin:0in 0in 0in 0.=
5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span s=
tyle=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norma=
l;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-hei=
ght:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>If the message contains a DKIM signature that
does not verify:</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>the message was forwarded with modifications</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>the signature hash was computed incorrectly at
creation</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>the signature hash was computed incorrectly at
reception</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>the signature and the message are fraudulent</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 0=
.5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span =
style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norm=
al;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-he=
ight:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>If the message does not contain a DKIM signature
at all:</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>the SPF policy has an omission</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>the SPF policy has a PERMERROR mistake</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>the message was forwarded</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>the message is from a tolerated and non-malicious
impersonator</p>

<p class=3D"gmail-MsoListParagraphCxSpLast" style=3D"margin:0in 0in 8pt 1in=
;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span styl=
e=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nume=
ric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt=
;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>the message is fraudulent</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Given these diverse possibilities, =
DMARC FAIL is not a
reliable indication that the message should be blocked, whatever the sender
policy.=C2=A0 Quarantining might be the best
response, if evaluators have the human resources with sufficient skills to
evaluate each such message, so that a determinative policy can be created.<=
/p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Overall, Sender Authentication meet=
s the primary needs of message
senders:=C2=A0=C2=A0 their messages can be verified
with SPF or DKIM in the hope that their messages will be more likely to be
given preferred handling.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Message receivers are very concerne=
d about malicious
messages being accepted, so repudiation has a high interest level, and thes=
e
interests are not satisfied with an Authentication-Only result.=C2=A0=C2=A0=
 Some vendor products and some system managers
have responded to this need by treating an authentication failure as if it =
provides
confirmed repudiation.=C2=A0 Such behavior is
not justified and has created all of the problems documented by RFC 7960.</=
p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">The notion of an NP policy reverses=
 this situation.=C2=A0 NP has no ability to provide authentication, and
is only evaluated when authentication fails.=C2=A0=C2=A0=C2=A0
But it can provide confirmed repudiation for a subset of the organization
or PSD name space, specifically the names which are never used for a partic=
ular
purpose.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">The PSD proposal defined a two-way =
split:=C2=A0=C2=A0 names which are plausibly used for SMTP are
considered valid, and names which are not plausibly used for SMTP are
considered invalid.=C2=A0=C2=A0 As I have discussed
elsewhere, this creates errors because it involves guessing the sender=E2=
=80=99s intention
and it excludes certain name usage scenarios. </p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Given that we have two usage states=
 (valid or invalid) and two
usage locations (RFC5321.MailFrom and RFC5322.From), we have four possibili=
ties
for any specific name:</p>

<p class=3D"gmail-MsoListParagraphCxSpFirst" style=3D"margin:0in 0in 0in 41=
.25pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">1.<sp=
an style=3D"font-variant-numeric:normal;font-variant-east-asian:normal;font=
-stretch:normal;font-size:7pt;line-height:normal;font-family:&quot;Times Ne=
w Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span>Name used by domain owner for both MailFrom and
From.=C2=A0=C2=A0 A message which uses this name is
not repudiated.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 4=
1.25pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">2.<s=
pan style=3D"font-variant-numeric:normal;font-variant-east-asian:normal;fon=
t-stretch:normal;font-size:7pt;line-height:normal;font-family:&quot;Times N=
ew Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span>Name used by domain owner for MailFrom only.=C2=A0=C2=A0 A message w=
hich uses this name in the From header
is repudiated.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 4=
1.25pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">3.<s=
pan style=3D"font-variant-numeric:normal;font-variant-east-asian:normal;fon=
t-stretch:normal;font-size:7pt;line-height:normal;font-family:&quot;Times N=
ew Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span>Name used by domain owner for From only.=C2=A0 A message which uses =
this name in the MailFrom
address is repudiated.</p>

<p class=3D"gmail-MsoListParagraphCxSpLast" style=3D"margin:0in 0in 8pt 41.=
25pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">4.<spa=
n style=3D"font-variant-numeric:normal;font-variant-east-asian:normal;font-=
stretch:normal;font-size:7pt;line-height:normal;font-family:&quot;Times New=
 Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span>Name used by domain owner for neither MailFrom
nor From.=C2=A0 A message which uses this name
is repudiated.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">How to document and evaluate these =
categories:</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">We have the available tools to dist=
inguish the SMTP portion
of this problem:</p>

<p class=3D"gmail-MsoListParagraphCxSpFirst" style=3D"margin:0in 0in 0in 0.=
5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span s=
tyle=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norma=
l;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-hei=
ght:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>An SPF policy which evaluates to at least one IP
address indicates that the message is used for SMTP, and the message must b=
e in
categories 1 or 2.<br>
<br>
</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 0=
.5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span =
style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norm=
al;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-he=
ight:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>An SPF policy of &quot;-ALL&quot; indicates that the name is
never used for SMTP.=C2=A0=C2=A0 The message must
be in category 3 or 4.<br>
<br>
</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 0=
.5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span =
style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norm=
al;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-he=
ight:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>An SPF policy lookup which returns NXDOMAIN
indicates that the name is not defined in DNS, and therefore has no return =
path.=C2=A0=C2=A0 For purposes of NP processing, it is appropriate
to treat this result as equivalent to a policy of =E2=80=9C-ALL=E2=80=9D.=
=C2=A0=C2=A0 The message must be in category 3 or 4.<br>
<br>
</p>

<p class=3D"gmail-MsoListParagraphCxSpLast" style=3D"margin:0in 0in 8pt 0.5=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:normal=
;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-heig=
ht:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>A message which does not have an SPF policy is
ambiguous, but if the domain owner has published an NP policy of reject or
quarantine, the absence of an SPF policy should be treated as equivalent to=
 rejection
(=E2=80=9C-All=E2=80=9D).</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">What we lack is an equivalent mecha=
nism for indicating whether
a name is used in an RFC5322.From header.=C2=A0=C2=A0
I have proposed that this be implemented as a TXT record, because it must
be possible to assign the signal to any possible DNS name.=C2=A0 To handle =
all four categories, we need both a
positive signal (name is used for From) and a negative signal (name is neve=
r
used for From).</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">We can assume that in the absence o=
f a signal, the From
signal matches the MailFrom signal.=C2=A0 This
minimizes the number of DNS entries required, and simplifies the conformanc=
e
effort for domain owners who wish to utilize the NP policy. </p>

<p class=3D"gmail-MsoListParagraphCxSpFirst" style=3D"margin:0in 0in 0in 0.=
5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span s=
tyle=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norma=
l;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-hei=
ght:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>When SPF evaluation indicates that the name is
valid for SMTP, then</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>If the DMARC signal is present and positive, the
signal is redundant and category 1 applies.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>If the DMARC signal is absent, positive is
assumed and category 1 applies.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>If the DMARC signal is negative, category 2
applies.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 0=
.5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span =
style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norm=
al;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-he=
ight:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>When SPF evaluation indicates that the name is
not valid for SMTP, then</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>If the DMARC signal is present and positive, category
3 applies</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 1=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nu=
meric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7=
pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>If the DMARC signal is absent, negative is
assumed and category 4 applies.</p>

<p class=3D"gmail-MsoListParagraphCxSpLast" style=3D"margin:0in 0in 8pt 1in=
;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span styl=
e=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant-nume=
ric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt=
;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0
</span></span>If the DMARC signal is negative, category 4
applies.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Application of the NP policy</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">If the NP policy is NONE or not pub=
lished, the domain owner
has not indicated compliance with this mechanism, and the SP policy is appl=
ied.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">If the NP policy evaluates to =E2=
=80=9Cnot repudiated=E2=80=9D, then the SP policy
applies.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">If both NP and SP are set to reject=
 or quarantine, then all
unauthenticated messages will be rejected by one or the other of the polici=
es.=C2=A0=C2=A0 Messages rejected because of NP have a higher
level of certainty because they are verifiably repudiated.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Notes about the NP approach:</p>

<p class=3D"gmail-MsoListParagraphCxSpFirst" style=3D"margin:0in 0in 0in 0.=
5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span s=
tyle=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norma=
l;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-hei=
ght:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>NP does not protect all names; it only protects
unused names.=C2=A0=C2=A0 For example, it does not
solve the problem of messages that are processed through a content-altering
mailing list.=C2=A0=C2=A0 However, the mailing list
problem only applies to names that are valid, so a message with a repudiate=
d
name is reliably not affected by the mailing list problem.=C2=A0 The univer=
se of unused names is very large,
so blocking such usage is a significant benefit to mail evaluators.<br>
<br>
</p>

<p class=3D"gmail-MsoListParagraphCxSpLast" style=3D"margin:0in 0in 8pt 0.5=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:normal=
;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-heig=
ht:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>Some DMARC failures are caused by non-malicious
impersonation by trusted senders, and these can be wanted messages which wi=
ll
be given a DMARC exception.=C2=A0=C2=A0 Operational
experience indicates that these senders only impersonate existing names tha=
t they
have obtained through legitimate interactions, so they will not be using
invalid names and will be unaffected by the NP policy.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Conformance effort for domain owner=
s:</p>

<p class=3D"gmail-MsoListParagraphCxSpFirst" style=3D"margin:0in 0in 0in 0.=
5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span s=
tyle=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norma=
l;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-hei=
ght:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>Determine all used names and how they are used.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 0=
.5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span =
style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norm=
al;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-he=
ight:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>Add DMARC positive DNS entries as needed to
indicate names in 3.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0in 0=
.5in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span =
style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:norm=
al;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-he=
ight:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>If desired, add DMARC negative DNS entries to distinguish
category 2 from category 1 for improved enforcement.=C2=A0 In the absence o=
f a negative signal, category
2 messages will be handled as category 1 and never repudiated.</p>

<p class=3D"gmail-MsoListParagraphCxSpLast" style=3D"margin:0in 0in 8pt 0.5=
in;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span st=
yle=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:normal=
;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;line-heig=
ht:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>When ready, publish a NP policy of quarantine or
reject.</p><p class=3D"gmail-MsoListParagraphCxSpLast" style=3D"margin:0in =
0in 8pt 0.5in;line-height:107%"><font face=3D"Calibri, sans-serif"><span st=
yle=3D"font-size:14.6667px"><br></span></font><span style=3D"font-family:Ca=
libri,sans-serif;font-size:11pt">Doug Foster</span><br></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">=C2=A0</p></div>

--0000000000003cb1a705c5add974--


From nobody Mon Jun 28 05:57:44 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 14B9E3A3857 for <dmarc@ietfa.amsl.com>; Mon, 28 Jun 2021 05:57:43 -0700 (PDT)
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 (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 y5bRNhQgX_vr for <dmarc@ietfa.amsl.com>; Mon, 28 Jun 2021 05:57:38 -0700 (PDT)
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 4D3A23A3856 for <dmarc@ietf.org>; Mon, 28 Jun 2021 05:57:38 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id w26so13420224qto.13 for <dmarc@ietf.org>; Mon, 28 Jun 2021 05:57:38 -0700 (PDT)
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=hCDxyt0BodFOVIVMkTKPd0lR1S7TEsYxZvUiYy0rlgg=; b=eq8nCF+Qi1Hplil2u1pqiQpwSQmR3eY0NtOoaZXrdoDud3l6PEhh5PLE+P36k6d2fd ZSK7qHm2ioYtmBUCm474VcJV/d+D6pLthM3cv8KtRoxiZ/iml7SIgnMPaAyYX8p5S0Q0 1bs/bn/ebvqDJYLwL8gwPZNpnzMeOteXJ0N53bV65fwJl27VWYZSn+vnvevDjSbcShH5 Iq7GibirBrTUy/gctqnL6e8jGo++67u1vaJNV/jK10I5zWEYy/s+9PYxt73VcxsabT03 riM0jvzePlFS0vxwa9sCOWNwn95D2xY+Ne4soKvRYmI0GyjWxVUZzUtjqRlBesL2Mq8z ZgtA==
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=hCDxyt0BodFOVIVMkTKPd0lR1S7TEsYxZvUiYy0rlgg=; b=RVD2I/FlnRmLV+gbR99uvfnPs9Eo2tYoYN0TbC5awLz7D6sBOP2lY2eO0+wDdKJWRG 5wgwPQyIWrD4+om5vxvOW3uPfmPe9x7LD6GXqh+3FQaEy2Fu2MhbHV1qM5KnMRON3EXg 9IBIcWF+0PMxU0Y+gGkji9lsI6qtizSo20cvrHT6nXObsWxm6LmObG5t8MB8I8+iKpEK mgGbURYoEok4tpL7TLjFdrn1GsW8XrwjOSWDK+qKiS3N73RBX4/jM4n8vE+zGBmWh3mp CLj0qOf2nhu216fdooy3Q8DOIu5KxWJidV9yvLNgYXFrVmKL+nv5lBJR0KWUyXt+dEk0 Ln2g==
X-Gm-Message-State: AOAM532PYXziZqXabnF/K8/FEI/D3hB73a8fhXwDRFFCQQ4bZxFswv2c Zfs6fOgmKnUlEvE2YKm0jMnfY1YXW5at8fzuV8XMeg==
X-Google-Smtp-Source: ABdhPJz9/QXRoS3I/VXAhsydq8xbFke25Cn9ZoTW/BLAgA0K9m6m3I+0eRTBU51PCvqniePs90N8jeF/sPLcE8r8l3E=
X-Received: by 2002:a05:622a:199e:: with SMTP id u30mr17292802qtc.208.1624885056406;  Mon, 28 Jun 2021 05:57:36 -0700 (PDT)
MIME-Version: 1.0
References: <CAH48Zfyai_qZzMt5VDhpWj5wHrYAyLA5hEssvKXwXn9v006XDg@mail.gmail.com>
In-Reply-To: <CAH48Zfyai_qZzMt5VDhpWj5wHrYAyLA5hEssvKXwXn9v006XDg@mail.gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Mon, 28 Jun 2021 08:57:20 -0400
Message-ID: <CAHej_8=S94d=HU578WekbR8Q-GOKJnfqjED_H4s-P_7hyo-hxw@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000969f0b05c5d308e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/IkXDS629iYTYjcr8loOY44PsiIo>
Subject: Re: [dmarc-ietf] Ticket #112 - Authentication vs. Repudiation.
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 28 Jun 2021 12:57:43 -0000

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

On Sat, Jun 26, 2021 at 12:36 PM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> DMARC is very effective for message authentication.  DMARC PASS allows
> preferred handling to be applied without fear of spoofing.  For example:
>
> If DMARC=3DPASS
> and RFC5322.FROM ends with =E2=80=9CEXAMPLE.COM=E2=80=9D
> they Bypass Tests ( =E2=80=9CSpam Scoring=E2=80=9D,  =E2=80=9CAttachment =
Restrictions=E2=80=9D )
>
> (Curiously, I had trouble finding products which could implement this typ=
e
> of rule, suggesting that we need more best practice documentation.)
>
>
> The reason you can't find products implementing that type of rule is
because there is no need for such a rule.

DMARC establishes the authenticity of the identity of the party responsible
for the message; DMARC makes no claim as to the quality, worthiness, or
desirability of the message.

DMARC ensures that your mail gets treated in a manner that is consistent
with the reputation earned by the responsible identity. Spam messages can
and do pass DMARC authentication checks every single day, and in large
numbers.

Passing DMARC should not lead to bypassing tests such as Spam Scoring or
Attachment Restrictions. All spoofs are spam, but not all spam is spoofed.

--=20

*Todd Herr* | Technical Director, Standards and Ecosystem
*e:* todd.herr@valimail.com
*m:* 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.

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

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:tahoma,sans-serif"><span style=3D"font-family:Arial,Helvetica,sans=
-serif">On Sat, Jun 26, 2021 at 12:36 PM Douglas Foster &lt;<a href=3D"mail=
to:dougfoster.emailstandards@gmail.com">dougfoster.emailstandards@gmail.com=
</a>&gt; wrote:</span><br></div></div><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><p class=3D"MsoNor=
mal" style=3D"margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-famil=
y:Calibri,sans-serif"><span style=3D"font-size:11pt">DMARC is very effectiv=
e for message authentication.=C2=A0 DMARC PASS allows preferred handling to=
 be
applied without fear of spoofing.=C2=A0 For
example:</span><br></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt 0.5in;line-height:107%;f=
ont-size:11pt;font-family:Calibri,sans-serif">If DMARC=3DPASS <br>
and RFC5322.FROM ends with =E2=80=9C<a href=3D"http://EXAMPLE.COM" target=
=3D"_blank">EXAMPLE.COM</a>=E2=80=9D <br>
they Bypass Tests ( =E2=80=9CSpam Scoring=E2=80=9D, =C2=A0=E2=80=9CAttachme=
nt
Restrictions=E2=80=9D )</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">(Curiously, I had trouble finding p=
roducts which could implement
this type of rule, suggesting that we need more best practice documentation=
.)</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif"><br></p></div></blockquote><div><sp=
an class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">The reas=
on you can&#39;t find products implementing that type of rule is because th=
ere is no need for such a rule.</span></div><div><span class=3D"gmail_defau=
lt" style=3D"font-family:tahoma,sans-serif"><br></span></div><div><span cla=
ss=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">DMARC establis=
hes the authenticity of the identity of the party responsible for the messa=
ge; DMARC makes no claim as to the quality, worthiness, or desirability of =
the message.=C2=A0</span></div><div><span class=3D"gmail_default" style=3D"=
font-family:tahoma,sans-serif"><br></span></div><div><span class=3D"gmail_d=
efault" style=3D"font-family:tahoma,sans-serif">DMARC ensures that your mai=
l gets treated in a manner that is consistent with the reputation earned by=
 the responsible identity. Spam messages can and do pass DMARC authenticati=
on checks every single day, and in large numbers.</span></div><div><span cl=
ass=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><br></span></=
div><div><span class=3D"gmail_default" style=3D"font-family:tahoma,sans-ser=
if">Passing DMARC should not lead to bypassing tests such as Spam Scoring o=
r Attachment Restrictions. All spoofs are spam, but not all spam is spoofed=
.</span></div><div><span class=3D"gmail_default" style=3D"font-family:tahom=
a,sans-serif"></span>=C2=A0</div></div>-- <br><div dir=3D"ltr" class=3D"gma=
il_signature"><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0p=
t;margin-bottom:0pt"></p><div style=3D"text-align:left"><span style=3D"vert=
ical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Arial"=
><b>Todd Herr</b></span><span style=3D"vertical-align:baseline;white-space:=
pre-wrap;font-size:small;font-family:Arial"> | Technical Director, Standard=
s and Ecosystem</span></div><span style=3D"vertical-align:baseline;white-sp=
ace:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-align:le=
ft"><span style=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"=
vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail.com" target=
=3D"_blank">todd.herr@valimail.com</a> </span></div></span><span><div><span=
><b>m:</b></span><span> 703.220.4153</span><span></span></div><div style=3D=
"text-align:left"><img style=3D"width: 175px; height: 43px;" src=3D"https:/=
/hosted-packages.s3-us-west-1.amazonaws.com/Valimail+Logo.png"></div></span=
><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 all =
data transmitted with it contains confidential and/or proprietary informati=
on intended solely for the use of individual(s) authorized to receive it. I=
f 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 s=
ystem.</span></font></p></span></div></div>

--000000000000969f0b05c5d308e1--


From nobody Tue Jun 29 07:54:37 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 DC4E63A36AF for <dmarc@ietfa.amsl.com>; Tue, 29 Jun 2021 07:54:36 -0700 (PDT)
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 StgM1INxl1aK for <dmarc@ietfa.amsl.com>; Tue, 29 Jun 2021 07:54:34 -0700 (PDT)
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 1E84A3A36AE for <dmarc@ietf.org>; Tue, 29 Jun 2021 07:54:33 -0700 (PDT)
Received: by mail-oi1-x231.google.com with SMTP id k206so7679800oif.2 for <dmarc@ietf.org>; Tue, 29 Jun 2021 07:54:33 -0700 (PDT)
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=FSOq8w2Edhpa6tMyqhSWLx7DZcX5nKK1mu+RUvfmVSA=; b=d8fPOhQXSLUvjJ+vhvf43VUd8UU9mdhb4oQBBc1yahelH/bsYFdc1vBAQ9Sy5rgPGC GoTZeQ5vgTb4uluZTCQb8+caSO9jWZtOOMWtt8mqSX0lX0SGoW2gYgWzRB8HKlO9EQaA tX7lti28+eInNuiXl8wLqItrlXyzVUepPD5MP8dcaF/V3Q4vdtWQPEz+8hYVNg6+odca rHF0wQQVrKS62tKA1i0+w/gu/tScWDpLOl2ntFv6Gu5JV3PrPvA/lsVBpd1pQEGlBAcH V3TisHQPxh8n4luDVwnNUTV6OziLaR/uFRA5uGSCSD4D9dC1ccTuYVS9mmrPijt4ZYLX mFgg==
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=FSOq8w2Edhpa6tMyqhSWLx7DZcX5nKK1mu+RUvfmVSA=; b=AFsv5DcY3Rx/R8my2jTgayCDfYd5ZibUT8t8mnXg724/zQo/yzPMd4J3nvy88OmK31 NGmGqKLJpv0JrFQedJf4SXfoKxuOmxczy7GFPMt4FCKBAzWRwkSG/xO28EvBYHEuwdJ7 0Vefe12QlcM/3yczRb7YZAfWZvhNO4BxP1xsej0U8D9ULh2VVRHuih2pgSgjW6tify88 NmU8/mRg13FGEFWf8dWDEFH1qNqFTM4oSm7wj8HKx3ZTxZlADrvfC5OlS3al+d2BX8it ci2L/ODaIXR/aHAF4MgugWPRzaicKbdJlUFjLs45Qr2E10HawQ892FFPirZJQqNbdgeZ TRVA==
X-Gm-Message-State: AOAM532kxphd37o/Eo6gFe70vc2AqI78tIs3Uv70+pIosm5StOgpIei5 b+B7mFD+f0p1CZvX7I7IwdtI4yAsNr4b4ZjDwba5R3LQEyke2A==
X-Google-Smtp-Source: ABdhPJyiLn8h3g0vHR+ewGkKj6L1wkS1DdKzB8I3cw4dm/fvO5m9o7IYpd0YW+AVzPZFGMHaFBbQfsBprs995znH6Xc=
X-Received: by 2002:a05:6808:cb:: with SMTP id t11mr8517129oic.73.1624978472720;  Tue, 29 Jun 2021 07:54:32 -0700 (PDT)
MIME-Version: 1.0
References: <CAH48Zfyai_qZzMt5VDhpWj5wHrYAyLA5hEssvKXwXn9v006XDg@mail.gmail.com> <CAHej_8=S94d=HU578WekbR8Q-GOKJnfqjED_H4s-P_7hyo-hxw@mail.gmail.com>
In-Reply-To: <CAHej_8=S94d=HU578WekbR8Q-GOKJnfqjED_H4s-P_7hyo-hxw@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 29 Jun 2021 10:54:25 -0400
Message-ID: <CAH48Zfwu-Fdv-=tf_QE-hCKMuNafkfYdLL3jYwqVqFQ_-3d7fA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a25cc405c5e8c8ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/gXwmWAoUJgrR8QaBHAs94NdYowY>
Subject: Re: [dmarc-ietf] Ticket #112 - Authentication vs. Repudiation.
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 29 Jun 2021 14:54:37 -0000

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

What is so hard to grasp'?

"Treated in a manner that is consistent with the reputation of the
responsible party"
means that
"the message is safe to whitelist if whitelisting is desired."

I was not saying that DMARC=PASS was a basis for whitelisting.   I said
that DMARC=PASS and a trusted identifier is a basis for whitelisting (when
necessary to avoid false positives.)

Any product can do whitelisting based on a single attribute, but
whitelisting requires at least two attributes:  a trusted identifier or set
of identifiers, and a verification status which indicates that the
identifiers are not spoofed.   Therefore the primary value-add from sender
authentication is that it allows me to whitelist messages from trusted
senders to avoid false positives.   As we have both said, sender
authentication=FAIL is a can of worms, but it is not identical with
Repudiate.

BUT MORE TO THE POINT

If you believe that the ex'sting NP language is sufficient and effective,
just explain why you believe this is so.   A justification is all that my
original topics requested, and this has not been done.  For my part, I
don't see a test definition that can be implemented reliably, all I see is
a test name.  Any attempt to code the test introduces questions that have
not been addressed, such as SP="-ALL" and MX= ".".  Similarly, I see a
concept name, "non-existent", which is also undefined.  Any attempt to
interpret "non-existent" will expose ambiguities.   This language is simply
not up to IETF standards.  When I try to fix the language, I find that the
design is not merely vague, it is wrong.

So please answer these questions:

   - Do you believe the problem and the solution are well defined in the
   current specification?
   - Can you explain why the solution is the best possible fit for the
   problem?
   - Have you evaluated the problem and solution against an actual mail
   stream to see if it works?
   - Have you asked someone to attempt an implementation of this part of
   the specification?

In short, the group needs to stop telling me why I don't think straight, or
why I am incomprehensible, why I should shut up, and instead start telling
me what they believe and why.

Those who cannot or will not do these things, should let someone who has
evaluated this idea against a real mail stream take the lead.

Doug Foster

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

<div dir=3D"ltr"><div>What=C2=A0is so hard to grasp&#39;?</div><div><br></d=
iv>&quot;Treated in a manner that is consistent with the reputation of the =
responsible party&quot;=C2=A0<div>means=C2=A0that=C2=A0</div><div>&quot;the=
 message is safe to whitelist if whitelisting is desired.&quot;=C2=A0=C2=A0=
</div><div><br></div><div>I was not saying that DMARC=3DPASS was a basis fo=
r whitelisting.=C2=A0 =C2=A0I said that DMARC=3DPASS and a trusted identifi=
er is a basis for whitelisting (when necessary to avoid false positives.)<d=
iv><br></div><div>Any product can do whitelisting based on a single attribu=
te, but whitelisting requires at least two attributes:=C2=A0 a trusted iden=
tifier or set of identifiers, and a verification status which indicates tha=
t the identifiers are not spoofed.=C2=A0 =C2=A0Therefore the primary value-=
add from sender authentication is that it allows me to whitelist messages f=
rom trusted senders to avoid false positives.=C2=A0 =C2=A0As we have both s=
aid, sender authentication=3DFAIL is a can of worms, but it is not identica=
l with Repudiate.</div><div><div><br></div><div>BUT MORE TO THE POINT</div>=
<br class=3D"gmail-Apple-interchange-newline"></div><div>If you believe tha=
t the ex&#39;sting NP language is sufficient and effective, just explain wh=
y you believe this is so.=C2=A0 =C2=A0A justification is all that my origin=
al topics requested, and this has not been done.=C2=A0 For my part, I don&#=
39;t see a test definition that can be implemented reliably, all I see is a=
 test name.=C2=A0 Any attempt to code the test introduces questions that ha=
ve not been addressed, such as SP=3D&quot;-ALL&quot; and MX=3D &quot;.&quot=
;.=C2=A0 Similarly, I see a concept name, &quot;non-existent&quot;, which i=
s also undefined.=C2=A0 Any attempt to interpret &quot;non-existent&quot; w=
ill expose ambiguities.=C2=A0 =C2=A0This language is simply not up to IETF =
standards.=C2=A0 When I try to fix the language, I find that the design is =
not merely vague, it is wrong.</div><div><br></div><div>So please answer th=
ese questions:</div><div><ul><li>Do you believe the problem and the solutio=
n are well defined in the current specification?</li><li>Can you explain wh=
y the solution is the best possible fit for the problem?</li><li>Have you e=
valuated the problem and solution against an actual mail stream to see if i=
t works?</li><li>Have you asked someone to attempt an implementation of thi=
s part of the specification?</li></ul></div><div>In short, the group needs =
to stop telling me why I don&#39;t think straight, or why I am incomprehens=
ible, why I should shut up, and instead start telling me what they believe =
and why.<br></div><div><br></div><div>Those who cannot or will not do these=
 things, should let someone who has evaluated this idea against a real mail=
 stream take the lead.</div><div><br></div><div>Doug Foster<br></div><div><=
br></div></div></div>

--000000000000a25cc405c5e8c8ef--

