
From nobody Tue Jul  6 05:45:59 2021
Return-Path: <todd.herr@valimail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A3873A2689 for <dmarc@ietfa.amsl.com>; Tue,  6 Jul 2021 05:45: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 YYQ5d6kzU06i for <dmarc@ietfa.amsl.com>; Tue,  6 Jul 2021 05:45:53 -0700 (PDT)
Received: from mail-qv1-xf2c.google.com (mail-qv1-xf2c.google.com [IPv6:2607:f8b0:4864:20::f2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52C493A2683 for <dmarc@ietf.org>; Tue,  6 Jul 2021 05:45:53 -0700 (PDT)
Received: by mail-qv1-xf2c.google.com with SMTP id f5so9637563qvu.8 for <dmarc@ietf.org>; Tue, 06 Jul 2021 05:45:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:from:date:message-id:subject:to; bh=aU/BjlatMAU3/ziYVvy34Rot4WB919eNLR56permkDA=; b=OjuSxrcKhvLOjjRw+oa0ujYzdFW65V0QWKVn/c9OQ6jQBtfhRhS/SbXA7OQBldXaFw G847gCuF7iA6UK0N5BNIzmzSnbno/jz+p+AzOgtIUpLzNaJQFDs9sF2+55EnnR4ylR91 257uN7RYHt0jI0cJeIG8ZOeTlS+6865VvTCLE0bFlBX5SPrN/4QaDwXsNO0P73Z2/w1M YXjjMmys/uBxI4n3CHfL2DNRLXQDYfroMnnpYfDlxDjhF6NkHmk2kQ8f+j5EYfG7HA5q ub45ufT347Ak/pbw6QAJF5rpB20o55vA31tJv8KOtxUcuFL+86WB0JSALxFSCzPIh+Nb E09g==
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=aU/BjlatMAU3/ziYVvy34Rot4WB919eNLR56permkDA=; b=j9a+zT1Q3HRp3Pu0uFj91kgncE2pZQAYcjGG9rCqdY67EWDdMED4u38ILJZVHOUfJQ Mbck6TSsPKbCgMuuO1vcAMCKGzQh8w8lL8YoPHZ4fW3/9DU8ka8CQMetiz8SNmiVn3mQ U7N32+Cr1AYBTk0Mph9CNTT1neq4sG8CmRzGgF1m5UPyi8NUYdBgF6l2bmQXiLmWqer9 jI7pYYdYh+o4gcsZ4Gx3DLL32nitqR061b+DKk1lmPnfCxM3fMq5PcfiKSm7OIUMcOkG 6af/NCtwnw5ZdHpHfnGYqwoysOdiFeD4AaqmL+gxmhIGg9D43BfHFhs4QOHmZa1LP8kK s9XA==
X-Gm-Message-State: AOAM5318tIOF4lgMwp3woR+7QpNRuV8u3UG2KzlZo5sDWTJIxxF1l6yE /ZHZKYIn+T8bZXfDMtRQUfC6Mm/poygVTFVpUjT6D/8O+JajzA==
X-Google-Smtp-Source: ABdhPJyBy4gWpGr5Wz3YhWHhz4ECUShhVR7FtGT0LtXhT4x6okxKtfg0IlIPcb/xOtwdknJX9T9fnff3aVIKXCi0iXQ=
X-Received: by 2002:a05:6214:364:: with SMTP id t4mr17861161qvu.54.1625575550921;  Tue, 06 Jul 2021 05:45:50 -0700 (PDT)
MIME-Version: 1.0
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 6 Jul 2021 08:45:35 -0400
Message-ID: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000044bef005c673cd97"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/j1NKQzhPWhgn77saJydZ7QESxbI>
Subject: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 06 Jul 2021 12:45:58 -0000

--00000000000044bef005c673cd97
Content-Type: text/plain; charset="UTF-8"

Greetings.

The theoretical goal of any domain owner that publishes a DMARC record is
to transition from an initial policy of p=none to a final one of p=reject,
because it is only at p=reject that DMARC's intended purpose of preventing
same-domain spoofing can be fully realized.

Many domain owners see the transition from p=none to p=reject as a black
box, in that they believe they have no way of knowing what the full impact
of such a change might have on their mail, and they fear irreparable harm
to their mail if they make a mistake.

The designers of DMARC anticipated this fear, and built several different
transitional states, or ratchets, into the protocol, including:

   - The "pct" tag (https://trac.ietf.org/trac/dmarc/ticket/47)
   - The "sp" tag (https://trac.ietf.org/trac/dmarc/ticket/48)
   - "quarantine" as a value for "p=" (
   https://trac.ietf.org/trac/dmarc/ticket/39)

All of these are designed to allow the domain owner to request that some,
but not all, of its mail be held to stricter authentication standards so
that the domain owner can dip a toe in the water before jumping in.

The ratchets have introduced some problems, though:

   - The 'pct' tag doesn't exactly work like it's intended to, and really
   can't because of the nature of mail flow, unless there is a high volume of
   failed authentication for the domain in question. (There is a much longer
   discussion of this in section 6.7.4, Message Sampling, of
   draft-ietf-dmarc-dmarcbis-02.)
   - Some domain owners have taken a "more is more" approach to ratchets,
   figuring if one is good, all are better, resulting in needlessly
   complicated policy records

The purpose of this email is to get folks thinking about possibly
simplifying the ratchet mechanisms, perhaps boiling them down into one.
This thinking and on-list discussion on this topic would serve as a
precursor to further face-to-face discussion at the next interim working
group meeting.

I'll start the discussion by taking an extreme position...

Ratchet mechanisms don't help in any way that a short TTL on your DMARC
record won't help, and in fact you need the short TTL on your record
anyway, because if you're trying a ratchet mechanism and find it's too
much, you still gotta update DNS to roll it back.

Getting to p=reject isn't a difficult undertaking, at least from a
technical standpoint. Enumerate all your mail streams, ensure that they're
authenticating properly, and boom, you're done. The proper tools for doing
that are p=none, a rua tag pointed at a mailbox that is parsed by automated
means, active daily monitoring of the data consumed in those aggregate
reports (so that mail streams can be enumerated and authentication problems
addressed), and time. Time is the big one here, because sufficient time
must elapse to ensure that all of your legitimate mail streams are
exercised and reported upon, and that can take many months in large
organizations or at companies that are in the business of seasonal email
sending.

The big challenge to fixing authentication issues, especially in large
organizations, is usually in just finding who owns the host/process that's
generating that unauthenticated mail. That can add time to the process, but
once you've enumerated them all, updated your SPF record and/or made sure
they're all properly DKIM signing, you can skip right from p=none to
p=reject.

I look forward to lively conversation...

-- 

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

--00000000000044bef005c673cd97
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">Greetings.<br clear=3D"all"></div><div class=3D"gmail_default" s=
tyle=3D"font-family:tahoma,sans-serif"><br></div><div class=3D"gmail_defaul=
t" style=3D"font-family:tahoma,sans-serif">The theoretical goal of any doma=
in owner that publishes a DMARC record is to transition from an initial pol=
icy of p=3Dnone to a final one of p=3Dreject, because it is only at p=3Drej=
ect that DMARC&#39;s intended purpose of preventing same-domain spoofing ca=
n be fully realized.</div><div class=3D"gmail_default" style=3D"font-family=
:tahoma,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-fa=
mily:tahoma,sans-serif">Many domain owners see the transition from p=3Dnone=
 to p=3Dreject as a black box, in that they believe they have no way of kno=
wing what the full impact of such a change might have on their mail, and th=
ey fear irreparable harm to their mail if they make a mistake.=C2=A0</div><=
div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><br></d=
iv><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">The=
 designers of DMARC anticipated this fear, and built several different tran=
sitional states, or ratchets, into the protocol, including:</div><div class=
=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><ul><li>The &quo=
t;pct&quot; tag (<a href=3D"https://trac.ietf.org/trac/dmarc/ticket/47" tar=
get=3D"_blank">https://trac.ietf.org/trac/dmarc/ticket/47</a>)</li><li>The =
&quot;sp&quot; tag (<a href=3D"https://trac.ietf.org/trac/dmarc/ticket/48" =
target=3D"_blank">https://trac.ietf.org/trac/dmarc/ticket/48</a>)</li><li>&=
quot;quarantine&quot; as a value for &quot;p=3D&quot; (<a href=3D"https://t=
rac.ietf.org/trac/dmarc/ticket/39" target=3D"_blank">https://trac.ietf.org/=
trac/dmarc/ticket/39</a>)</li></ul></div><div class=3D"gmail_default" style=
=3D"font-family:tahoma,sans-serif">All of these are designed to allow the d=
omain owner to request that some, but not all, of its mail be held to stric=
ter authentication standards so that the domain owner can dip a toe in the =
water before jumping in.</div><div class=3D"gmail_default" style=3D"font-fa=
mily:tahoma,sans-serif"><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:tahoma,sans-serif">The ratchets have introduced some problems, tho=
ugh:</div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-ser=
if"><ul><li>The &#39;pct&#39; tag doesn&#39;t exactly work like it&#39;s in=
tended to, and really can&#39;t because of the nature of mail flow, unless =
there is a high volume of failed authentication for the domain in question.=
 (There is a much longer discussion of this in section 6.7.4, Message Sampl=
ing, of draft-ietf-dmarc-dmarcbis-02.)</li><li>Some domain owners have take=
n a &quot;more is more&quot; approach to ratchets, figuring if one is good,=
 all are better, resulting in needlessly complicated policy records</li></u=
l><div>The purpose of this email is to get folks thinking about possibly si=
mplifying the ratchet mechanisms, perhaps boiling them down into one. This =
thinking and on-list discussion on this topic would serve as a precursor to=
 further face-to-face discussion at the next interim working group meeting.=
</div><div><br></div><div>I&#39;ll start the discussion by taking an extrem=
e position...<br><br></div><div><div class=3D"gmail_default">Ratchet mechan=
isms don&#39;t help in any way that a short TTL on your DMARC record won&#3=
9;t help, and in fact you need the short TTL on your record anyway, because=
 if you&#39;re trying=C2=A0a ratchet mechanism and find it&#39;s too much, =
you still gotta update DNS to roll it back.<br></div><div class=3D"gmail_de=
fault"><br></div><div class=3D"gmail_default">Getting to p=3Dreject isn&#39=
;t a difficult undertaking, at least from a technical standpoint. Enumerate=
 all your mail streams, ensure that they&#39;re authenticating properly, an=
d boom, you&#39;re done. The proper tools for doing that are p=3Dnone, a ru=
a tag pointed at a mailbox that is parsed by automated means, active daily =
monitoring of the data consumed in those aggregate reports (so that mail st=
reams can be enumerated and authentication problems addressed), and time. T=
ime is the big one here, because sufficient time must elapse to ensure that=
 all of your legitimate mail streams are exercised and reported upon, and t=
hat can take many months in large organizations or at companies that are in=
 the business of seasonal email sending.</div><div class=3D"gmail_default">=
<br></div></div></div><div class=3D"gmail_default" style=3D"font-family:tah=
oma,sans-serif">The big challenge to fixing authentication issues, especial=
ly in large organizations, is usually in just finding who owns the host/pro=
cess that&#39;s generating that unauthenticated mail. That can add time to =
the process, but once you&#39;ve enumerated them all, updated your SPF reco=
rd and/or made sure they&#39;re all properly DKIM signing, you can skip rig=
ht from p=3Dnone to p=3Dreject.<br></div><div class=3D"gmail_default" style=
=3D"font-family:tahoma,sans-serif"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-family:tahoma,sans-serif">I look forward to lively conversatio=
n...</div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-ser=
if"><br></div>-- <br><div dir=3D"ltr" data-smartmail=3D"gmail_signature"><s=
pan><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:basel=
ine;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-si=
ze:small;font-family:Arial"> | Technical Director, Standards and Ecosystem<=
/span></div><span style=3D"vertical-align:baseline;white-space:pre-wrap;fon=
t-size:small;font-family:Arial"><div style=3D"text-align:left"><span style=
=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:=
baseline"> <a href=3D"mailto:todd.herr@valimail.com" target=3D"_blank">todd=
.herr@valimail.com</a> </span></div></span><span><div><span><b>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" styl=
e=3D"background-color:rgb(255,255,255);line-height:1.38;margin-top:0pt;marg=
in-bottom:0pt"><font face=3D"Arial" color=3D"#666666"><span style=3D"font-s=
ize:10.6667px;white-space:pre-wrap">This email and all data transmitted wit=
h it contains confidential and/or proprietary information intended solely f=
or the use of individual(s) authorized to receive it. If you are not an int=
ended and authorized recipient you are hereby notified of any use, disclosu=
re, copying or distribution of the information included in this transmissio=
n is prohibited and may be unlawful. Please immediately notify the sender b=
y replying to this email and then delete it from your system.</span></font>=
</p></span></div></div>

--00000000000044bef005c673cd97--


From nobody Tue Jul  6 08:04:38 2021
Return-Path: <Dilyan.Palauzov@aegee.org>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA0603A2ACE for <dmarc@ietfa.amsl.com>; Tue,  6 Jul 2021 08:04:36 -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, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=aegee.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VW-TV9_2bnGq for <dmarc@ietfa.amsl.com>; Tue,  6 Jul 2021 08:04:31 -0700 (PDT)
Received: from mail.aegee.org (mail.aegee.org [144.76.142.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A46E23A2AC4 for <dmarc@ietf.org>; Tue,  6 Jul 2021 08:04:29 -0700 (PDT)
Received: from mail.aegee.org (localhost [127.0.0.1]) by mail.aegee.org (8.15.2/8.15.2) with ESMTP id 166F4QOe1757105 for <dmarc@ietf.org>; Tue, 6 Jul 2021 15:04:26 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1625583866; i=dkim+sm-localhost@aegee.org; bh=saB8KFCblSsJiqhQ0A/DORimSAqWKUz1gMaig1h5ctk=; h=Date:From:To:Subject:In-Reply-To; b=ihyjBB+6jO9oHfqvfdEbk/F495GocQRsZDiBJZiCKNXCSf4I2R298cZgfSsFZ4qQD aGHGw319/HYHdHjpy5kE+69HdBBo/n61iBvvnMC/hxaRjGIe3JQKuvFbyP+T6d4h7w FP9BmHCq56OUCBbDpyrj5TvyjODv4WLqpbo3BbBhRi1Rbe5w3cSfmqBLpoJEvw82AF Tl0fpFjtUZ+BwG8FgxawcaguW3DYhLG4N2PX5LFgAFhmcTLnFxIo8r83hwVPaoWl/a hHAnI7cmrsxSmKHoJBIEFt5o+37HWqOTL8DmcOrkAj8q9HQih+I+DpypS0vmI+i3uV IcneYzjpEwq3Ax/c6/wJDrzQ6WyWGd6kUmzACyAkLg1iUzlm/wOEAdEt6zrk2ajHlz B5AyUveQW4TUF3ONiM5XyFxPwYsERWBJ7yzELlPUJr3G6HMyhFPsp71VzZQyQaLCFt TrQqtkTPR6F9j+J3nQ0Coggi2VFgfNIoLLiZLAl+au3i02asHuQW8BSSQBMHlHTCHF 5ody593UkV9RnRkZMP3TXe2cQg+2k63shhdwl0KlYcnNv6Yb6P6/9LYHJWtGLaBNJF l3S2FGBszAZuo/kWue24LliBiFkuZe79llVYNvpqCtGB+NgFZcTZwZ7NeLz1zVr+HH +dvluMdNld3keXgu2/ITmI0Y=
Authentication-Results: mail.aegee.org/166F4QOe1757105; dkim=none
Received: from 87.118.146.153.topnet.bg (87.118.146.153.topnet.bg [87.118.146.153]) by webmail.aegee.org (Horde Framework) with HTTPS; Tue, 06 Jul 2021 15:04:26 +0000
Date: Tue, 06 Jul 2021 15:04:26 +0000
Message-ID: <20210706150426.Horde.k6SnZxIEAbA62SaG9Ekjc2b@webmail.aegee.org>
From: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
To: dmarc@ietf.org
In-Reply-To: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qB2HBRx1Jvx-3UavSKAuZcXdncw>
Subject: Re: [dmarc-ietf] Priming the Pump for Discussion - Ratchets p=quarantine
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 06 Jul 2021 15:04:37 -0000

Hello,

Is the period for abstentions on posting now over?

> The designers of DMARC anticipated this fear, and built several different
> transitional states, or ratchets, into the protocol, including:
>
>    - "quarantine" as a value for "p=" (
>    https://trac.ietf.org/trac/dmarc/ticket/39)

After reading several opinions on this, I do not think that  
“quarantine” means a transitional state between “reject” and “none”,  
according to the majority.  The distinct “quarantine” and “reject”  
options exist, solely because the SMTP protocol does permit this  
distinction.  Both options protect the domain equally good.  Both  
options are only hints from the domain owner, which hints can be  
altered by the recipient (the recipient can handle all “reject” as  
“quarantine” and all “quarantine” as “reject”).

I have not read the recent drafts.  In case the drafts do not discuss,  
while reject is better than quarantine, it is not better: reject and  
quarantine are equally good final states.

There are two exceptions:
• Reject allows the sender of emails (the administrator/postmaster) to  
get an (immediate) notification, when the DKIM+DMARC implementations  
on sender and receiver disagree, quarantine does not allow such  
feedback.  The administrator can take actions to fix the  
implementation, based on the feedback for a concrete message.
• Reject allows the sender (the user, mailbox owner) to look for  
alternative means to contact the recipient, once the mail is  
immediately returned.  When quarantine is used, a DMARC/DKIM  
implementations on an end has errors, or transitional DNS problems  
happen, and the recipient does not (regularly) check its spam folder,  
the mail is essentially lost and nobody is notified.

With the above exceptions in mind, that have negative impact only when  
quarantine is used, it is biased to state, that quarantine is a  
transitional state between reject and none.

Past experience showed, that reducing the ratches, by striking  
quarantine out, leads to endless mail threads, which nobody can follow.

I think it is realistic to mention the above two exceptions.

In fact, as somebody mentioned two years ago, the DMARC wording  
suggests that reject is stronger than quarantine.  The wording at  
https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-dmarcbis-02#section-6.7.4.1 (pct fallback to quarantine from reject) does currently support this concept.  As far as I remember, there was consensus to remove this text. (pct=10; p=reject shall fall back to p=none, not to p=quarantine).  If the reasoning on why shall QUARANTINE be kept, is taken into account (=because SMTP allows this variant), the reasoning in no way explains, why is quarantine a transitional  
state.

My opinion is, that the current editing process does improve the  
situation, but DMARC/DKIM will remain complex topics.  Even if a  
misunderstanding on why is reject stronger (better) protection than  
quarantine remains, there will still be improvements in other areas.

The “extreme position” below is not extreme enough: since SPF is  
pointless in indirect mail loops, SPF records shall never be touched  
when dealing with DMARC.  I agree with the extreme position, but I do  
not believe there will be consensus on it.

Greetings
   Дилян

----- Message from Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>  
---------
    Date: Tue, 6 Jul 2021 08:45:35 -0400
    From: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>
Subject: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
      To: IETF DMARC WG <dmarc@ietf.org>


> Greetings.
>
> The theoretical goal of any domain owner that publishes a DMARC record is
> to transition from an initial policy of p=none to a final one of p=reject,
> because it is only at p=reject that DMARC's intended purpose of preventing
> same-domain spoofing can be fully realized.
>
> Many domain owners see the transition from p=none to p=reject as a black
> box, in that they believe they have no way of knowing what the full impact
> of such a change might have on their mail, and they fear irreparable harm
> to their mail if they make a mistake.
>
> The designers of DMARC anticipated this fear, and built several different
> transitional states, or ratchets, into the protocol, including:
>
>    - The "pct" tag (https://trac.ietf.org/trac/dmarc/ticket/47)
>    - The "sp" tag (https://trac.ietf.org/trac/dmarc/ticket/48)
>    - "quarantine" as a value for "p=" (
>    https://trac.ietf.org/trac/dmarc/ticket/39)
>
> All of these are designed to allow the domain owner to request that some,
> but not all, of its mail be held to stricter authentication standards so
> that the domain owner can dip a toe in the water before jumping in.
>
> The ratchets have introduced some problems, though:
>
>    - The 'pct' tag doesn't exactly work like it's intended to, and really
>    can't because of the nature of mail flow, unless there is a high volume of
>    failed authentication for the domain in question. (There is a much longer
>    discussion of this in section 6.7.4, Message Sampling, of
>    draft-ietf-dmarc-dmarcbis-02.)
>    - Some domain owners have taken a "more is more" approach to ratchets,
>    figuring if one is good, all are better, resulting in needlessly
>    complicated policy records
>
> The purpose of this email is to get folks thinking about possibly
> simplifying the ratchet mechanisms, perhaps boiling them down into one.
> This thinking and on-list discussion on this topic would serve as a
> precursor to further face-to-face discussion at the next interim working
> group meeting.
>
> I'll start the discussion by taking an extreme position...
>
> Ratchet mechanisms don't help in any way that a short TTL on your DMARC
> record won't help, and in fact you need the short TTL on your record
> anyway, because if you're trying a ratchet mechanism and find it's too
> much, you still gotta update DNS to roll it back.
>
> Getting to p=reject isn't a difficult undertaking, at least from a
> technical standpoint. Enumerate all your mail streams, ensure that they're
> authenticating properly, and boom, you're done. The proper tools for doing
> that are p=none, a rua tag pointed at a mailbox that is parsed by automated
> means, active daily monitoring of the data consumed in those aggregate
> reports (so that mail streams can be enumerated and authentication problems
> addressed), and time. Time is the big one here, because sufficient time
> must elapse to ensure that all of your legitimate mail streams are
> exercised and reported upon, and that can take many months in large
> organizations or at companies that are in the business of seasonal email
> sending.
>
> The big challenge to fixing authentication issues, especially in large
> organizations, is usually in just finding who owns the host/process that's
> generating that unauthenticated mail. That can add time to the process, but
> once you've enumerated them all, updated your SPF record and/or made sure
> they're all properly DKIM signing, you can skip right from p=none to
> p=reject.
>
> I look forward to lively conversation...
>
> --
>
> *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.


----- End message from Todd Herr  
<todd.herr=40valimail.com@dmarc.ietf.org> -----




From nobody Tue Jul  6 10:59:01 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6B583A2FCF for <dmarc@ietfa.amsl.com>; Tue,  6 Jul 2021 10:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.736
X-Spam-Level: 
X-Spam-Status: No, score=-4.736 tagged_above=-999 required=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.338, 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 7HHjYaGUjLa1 for <dmarc@ietfa.amsl.com>; Tue,  6 Jul 2021 10:58:55 -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 A64F03A304A for <dmarc@ietf.org>; Tue,  6 Jul 2021 10:58:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1625594317; bh=7YlqaX7MmqxnSrYoNGkr7O4WozJknS9Iph/yZ3+GqJo=; l=1500; h=To:References:From:Date:In-Reply-To; b=DJO4yV+BnUUFmMigwRPYc6pb8qAGk+wIL/almLa3VA2X1NV0w2pmrHbZrDkT3s+Vt 9AgJ1Y3UAbc6cez59xnTcNUejlKmt4QcE8fGLUto+UvML8KiuOlwnHsq3goHcjBiBd STWmBI6LjKXo34cpjy3SbjwHfcXs1Z3RyLczIbIjch71SdBnUhDvYtISbOW05
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.0000000060E499CD.00001702; Tue, 06 Jul 2021 19:58:37 +0200
To: dmarc@ietf.org
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <d80b0a14-0f4d-8266-8d42-8d9a6b02413d@tana.it>
Date: Tue, 6 Jul 2021 19:58:37 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@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/-o7nB0-W9XMRiNsNLVXX7BeB9PM>
Subject: Re: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 06 Jul 2021 17:59:00 -0000

Hi,

On Tue 06/Jul/2021 14:45:35 +0200 Todd Herr wrote:
> 
> The theoretical goal of any domain owner that publishes a DMARC record is
> to transition from an initial policy of p=none to a final one of p=reject,
> because it is only at p=reject that DMARC's intended purpose of preventing
> same-domain spoofing can be fully realized.


I slightly disagree on that.  Both p=none and p=quarantine have their own 
merits, and the transition can take a very long time.


> Getting to p=reject isn't a difficult undertaking, at least from a technical
> standpoint. Enumerate all your mail streams, ensure that they're
> authenticating properly, and boom, you're done.


I keep seeing authentication failures on mailing lists.  Speaking for myself, 
MLs constitute a relevant percentage of my mail traffic.  I'm going to stay at 
p=none (or maybe p=quarantine; pct=0) until that is fixed.


> The purpose of this email is to get folks thinking about possibly
> simplifying the ratchet mechanisms, perhaps boiling them down into one.


I'd rather propose to add another p= level, in between p=none and p=quarantine. 
  I'd want receivers to reject my mail if it fails authentication, but only on 
the first hop.  In particular, I'd want mailing lists (whether or not doing 
From: munging) to reject unauthenticated messages claiming to come from me. 
(And, given that it's hard to specify "first hop", it would be fine to word 
such policy as "reject by MLMs only".)


Best
Ale
-- 





















From nobody Tue Jul  6 12:24:30 2021
Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F28C3A3254 for <dmarc@ietfa.amsl.com>; Tue,  6 Jul 2021 12:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=sOzalWCa; dkim=pass (2048-bit key) header.d=taugh.com header.b=buhgMSG3
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZIq71I3IFAw for <dmarc@ietfa.amsl.com>; Tue,  6 Jul 2021 12:24:23 -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 C01E53A3256 for <dmarc@ietf.org>; Tue,  6 Jul 2021 12:24:22 -0700 (PDT)
Received: (qmail 44020 invoked from network); 6 Jul 2021 19:24:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=abed.60e4ade4.k2107; bh=JQ62CY20biuXaVY6x7ltn8yqlF+cgosnpkc/SM5QGek=; b=sOzalWCaVZS2ra52x+glE8NQCpuwODvwHyw5ZjdfeFmfeGh0XAY0BxU5Dzq7waChL23lUsU2wiTt5W/8I83Zyec3zmIMjFUx796BZwvh+ePe/3N0QaGDsFq/KZBc48sjKh/uENd2T4JHqz7iGCAdG4dFJgNoYP2GQq54GInD12YYk/LJSL+26NG3VqoCQgj97iSZto1x2+ygH23pPW5CUwBx6V0ABdPVOkjoqfxXoRTd68VqdZNXps/nw+BbnBUjekRX6IunZNEHyNkUGSRXGOEdCM2/VsdLXqaYw2qV45ifo01WgTcmxQjnZ88UXeHM3RDt/R2rHI5JhpTQHa82mg==
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=abed.60e4ade4.k2107; bh=JQ62CY20biuXaVY6x7ltn8yqlF+cgosnpkc/SM5QGek=; b=buhgMSG35Q1cv33ekv6U8b2lnjgxY6Ous2JZuhOfGRVnZtdkYwNxVMQASp7ogWUELh2UkeGLVrjUp9MNd7omD4MKdMRrWY/YGNWlpXSgQ+DBIncAPyBEw6S3cMG9shbRK7TlAj0uWfSN1eDXtmSICXYTP/F/E432KntFJYGMb0xJOGj3ZQJcp39a/ctCm/VDw4hkpJBoqaqFK8qIS66g5HSvLYVWWKeq44FiWtEIZa43aZ5fGT8k3PeVJTHDuVcmsxfhQsOBtKTxh7+2ZgaefXSsxEPMpDtee9Nq0WgLE3vv/jlL5AT0YilH9DLUg+jqJ+nulJfk92RJl6+eLysUOw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 06 Jul 2021 19:24:20 -0000
Received: by ary.qy (Postfix, from userid 501) id AD3641DDDD7A; Tue,  6 Jul 2021 14:50:57 -0400 (EDT)
Date: 6 Jul 2021 14:50:57 -0400
Message-Id: <20210706192416.AD3641DDDD7A@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: todd.herr@valimail.com
In-Reply-To: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4Z1evopz-xWN8jZMk9QbWDO5da4>
Subject: Re: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 06 Jul 2021 19:24:28 -0000

I don't really have a horse in this race since I never plan to publish anything
other than p=none, but ...

It appears that Todd Herr  <todd.herr@valimail.com> said:
>Ratchet mechanisms don't help in any way that a short TTL on your DMARC
>record won't help, and in fact you need the short TTL on your record
>anyway, because if you're trying a ratchet mechanism and find it's too
>much, you still gotta update DNS to roll it back.

Given that the reports are completely independent of the policy, of course.

I believe the goal of the rachet mechanisms was that you can turn them
up a little bit, so if they're wrong, they'll only screw up a little
bit of your mail. But the fallacy is that if your mail is only a
little bit screwed up, you won't be able to tell from the sending end
whether anything is wrong. Better to take a deep breath, set the TTL to
10 seconds, throw the switch, and if you screwed up, you'll find out
quickly.

My inclination is to deprecate pct= and say receivers can ignore it.  Deprecate p=quarantine,
and say that receivers SHOULD treat p=quarantine and p=reject the same, with the actual
handling to be determined by receivers who know a lot more about their users' behavior
than senders do.

Some people use pct=0 as a flag to say that things like mailing lists should do
DMARC-evading things, but I think there are better ways to debug list software.

R's,
John

PS: https://www.theonion.com/americans-eagerly-check-to-see-if-they-got-any-emails-t-1847220852


From nobody Sun Jul 11 12:32:36 2021
Return-Path: <dougfoster.emailstandards@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8160E3A1AA3 for <dmarc@ietfa.amsl.com>; Sun, 11 Jul 2021 12:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gDpiOkfwEZZg for <dmarc@ietfa.amsl.com>; Sun, 11 Jul 2021 12:32:30 -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 C8E0F3A1AA0 for <dmarc@ietf.org>; Sun, 11 Jul 2021 12:32:30 -0700 (PDT)
Received: by mail-oi1-x231.google.com with SMTP id x70so10374501oif.11 for <dmarc@ietf.org>; Sun, 11 Jul 2021 12:32:30 -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=t+Ff5kyK9rvqSGMl48LEK/odKRZfJMJOZpGJ9HRF+2M=; b=rg2GicLk+SKPcW+TObme7CZTkaLLBAbmA9hE6P0jUtc2xyNHNVDiR/1aKSnZHheJew SdL4s3PMXCUgLYDsbioiElgtJF5jA1iOdKqkr5hO+kitMChs2SV5e+WHIxF0lZR2uxo1 k0x9j/UjKV2F7+oLbUczgcRyiq6KRkiy5/JTlAtRpXDcjD3MjfqtPplE30HnfOFztcG6 D+xWAy4YEj6VtAzBg5vOpdPZsJ2Aa0gGsQ1exzVLCP3dlWH1gODcRlVH16jQtDkaxmjT TJQzcCV75r4e0c+pKlWGQiDtWOb5KGD9UbO8PaluVGrmOer/UAAMYq2zoLzOlzJ2+y0z duVQ==
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=t+Ff5kyK9rvqSGMl48LEK/odKRZfJMJOZpGJ9HRF+2M=; b=LXTNaWvb3UHUamOud2gMtPjmsUjRDXQIBRLsUE7ZQfze7BDdj6OgouoZorzCkT9GxE Kaz/QKOlR6t7AK2McE2teoUxirzcIj7ASLziH/GBqNGbSBIAGlDfaoHbV4smQ8Ir0iIM 4mGrzpRwPr4VzhdUQmczBEWSpjvMgdsiRrvbsls8nFXyTbGYuyYDunVrA6iLCMHCZZhd ZWkb8baVGhxrXFzZ8ZSmaAYd8qhvzoKwJzUBN2qvz7w9n1DYGLSzZHqL1z5cOxSwSuAO G9Np5Che1CCwRIBTneiZ9tjI+7S1CYiMxtcjqOZLez2XFqjuKDuwttwpwPEfkdxfWQvb PYGg==
X-Gm-Message-State: AOAM5302mrwOaRJwr+Sp6ViNjDRt778SJ7YmvnshIv7rV5/nAkrcXZjn RO7jwOl7UDtL2HEoki2pFavwnd3XIao1n2bi3+5cDk8NPpc=
X-Google-Smtp-Source: ABdhPJzSX723qgX0juH2NBuojBVASbGzj+87MwjIKrlV3tq2dwoLtYrIb8oWlHL6Ka+3vdM3OqlSbiRwa8oW672WWp4=
X-Received: by 2002:a05:6808:1153:: with SMTP id u19mr7737520oiu.20.1626031949390;  Sun, 11 Jul 2021 12:32:29 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
In-Reply-To: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sun, 11 Jul 2021 15:32:18 -0400
Message-ID: <CAH48ZfzzVV90CkKX+mCKAfDvgzQY62csCO6Vp92Bh03_zL8jWA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bca7c505c6de107f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VjuEjsBBaBfNDA4IjqMvvtYLHQQ>
Subject: Re: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 11 Jul 2021 19:32:36 -0000

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

If we are willing to break upward compatibility, it might be preferable to
define policy in terms of what the sender knows, rather than what the
receiver should do.   After collecting feedback, the sender should know
whether all message sources are sending with SPF PASS, DKIM PASS, or both.


This could be implemented with granularity based on the domain-part used in
MAILFROM, and these four possible policy statements:

Messages sent using organization domain for SMTP:

=C2=B7         All messages with MAILFROM matching <FROM scope> will produc=
e SPF
PASS, at first hop.

=C2=B7         All messages with MAILFROM matching <FROM scope> will produc=
e
DKIM PASS based on the FROM address, at first hop.

Messages sent by mailing service providers using the service provider
domain for SMTP:

=C2=B7         All messages with MAILFROM not matching <FROM scope> will pr=
oduce
SPF PASS based on the SMTP address used, at first hop.

=C2=B7         All messages with MAILFROM not matching <FROM scope> will pr=
oduce
DKIM PASS based on the FROM address, at first hop.

We know that forwarding can affect DMARC and SPF evaluation, and that
forwarding is outside the control of the sender.   Consequently, when
verification fails, it is the recipient system=E2=80=99s burden to determin=
e
whether forwarding has occurred, how the forwarding action affects the
trust level of the message, and consequently whether the forwarding path is
acceptable.   One way to handle this would be for recipients of forwarded
mail to register that fact with the system administrator, so that the
system administrator could configure appropriate rules in the message
evaluation system.

Additionally, not all DMARC-violating impersonation is malicious, so even
when impersonation is confirmed, it remains the recipient system=E2=80=99s =
burden
to decide whether the impersonation should be tolerated or repudiated.

Some implementations of sender authentication have used IETF specifications
to simplistically implement message repudiation, without understanding the
possible exceptions, and consequently without providing the necessary
exception mechanisms.  I am hoping that DMARCbis will include enough
discussion of exceptions to reduce the likelihood of this error persisting
forever.   Changing the way we define policy might help achieve this goal.


 Doug Foster





On Tue, Jul 6, 2021 at 8:46 AM Todd Herr <todd.herr=3D
40valimail.com@dmarc.ietf.org> wrote:

> Greetings.
>
> The theoretical goal of any domain owner that publishes a DMARC record is
> to transition from an initial policy of p=3Dnone to a final one of p=3Dre=
ject,
> because it is only at p=3Dreject that DMARC's intended purpose of prevent=
ing
> same-domain spoofing can be fully realized.
>
> Many domain owners see the transition from p=3Dnone to p=3Dreject as a bl=
ack
> box, in that they believe they have no way of knowing what the full impac=
t
> of such a change might have on their mail, and they fear irreparable harm
> to their mail if they make a mistake.
>
> The designers of DMARC anticipated this fear, and built several different
> transitional states, or ratchets, into the protocol, including:
>
>    - The "pct" tag (https://trac.ietf.org/trac/dmarc/ticket/47)
>    - The "sp" tag (https://trac.ietf.org/trac/dmarc/ticket/48)
>    - "quarantine" as a value for "p=3D" (
>    https://trac.ietf.org/trac/dmarc/ticket/39)
>
> All of these are designed to allow the domain owner to request that some,
> but not all, of its mail be held to stricter authentication standards so
> that the domain owner can dip a toe in the water before jumping in.
>
> The ratchets have introduced some problems, though:
>
>    - The 'pct' tag doesn't exactly work like it's intended to, and really
>    can't because of the nature of mail flow, unless there is a high volum=
e of
>    failed authentication for the domain in question. (There is a much lon=
ger
>    discussion of this in section 6.7.4, Message Sampling, of
>    draft-ietf-dmarc-dmarcbis-02.)
>    - Some domain owners have taken a "more is more" approach to ratchets,
>    figuring if one is good, all are better, resulting in needlessly
>    complicated policy records
>
> The purpose of this email is to get folks thinking about possibly
> simplifying the ratchet mechanisms, perhaps boiling them down into one.
> This thinking and on-list discussion on this topic would serve as a
> precursor to further face-to-face discussion at the next interim working
> group meeting.
>
> I'll start the discussion by taking an extreme position...
>
> Ratchet mechanisms don't help in any way that a short TTL on your DMARC
> record won't help, and in fact you need the short TTL on your record
> anyway, because if you're trying a ratchet mechanism and find it's too
> much, you still gotta update DNS to roll it back.
>
> Getting to p=3Dreject isn't a difficult undertaking, at least from a
> technical standpoint. Enumerate all your mail streams, ensure that they'r=
e
> authenticating properly, and boom, you're done. The proper tools for doin=
g
> that are p=3Dnone, a rua tag pointed at a mailbox that is parsed by autom=
ated
> means, active daily monitoring of the data consumed in those aggregate
> reports (so that mail streams can be enumerated and authentication proble=
ms
> addressed), and time. Time is the big one here, because sufficient time
> must elapse to ensure that all of your legitimate mail streams are
> exercised and reported upon, and that can take many months in large
> organizations or at companies that are in the business of seasonal email
> sending.
>
> The big challenge to fixing authentication issues, especially in large
> organizations, is usually in just finding who owns the host/process that'=
s
> generating that unauthenticated mail. That can add time to the process, b=
ut
> once you've enumerated them all, updated your SPF record and/or made sure
> they're all properly DKIM signing, you can skip right from p=3Dnone to
> p=3Dreject.
>
> I look forward to lively conversation...
>
> --
>
> *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 prohibit=
ed
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

--000000000000bca7c505c6de107f
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">If we are willing =
to break upward compatibility, it might be
preferable to define policy in terms of what the sender knows, rather than =
what
the receiver should do.=C2=A0=C2=A0 After collecting
feedback, the sender should know whether all message sources are sending wi=
th
SPF PASS, DKIM PASS, or both.=C2=A0</p><p class=3D"MsoNormal" style=3D"marg=
in:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-ser=
if"><br></p><p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:=
107%;font-size:11pt;font-family:Calibri,sans-serif">This could be implement=
ed with<span style=3D"font-size:11pt">=C2=A0granularity
based on the domain-part used in MAILFROM, and these four possible policy
statements:</span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Messages sent using organization do=
main for SMTP:</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>All messages with MAILFROM matching &lt;FROM scope&gt;
will produce SPF PASS, at first hop.</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>All messages with MAILFROM matching &lt;FROM scope&gt;
will produce DKIM PASS based on the FROM address, at first hop.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Messages sent by mailing service pr=
oviders using the service
provider domain for SMTP:</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>All messages with MAILFROM not matching &lt;FROM
scope&gt; will produce SPF PASS based on the SMTP address used, at first ho=
p.</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>All messages with MAILFROM not matching &lt;FROM
scope&gt; will produce DKIM PASS based on the FROM address, at first hop.</=
p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">We know that forwarding can affect =
DMARC and SPF evaluation,
and that forwarding is outside the control of the sender.=C2=A0=C2=A0 Conse=
quently, when verification fails, it is
the recipient system=E2=80=99s burden to determine whether forwarding has o=
ccurred, how
the forwarding action affects the trust level of the message, and consequen=
tly whether
the forwarding path is acceptable.=C2=A0=C2=A0 One way
to handle this would be for recipients of forwarded mail to register that f=
act
with the system administrator, so that the system administrator could confi=
gure
appropriate rules in the message evaluation system.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Additionally, not all DMARC-violati=
ng impersonation is
malicious, so even when impersonation is confirmed, it remains the recipien=
t
system=E2=80=99s burden to decide whether the impersonation should be toler=
ated or repudiated.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Some implementations of sender auth=
entication have used IETF specifications to simplistically implement messag=
e repudiation,
without understanding the possible exceptions, and consequently without pro=
viding
the necessary exception mechanisms.=C2=A0 I am hoping that DMARCbis
will include enough discussion of exceptions to reduce the likelihood of th=
is
error persisting forever.=C2=A0=C2=A0 Changing the
way we define policy might help achieve this goal.</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>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">=C2=A0Doug Foster</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>

<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><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 6, 2021 at 8:=
46 AM Todd Herr &lt;todd.herr=3D<a href=3D"mailto:40valimail.com@dmarc.ietf=
.org">40valimail.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_def=
ault" style=3D"font-family:tahoma,sans-serif">Greetings.<br clear=3D"all"><=
/div><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-seri=
f">The theoretical goal of any domain owner that publishes a DMARC record i=
s to transition from an initial policy of p=3Dnone to a final one of p=3Dre=
ject, because it is only at p=3Dreject that DMARC&#39;s intended purpose of=
 preventing same-domain spoofing can be fully realized.</div><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">Many domain owne=
rs see the transition from p=3Dnone to p=3Dreject as a black box, in that t=
hey believe they have no way of knowing what the full impact of such a chan=
ge might have on their mail, and they fear irreparable harm to their mail i=
f they make a mistake.=C2=A0</div><div class=3D"gmail_default" style=3D"fon=
t-family:tahoma,sans-serif"><br></div><div class=3D"gmail_default" style=3D=
"font-family:tahoma,sans-serif">The designers of DMARC anticipated this fea=
r, and built several different transitional states, or ratchets, into the p=
rotocol, including:</div><div class=3D"gmail_default" style=3D"font-family:=
tahoma,sans-serif"><ul><li>The &quot;pct&quot; tag (<a href=3D"https://trac=
.ietf.org/trac/dmarc/ticket/47" target=3D"_blank">https://trac.ietf.org/tra=
c/dmarc/ticket/47</a>)</li><li>The &quot;sp&quot; tag (<a href=3D"https://t=
rac.ietf.org/trac/dmarc/ticket/48" target=3D"_blank">https://trac.ietf.org/=
trac/dmarc/ticket/48</a>)</li><li>&quot;quarantine&quot; as a value for &qu=
ot;p=3D&quot; (<a href=3D"https://trac.ietf.org/trac/dmarc/ticket/39" targe=
t=3D"_blank">https://trac.ietf.org/trac/dmarc/ticket/39</a>)</li></ul></div=
><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">All o=
f these are designed to allow the domain owner to request that some, but no=
t all, of its mail be held to stricter authentication standards so that the=
 domain owner can dip a toe in the water before jumping in.</div><div class=
=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><br></div><div c=
lass=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">The ratchets=
 have introduced some problems, though:</div><div class=3D"gmail_default" s=
tyle=3D"font-family:tahoma,sans-serif"><ul><li>The &#39;pct&#39; tag doesn&=
#39;t exactly work like it&#39;s intended to, and really can&#39;t because =
of the nature of mail flow, unless there is a high volume of failed authent=
ication for the domain in question. (There is a much longer discussion of t=
his in section 6.7.4, Message Sampling, of draft-ietf-dmarc-dmarcbis-02.)</=
li><li>Some domain owners have taken a &quot;more is more&quot; approach to=
 ratchets, figuring if one is good, all are better, resulting in needlessly=
 complicated policy records</li></ul><div>The purpose of this email is to g=
et folks thinking about possibly simplifying the ratchet mechanisms, perhap=
s boiling them down into one. This thinking and on-list discussion on this =
topic would serve as a precursor to further face-to-face discussion at the =
next interim working group meeting.</div><div><br></div><div>I&#39;ll start=
 the discussion by taking an extreme position...<br><br></div><div><div cla=
ss=3D"gmail_default">Ratchet mechanisms don&#39;t help in any way that a sh=
ort TTL on your DMARC record won&#39;t help, and in fact you need the short=
 TTL on your record anyway, because if you&#39;re trying=C2=A0a ratchet mec=
hanism and find it&#39;s too much, you still gotta update DNS to roll it ba=
ck.<br></div><div class=3D"gmail_default"><br></div><div class=3D"gmail_def=
ault">Getting to p=3Dreject isn&#39;t a difficult undertaking, at least fro=
m a technical standpoint. Enumerate all your mail streams, ensure that they=
&#39;re authenticating properly, and boom, you&#39;re done. The proper tool=
s for doing that are p=3Dnone, a rua tag pointed at a mailbox that is parse=
d by automated means, active daily monitoring of the data consumed in those=
 aggregate reports (so that mail streams can be enumerated and authenticati=
on problems addressed), and time. Time is the big one here, because suffici=
ent time must elapse to ensure that all of your legitimate mail streams are=
 exercised and reported upon, and that can take many months in large organi=
zations or at companies that are in the business of seasonal email sending.=
</div><div class=3D"gmail_default"><br></div></div></div><div class=3D"gmai=
l_default" style=3D"font-family:tahoma,sans-serif">The big challenge to fix=
ing authentication issues, especially in large organizations, is usually in=
 just finding who owns the host/process that&#39;s generating that unauthen=
ticated mail. That can add time to the process, but once you&#39;ve enumera=
ted them all, updated your SPF record and/or made sure they&#39;re all prop=
erly DKIM signing, you can skip right from p=3Dnone to p=3Dreject.<br></div=
><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">I=
 look forward to lively conversation...</div><div class=3D"gmail_default" s=
tyle=3D"font-family:tahoma,sans-serif"><br></div>-- <br><div dir=3D"ltr"><s=
pan><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:basel=
ine;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-si=
ze:small;font-family:Arial"> | Technical Director, Standards and Ecosystem<=
/span></div><span style=3D"vertical-align:baseline;white-space:pre-wrap;fon=
t-size:small;font-family:Arial"><div style=3D"text-align:left"><span style=
=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:=
baseline"> <a href=3D"mailto:todd.herr@valimail.com" target=3D"_blank">todd=
.herr@valimail.com</a> </span></div></span><span><div><span><b>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"fo=
nt-size:10.6667px;white-space:pre-wrap">This email and all data transmitted=
 with it contains confidential and/or proprietary information intended sole=
ly 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, disc=
losure, copying or distribution of the information included in this transmi=
ssion is prohibited and may be unlawful. Please immediately notify the send=
er by replying to this email and then delete it from your system.</span></f=
ont></p></span></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--000000000000bca7c505c6de107f--


From nobody Sun Jul 11 14:43:08 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 631053A1FBB for <dmarc@ietfa.amsl.com>; Sun, 11 Jul 2021 14:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level: 
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tC-reKooNHY6 for <dmarc@ietfa.amsl.com>; Sun, 11 Jul 2021 14:42:54 -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 74B5F3A1F97 for <dmarc@ietf.org>; Sun, 11 Jul 2021 14:42:54 -0700 (PDT)
Received: by mail-oi1-x234.google.com with SMTP id t25so2777329oiw.13 for <dmarc@ietf.org>; Sun, 11 Jul 2021 14:42:54 -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=eG06tkuUXL7Ac2YsPgHHebopS67AHV+dJWo7R4qFFb0=; b=ahS0w/4Nc3W6mE2z8JBkyh5WZ7AlOWuQoX/nIgY4hBa7v9Sm/JSQLhItMhJxZRuAA8 fEOfR9wtfS5MyvFtcPuBDGdigi629DVDJCvgM+jaBLbWZrroIqHGlEhONBgIJv6poRfp WV+gKaWYlRNRNlHjdjvNyAn/RltRmeMO4OGaJj40jbpXqGKDwV39VpHYDwjkNlLHdA94 nOvvSxYJakoibLarb4CQ4vyLPrX1YNQNpHTyGurntwiV/0wQT018+xAB9ye4qAyos6Qk OgbCd/2lyXoTkl4ByyYFDtx+2CTBO7P/7KiimJgW+QGV3fcKUc1EU9DMNl1QObIYNNqW bj8g==
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=eG06tkuUXL7Ac2YsPgHHebopS67AHV+dJWo7R4qFFb0=; b=uPg7asy9veyY7FhfOJSPT7hepsZqgnOH9Y6M4KXlQz/cN9DAl5s79uG1DlqJ60iO/X RM7jc8fHxN52CsXc2jbwzhq7mA9fcWtyiZgeEr4+FF9owtIFtzhC1erA91LBWG5qDJkT oKJ0t85Ueij8OuJGsp7riaUt3O64xcJ9Hdni90ww0HuhJsi3xDhG82ZxQVARI5qEvb+H qUtIUSP3C+SwZ0xrAVsfHLa59XZsMiwEdj8G8V7iOzCo5QhL/suaHTffN0W5UqsAXB60 miePAprXm7aclpUaGtyJ+tmiCzWNlxw8wOVU/NEst70JbifXpLaGypLt1abiMlutdlxq LY9g==
X-Gm-Message-State: AOAM532PDM8Eb0tN4kAxacvrqPri4KDKS5tgkS2cYXkzn9V3RKSOnylx T9Q3IFNpz9xfC7QcNWlAKcsmCOF9lRcOhyREzs6x1qAgG6E=
X-Google-Smtp-Source: ABdhPJxd7VFaOj48SlcKDPOFbaiZIV3qsMtbVhYVbzM1E+nhS9g9hbwrWRq/EOWZK3CkGJKdBFC6Kml/wrXOTNLs/6s=
X-Received: by 2002:aca:c6cf:: with SMTP id w198mr7730623oif.73.1626039772406;  Sun, 11 Jul 2021 14:42:52 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48ZfzzVV90CkKX+mCKAfDvgzQY62csCO6Vp92Bh03_zL8jWA@mail.gmail.com>
In-Reply-To: <CAH48ZfzzVV90CkKX+mCKAfDvgzQY62csCO6Vp92Bh03_zL8jWA@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sun, 11 Jul 2021 17:42:41 -0400
Message-ID: <CAH48Zfz80FfDKEhPsEQPseR5eYJeuEGa5K1HU2MDWabO+0rZNg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000666b105c6dfe3cf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/HDyjTsaFYuX4mO-Kyr6etnRglUs>
Subject: Re: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 11 Jul 2021 21:43:06 -0000

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

Sorry, I got tangled up in the weeds between policy scope and alignment.
 The four policy assertions should have been phrased as:

For messages with FROM within <policy scope>,


=C2=B7         All messages with MAILFROM algined to FROM will produce SPF =
PASS,
at first hop.

=C2=B7         All messages with MAILFROM aligned to FROM will produce DKIM
PASS, based on the FROM address, at first hop.

=C2=B7         All messages with MAILFROM not algned to FROM will produce S=
PF
PASS based on the SMTP address used, at first hop.

=C2=B7         All messages with MAILFROM not aligned to FROM will produce =
DKIM
PASS, based on the FROM address, at first hop.


These are intended to be four independent assertions which can be
individually ON or OFF.   To implement this concept, we would need one or
four new keyword=3Dvalue tokens.    DMARCv1 senders and receivers would use
the existing tokens and values (of which it has been said, 94% are NONE or
PCT=3D0.)   DMARCbis senders and receivers would use the new tokens based o=
n
this concept.

This is intended to address Dave Crocker's concerns which led to a rewrite
of the introduction, Todd Herr's comments that DMARC FAIL should only be a
data point which is integrated into the evaluation algorithm, and
Alessandro's request for a partial implementation between NONE and
QUARANTINE.


Doug Foster

On Sun, Jul 11, 2021 at 3:32 PM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> If we are willing to break upward compatibility, it might be preferable t=
o
> define policy in terms of what the sender knows, rather than what the
> receiver should do.   After collecting feedback, the sender should know
> whether all message sources are sending with SPF PASS, DKIM PASS, or both=
.
>
>
> This could be implemented with granularity based on the domain-part used
> in MAILFROM, and these four possible policy statements:
>
> Messages sent using organization domain for SMTP:
>
> =C2=B7         All messages with MAILFROM matching <FROM scope> will prod=
uce
> SPF PASS, at first hop.
>
> =C2=B7         All messages with MAILFROM matching <FROM scope> will prod=
uce
> DKIM PASS based on the FROM address, at first hop.
>
> Messages sent by mailing service providers using the service provider
> domain for SMTP:
>
> =C2=B7         All messages with MAILFROM not matching <FROM scope> will
> produce SPF PASS based on the SMTP address used, at first hop.
>
> =C2=B7         All messages with MAILFROM not matching <FROM scope> will
> produce DKIM PASS based on the FROM address, at first hop.
>
> We know that forwarding can affect DMARC and SPF evaluation, and that
> forwarding is outside the control of the sender.   Consequently, when
> verification fails, it is the recipient system=E2=80=99s burden to determ=
ine
> whether forwarding has occurred, how the forwarding action affects the
> trust level of the message, and consequently whether the forwarding path =
is
> acceptable.   One way to handle this would be for recipients of forwarded
> mail to register that fact with the system administrator, so that the
> system administrator could configure appropriate rules in the message
> evaluation system.
>
> Additionally, not all DMARC-violating impersonation is malicious, so even
> when impersonation is confirmed, it remains the recipient system=E2=80=99=
s burden
> to decide whether the impersonation should be tolerated or repudiated.
>
> Some implementations of sender authentication have used IETF
> specifications to simplistically implement message repudiation, without
> understanding the possible exceptions, and consequently without providing
> the necessary exception mechanisms.  I am hoping that DMARCbis will inclu=
de
> enough discussion of exceptions to reduce the likelihood of this error
> persisting forever.   Changing the way we define policy might help achiev=
e
> this goal.
>
>
>  Doug Foster
>
>
>
>
>
> On Tue, Jul 6, 2021 at 8:46 AM Todd Herr <todd.herr=3D
> 40valimail.com@dmarc.ietf.org> wrote:
>
>> Greetings.
>>
>> The theoretical goal of any domain owner that publishes a DMARC record i=
s
>> to transition from an initial policy of p=3Dnone to a final one of p=3Dr=
eject,
>> because it is only at p=3Dreject that DMARC's intended purpose of preven=
ting
>> same-domain spoofing can be fully realized.
>>
>> Many domain owners see the transition from p=3Dnone to p=3Dreject as a b=
lack
>> box, in that they believe they have no way of knowing what the full impa=
ct
>> of such a change might have on their mail, and they fear irreparable har=
m
>> to their mail if they make a mistake.
>>
>> The designers of DMARC anticipated this fear, and built several differen=
t
>> transitional states, or ratchets, into the protocol, including:
>>
>>    - The "pct" tag (https://trac.ietf.org/trac/dmarc/ticket/47)
>>    - The "sp" tag (https://trac.ietf.org/trac/dmarc/ticket/48)
>>    - "quarantine" as a value for "p=3D" (
>>    https://trac.ietf.org/trac/dmarc/ticket/39)
>>
>> All of these are designed to allow the domain owner to request that some=
,
>> but not all, of its mail be held to stricter authentication standards so
>> that the domain owner can dip a toe in the water before jumping in.
>>
>> The ratchets have introduced some problems, though:
>>
>>    - The 'pct' tag doesn't exactly work like it's intended to, and
>>    really can't because of the nature of mail flow, unless there is a hi=
gh
>>    volume of failed authentication for the domain in question. (There is=
 a
>>    much longer discussion of this in section 6.7.4, Message Sampling, of
>>    draft-ietf-dmarc-dmarcbis-02.)
>>    - Some domain owners have taken a "more is more" approach to
>>    ratchets, figuring if one is good, all are better, resulting in needl=
essly
>>    complicated policy records
>>
>> The purpose of this email is to get folks thinking about possibly
>> simplifying the ratchet mechanisms, perhaps boiling them down into one.
>> This thinking and on-list discussion on this topic would serve as a
>> precursor to further face-to-face discussion at the next interim working
>> group meeting.
>>
>> I'll start the discussion by taking an extreme position...
>>
>> Ratchet mechanisms don't help in any way that a short TTL on your DMARC
>> record won't help, and in fact you need the short TTL on your record
>> anyway, because if you're trying a ratchet mechanism and find it's too
>> much, you still gotta update DNS to roll it back.
>>
>> Getting to p=3Dreject isn't a difficult undertaking, at least from a
>> technical standpoint. Enumerate all your mail streams, ensure that they'=
re
>> authenticating properly, and boom, you're done. The proper tools for doi=
ng
>> that are p=3Dnone, a rua tag pointed at a mailbox that is parsed by auto=
mated
>> means, active daily monitoring of the data consumed in those aggregate
>> reports (so that mail streams can be enumerated and authentication probl=
ems
>> addressed), and time. Time is the big one here, because sufficient time
>> must elapse to ensure that all of your legitimate mail streams are
>> exercised and reported upon, and that can take many months in large
>> organizations or at companies that are in the business of seasonal email
>> sending.
>>
>> The big challenge to fixing authentication issues, especially in large
>> organizations, is usually in just finding who owns the host/process that=
's
>> generating that unauthenticated mail. That can add time to the process, =
but
>> once you've enumerated them all, updated your SPF record and/or made sur=
e
>> they're all properly DKIM signing, you can skip right from p=3Dnone to
>> p=3Dreject.
>>
>> I look forward to lively conversation...
>>
>> --
>>
>> *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 prohibi=
ted
>> and may be unlawful. Please immediately notify the sender by replying to
>> this email and then delete it from your system.
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>>
>

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

<div dir=3D"ltr"><div dir=3D"ltr">Sorry, I got tangled up in the weeds betw=
een policy scope and alignment.=C2=A0 =C2=A0The four policy assertions shou=
ld have been phrased as:</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">F=
or messages with FROM within &lt;policy scope&gt;,<br><div><p style=3D"marg=
in:0in 0in 0in 0.5in;line-height:15.6933px;font-size:11pt;font-family:Calib=
ri,sans-serif"><span style=3D"font-family:Symbol"><br>=C2=B7<span style=3D"=
font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:nor=
mal;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=C2=A0=C2=A0=C2=A0</span></span>All =
messages with MAILFROM algined=C2=A0to FROM=C2=A0will produce SPF PASS, at =
first hop.</p><p style=3D"margin:0in 0in 8pt 0.5in;line-height:15.6933px;fo=
nt-size:11pt;font-family:Calibri,sans-serif"><span style=3D"font-family:Sym=
bol">=C2=B7<span style=3D"font-variant-numeric:normal;font-variant-east-asi=
an: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=C2=A0=C2=
=A0=C2=A0</span></span>All messages with MAILFROM aligned to FROM will prod=
uce DKIM PASS, based on the FROM address, at first hop.</p><p style=3D"marg=
in:0in 0in 8pt 0.5in;line-height:15.6933px;font-size:11pt;font-family:Calib=
ri,sans-serif"><span style=3D"font-size:11pt;font-family:Symbol">=C2=B7<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=C2=A0=C2=A0=C2=A0</span>=
</span><span style=3D"font-size:11pt">All messages with </span>MAILFROM<spa=
n style=3D"font-size:11pt"> not </span>algned<span style=3D"font-size:11pt"=
> to </span>FROM<span style=3D"font-size:11pt">=C2=A0will produce SPF PASS =
based on the SMTP address used, at first hop.</span></p><p style=3D"margin:=
0in 0in 8pt 0.5in;line-height:15.6933px;font-size:11pt;font-family:Calibri,=
sans-serif"><span style=3D"font-family:Symbol">=C2=B7<span style=3D"font-va=
riant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;fon=
t-size:7pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0</span></span>All messag=
es with MAILFROM not aligned to FROM will produce DKIM PASS, based on the F=
ROM address, at first hop.</p><p style=3D"margin:0in 0in 8pt 0.5in;line-hei=
ght:15.6933px;font-size:11pt;font-family:Calibri,sans-serif"><br></p><p sty=
le=3D"margin:0in 0in 8pt 0.5in;line-height:15.6933px;font-size:11pt;font-fa=
mily:Calibri,sans-serif">These are intended to be four independent assertio=
ns which can be individually ON or OFF.=C2=A0 =C2=A0To implement this conce=
pt, we would need one or four new keyword=3Dvalue tokens.=C2=A0 =C2=A0 DMAR=
Cv1 senders and receivers would use the existing tokens and values (of whic=
h it has been said, 94% are NONE or PCT=3D0.)=C2=A0 =C2=A0DMARCbis senders =
and receivers would use the new tokens based on this concept.</p><p style=
=3D"margin:0in 0in 8pt 0.5in;line-height:15.6933px;font-size:11pt;font-fami=
ly:Calibri,sans-serif">This is intended to address Dave Crocker&#39;s conce=
rns which led to a rewrite of the introduction, Todd Herr&#39;s comments th=
at DMARC FAIL should only be a data point which is integrated into the eval=
uation=C2=A0algorithm, and Alessandro&#39;s request for a partial implement=
ation between NONE and QUARANTINE.</p><p style=3D"margin:0in 0in 8pt 0.5in;=
line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif"><br></=
p><p style=3D"margin:0in 0in 8pt 0.5in;line-height:15.6933px;font-size:11pt=
;font-family:Calibri,sans-serif">Doug Foster</p></div></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Jul 11,=
 2021 at 3:32 PM Douglas Foster &lt;<a href=3D"mailto:dougfoster.emailstand=
ards@gmail.com">dougfoster.emailstandards@gmail.com</a>&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><p clas=
s=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-size:11pt=
;font-family:Calibri,sans-serif">If we are willing to break upward compatib=
ility, it might be
preferable to define policy in terms of what the sender knows, rather than =
what
the receiver should do.=C2=A0=C2=A0 After collecting
feedback, the sender should know whether all message sources are sending wi=
th
SPF PASS, DKIM PASS, or both.=C2=A0</p><p class=3D"MsoNormal" style=3D"marg=
in:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-ser=
if"><br></p><p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:=
107%;font-size:11pt;font-family:Calibri,sans-serif">This could be implement=
ed with<span style=3D"font-size:11pt">=C2=A0granularity
based on the domain-part used in MAILFROM, and these four possible policy
statements:</span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Messages sent using organization do=
main for SMTP:</p>

<p style=3D"margin:0in 0in 0in 0.5in;line-height:107%;font-size:11pt;font-f=
amily:Calibri,sans-serif"><span style=3D"font-family:Symbol">=C2=B7<span st=
yle=3D"font-variant-numeric:normal;font-variant-east-asian:normal;font-stre=
tch:normal;font-size:7pt;line-height:normal;font-family:&quot;Times New Rom=
an&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>All messages with MAILFROM matching &lt;FROM scope&gt;
will produce SPF PASS, at first hop.</p>

<p style=3D"margin:0in 0in 8pt 0.5in;line-height:107%;font-size:11pt;font-f=
amily:Calibri,sans-serif"><span style=3D"font-family:Symbol">=C2=B7<span st=
yle=3D"font-variant-numeric:normal;font-variant-east-asian:normal;font-stre=
tch:normal;font-size:7pt;line-height:normal;font-family:&quot;Times New Rom=
an&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>All messages with MAILFROM matching &lt;FROM scope&gt;
will produce DKIM PASS based on the FROM address, at first hop.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Messages sent by mailing service pr=
oviders using the service
provider domain for SMTP:</p>

<p style=3D"margin:0in 0in 0in 0.5in;line-height:107%;font-size:11pt;font-f=
amily:Calibri,sans-serif"><span style=3D"font-family:Symbol">=C2=B7<span st=
yle=3D"font-variant-numeric:normal;font-variant-east-asian:normal;font-stre=
tch:normal;font-size:7pt;line-height:normal;font-family:&quot;Times New Rom=
an&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>All messages with MAILFROM not matching &lt;FROM
scope&gt; will produce SPF PASS based on the SMTP address used, at first ho=
p.</p>

<p style=3D"margin:0in 0in 8pt 0.5in;line-height:107%;font-size:11pt;font-f=
amily:Calibri,sans-serif"><span style=3D"font-family:Symbol">=C2=B7<span st=
yle=3D"font-variant-numeric:normal;font-variant-east-asian:normal;font-stre=
tch:normal;font-size:7pt;line-height:normal;font-family:&quot;Times New Rom=
an&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span></span>All messages with MAILFROM not matching &lt;FROM
scope&gt; will produce DKIM PASS based on the FROM address, at first hop.</=
p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">We know that forwarding can affect =
DMARC and SPF evaluation,
and that forwarding is outside the control of the sender.=C2=A0=C2=A0 Conse=
quently, when verification fails, it is
the recipient system=E2=80=99s burden to determine whether forwarding has o=
ccurred, how
the forwarding action affects the trust level of the message, and consequen=
tly whether
the forwarding path is acceptable.=C2=A0=C2=A0 One way
to handle this would be for recipients of forwarded mail to register that f=
act
with the system administrator, so that the system administrator could confi=
gure
appropriate rules in the message evaluation system.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Additionally, not all DMARC-violati=
ng impersonation is
malicious, so even when impersonation is confirmed, it remains the recipien=
t
system=E2=80=99s burden to decide whether the impersonation should be toler=
ated or repudiated.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Some implementations of sender auth=
entication have used IETF specifications to simplistically implement messag=
e repudiation,
without understanding the possible exceptions, and consequently without pro=
viding
the necessary exception mechanisms.=C2=A0 I am hoping that DMARCbis
will include enough discussion of exceptions to reduce the likelihood of th=
is
error persisting forever.=C2=A0=C2=A0 Changing the
way we define policy might help achieve this goal.</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>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">=C2=A0Doug Foster</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>

<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><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 6, 2021 at 8:=
46 AM Todd Herr &lt;todd.herr=3D<a href=3D"mailto:40valimail.com@dmarc.ietf=
.org" target=3D"_blank">40valimail.com@dmarc.ietf.org</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div =
class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">Greetings.<=
br clear=3D"all"></div><div class=3D"gmail_default" style=3D"font-family:ta=
homa,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-famil=
y:tahoma,sans-serif">The theoretical goal of any domain owner that publishe=
s a DMARC record is to transition from an initial policy of p=3Dnone to a f=
inal one of p=3Dreject, because it is only at p=3Dreject that DMARC&#39;s i=
ntended purpose of preventing same-domain spoofing can be fully realized.</=
div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><b=
r></div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif=
">Many domain owners see the transition from p=3Dnone to p=3Dreject as a bl=
ack box, in that they believe they have no way of knowing what the full imp=
act of such a change might have on their mail, and they fear irreparable ha=
rm to their mail if they make a mistake.=C2=A0</div><div class=3D"gmail_def=
ault" style=3D"font-family:tahoma,sans-serif"><br></div><div class=3D"gmail=
_default" style=3D"font-family:tahoma,sans-serif">The designers of DMARC an=
ticipated this fear, and built several different transitional states, or ra=
tchets, into the protocol, including:</div><div class=3D"gmail_default" sty=
le=3D"font-family:tahoma,sans-serif"><ul><li>The &quot;pct&quot; tag (<a hr=
ef=3D"https://trac.ietf.org/trac/dmarc/ticket/47" target=3D"_blank">https:/=
/trac.ietf.org/trac/dmarc/ticket/47</a>)</li><li>The &quot;sp&quot; tag (<a=
 href=3D"https://trac.ietf.org/trac/dmarc/ticket/48" target=3D"_blank">http=
s://trac.ietf.org/trac/dmarc/ticket/48</a>)</li><li>&quot;quarantine&quot; =
as a value for &quot;p=3D&quot; (<a href=3D"https://trac.ietf.org/trac/dmar=
c/ticket/39" target=3D"_blank">https://trac.ietf.org/trac/dmarc/ticket/39</=
a>)</li></ul></div><div class=3D"gmail_default" style=3D"font-family:tahoma=
,sans-serif">All of these are designed to allow the domain owner to request=
 that some, but not all, of its mail be held to stricter authentication sta=
ndards so that the domain owner can dip a toe in the water before jumping i=
n.</div><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-s=
erif">The ratchets have introduced some problems, though:</div><div class=
=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><ul><li>The &#39=
;pct&#39; tag doesn&#39;t exactly work like it&#39;s intended to, and reall=
y can&#39;t because of the nature of mail flow, unless there is a high volu=
me of failed authentication for the domain in question. (There is a much lo=
nger discussion of this in section 6.7.4, Message Sampling, of draft-ietf-d=
marc-dmarcbis-02.)</li><li>Some domain owners have taken a &quot;more is mo=
re&quot; approach to ratchets, figuring if one is good, all are better, res=
ulting in needlessly complicated policy records</li></ul><div>The purpose o=
f this email is to get folks thinking about possibly simplifying the ratche=
t mechanisms, perhaps boiling them down into one. This thinking and on-list=
 discussion on this topic would serve as a precursor to further face-to-fac=
e discussion at the next interim working group meeting.</div><div><br></div=
><div>I&#39;ll start the discussion by taking an extreme position...<br><br=
></div><div><div class=3D"gmail_default">Ratchet mechanisms don&#39;t help =
in any way that a short TTL on your DMARC record won&#39;t help, and in fac=
t you need the short TTL on your record anyway, because if you&#39;re tryin=
g=C2=A0a ratchet mechanism and find it&#39;s too much, you still gotta upda=
te DNS to roll it back.<br></div><div class=3D"gmail_default"><br></div><di=
v class=3D"gmail_default">Getting to p=3Dreject isn&#39;t a difficult under=
taking, at least from a technical standpoint. Enumerate all your mail strea=
ms, ensure that they&#39;re authenticating properly, and boom, you&#39;re d=
one. The proper tools for doing that are p=3Dnone, a rua tag pointed at a m=
ailbox that is parsed by automated means, active daily monitoring of the da=
ta consumed in those aggregate reports (so that mail streams can be enumera=
ted and authentication problems addressed), and time. Time is the big one h=
ere, because sufficient time must elapse to ensure that all of your legitim=
ate mail streams are exercised and reported upon, and that can take many mo=
nths in large organizations or at companies that are in the business of sea=
sonal email sending.</div><div class=3D"gmail_default"><br></div></div></di=
v><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">The =
big challenge to fixing authentication issues, especially in large organiza=
tions, is usually in just finding who owns the host/process that&#39;s gene=
rating that unauthenticated mail. That can add time to the process, but onc=
e you&#39;ve enumerated them all, updated your SPF record and/or made sure =
they&#39;re all properly DKIM signing, you can skip right from p=3Dnone to =
p=3Dreject.<br></div><div class=3D"gmail_default" style=3D"font-family:taho=
ma,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-family:=
tahoma,sans-serif">I look forward to lively conversation...</div><div class=
=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><br></div>-- <br=
><div dir=3D"ltr"><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-to=
p:0pt;margin-bottom:0pt"></p><div style=3D"text-align:left"><span style=3D"=
vertical-align:baseline;white-space:pre-wrap;font-size:small;font-family:Ar=
ial"><b>Todd Herr</b></span><span style=3D"vertical-align:baseline;white-sp=
ace:pre-wrap;font-size:small;font-family:Arial"> | Technical Director, Stan=
dards and Ecosystem</span></div><span style=3D"vertical-align:baseline;whit=
e-space:pre-wrap;font-size:small;font-family:Arial"><div style=3D"text-alig=
n:left"><span style=3D"vertical-align:baseline"><b>e:</b></span><span style=
=3D"vertical-align:baseline"> <a href=3D"mailto:todd.herr@valimail.com" tar=
get=3D"_blank">todd.herr@valimail.com</a> </span></div></span><span><div><s=
pan><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"http=
s://hosted-packages.s3-us-west-1.amazonaws.com/Valimail+Logo.png"></div></s=
pan><p dir=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1=
.38;margin-top:0pt;margin-bottom:0pt"><font face=3D"Arial" color=3D"#666666=
"><span style=3D"font-size:10.6667px;white-space:pre-wrap">This email and a=
ll data transmitted with it contains confidential and/or proprietary inform=
ation intended solely for the use of individual(s) authorized to receive it=
. If you are not an intended and authorized recipient you are hereby notifi=
ed of any use, disclosure, copying or distribution of the information inclu=
ded in this transmission is prohibited and may be unlawful. Please immediat=
ely notify the sender by replying to this email and then delete it from you=
r system.</span></font></p></span></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>
</blockquote></div>

--0000000000000666b105c6dfe3cf--


From nobody Tue Jul 13 04:02:48 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 D82643A13AE for <dmarc@ietfa.amsl.com>; Tue, 13 Jul 2021 04:02:46 -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 UZ4eX63sjDGw for <dmarc@ietfa.amsl.com>; Tue, 13 Jul 2021 04:02:45 -0700 (PDT)
Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39D3A3A13AC for <dmarc@ietf.org>; Tue, 13 Jul 2021 04:02:44 -0700 (PDT)
Received: by mail-oi1-x22b.google.com with SMTP id c197so448530oib.11 for <dmarc@ietf.org>; Tue, 13 Jul 2021 04:02: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;  bh=f/klUnQLsZ3ePFPBgi7OLp7J9toLi358WLFww8bX/Fw=; b=vgPPOCLSKAMszObFOTjxjZghy8CvUv5w3uQwqV0RNYZ/oofn6JF9h11CUCKwhHPT0T oOmq1nq1ZAf3iZ34HS0bn9EhlhSP6fjWY2yU/Ee/ENM9rFaNTDjjshAUJfWv5mJqp9Zf McQK/hTXPnvpuclNOVHxcwDTEKRMK0RvZCLnSl8S5Q/VQnE3WSRV95XlRzFTm0RpXw9g 0F/EkCLZTMfAyWIvB8HoVnnJk+eDDwZVYc2L2xKY9jQ/V+t/kis7YNo0Km9/TqpkJsTP HERXBhLZ/vXNWsNxrandvdCfHWu26aDHcYO+O/9Id6vggIR0FcPppNBJOFAgT4YycPQD TfHA==
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=f/klUnQLsZ3ePFPBgi7OLp7J9toLi358WLFww8bX/Fw=; b=s0qLlfM5OGAOhgwsjutp/vM8F4ZqdnBksIOPRJ+CCwFj4I1kPwCIj95TpPX7oSuc3r sBG9GDIwn49E5V/O/qwcOyNweKIN4LzuWrxbLD2IFvqfuITF/O/KDCyORw1O5+3VPv1t ohQoQu3o2vABM7g/TWCp2qfT5MIZNzd4hOLYWsl5wm8aDgdHqqMGFeukthetMJ97krah pXJ8lDmPaOPlG6S4D3PxhueulkKuO3q9YjYMECPXhYLc+3BMZytDdR//JyK849pAPuQm TkbMFodKnVevK8mlLZVrMnDCl5dRPBUwwaAbsNeay+7iJXwuV6/DWLW6fYAsgoUs9XEv QU9A==
X-Gm-Message-State: AOAM530m5lEXY8mrGRkyR1mfAMl0DXqJtkbY7tXfWHQAbnH0RlET/7Pt PO/LokzGnUUIMtjsbEfDPLx7JtMpaS6AHqXv7AOAInF3
X-Google-Smtp-Source: ABdhPJzPJ5Mm0taX1dWbkc5B4gwSSKPyXOfMkVl5XTRAoDlQhrf7fAlwJA4RBCq56ytflchzfEM38yerZv0IN2q5E3k=
X-Received: by 2002:a05:6808:1153:: with SMTP id u19mr14324126oiu.20.1626174163551;  Tue, 13 Jul 2021 04:02:43 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
In-Reply-To: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 13 Jul 2021 07:02:34 -0400
Message-ID: <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005c884805c6ff2dae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/8u60kxGAbi-fQWOC9cidURAHDE4>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 13 Jul 2021 11:02:47 -0000

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

I understand that under the current specification, PCT has been useful
because P=NONE with PCT=100 produces different results than QUARANTINE with
PCT=0.   This is an anomaly that I would hope we can fix, but if not, we
need to specify that the only valid settings are PCT=0 or PCT=100.   The
specification should force numbers between 1 and 99 to be interpreted as
either 0 or 100.

The current PCT specification is fatally flawed because the denominator is
undefined and unstable.  Suppose that a domain owner concludes that most
but not all of his traffic will produce DMARC PASS.   Should the percentage
be based on message volume or Source IP counts?    Either way, the volume
distribution received by any single evaluator will be different than the
volume distribution sent out.

But the larger problem is that the evaluator is performing a conditional
probability, because the policy is only applied to messages that produce
DMARC FAIL.    If there is no impersonation, an unauthenticated message has
a 100% probability of being legitimate.    The denominator is determined by
the volume of impersonation messages, not by the volume of legitimate
messages.   The percentage offered by the sending domain owner is useless.

Next, assume that an accurate probability can be determined, and that 80%
of unauthenticated messages are legitimate and 20% are impersonations.
Does it make sense to apply that probability rule to
message disposition?    It will produce these results:

Legitimate and DMARC ignored, message accepted = 80%*80% = 64% of total

Legitimate and DMARC enforced, message blocked = 80%*20% = 16% of total

Impersonation and DMARC ignored, message accepted = 20%*80% = 16% of total

Impersonation and DMARC enforced, message blocked = 20%*20% = 4% of total

Therefore, the correct decision is applied only 68% of the time, and the
wrong decision is applied 32% of the time.   This is unsatisfactory for
protecting against ransomware, and also unsatisfactory for reliably
delivering wanted messages.

The actual volume of impersonating messages will be determined by the
spammer, not by the domain owner, so the whole notion of choosing a
percentage is flawed.    The domain owner does not have the information
needed to provide a usable percentage.   The message evaluator can only
determine the percentage by carefully examining many messages and
categorizing the source.  Once the source is categorized, guessing is no
longer necessary and the percentage is irrelevant.


Doug Foster

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

<div dir=3D"ltr"><div dir=3D"ltr"><p class=3D"MsoNormal" style=3D"margin:0i=
n 0in 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif">I=
 understand that under the current specification, PCT has
been useful because P=3DNONE with PCT=3D100 produces different results than=
 QUARANTINE with PCT=3D0.=C2=A0=C2=A0 This is an anomaly that I would
hope we can fix, but if not, we need to specify that the only valid setting=
s
are PCT=3D0 or PCT=3D100.=C2=A0=C2=A0 The specification
should force numbers between 1 and 99 to be interpreted as either 0 or 100.=
 </p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">The current PCT specification is fa=
tally flawed because the
denominator is undefined and unstable.=C2=A0
Suppose that a domain owner concludes that most but not all of his traffic
will produce DMARC PASS.=C2=A0=C2=A0 Should the
percentage be based on message volume or Source IP counts?=C2=A0=C2=A0=C2=
=A0 Either way, the volume distribution received
by any single evaluator will be different than the volume distribution sent
out.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">But the larger problem is that the =
evaluator is performing a
conditional probability, because the policy is only applied to messages tha=
t
produce DMARC FAIL.=C2=A0=C2=A0=C2=A0 If there is no
impersonation, an unauthenticated message has a 100% probability of being
legitimate.=C2=A0=C2=A0=C2=A0 The denominator is
determined by the volume of impersonation messages, not by the volume of
legitimate messages.=C2=A0=C2=A0 The percentage
offered by the sending domain owner is useless.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Next, assume that an accurate proba=
bility can be determined,
and that 80% of unauthenticated messages are legitimate and 20% are
impersonations.=C2=A0=C2=A0 Does it make sense to
apply that probability rule to message=C2=A0disposition?=C2=A0=C2=A0=C2=A0
It will produce these results:</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Legitimate and DMARC ignored, messa=
ge accepted =3D 80%*80% =3D
64% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Legitimate and DMARC enforced, mess=
age blocked =3D 80%*20% =3D
16% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Impersonation and DMARC ignored, me=
ssage accepted =3D 20%*80%
=3D 16% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Impersonation and DMARC enforced, m=
essage blocked =3D 20%*20%
=3D 4% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Therefore, the correct decision is =
applied only 68% of the
time, and the wrong decision is applied 32% of the time.=C2=A0 =C2=A0This
is unsatisfactory for protecting against ransomware, and also unsatisfactor=
y
for reliably delivering wanted messages.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">The actual volume of impersonating =
messages will be
determined by the spammer, not by the domain owner, so the whole notion of
choosing a percentage is flawed.=C2=A0=C2=A0=C2=A0 The
domain owner does not have the information needed to provide a usable
percentage.=C2=A0=C2=A0 The message evaluator can
only determine the percentage by carefully examining many messages and
categorizing the source.=C2=A0 Once the source
is categorized, guessing is no longer necessary and the percentage is
irrelevant.</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><p class=3D"MsoNormal" styl=
e=3D"margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:Calibri=
,sans-serif">Doug Foster</p></div></div>

--0000000000005c884805c6ff2dae--


From nobody Tue Jul 13 11:10:09 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 532893A13B6 for <dmarc@ietfa.amsl.com>; Tue, 13 Jul 2021 11:10:08 -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=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 QDYf_QVWcUXr for <dmarc@ietfa.amsl.com>; Tue, 13 Jul 2021 11:10:03 -0700 (PDT)
Received: from mail-qv1-xf2c.google.com (mail-qv1-xf2c.google.com [IPv6:2607:f8b0:4864:20::f2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FB673A13B3 for <dmarc@ietf.org>; Tue, 13 Jul 2021 11:10:02 -0700 (PDT)
Received: by mail-qv1-xf2c.google.com with SMTP id h9so6899789qvs.0 for <dmarc@ietf.org>; Tue, 13 Jul 2021 11:10:02 -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=NuvKqH4FXp4/6MEtzbOf8XuBtP014BRyQOnmsXGAciI=; b=YXtU4milWgnB4N0ytTxQI1lSI2Foo99My6QMxpikcn+SWvn1vwilFYvh3qSOCuypnr uOvb0hK9oV8gvCCoTQhwEOrKpOfjiceqxiTvYUc65GmpkzHMpfqcC2Hi6Zk6OtL99plY ORSKxdM8787UZKg0lDqvWAm20/4pvW6w1ivepAwJXeiwXRsuWMjC+R3Hb5flQCUEmTzL dGPscLid2j8J/7JYL9tqBxTyhNcBuPUa1WrkqiGUalAOkhNhvuyaCl0Z+YHIKM6+Wbs+ fSBxHzLdDTjM3BAPzb0y32QyCeBxO83ptbe9CyqqP6cXZ0fz6yFVYYCpNOgJzsfRreYG 3hZg==
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=NuvKqH4FXp4/6MEtzbOf8XuBtP014BRyQOnmsXGAciI=; b=j6VhQPYjJutFH8EeB7gqfDsZKj90gYCefhdOJqfaMQy7MrS3rEB7IC4IKxSVKylPgU iGyVo1d1KaQ+UOYbp+Qh0SHUoF4VYgTliafii2CxMnMTUq3OQKzR+7AM6bee+26agNaF nY9pYGzFn/BTNf6NtaQVihA7usN2oLVjCzve2pmdG0jcI5/rF/NkTPKm/obXWvkI4byi 0ZRP34NIa13XSd+hjTP3MXfBMdBvieGzC1cywVEH9vtKuwaq5IjT1EFWtj+sbqxVJ8Bz D1dmwIJi1ju02n3+iBXJ5AEHPxmNzht92pT9LfSyPi6QLZMAZrF8pLl8sw87J1C3nM5x X2Dw==
X-Gm-Message-State: AOAM531fOPFLe3OCqEjwv4Cs2aAC77crItmRNKGwdp/CVwE7UQt3XuAz Wbb5Gdt190uQfuNErSmIJzDxhvieZW75RG6wCYflx/NB59/5IA==
X-Google-Smtp-Source: ABdhPJzBrLT/QOvn/CLIcE9USZHq1+AmZLfRHqep0NtQHELky7i0DbS8UsWc5LZMU0zzHkB4Lc038BsoEH32ITz8AWI=
X-Received: by 2002:a05:6214:19e1:: with SMTP id q1mr6137788qvc.44.1626199800838;  Tue, 13 Jul 2021 11:10:00 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com>
In-Reply-To: <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 13 Jul 2021 14:09:45 -0400
Message-ID: <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000076925105c705259a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/go4HfF0F-aK6iK1Gw0lz5o_TZIw>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 13 Jul 2021 18:10:08 -0000

--00000000000076925105c705259a
Content-Type: text/plain; charset="UTF-8"

On Tue, Jul 13, 2021 at 7:03 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> I understand that under the current specification, PCT has been useful
> because P=NONE with PCT=100 produces different results than QUARANTINE with
> PCT=0.   This is an anomaly that I would hope we can fix, but if not, we
> need to specify that the only valid settings are PCT=0 or PCT=100.   The
> specification should force numbers between 1 and 99 to be interpreted as
> either 0 or 100.
>
> The current PCT specification is fatally flawed because the denominator is
> undefined and unstable.  Suppose that a domain owner concludes that most
> but not all of his traffic will produce DMARC PASS.   Should the percentage
> be based on message volume or Source IP counts?    Either way, the volume
> distribution received by any single evaluator will be different than the
> volume distribution sent out.
>
> But the larger problem is that the evaluator is performing a conditional
> probability, because the policy is only applied to messages that produce
> DMARC FAIL.    If there is no impersonation, an unauthenticated message has
> a 100% probability of being legitimate.    The denominator is determined by
> the volume of impersonation messages, not by the volume of legitimate
> messages.   The percentage offered by the sending domain owner is useless.
>
> Next, assume that an accurate probability can be determined, and that 80%
> of unauthenticated messages are legitimate and 20% are impersonations.
> Does it make sense to apply that probability rule to
> message disposition?    It will produce these results:
>
> Legitimate and DMARC ignored, message accepted = 80%*80% = 64% of total
>
> Legitimate and DMARC enforced, message blocked = 80%*20% = 16% of total
>
> Impersonation and DMARC ignored, message accepted = 20%*80% = 16% of total
>
> Impersonation and DMARC enforced, message blocked = 20%*20% = 4% of total
>
> Therefore, the correct decision is applied only 68% of the time, and the
> wrong decision is applied 32% of the time.   This is unsatisfactory for
> protecting against ransomware, and also unsatisfactory for reliably
> delivering wanted messages.
>
> The actual volume of impersonating messages will be determined by the
> spammer, not by the domain owner, so the whole notion of choosing a
> percentage is flawed.    The domain owner does not have the information
> needed to provide a usable percentage.   The message evaluator can only
> determine the percentage by carefully examining many messages and
> categorizing the source.  Once the source is categorized, guessing is no
> longer necessary and the percentage is irrelevant.
>
>
>
I believe you'll find that your ideas, or at least sentiments quite similar
to them, are captured in draft-ietf-dmarc-dmarcbis-02

First, draft-ietf-dmarc-dmarcbis-02 makes a small but substantial change to
the definition of the pct tag from what's currently in RFC 7489. Where RFC
7489 reads:

   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.


draft-ietf-dmarc-dmarcbis-02 instead starts with this text:

   pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;

      default is 100).  For the RFC5322.From domain to which the DMARC

      record applies, the "pct" tag is the percentage of messages

      producing a DMARC result of "fail" to which the Domain Owner
      wishes its preferred handling policy be applied.

Since the concept of applying DMARC policy to messages that produce a DMARC
result of "pass" doesn't exist, it doesn't make sense to claim that "pct"
applies to the entire mailstream.

Next, draft-ietf-dmarc-dmarcbis-02 contains a substantial rewrite of the
Message Sampling section (now section 6.7.4) that goes to great lengths to
attempt to show that the desired pct value really can't be counted on to be
applied as asked for, and what might actually happen could vary widely from
what's desired.

https://datatracker.ietf.org/doc/draft-ietf-dmarc-dmarcbis/


-- 

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

--00000000000076925105c705259a
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 Tue, Jul 13, 2021 at 7:03 AM Douglas Foster &lt;<a href=3D"mailt=
o:dougfoster.emailstandards@gmail.com">dougfoster.emailstandards@gmail.com<=
/a>&gt; wrote:</span><br></div></div><div class=3D"gmail_quote"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><p=
 class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-size=
:11pt;font-family:Calibri,sans-serif">I understand that under the current s=
pecification, PCT has
been useful because P=3DNONE with PCT=3D100 produces different results than=
 QUARANTINE with PCT=3D0.=C2=A0=C2=A0 This is an anomaly that I would
hope we can fix, but if not, we need to specify that the only valid setting=
s
are PCT=3D0 or PCT=3D100.=C2=A0=C2=A0 The specification
should force numbers between 1 and 99 to be interpreted as either 0 or 100.=
 </p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">The current PCT specification is fa=
tally flawed because the
denominator is undefined and unstable.=C2=A0
Suppose that a domain owner concludes that most but not all of his traffic
will produce DMARC PASS.=C2=A0=C2=A0 Should the
percentage be based on message volume or Source IP counts?=C2=A0=C2=A0=C2=
=A0 Either way, the volume distribution received
by any single evaluator will be different than the volume distribution sent
out.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">But the larger problem is that the =
evaluator is performing a
conditional probability, because the policy is only applied to messages tha=
t
produce DMARC FAIL.=C2=A0=C2=A0=C2=A0 If there is no
impersonation, an unauthenticated message has a 100% probability of being
legitimate.=C2=A0=C2=A0=C2=A0 The denominator is
determined by the volume of impersonation messages, not by the volume of
legitimate messages.=C2=A0=C2=A0 The percentage
offered by the sending domain owner is useless.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Next, assume that an accurate proba=
bility can be determined,
and that 80% of unauthenticated messages are legitimate and 20% are
impersonations.=C2=A0=C2=A0 Does it make sense to
apply that probability rule to message=C2=A0disposition?=C2=A0=C2=A0=C2=A0
It will produce these results:</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Legitimate and DMARC ignored, messa=
ge accepted =3D 80%*80% =3D
64% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Legitimate and DMARC enforced, mess=
age blocked =3D 80%*20% =3D
16% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Impersonation and DMARC ignored, me=
ssage accepted =3D 20%*80%
=3D 16% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Impersonation and DMARC enforced, m=
essage blocked =3D 20%*20%
=3D 4% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Therefore, the correct decision is =
applied only 68% of the
time, and the wrong decision is applied 32% of the time.=C2=A0 =C2=A0This
is unsatisfactory for protecting against ransomware, and also unsatisfactor=
y
for reliably delivering wanted messages.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">The actual volume of impersonating =
messages will be
determined by the spammer, not by the domain owner, so the whole notion of
choosing a percentage is flawed.=C2=A0=C2=A0=C2=A0 The
domain owner does not have the information needed to provide a usable
percentage.=C2=A0=C2=A0 The message evaluator can
only determine the percentage by carefully examining many messages and
categorizing the source.=C2=A0 Once the source
is categorized, guessing is no longer necessary and the percentage is
irrelevant.</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></div></blockquote><d=
iv><br></div><div class=3D"gmail_default" style=3D""><font face=3D"tahoma, =
sans-serif">I believe you&#39;ll find that your ideas, or at least sentimen=
ts quite similar to them, are captured in draft-ietf-dmarc-dmarcbis-02</fon=
t></div><div class=3D"gmail_default" style=3D""><font face=3D"tahoma, sans-=
serif"><br></font></div><div class=3D"gmail_default" style=3D""><font face=
=3D"tahoma, sans-serif">First, draft-ietf-dmarc-dmarcbis-02 makes a small b=
ut substantial change to the definition of the pct tag from what&#39;s curr=
ently in RFC 7489. Where RFC 7489 reads:</font></div><div class=3D"gmail_de=
fault" style=3D""><pre class=3D"gmail-newpage"><font face=3D"tahoma, sans-s=
erif">   pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
      default is 100).  Percentage of messages from the Domain Owner&#39;s
      mail stream to which the DMARC policy is to be applied.</font></pre><=
/div></div><div><font face=3D"tahoma, sans-serif"><br></font></div><div><fo=
nt face=3D"tahoma, sans-serif">draft-ietf-dmarc-dmarcbis-02<span class=3D"g=
mail_default" style=3D""> instead starts with this text:</span></font></div=
><div><font face=3D"tahoma, sans-serif"><br></font></div>





<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;line-height:normal;color:rgb(=
0,0,0)"><span class=3D"gmail-s1" style=3D"font-variant-ligatures:no-common-=
ligatures"><font face=3D"tahoma, sans-serif"><span class=3D"gmail-Apple-con=
verted-space">=C2=A0 =C2=A0</span>pct:<span class=3D"gmail-Apple-converted-=
space">=C2=A0 </span>(plain-text integer between 0 and 100, inclusive; OPTI=
ONAL;</font></span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;line-height:normal;color:rgb(=
0,0,0)"><span class=3D"gmail-s1" style=3D"font-variant-ligatures:no-common-=
ligatures"><font face=3D"tahoma, sans-serif"><span class=3D"gmail-Apple-con=
verted-space">=C2=A0 =C2=A0 =C2=A0 </span>default is 100).<span class=3D"gm=
ail-Apple-converted-space">=C2=A0 </span>For the RFC5322.From domain to whi=
ch the DMARC</font></span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;line-height:normal;color:rgb(=
0,0,0)"><span class=3D"gmail-s1" style=3D"font-variant-ligatures:no-common-=
ligatures"><font face=3D"tahoma, sans-serif"><span class=3D"gmail-Apple-con=
verted-space">=C2=A0 =C2=A0 =C2=A0 </span>record applies, the &quot;pct&quo=
t; tag is the percentage of messages</font></span></p>
<p class=3D"gmail-p1" style=3D"margin:0px;font-variant-numeric:normal;font-=
variant-east-asian:normal;font-stretch:normal;line-height:normal;color:rgb(=
0,0,0)"><span class=3D"gmail-s1" style=3D"font-variant-ligatures:no-common-=
ligatures"><font face=3D"tahoma, sans-serif"><span class=3D"gmail-Apple-con=
verted-space">=C2=A0 =C2=A0 =C2=A0 </span>producing a DMARC result of &quot=
;fail&quot; to which the Domain Owner</font></span></p>
<div><font face=3D"tahoma, sans-serif"><span class=3D"gmail-Apple-converted=
-space" style=3D"font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0=
)">=C2=A0 =C2=A0 =C2=A0=C2=A0</span><span style=3D"font-variant-ligatures:n=
o-common-ligatures;color:rgb(0,0,0)">wishes its preferred handling policy b=
e applied.</span></font></div><div><font face=3D"tahoma, sans-serif"><br></=
font></div><div><span class=3D"gmail_default" style=3D""><font face=3D"taho=
ma, sans-serif">Since the concept of applying DMARC policy to messages that=
 produce a DMARC result of &quot;pass&quot; doesn&#39;t exist, it doesn&#39=
;t make sense to claim that &quot;pct&quot; applies to the entire mailstrea=
m.</font></span></div><div><span class=3D"gmail_default" style=3D""><font f=
ace=3D"tahoma, sans-serif"><br></font></span></div><div><font face=3D"tahom=
a, sans-serif"><span class=3D"gmail_default" style=3D"">Next,=C2=A0</span>d=
raft-ietf-dmarc-dmarcbis-02<span class=3D"gmail_default" style=3D""> contai=
ns a substantial rewrite of the Message Sampling section (now section 6.7.4=
) that goes to great lengths to attempt to show that the desired pct value =
really can&#39;t be counted on to be applied as asked for, and what might a=
ctually happen could vary widely from what&#39;s desired.</span></font></di=
v><div><font face=3D"tahoma, sans-serif"><br></font></div><blockquote style=
=3D"margin:0 0 0 40px;border:none;padding:0px"><div><font face=3D"tahoma, s=
ans-serif"><a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dmarc-dma=
rcbis/">https://datatracker.ietf.org/doc/draft-ietf-dmarc-dmarcbis/</a></fo=
nt><span style=3D"font-family:tahoma,sans-serif"></span></div></blockquote>=
<div><br></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><span><p d=
ir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p=
><div style=3D"text-align:left"><span style=3D"vertical-align:baseline;whit=
e-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></span>=
<span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small=
;font-family:Arial"> | Technical Director, Standards and Ecosystem</span></=
div><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:s=
mall;font-family:Arial"><div style=3D"text-align:left"><span style=3D"verti=
cal-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@val=
imail.com</a> </span></div></span><span><div><span><b>m:</b></span><span> 7=
03.220.4153</span><span></span></div><div style=3D"text-align:left"><img st=
yle=3D"width: 175px; height: 43px;" src=3D"https://hosted-packages.s3-us-we=
st-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-bo=
ttom:0pt"><font face=3D"Arial" color=3D"#666666"><span style=3D"font-size:1=
0.6667px;white-space:pre-wrap">This email and all data transmitted with it =
contains confidential and/or proprietary information intended solely for th=
e 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, c=
opying or distribution of the information included in this transmission is =
prohibited and may be unlawful. Please immediately notify the sender by rep=
lying to this email and then delete it from your system.</span></font></p><=
/span></div></div>

--00000000000076925105c705259a--


From nobody Tue Jul 13 14:22:02 2021
Return-Path: <dougfoster.emailstandards@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B91D3A1071 for <dmarc@ietfa.amsl.com>; Tue, 13 Jul 2021 14:21:59 -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 hGXSXBnLTFyS for <dmarc@ietfa.amsl.com>; Tue, 13 Jul 2021 14:21:55 -0700 (PDT)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D54D3A106E for <dmarc@ietf.org>; Tue, 13 Jul 2021 14:21:55 -0700 (PDT)
Received: by mail-oi1-x22c.google.com with SMTP id s23so15449304oij.0 for <dmarc@ietf.org>; Tue, 13 Jul 2021 14:21:55 -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=OYFsf/zP3rLJ5b1ehMz7+IGyuuXtnVOEX6wfRv/WaPg=; b=k2Fei3syJ1BhLE3C7gARXXrUvrbXZfybBrvEejARjef+iRy1lDqNgRtw7s87IbKzaQ wG4ytMuvIllc8OkIouIJdjx9esrQbQh9XD03TcP91s0xNUAsvhfun3wkyHb4Yq3UOq0u I/uzuLwFOJsQhqmTF5ILBPywgzSFdG4x1oTDsZQ8JGKONrYY7hGaixaZcvcsPwk4DRuV GZe+MfJBuroC0K+y6CDSVCrTEPvzhALo5yME8yTqu1WxKCUynBIJV7D8/GiBwnmOv72c +x1ek0+2tDkuLQQH9OYT46CI4BfwOrHw8yc84biNXjjk3D8mDJC5lk4bASYvSAxAkclR j+7w==
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=OYFsf/zP3rLJ5b1ehMz7+IGyuuXtnVOEX6wfRv/WaPg=; b=FEQKyYbZBJ3qqdwRtz9glntXDzf6MG37QiPqwAv7EK56ZY2tQRHoR4NUNVYgHE4ycp nVEXLZS8cMiwRZRBBkz9vpzXK/3FWEEKRbcG02x2e/vJSaU9pBQdHIU98VzU9/pc7ClH esLhS9AFb8xGPQEo49OdFhEM3e8VdeTVAsDIzhxQCvDuyQ0KLWuuiCERRHNWA2R0M3f5 uElbOW1grJ/hr66GGk239OIlBTo/9IBIAqvTemetwGJvhrA65EHej+w3/xR6yULlIIv3 SrmEu/7ggwBEqmq5mX+VdDcmuDQE1vJ21iH9+JbfGQDfnrJb5n7FBTV0SDx2sqhXWnwR NdoA==
X-Gm-Message-State: AOAM532nLpWGhqHrohDFKnskd7YEQtRyHWwONBjFaH/XLQNUfTXaFZM6 wPdc5TRYPW3FbsZrCfTzFvgKMZvLrw1PR0T9+Jnl6me2
X-Google-Smtp-Source: ABdhPJw+JXKOcSqSb6SuHE9tPl4XgFivZEykZkJ3b0QvimA7JueBP7b7LLfm5Q9Vqm3O/22m1RwrZgKVO4anc9MmI14=
X-Received: by 2002:aca:c6cf:: with SMTP id w198mr168546oif.73.1626211313711;  Tue, 13 Jul 2021 14:21:53 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com>
In-Reply-To: <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Tue, 13 Jul 2021 17:21:40 -0400
Message-ID: <CAH48Zfy2enymaSpHXJ0EpBS29iunt-Dnm1H58vEsX4fc7LEdvA@mail.gmail.com>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aefc7005c707d3f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/28HvlSKdJrJ7pxID7xXny4Z-Veg>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 13 Jul 2021 21:22:00 -0000

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

Thank you.   I will review it.

On Tue, Jul 13, 2021, 2:10 PM Todd Herr <todd.herr=
40valimail.com@dmarc.ietf.org> wrote:

> On Tue, Jul 13, 2021 at 7:03 AM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> I understand that under the current specification, PCT has been useful
>> because P=NONE with PCT=100 produces different results than QUARANTINE with
>> PCT=0.   This is an anomaly that I would hope we can fix, but if not, we
>> need to specify that the only valid settings are PCT=0 or PCT=100.   The
>> specification should force numbers between 1 and 99 to be interpreted as
>> either 0 or 100.
>>
>> The current PCT specification is fatally flawed because the denominator
>> is undefined and unstable.  Suppose that a domain owner concludes that most
>> but not all of his traffic will produce DMARC PASS.   Should the percentage
>> be based on message volume or Source IP counts?    Either way, the volume
>> distribution received by any single evaluator will be different than the
>> volume distribution sent out.
>>
>> But the larger problem is that the evaluator is performing a conditional
>> probability, because the policy is only applied to messages that produce
>> DMARC FAIL.    If there is no impersonation, an unauthenticated message has
>> a 100% probability of being legitimate.    The denominator is determined by
>> the volume of impersonation messages, not by the volume of legitimate
>> messages.   The percentage offered by the sending domain owner is useless.
>>
>> Next, assume that an accurate probability can be determined, and that 80%
>> of unauthenticated messages are legitimate and 20% are impersonations.
>> Does it make sense to apply that probability rule to
>> message disposition?    It will produce these results:
>>
>> Legitimate and DMARC ignored, message accepted = 80%*80% = 64% of total
>>
>> Legitimate and DMARC enforced, message blocked = 80%*20% = 16% of total
>>
>> Impersonation and DMARC ignored, message accepted = 20%*80% = 16% of total
>>
>> Impersonation and DMARC enforced, message blocked = 20%*20% = 4% of total
>>
>> Therefore, the correct decision is applied only 68% of the time, and the
>> wrong decision is applied 32% of the time.   This is unsatisfactory for
>> protecting against ransomware, and also unsatisfactory for reliably
>> delivering wanted messages.
>>
>> The actual volume of impersonating messages will be determined by the
>> spammer, not by the domain owner, so the whole notion of choosing a
>> percentage is flawed.    The domain owner does not have the information
>> needed to provide a usable percentage.   The message evaluator can only
>> determine the percentage by carefully examining many messages and
>> categorizing the source.  Once the source is categorized, guessing is no
>> longer necessary and the percentage is irrelevant.
>>
>>
>>
> I believe you'll find that your ideas, or at least sentiments quite
> similar to them, are captured in draft-ietf-dmarc-dmarcbis-02
>
> First, draft-ietf-dmarc-dmarcbis-02 makes a small but substantial change
> to the definition of the pct tag from what's currently in RFC 7489. Where
> RFC 7489 reads:
>
>    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.
>
>
> draft-ietf-dmarc-dmarcbis-02 instead starts with this text:
>
>    pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
>
>       default is 100).  For the RFC5322.From domain to which the DMARC
>
>       record applies, the "pct" tag is the percentage of messages
>
>       producing a DMARC result of "fail" to which the Domain Owner
>       wishes its preferred handling policy be applied.
>
> Since the concept of applying DMARC policy to messages that produce a
> DMARC result of "pass" doesn't exist, it doesn't make sense to claim that
> "pct" applies to the entire mailstream.
>
> Next, draft-ietf-dmarc-dmarcbis-02 contains a substantial rewrite of the
> Message Sampling section (now section 6.7.4) that goes to great lengths to
> attempt to show that the desired pct value really can't be counted on to be
> applied as asked for, and what might actually happen could vary widely from
> what's desired.
>
> https://datatracker.ietf.org/doc/draft-ietf-dmarc-dmarcbis/
>
>
> --
>
> *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.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"auto">Thank you.=C2=A0 =C2=A0I will review it.</div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 13, 2=
021, 2:10 PM Todd Herr &lt;todd.herr=3D<a href=3D"mailto:40valimail.com@dma=
rc.ietf.org">40valimail.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmai=
l_default" style=3D"font-family:tahoma,sans-serif"><span style=3D"font-fami=
ly:Arial,Helvetica,sans-serif">On Tue, Jul 13, 2021 at 7:03 AM Douglas Fost=
er &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com" target=3D"_bl=
ank" rel=3D"noreferrer">dougfoster.emailstandards@gmail.com</a>&gt; wrote:<=
/span><br></div></div><div class=3D"gmail_quote"><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><p class=3D"MsoNo=
rmal" style=3D"margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-fami=
ly:Calibri,sans-serif">I understand that under the current specification, P=
CT has
been useful because P=3DNONE with PCT=3D100 produces different results than=
 QUARANTINE with PCT=3D0.=C2=A0=C2=A0 This is an anomaly that I would
hope we can fix, but if not, we need to specify that the only valid setting=
s
are PCT=3D0 or PCT=3D100.=C2=A0=C2=A0 The specification
should force numbers between 1 and 99 to be interpreted as either 0 or 100.=
 </p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">The current PCT specification is fa=
tally flawed because the
denominator is undefined and unstable.=C2=A0
Suppose that a domain owner concludes that most but not all of his traffic
will produce DMARC PASS.=C2=A0=C2=A0 Should the
percentage be based on message volume or Source IP counts?=C2=A0=C2=A0=C2=
=A0 Either way, the volume distribution received
by any single evaluator will be different than the volume distribution sent
out.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">But the larger problem is that the =
evaluator is performing a
conditional probability, because the policy is only applied to messages tha=
t
produce DMARC FAIL.=C2=A0=C2=A0=C2=A0 If there is no
impersonation, an unauthenticated message has a 100% probability of being
legitimate.=C2=A0=C2=A0=C2=A0 The denominator is
determined by the volume of impersonation messages, not by the volume of
legitimate messages.=C2=A0=C2=A0 The percentage
offered by the sending domain owner is useless.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Next, assume that an accurate proba=
bility can be determined,
and that 80% of unauthenticated messages are legitimate and 20% are
impersonations.=C2=A0=C2=A0 Does it make sense to
apply that probability rule to message=C2=A0disposition?=C2=A0=C2=A0=C2=A0
It will produce these results:</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Legitimate and DMARC ignored, messa=
ge accepted =3D 80%*80% =3D
64% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Legitimate and DMARC enforced, mess=
age blocked =3D 80%*20% =3D
16% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Impersonation and DMARC ignored, me=
ssage accepted =3D 20%*80%
=3D 16% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Impersonation and DMARC enforced, m=
essage blocked =3D 20%*20%
=3D 4% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Therefore, the correct decision is =
applied only 68% of the
time, and the wrong decision is applied 32% of the time.=C2=A0 =C2=A0This
is unsatisfactory for protecting against ransomware, and also unsatisfactor=
y
for reliably delivering wanted messages.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">The actual volume of impersonating =
messages will be
determined by the spammer, not by the domain owner, so the whole notion of
choosing a percentage is flawed.=C2=A0=C2=A0=C2=A0 The
domain owner does not have the information needed to provide a usable
percentage.=C2=A0=C2=A0 The message evaluator can
only determine the percentage by carefully examining many messages and
categorizing the source.=C2=A0 Once the source
is categorized, guessing is no longer necessary and the percentage is
irrelevant.</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></div></blockquote><d=
iv><br></div><div class=3D"gmail_default"><font face=3D"tahoma, sans-serif"=
>I believe you&#39;ll find that your ideas, or at least sentiments quite si=
milar to them, are captured in draft-ietf-dmarc-dmarcbis-02</font></div><di=
v class=3D"gmail_default"><font face=3D"tahoma, sans-serif"><br></font></di=
v><div class=3D"gmail_default"><font face=3D"tahoma, sans-serif">First, dra=
ft-ietf-dmarc-dmarcbis-02 makes a small but substantial change to the defin=
ition of the pct tag from what&#39;s currently in RFC 7489. Where RFC 7489 =
reads:</font></div><div class=3D"gmail_default"><pre><font face=3D"tahoma, =
sans-serif">   pct:  (plain-text integer between 0 and 100, inclusive; OPTI=
ONAL;
      default is 100).  Percentage of messages from the Domain Owner&#39;s
      mail stream to which the DMARC policy is to be applied.</font></pre><=
/div></div><div><font face=3D"tahoma, sans-serif"><br></font></div><div><fo=
nt face=3D"tahoma, sans-serif">draft-ietf-dmarc-dmarcbis-02<span class=3D"g=
mail_default"> instead starts with this text:</span></font></div><div><font=
 face=3D"tahoma, sans-serif"><br></font></div>





<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><span style=
=3D"font-variant-ligatures:no-common-ligatures"><font face=3D"tahoma, sans-=
serif"><span>=C2=A0 =C2=A0</span>pct:<span>=C2=A0 </span>(plain-text intege=
r between 0 and 100, inclusive; OPTIONAL;</font></span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><span style=
=3D"font-variant-ligatures:no-common-ligatures"><font face=3D"tahoma, sans-=
serif"><span>=C2=A0 =C2=A0 =C2=A0 </span>default is 100).<span>=C2=A0 </spa=
n>For the RFC5322.From domain to which the DMARC</font></span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><span style=
=3D"font-variant-ligatures:no-common-ligatures"><font face=3D"tahoma, sans-=
serif"><span>=C2=A0 =C2=A0 =C2=A0 </span>record applies, the &quot;pct&quot=
; tag is the percentage of messages</font></span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><span style=
=3D"font-variant-ligatures:no-common-ligatures"><font face=3D"tahoma, sans-=
serif"><span>=C2=A0 =C2=A0 =C2=A0 </span>producing a DMARC result of &quot;=
fail&quot; to which the Domain Owner</font></span></p>
<div><font face=3D"tahoma, sans-serif"><span style=3D"font-variant-ligature=
s:no-common-ligatures;color:rgb(0,0,0)">=C2=A0 =C2=A0 =C2=A0=C2=A0</span><s=
pan style=3D"font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)">w=
ishes its preferred handling policy be applied.</span></font></div><div><fo=
nt face=3D"tahoma, sans-serif"><br></font></div><div><span class=3D"gmail_d=
efault"><font face=3D"tahoma, sans-serif">Since the concept of applying DMA=
RC policy to messages that produce a DMARC result of &quot;pass&quot; doesn=
&#39;t exist, it doesn&#39;t make sense to claim that &quot;pct&quot; appli=
es to the entire mailstream.</font></span></div><div><span class=3D"gmail_d=
efault"><font face=3D"tahoma, sans-serif"><br></font></span></div><div><fon=
t face=3D"tahoma, sans-serif"><span class=3D"gmail_default">Next,=C2=A0</sp=
an>draft-ietf-dmarc-dmarcbis-02<span class=3D"gmail_default"> contains a su=
bstantial rewrite of the Message Sampling section (now section 6.7.4) that =
goes to great lengths to attempt to show that the desired pct value really =
can&#39;t be counted on to be applied as asked for, and what might actually=
 happen could vary widely from what&#39;s desired.</span></font></div><div>=
<font face=3D"tahoma, sans-serif"><br></font></div><blockquote style=3D"mar=
gin:0 0 0 40px;border:none;padding:0px"><div><font face=3D"tahoma, sans-ser=
if"><a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dmarc-dmarcbis/"=
 target=3D"_blank" rel=3D"noreferrer">https://datatracker.ietf.org/doc/draf=
t-ietf-dmarc-dmarcbis/</a></font><span style=3D"font-family:tahoma,sans-ser=
if"></span></div></blockquote><div><br></div>-- <br><div dir=3D"ltr"><span>=
<p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"=
></p><div style=3D"text-align:left"><span style=3D"vertical-align:baseline;=
white-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></s=
pan><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:s=
mall;font-family:Arial"> | Technical Director, Standards and Ecosystem</spa=
n></div><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-si=
ze:small;font-family:Arial"><div style=3D"text-align:left"><span style=3D"v=
ertical-align:baseline"><b>e:</b></span><span style=3D"vertical-align:basel=
ine"> <a href=3D"mailto:todd.herr@valimail.com" target=3D"_blank" rel=3D"no=
referrer">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"t=
ext-align:left"><img style=3D"width:175px;height:43px" src=3D"https://hoste=
d-packages.s3-us-west-1.amazonaws.com/Valimail+Logo.png"></div></span><p di=
r=3D"ltr" style=3D"background-color:rgb(255,255,255);line-height:1.38;margi=
n-top:0pt;margin-bottom:0pt"><font face=3D"Arial" color=3D"#666666"><span s=
tyle=3D"font-size:10.6667px;white-space:pre-wrap">This email and all data t=
ransmitted with it contains confidential and/or proprietary information int=
ended 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 th=
is transmission is prohibited and may be unlawful. Please immediately notif=
y the sender by replying to this email and then delete it from your system.=
</span></font></p></span></div></div>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank" rel=3D"noreferrer">dmar=
c@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a=
><br>
</blockquote></div>

--000000000000aefc7005c707d3f3--


From nobody Tue Jul 13 18:24:23 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 34A213A0E1C for <dmarc@ietfa.amsl.com>; Tue, 13 Jul 2021 18:24:12 -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, 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 M_KK6Jdad1AA for <dmarc@ietfa.amsl.com>; Tue, 13 Jul 2021 18:24:07 -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 C3F243A0DF7 for <dmarc@ietf.org>; Tue, 13 Jul 2021 18:24:07 -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 16E1NsiO016451 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NO) for <dmarc@ietf.org>; Wed, 14 Jul 2021 01:24:03 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com 16E1NsiO016451
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1626225844; bh=MIUwtpB/gq+m8HU8l5GkVwTYcwm+rkJyYXllQZ2t17g=; h=Subject:To:References:From:Date:In-Reply-To; b=WGPRzmloO5cuywx8UuKcR6tpQbqS5b72IgRy/DAus7kO1JdDQRyLvbbCFYeifEXzH FH2KVSw4YeATSkStWmSlQzBF6uADwr6oUIjfSzLGWieJXtelpm+8F+mFPVbvmIDfIW 34bJ7jcybvVV0VMGbZpwl2RKtyrx3oz0oT+rAV02ejymNQCBtKX1+7W9ErMyZ+kI9l uXzHGIiK2w+UkKwrLY2urYYIpLOVrjMXzD6LZKKcpLLmz1QHxMhzifHDv0QgPKh670 gN5PXdmW5AJ4N8rGvBZwHcFQZW0mW9PePIgi0XlOB6Uf4bk+4hIRdsqKdH6xcD50/z YpuxECavFJ9Qg==
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_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
From: Steven M Jones <smj@crash.com>
Message-ID: <b73035f2-e098-06d7-58c5-8264a5bb0980@crash.com>
Date: Tue, 13 Jul 2021 18:23:54 -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: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------3B7A69AEB55848BE73505879"
Content-Language: en-US
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Wed, 14 Jul 2021 01:24:03 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/KSs73rJD2wpHqFMnoT_RIaqCO34>
Subject: Re: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 14 Jul 2021 01:24:22 -0000

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

On 7/6/21 05:45, Todd Herr wrote:
>
> The theoretical goal of any domain owner that publishes a DMARC record
> is to transition from an initial policy of p=none to a final one of
> p=reject, because it is only at p=reject that DMARC's intended purpose
> of preventing same-domain spoofing can be fully realized.

While preventing impersonation of "high value" domains was the original
impetus for DMARC, and preventing same-domain spoofing is a/the core
benefit, it provides value for other use cases as well. For example, a
domain that doesn't currently see much abuse and has several indirect
mailflows (so "p=none"), but wants reporting as an "early warning
system" in case they're targeted later.

Broad applicability helps justify putting DMARC on the Standards Track,
so IMO we should be careful not to preclude other use cases, or give the
impression they aren't seen as valid.

--S.



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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 7/6/21 05:45, Todd Herr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div class="gmail_default" style="font-family:tahoma,sans-serif"><br
            clear="all">
        </div>
        <div class="gmail_default" style="font-family:tahoma,sans-serif">The
          theoretical goal of any domain owner that publishes a DMARC
          record is to transition from an initial policy of p=none to a
          final one of p=reject, because it is only at p=reject that
          DMARC's intended purpose of preventing same-domain spoofing
          can be fully realized.</div>
      </div>
    </blockquote>
    <p>While preventing impersonation of "high value" domains was the
      original impetus for DMARC, and preventing same-domain spoofing is
      a/the core benefit, it provides value for other use cases as well.
      For example, a domain that doesn't currently see much abuse and
      has several indirect mailflows (so "p=none"), but wants reporting
      as an "early warning system" in case they're targeted later.<br>
    </p>
    <p>Broad applicability helps justify putting DMARC on the Standards
      Track, so IMO we should be careful not to preclude other use
      cases, or give the impression they aren't seen as valid.<br>
    </p>
    <p>--S.</p>
    <p><br>
    </p>
  </body>
</html>

--------------3B7A69AEB55848BE73505879--


From nobody Wed Jul 14 09:52:40 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 BBDF43A24C3 for <dmarc@ietfa.amsl.com>; Wed, 14 Jul 2021 09:52:38 -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, HEADER_FROM_DIFFERENT_DOMAINS=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=mp8YicqC; dkim=pass (2048-bit key) header.d=taugh.com header.b=oqXuMai+
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tI0uDhNrrh7W for <dmarc@ietfa.amsl.com>; Wed, 14 Jul 2021 09:52:33 -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 B72A63A24C2 for <dmarc@ietf.org>; Wed, 14 Jul 2021 09:52:33 -0700 (PDT)
Received: (qmail 41046 invoked from network); 14 Jul 2021 16:52:30 -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=a054.60ef164e.k2107; bh=7okUPZGIKRRfVF1RE/ZxEg+OTRdvmSKqvXmgypbGc2M=; b=mp8YicqC8aLsCRk6uOl0AC3ns7+VlfLGqTxLEmNLJzenj6ve9+b3eOARZr+fYrvGxKe9FxZrnpm7e95UC9TgzOjsry8ADzwd0xTJZ8WzsRmn1u4lt6P98tDUZJ+0lGdMYoI+iNLjv5fKYzZZbgro5XNAa84IDHzl2c0O3GsUE2IfUcHRXTrImY6wIkiYYr3+jvt4CaAxi8mJGQtP7BDFoXh29fxZ8zu4+v4kgEhnShavNF0OjQMadHJIvGNqlK4LTK5TEQaeJtKBg8HMOT4+Mxk+jtQD9R8x40Bq0ft0NO+jgJ55PKh3yas1Q0k7zmpiGDabPqlh3oxRN4jYRkHP3A==
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=a054.60ef164e.k2107; bh=7okUPZGIKRRfVF1RE/ZxEg+OTRdvmSKqvXmgypbGc2M=; b=oqXuMai+dCmmiCwrdhF0rcxhy2zOOi/h7SoKXjJxOnl47V0tL7Day36OGK0NgBksVskSNYlpmn7H1kSqorHmDZGE+1UWLtqrPEozPUnMn8V+VTjp3D/7xyZO9d7b9dKw3qgpCaKZMXRWTuytKBydU6YcB1Uh5yIpKvv8FhmmY8FjKtYQVRVqspVSqLbPlQsyygkMVDpDFFQ3QGc363crd5M93c6TJ3a8IZqD/UUFB0aVW1s2qhlkm1hqX7HMCHHjCu50QbL2USfgb2ABrrLXK1HQkGGWX5HQADkHxhSvXqrC6W7D3c18JiebmHJXgB9O5XRZw2NJiuLeOkzw8mDq3Q==
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 Jul 2021 16:52:30 -0000
Received: by ary.qy (Postfix, from userid 501) id EE9BA2251014; Wed, 14 Jul 2021 12:52:28 -0400 (EDT)
Date: 14 Jul 2021 12:52:28 -0400
Message-Id: <20210714165229.EE9BA2251014@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: smj@crash.com
In-Reply-To: <b73035f2-e098-06d7-58c5-8264a5bb0980@crash.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/FvFNKkXvbBFUc1jzvMwZw5FT9Gc>
Subject: Re: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 14 Jul 2021 16:52:39 -0000

It appears that Steven M Jones  <smj@crash.com> said:
>-=-=-=-=-=-
>
>On 7/6/21 05:45, Todd Herr wrote:
>>
>> The theoretical goal of any domain owner that publishes a DMARC record
>> is to transition from an initial policy of p=none to a final one of
>> p=reject, because it is only at p=reject that DMARC's intended purpose
>> of preventing same-domain spoofing can be fully realized.
>
>While preventing impersonation of "high value" domains was the original
>impetus for DMARC, and preventing same-domain spoofing is a/the core
>benefit, it provides value for other use cases as well. For example, a
>domain that doesn't currently see much abuse and has several indirect
>mailflows (so "p=none"), but wants reporting as an "early warning
>system" in case they're targeted later.

Good point -- that's exactly why I use it, even though I have no intention
of ever publishing a policy other than p=none.

The reports are quite interesting.

R's,
John


From nobody Thu Jul 15 18:07:44 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 00C4A3A1DD0 for <dmarc@ietfa.amsl.com>; Thu, 15 Jul 2021 18:07:43 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 BSp14vF6nWXj for <dmarc@ietfa.amsl.com>; Thu, 15 Jul 2021 18:07:38 -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 D565C3A1DCE for <dmarc@ietf.org>; Thu, 15 Jul 2021 18:07:37 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id e1-20020a9d63c10000b02904b8b87ecc43so8225872otl.4 for <dmarc@ietf.org>; Thu, 15 Jul 2021 18:07:37 -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=86xiQgla1iyE2W3/jyFq0klTbkIp+8rkqBckv3ePv8s=; b=Hro/j5btrIRAjm3tZzd9VBGPKHz4Owoe7EkJBxpX5y9k1DPcGkTEW4qgnb3NIPu0iy KCE/PvNHD7+KBO7t0hk3HdtXzxcsJ83Og4JrL0eiAGtH74PG4xLWii3wn5kjAkkaibaQ pP6Zq3BAXJ/ABZ4Vh1H9PoLS2/YZpUnshjHHRS+jfxrtiSFa9LvMxfodGn13YGVD+Mp5 D9usMK9NyI2RbaFfvcJNLhCerzBclL0dK+7ktm3J31o2btllGaO0hPtDKm6byBAEXMjN bE/vVTCaPNpOJScwDixNe0qxYWWuLr6AfDIiOfo7hMgYfCzqSF+5xojICSUTTBQgxzTj mv5Q==
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=86xiQgla1iyE2W3/jyFq0klTbkIp+8rkqBckv3ePv8s=; b=Ux0zyI0v7W5zMX6pXFd9K17oqa1ZQ92073USe7cxemPJGCSljwHTUyucrZfL4d4/rL X9jeSMi5tWY1ma6ZkYC7YqnGXBD00iQiImVgmKDc8/FQjTP/Npd6J9SxpS81K/4JJQgk aabACHJjhJfIeTc8zSJFZvNW4sSY8l6eXgCivQ1Xy9lcTJi9gsi1aGDt2tzf/WafBQc3 xKsCUg5d9/dKMk9r6LwzZeKy5ZjksawUif/TSHfFolBZEnmsYFotuFgLH5L1bO/JzX6M Bj+o0bFs51V/yrgczX2Ao0PO5VElv7R4E4Ww4Bg8gnjtwrzcxHzJY2UCp3dD2QmdiUIx Uq1A==
X-Gm-Message-State: AOAM533Il/87SPpsrFBJYGF7reCUtrkFmQVlXLrvw2vrLU4wXsLrkXZE i1S7ZJJnvfRKHmVqRWxIdHoeXs6tLMHMD4Stjk87SHWrKhsTbQ==
X-Google-Smtp-Source: ABdhPJzuu4J0NtAR3budkhGhb05lCRsiMIIQW0m68W+N540FBLntIz1eMmG1IQoNvu8+FNWdRChAlZlX/j/Vi0l+OBA=
X-Received: by 2002:a9d:7010:: with SMTP id k16mr5812834otj.298.1626397655612;  Thu, 15 Jul 2021 18:07:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <d80b0a14-0f4d-8266-8d42-8d9a6b02413d@tana.it>
In-Reply-To: <d80b0a14-0f4d-8266-8d42-8d9a6b02413d@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Thu, 15 Jul 2021 21:07:25 -0400
Message-ID: <CAH48ZfyLvECR_nwLmw6R6RnE4EZa8g_i7MJaF32d2qk4RBCKRA@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000086bf1b05c733362a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/b1HFd_csxdfJIUjABczsgS0kIoM>
Subject: Re: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jul 2021 01:07:43 -0000

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

>
> We can and should provide an intermediate policy option, if we concentrat=
e
> on the principle that both authentication and repudiation require
> confirming evidence.  Repuudiation is not the simple opposite of
> authentication.   To this date, our choices have been limited because
> DMARCv1 did not design repudiation rules, but we can.
>
> The aligned DKIM signature test can have three conclusions, not just two:
>
> =C2=B7         Fully Authenticated:    A signature is present, a DNS publ=
ic
> key is available, and the key can be used to verify the signature.
>
> =C2=B7         Provided:  A signature is present, and a DNS public key is
> available, but the key cannot be used to validate the signature.
>
> =C2=B7         No Signature or No key:  A signature is not present or is
> present but the DNS public key is not available.
>
> If the domain owner indicates that all messages originate with a
> signature, then messages with =E2=80=9CNo Signature or No Key=E2=80=9D ar=
e verifiably not
> from the domain owner and can be confidently repudiated.
>
> Similarly, SPF checks can provide multiple levels of granularity:
>
> =C2=B7         Fully authenticated:   An SPF policy is found, it evaluate=
s to
> PASS, and the MAILFROM and FROM domains are aligned.
>
> =C2=B7         Well-identified source:   An SPF policy is found, it evalu=
ates
> to PASS, but the MAILFROM and FROM domains are not aligned.
>
> =C2=B7         Valid Identifier:  An SPF policy is found.
>
> =C2=B7         No policy:   An SPF lookup returns or NXDOMAIN.
>
> We can provide a repudiation test based on Valid Identifier.   Some
> forwarders will forward without MAILFROM rewrite, in which case SPF will
> fail, but the Valid Identifier test will pass.   Other forwarders will
> perform MAILFROM rewrite to ensure SPF PASS.  In either case, it is
> reasonable to conclude that all forwarded messages wiill pass the =E2=80=
=9CValid
> Identifier=E2=80=9D test.
>
> Consequently, a DMARCbis policy focused on =E2=80=9Cno false rejections=
=E2=80=9D will look
> like this:
>
> =C2=B7         Authenticated (unchanged):
>
> o   SPF PASS and aligned, or
>
> o   DKIM verified and aligned.
>
> =C2=B7         Repudiated (new):
>
> o   No DKIM signature or no DNS key for the signature, when the domain
> owner indicates that DKIM signatures are always present
>
> o   No SPF policy (NONE or NXDOMAIN) when  the domain owner indicates
> that SPF policies always exist.
>
> =C2=B7         Ambiguous (clarified):
>
> o   Any message which is neither Authenticated nor Repudiated.  This
> includes any authorized messages which have been processed through a
> mailing list.
>
Doug Foster

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><p class=3D"MsoNormal" style=3D"margin:0in 0in 10pt;line=
-height:115%;font-size:11pt;font-family:Calibri,sans-serif">We can and shou=
ld provide an intermediate policy option, if
we concentrate on the principle that both authentication and repudiation
require confirming evidence.=C2=A0 Repuudiation
is not the simple opposite of authentication.=C2=A0=C2=A0
To this date, our choices have been limited because DMARCv1 did not
design repudiation rules, but we can.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 10pt;line-height:115%;font-s=
ize:11pt;font-family:Calibri,sans-serif">The aligned DKIM signature test ca=
n have three conclusions,
not just two:</p>

<p class=3D"gmail-MsoListParagraphCxSpFirst" style=3D"margin:0in 0in 0.0001=
pt 0.5in;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"><s=
pan style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:=
normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;lin=
e-height: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>Fully Authenticated:=C2=A0=C2=A0=C2=A0 A signature is present=
, a DNS public key is
available, and the key can be used to verify the signature.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0.000=
1pt 0.5in;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"><=
span style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric=
:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;li=
ne-height: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>Provided:=C2=A0
A signature is present, and a DNS public key is available, but the key
cannot be used to validate the signature. =C2=A0</p>

<p class=3D"gmail-MsoListParagraphCxSpLast" style=3D"margin:0in 0in 10pt 0.=
5in;line-height:115%;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>No Signature or No key:=C2=A0 A signature is not present or i=
s present but
the DNS public key is not available.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 10pt;line-height:115%;font-s=
ize:11pt;font-family:Calibri,sans-serif">If the domain owner indicates that=
 all messages originate
with a signature, then messages with =E2=80=9CNo Signature or No Key=E2=80=
=9D are verifiably not
from the domain owner and can be confidently repudiated.=C2=A0=C2=A0 </p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 10pt;line-height:115%;font-s=
ize:11pt;font-family:Calibri,sans-serif">Similarly, SPF checks can provide =
multiple levels of
granularity:</p>

<p class=3D"gmail-MsoListParagraphCxSpFirst" style=3D"margin:0in 0in 0.0001=
pt 0.5in;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"><s=
pan style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric:=
normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;lin=
e-height: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>Fully authenticated:=C2=A0=C2=A0 An SPF policy is found, it e=
valuates to
PASS, and the MAILFROM and FROM domains are aligned.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0.000=
1pt 0.5in;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"><=
span style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric=
:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;li=
ne-height: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>Well-identified source:=C2=A0=C2=A0 An SPF policy is found, i=
t evaluates to
PASS, but the MAILFROM and FROM domains are not aligned.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0.000=
1pt 0.5in;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"><=
span style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeric=
:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;li=
ne-height: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>Valid Identifier:=C2=A0 An SPF policy is found.</p>

<p class=3D"gmail-MsoListParagraphCxSpLast" style=3D"margin:0in 0in 10pt 0.=
5in;line-height:115%;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>No policy:=C2=A0=C2=A0
An SPF lookup returns or NXDOMAIN.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 10pt;line-height:115%;font-s=
ize:11pt;font-family:Calibri,sans-serif">We can provide a repudiation test =
based on Valid
Identifier.=C2=A0=C2=A0 Some forwarders will forward
without MAILFROM rewrite, in which case SPF will fail, but the Valid Identi=
fier
test will pass.=C2=A0=C2=A0 Other forwarders will perform
MAILFROM rewrite to ensure SPF PASS.=C2=A0 In either
case, it is reasonable to conclude that all forwarded messages wiill pass t=
he =E2=80=9CValid
Identifier=E2=80=9D test.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 10pt;line-height:115%;font-s=
ize:11pt;font-family:Calibri,sans-serif">Consequently, a DMARCbis policy fo=
cused on =E2=80=9Cno false
rejections=E2=80=9D will look like this:</p>

<p class=3D"gmail-MsoListParagraphCxSpFirst" style=3D"margin:0in 0in 0.0001=
pt 38.25pt;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif">=
<span style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numeri=
c:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:7pt;l=
ine-height: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>Authenticated (unchanged): </p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0.000=
1pt 74.25pt;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"=
><span style=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-v=
ariant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;fo=
nt-size:7pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=
=A0=C2=A0
</span></span>SPF PASS and aligned, or </p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0.000=
1pt 74.25pt;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"=
><span style=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-v=
ariant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;fo=
nt-size:7pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=
=A0=C2=A0
</span></span>DKIM verified and aligned.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0.000=
1pt 38.25pt;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"=
><span style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numer=
ic: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=C2=A0=C2=A0
</span></span>Repudiated (new):</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0.000=
1pt 74.25pt;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"=
><span style=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-v=
ariant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;fo=
nt-size:7pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=
=A0=C2=A0
</span></span>No DKIM signature or no DNS key for the
signature, when the domain owner indicates that DKIM signatures are always
present</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0.000=
1pt 74.25pt;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"=
><span style=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-v=
ariant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;fo=
nt-size:7pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=
=A0=C2=A0
</span></span>No SPF policy (NONE or NXDOMAIN) when=C2=A0 the domain owner =
indicates that SPF policies
always exist.</p>

<p class=3D"gmail-MsoListParagraphCxSpMiddle" style=3D"margin:0in 0in 0.000=
1pt 38.25pt;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"=
><span style=3D"font-family:Symbol">=C2=B7<span style=3D"font-variant-numer=
ic: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=C2=A0=C2=A0
</span></span>Ambiguous (clarified):</p>

<p class=3D"gmail-MsoListParagraphCxSpLast" style=3D"margin:0in 0in 10pt 74=
.25pt;line-height:115%;font-size:11pt;font-family:Calibri,sans-serif"><span=
 style=3D"font-family:&quot;Courier New&quot;">o<span style=3D"font-variant=
-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-siz=
e:7pt;line-height:normal;font-family:&quot;Times New Roman&quot;">=C2=A0=C2=
=A0
</span></span>Any message which is neither Authenticated nor
Repudiated.=C2=A0 This includes any authorized
messages which have been processed through a mailing list.=C2=A0</p></block=
quote><div>Doug Foster=C2=A0</div></div></div>

--00000000000086bf1b05c733362a--


From nobody Fri Jul 16 02:32:27 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 A183D3A2FDA for <dmarc@ietfa.amsl.com>; Fri, 16 Jul 2021 02:32:25 -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 tCPA8JmP8rpN for <dmarc@ietfa.amsl.com>; Fri, 16 Jul 2021 02:32:20 -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 8997B3A2FD8 for <dmarc@ietf.org>; Fri, 16 Jul 2021 02:32:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1626427935; bh=VNQ7bW85MXom1Lgns0Ssl0sHOtbS2p3ChbhVXQxUcnY=; l=3534; h=To:References:From:Date:In-Reply-To; b=CmtUUMUKZdUoG9GYCkIRzAr0azZH+kIJ34xW9thfhSEaFmsh2MgpBarFy1awTf2Ma aOPixsFDjbtzpt/EbaqcsvbvmRpvxKhtOGvFvsPQ1SpVzDbf/38rXfOxEHBnT8wrtN jD30B4IiP1o8K8L6dORUFF4RvQOUayB8jstyNOKulfSfAsmfKGuLxHLQdUfuV
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC0D1.0000000060F1521F.00004D16; Fri, 16 Jul 2021 11:32:15 +0200
To: Todd Herr <todd.herr@valimail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <f45a2fb6-c907-feb9-fedd-4573f9685c0c@tana.it>
Date: Fri, 16 Jul 2021 11:32:15 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@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/yC06K85r-CtmKMlJ20YWHokARFk>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jul 2021 09:32:26 -0000

On Tue 13/Jul/2021 20:09:45 +0200 Todd Herr wrote:
> On Tue, Jul 13, 2021 at 7:03 AM Douglas Foster wrote:
> 
> 
> draft-ietf-dmarc-dmarcbis-02 instead starts with this text:
> 
>     pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
>        default is 100).  For the RFC5322.From domain to which the DMARC
>        record applies, the "pct" tag is the percentage of messages
>        producing a DMARC result of "fail" to which the Domain Owner
>        wishes its preferred handling policy be applied.
> 
> Since the concept of applying DMARC policy to messages that produce a DMARC
> result of "pass" doesn't exist, it doesn't make sense to claim that "pct"
> applies to the entire mailstream.


Why not?  I'd say that a DMARC filter takes no action when dmarc=pass (except 
for setting Authentication-Results: and feedback data).  The policy requests 
noop on pass, and it is applied indeed.


> Next, draft-ietf-dmarc-dmarcbis-02 contains a substantial rewrite of the
> Message Sampling section (now section 6.7.4) that goes to great lengths to
> attempt to show that the desired pct value really can't be counted on to be
> applied as asked for, and what might actually happen could vary widely from
> what's desired.


I find that section excessively long and difficult.  It doesn't mention the key 
point that the percentage is more and more exact as the number of (failed) 
messages grows.  Indeed, pct=20 doesn't say that the policy should apply to one 
of /the first five/ messages.

The second paragraph of Section 6.7.4.2 surmises that the percentage is meant 
on a daily basis.  From such assumption, it then infers its inexactness.

    The "pct" tag is a request to take a sample of a larger population
    and apply different rules to it.  The population is made up of all
    messages that produce DMARC "fail" results for that domain in a given
    day, and the sample size is the percentage of that population
    represented by the value of the "pct" tag.  It is trivial to perform
    this sampling to the exact number specified if the population size is
    known, but the nature of email is such that the population size
    cannot be known until all messages have been collected and evaluated
    that day.  Email traffic tends to flow in spurts, not at a constant
    level throughout the day, and so a volume seen during any time slice
    cannot be extrapolated across a 24 hour period.  Waiting until the
    end of the day to decide which messages to either quarantine or
    reject goes against all best practices and exposes the mail-receiving
    organization to vectors of abuse, and so we must approximate the
    population and sample sizes on the fly.

It would be untroubled to consider the population to be made up of all messages 
for that domain during all of the time while the given DMARC record holds.  The 
approximation then results from interrupting the message stream, or altering 
the record, before the applied percentage reaches the exact value expressed 
therein, which otherwise it will eventually meet.


The last paragraph of Section 6.7.4.2 seems to say that pct affects reporting:

    *  "0" - A request that zero percent of messages producing a DMARC
       "fail" result have the specified policy applied.  While this is
       seemingly a non-sensical request, this value has been given
       special meaning by some mailbox providers when combined with
       certain "p=" values to alter DMARC processing and/or reporting for
       the domain publishing such a policy.

I'd remove "and/or reporting".


Best
Ale
-- 















From nobody Fri Jul 16 06:45:02 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 A53AE3A37BC for <dmarc@ietfa.amsl.com>; Fri, 16 Jul 2021 06:45:00 -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 k_r86mVOUSOC for <dmarc@ietfa.amsl.com>; Fri, 16 Jul 2021 06:44:54 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E7AC3A37B6 for <dmarc@ietf.org>; Fri, 16 Jul 2021 06:44:54 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id r125so8718753qkf.1 for <dmarc@ietf.org>; Fri, 16 Jul 2021 06:44:54 -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=+RfzO71FEzqA7YRm8Ay9qgRsGj5SN3RxVS4ps11d+N8=; b=TEb+9Hzd3SR85DaIg6YOtsvYoDFsey5zEPHSE7Ozdj++5vQGrvAFS1jGsyi35gHk5I HgDoO8URAxdirpqDQAR2rnHJgnWDun0rCQnW4pmJO7Vm1S94V+OfvdSshRzjVqp8F3cX sOykmf2FY0OobN7vSf7KU76y/bN4hEbjvLxXcxhWfDWKdFKgHiKxn/kXbyB0ujOaUygq RpbVjRaFQc6NlNrrWda31nrJVnBgXXK2q5OLqYWAgYXoAT5M5Bn5l3TWnlKqkeEBUrXc 8Wq2gSpdB0XxZ5Up3swVFB5SPCyv/+ptbT31DBKbIil4WWwQOehRmQgkxCnPAVe4K4CE 6Z7Q==
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=+RfzO71FEzqA7YRm8Ay9qgRsGj5SN3RxVS4ps11d+N8=; b=ASlMs06DCqDI6RJhePgbLYF2ycT08wBcV0iJjM2oacPZiRI8JOlDjhWZxrWc3uXnL/ h14rgY9yXdqmjxHwNpquJkrfhu6xKqBaDzJG+ttJFWw9GpnJERWPbpkxS6n4y4eK1aWr +zALVM04yIRAhtWqeu+R8oxDF/H5ayX5Fd3w2eLlQb0C0tWj+CwerTOHFiSA9QpQ3zGm 0TBb5qqz3pllP2Rzdi4tH+HLW6OpKEnF7U/LynrrtN4MFJBqmNBNoQQ3RTZQNXLBaULO 9oL1IJRpFLIvsKkHOGv3ctBDkF9ch6zf6iAV51AzMKI5kaPVT9gIHcvpbhMVsakJ/wGU Z7xw==
X-Gm-Message-State: AOAM530jhL339vj8ysq80BVRIVDBuOk0Cpio2AlGjJhjdRcoeqSIYvEm SkBaZZmhF6eLXhMgjA9UARtYN1mkgviiA8FFmMQLYg==
X-Google-Smtp-Source: ABdhPJwJVvL7R1tUBk2NxiSDp2qwVttLfVNPYEpwTiBFnQ71JafLL/uXOZOS04i1jWz4ddjEiyHWxo23w6oZB0Vh5Wc=
X-Received: by 2002:a05:620a:244c:: with SMTP id h12mr9702529qkn.249.1626443091643;  Fri, 16 Jul 2021 06:44:51 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <f45a2fb6-c907-feb9-fedd-4573f9685c0c@tana.it>
In-Reply-To: <f45a2fb6-c907-feb9-fedd-4573f9685c0c@tana.it>
From: Todd Herr <todd.herr@valimail.com>
Date: Fri, 16 Jul 2021 09:44:35 -0400
Message-ID: <CAHej_8=-jUnQAs9yqhnC5-kOvKBWXL4DjHcsu=at-RF0VYxCtQ@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b99ff805c73dca4a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/1ts9k9MD_yHW1yOWa4Au-LPMB-4>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jul 2021 13:45:01 -0000

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

On Fri, Jul 16, 2021 at 5:32 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Tue 13/Jul/2021 20:09:45 +0200 Todd Herr wrote:
> > On Tue, Jul 13, 2021 at 7:03 AM Douglas Foster wrote:
> >
> >
> > draft-ietf-dmarc-dmarcbis-02 instead starts with this text:
> >
> >     pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
> >        default is 100).  For the RFC5322.From domain to which the DMARC
> >        record applies, the "pct" tag is the percentage of messages
> >        producing a DMARC result of "fail" to which the Domain Owner
> >        wishes its preferred handling policy be applied.
> >
> > Since the concept of applying DMARC policy to messages that produce a
> DMARC
> > result of "pass" doesn't exist, it doesn't make sense to claim that "pct"
> > applies to the entire mailstream.
>
>
> Why not?  I'd say that a DMARC filter takes no action when dmarc=pass
> (except
> for setting Authentication-Results: and feedback data).  The policy
> requests
> noop on pass, and it is applied indeed.
>
>
I will continue to maintain that it makes no sense to talk about the
concept of applying DMARC policy to messages which pass DMARC validation
checks, especially in the context of the 'pct' tag.

In RFC 7489, the definitions of "quarantine" and "reject" both speak of
their application in terms of "email that fails the DMARC mechanism check".

So, for a DMARC record such as this:

_dmarc.foo.com IN TXT "v=DMARC1; p=quarantine; pct=X; rua=...."


I assert that the domain owner is requesting that X percent of the messages
that fail the DMARC mechanism check be subjected to the "quarantine"
policy.

To assert that the domain owner is instead asking only that DMARC
validation checks be performed on X percent of the messages runs the very
real risk of the pct mechanism being even less useful as a ratchet,
especially when X is small, because that X% of the total mailstream might
not contain any DMARC failures.

It occurs to me now that something like the following is considered a valid
DMARC record, and we should probably fix that:

_dmarc.foo.com IN TXT "v=DMARC1; p=none; pct=25; rua=...."


The fix would be to describe the 'pct' tag as only valid with p= quarantine
or reject, because "p=none, pct=X" is just a nonsensical way of writing
"p=none; pct=100", because you're going to get "none" on all failures
regardless.


> > Next, draft-ietf-dmarc-dmarcbis-02 contains a substantial rewrite of the
> > Message Sampling section (now section 6.7.4) that goes to great lengths
> to
> > attempt to show that the desired pct value really can't be counted on to
> be
> > applied as asked for, and what might actually happen could vary widely
> from
> > what's desired.
>
>
> I find that section excessively long and difficult.  It doesn't mention
> the key
> point that the percentage is more and more exact as the number of (failed)
> messages grows.  Indeed, pct=20 doesn't say that the policy should apply
> to one
> of /the first five/ messages.
>
>
Please suggest alternate text.

>
>
> The last paragraph of Section 6.7.4.2 seems to say that pct affects
> reporting:
>
>     *  "0" - A request that zero percent of messages producing a DMARC
>        "fail" result have the specified policy applied.  While this is
>        seemingly a non-sensical request, this value has been given
>        special meaning by some mailbox providers when combined with
>        certain "p=" values to alter DMARC processing and/or reporting for
>        the domain publishing such a policy.
>
> I'd remove "and/or reporting".
>
>
This section is an attempt to discuss the need for one to have a policy of
"p=quarantine; pct=0" to get accurate reporting from Google in the past,
and was mentioned during the last interim -
https://datatracker.ietf.org/doc/minutes-interim-2021-dmarc-01-202105270900/

Please suggest alternate text.

-- 

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

--000000000000b99ff805c73dca4a
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 Fri, Jul 16, 2021 at 5:32 AM Alessandro Vesely &lt;<a href=3D"ma=
ilto:vesely@tana.it">vesely@tana.it</a>&gt; wrote:</span><br></div></div><d=
iv class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
On Tue 13/Jul/2021 20:09:45 +0200 Todd Herr wrote:<br>
&gt; On Tue, Jul 13, 2021 at 7:03 AM Douglas Foster wrote:<br>
&gt; <br>
&gt; <br>
&gt; draft-ietf-dmarc-dmarcbis-02 instead starts with this text:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0pct:=C2=A0 (plain-text integer between 0 and 100, i=
nclusive; OPTIONAL;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 default is 100).=C2=A0 For the RFC5322.From=
 domain to which the DMARC<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 record applies, the &quot;pct&quot; tag is =
the percentage of messages<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 producing a DMARC result of &quot;fail&quot=
; to which the Domain Owner<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 wishes its preferred handling policy be app=
lied.<br>
&gt; <br>
&gt; Since the concept of applying DMARC policy to messages that produce a =
DMARC<br>
&gt; result of &quot;pass&quot; doesn&#39;t exist, it doesn&#39;t make sens=
e to claim that &quot;pct&quot;<br>
&gt; applies to the entire mailstream.<br>
<br>
<br>
Why not?=C2=A0 I&#39;d say that a DMARC filter takes no action when dmarc=
=3Dpass (except <br>
for setting Authentication-Results: and feedback data).=C2=A0 The policy re=
quests <br>
noop on pass, and it is applied indeed.<br>
<br></blockquote><div><br></div><div class=3D"gmail_default" style=3D"font-=
family:tahoma,sans-serif">I will continue to maintain that it makes no sens=
e to talk about the concept of applying DMARC policy to messages which pass=
 DMARC validation checks, especially in the context of the &#39;pct&#39; ta=
g.=C2=A0</div><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">In RFC 7489, the definitions of &quot;quarantine&quot; and &quo=
t;reject&quot; both speak of their application in terms of &quot;email that=
 fails the DMARC mechanism check&quot;.</div></div><div class=3D"gmail_quot=
e"><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"=
>So, for a DMARC record such as this:</div><div class=3D"gmail_default" sty=
le=3D"font-family:tahoma,sans-serif"><br></div></div><blockquote style=3D"m=
argin:0 0 0 40px;border:none;padding:0px"><div class=3D"gmail_quote"><div c=
lass=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">_<a href=3D"=
http://dmarc.foo.com">dmarc.foo.com</a> IN TXT=C2=A0&quot;v=3DDMARC1; p=3Dq=
uarantine; pct=3DX; rua=3D....&quot;</div></div></blockquote><div class=3D"=
gmail_quote"><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-=
serif"><br></div><div class=3D"gmail_default" style=3D"font-family:tahoma,s=
ans-serif">I assert that the domain owner is requesting that X percent of t=
he messages that fail the DMARC mechanism check be subjected to the &quot;q=
uarantine&quot; policy.=C2=A0</div><div class=3D"gmail_default" style=3D"fo=
nt-family:tahoma,sans-serif"><br></div><div class=3D"gmail_default" style=
=3D"font-family:tahoma,sans-serif">To assert that the domain owner is inste=
ad asking only that DMARC validation checks be performed on X percent of th=
e messages runs the very real risk of the pct mechanism being even less use=
ful as a ratchet, especially when X is small, because that X% of the total =
mailstream might not contain any DMARC failures.</div><div class=3D"gmail_d=
efault" style=3D"font-family:tahoma,sans-serif"><br></div><div class=3D"gma=
il_default" style=3D"font-family:tahoma,sans-serif">It occurs to me now tha=
t something like the following is considered a valid DMARC record, and we s=
hould probably fix that:</div><div class=3D"gmail_default" style=3D"font-fa=
mily:tahoma,sans-serif"><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:tahoma,sans-serif"><blockquote style=3D"margin:0px 0px 0px 40px;bo=
rder:none;padding:0px"><div class=3D"gmail_quote"><div class=3D"gmail_defau=
lt">_<a href=3D"http://dmarc.foo.com">dmarc.foo.com</a> IN TXT=C2=A0&quot;v=
=3DDMARC1; p=3Dnone; pct=3D25; rua=3D....&quot;</div></div></blockquote><di=
v class=3D"gmail_quote"><div class=3D"gmail_default"></div></div></div><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">The fi=
x would be to describe the &#39;pct&#39; tag as only valid with p=3D quaran=
tine or reject, because &quot;p=3Dnone, pct=3DX&quot; is just a nonsensical=
 way of writing &quot;p=3Dnone; pct=3D100&quot;, because you&#39;re going t=
o get &quot;none&quot; on all failures regardless.</div><div class=3D"gmail=
_default" style=3D"font-family:tahoma,sans-serif"><br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
<br>
&gt; Next, draft-ietf-dmarc-dmarcbis-02 contains a substantial rewrite of t=
he<br>
&gt; Message Sampling section (now section 6.7.4) that goes to great length=
s to<br>
&gt; attempt to show that the desired pct value really can&#39;t be counted=
 on to be<br>
&gt; applied as asked for, and what might actually happen could vary widely=
 from<br>
&gt; what&#39;s desired.<br>
<br>
<br>
I find that section excessively long and difficult.=C2=A0 It doesn&#39;t me=
ntion the key <br>
point that the percentage is more and more exact as the number of (failed) =
<br>
messages grows.=C2=A0 Indeed, pct=3D20 doesn&#39;t say that the policy shou=
ld apply to one <br>
of /the first five/ messages.<br><br></blockquote><div><br></div><div class=
=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">Please suggest a=
lternate text.</div><div class=3D"gmail_default" style=3D"font-family:tahom=
a,sans-serif"></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">
<br>
<br>
The last paragraph of Section 6.7.4.2 seems to say that pct affects reporti=
ng:<br>
<br>
=C2=A0 =C2=A0 *=C2=A0 &quot;0&quot; - A request that zero percent of messag=
es producing a DMARC<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;fail&quot; result have the specified polic=
y applied.=C2=A0 While this is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0seemingly a non-sensical request, this value has=
 been given<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0special meaning by some mailbox providers when c=
ombined with<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0certain &quot;p=3D&quot; values to alter DMARC p=
rocessing and/or reporting for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0the domain publishing such a policy.<br>
<br>
I&#39;d remove &quot;and/or reporting&quot;.<br>
<br></blockquote><div><br></div><div class=3D"gmail_default" style=3D"font-=
family:tahoma,sans-serif">This section is an attempt to discuss the need fo=
r one to have a policy of &quot;p=3Dquarantine; pct=3D0&quot; to get accura=
te reporting from Google in the past, and was mentioned during the last int=
erim - <a href=3D"https://datatracker.ietf.org/doc/minutes-interim-2021-dma=
rc-01-202105270900/">https://datatracker.ietf.org/doc/minutes-interim-2021-=
dmarc-01-202105270900/</a></div><div class=3D"gmail_default" style=3D"font-=
family:tahoma,sans-serif"><br></div><div class=3D"gmail_default" style=3D"f=
ont-family:tahoma,sans-serif">Please suggest alternate text.</div></div><di=
v><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><s=
pan style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;f=
ont-family:Arial"> | Technical Director, Standards and Ecosystem</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>

--000000000000b99ff805c73dca4a--


From nobody Fri Jul 16 16:24:42 2021
Return-Path: <fenton@bluepopcorn.net>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8FD3A0A2C for <dmarc@ietfa.amsl.com>; Fri, 16 Jul 2021 16:24: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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O8__HLANWJLw for <dmarc@ietfa.amsl.com>; Fri, 16 Jul 2021 16:24:35 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE5CD3A0A2D for <dmarc@ietf.org>; Fri, 16 Jul 2021 16:24:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=WlU9mB4woAtMKqTIcaWh5Wu/Es/dZYVd2QD+Eh0FovY=; b=D66hoTaq8YB46+HmFvv5iM4WwJ YlWVdMS+vtuheI2seH718kUHVLF6fstt3ii8hixjV5It+MzDnTYQPO15yjyg6j871+2ezXOyXHpel AkDOxpzBbtKKgjb4sxnFg7Uau04wUrHDHiUJc/5qdjBSYb1/eakItTr7IqhYeXr3aHwc=;
Received: from [64.71.6.2] (helo=[10.100.11.204]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1m4XC2-0003fZ-A1; Fri, 16 Jul 2021 16:24:30 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Date: Fri, 16 Jul 2021 16:24:27 -0700
X-Mailer: MailMate (1.14r5819)
Message-ID: <1E1F7937-AFEC-4F5A-8A5A-229A99C94E8B@bluepopcorn.net>
In-Reply-To: <CAH48ZfyLvECR_nwLmw6R6RnE4EZa8g_i7MJaF32d2qk4RBCKRA@mail.gmail.com>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <d80b0a14-0f4d-8266-8d42-8d9a6b02413d@tana.it> <CAH48ZfyLvECR_nwLmw6R6RnE4EZa8g_i7MJaF32d2qk4RBCKRA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9MX8Z53j0gPUBdxbqJFuyQT0qVA>
Subject: Re: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jul 2021 23:24:41 -0000

On 15 Jul 2021, at 18:07, Douglas Foster wrote:

>> The aligned DKIM signature test can have three conclusions, not just t=
wo:
>>
>> =C2=B7         Fully Authenticated:    A signature is present, a DNS p=
ublic
>> key is available, and the key can be used to verify the signature.
>>
>> =C2=B7         Provided:  A signature is present, and a DNS public key=
 is
>> available, but the key cannot be used to validate the signature.
>>
>> =C2=B7         No Signature or No key:  A signature is not present or =
is
>> present but the DNS public key is not available.
>>
>> If the domain owner indicates that all messages originate with a
>> signature, then messages with =E2=80=9CNo Signature or No Key=E2=80=9D=
 are verifiably not
>> from the domain owner and can be confidently repudiated.

Why would =E2=80=9CProvided=E2=80=9D be handled any differently from =E2=80=
=9CNo signature or no key=E2=80=9D? An attacker can easily provide a sign=
ature for a message they are spoofing, and after observing some of that d=
omain=E2=80=99s traffic will know what selector name to use that has a pu=
blished public key.

DKIM is very explicit about its results: either the signature verifies or=
 it does not. There is no third case.

-Jim


From nobody Fri Jul 16 16:38:45 2021
Return-Path: <fenton@bluepopcorn.net>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DDC93A0B55; Fri, 16 Jul 2021 16:38:43 -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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6kKBcn0POTF; Fri, 16 Jul 2021 16:38:36 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A9043A0B67; Fri, 16 Jul 2021 16:38:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=+4u4KDs8AU5+nrnk5JhZat1E8W0lQ0rYaCJdQk1RxwE=; b=uD2c+re04Orh2jTfHZPPk7d4cd 1XtJ4rMk2j+NARUJelShm589G2xiP+82q53yajxjm/aluVyMCfu59sTbbkpAGErQ9W0FcWJkn7lh2 g+y3eDIo/5HkOTWsxEXcvXKAVJokCp2ecZ8ThTV9upBs5VBhuKUhfB2WhzX86gtaiXBI=;
Received: from [64.71.6.2] (helo=[10.100.11.204]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1m4XPe-0003ig-Ai; Fri, 16 Jul 2021 16:38:34 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>
Cc: IETF DMARC WG <dmarc@ietf.org>
Date: Fri, 16 Jul 2021 16:38:33 -0700
X-Mailer: MailMate (1.14r5819)
Message-ID: <4F0603A4-5C7F-4289-9CAB-D342C3FF7088@bluepopcorn.net>
In-Reply-To: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_7526C109-35FA-430F-9B25-9E670783F132_="
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/hzHU4wk-O5spO1gV37g44qIqXgw>
Subject: Re: [dmarc-ietf] Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 16 Jul 2021 23:38:44 -0000

--=_MailMate_7526C109-35FA-430F-9B25-9E670783F132_=
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 6 Jul 2021, at 5:45, Todd Herr wrote:

> Greetings.
>
> The theoretical goal of any domain owner that publishes a DMARC record 
> is
> to transition from an initial policy of p=none to a final one of 
> p=reject,
> because it is only at p=reject that DMARC's intended purpose of 
> preventing
> same-domain spoofing can be fully realized.

*Any* domain owner? That is not a goal of any of my domains.

A DMARC record should reflect the sending behavior of the domain it’s 
associated with. If the domain, for any number of reasons, does not have 
the ability to authenticate all of its outgoing mail in an aligned way, 
it should either publish p=none and leave it at that, or not publish a 
DMARC record at all (if it doesn’t want any reports).

-Jim

P.S. What I think you are describing here is what I consider the 
converse of a ratchet. A ratchet allows movement in one direction, not 
the other, and you seem to be talking about going from a p=reject policy 
back to something less strict if there is a problem.

--=_MailMate_7526C109-35FA-430F-9B25-9E670783F132_=
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 6 Jul 2021, at 5:45, Todd Herr wrote:</p>
</div><div style=3D"white-space:normal"><blockquote style=3D"border-left:=
2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"a=
uto">Greetings.</p>
<p dir=3D"auto">The theoretical goal of any domain owner that publishes a=
 DMARC record is
<br>
to transition from an initial policy of p=3Dnone to a final one of p=3Dre=
ject,
<br>
because it is only at p=3Dreject that DMARC's intended purpose of prevent=
ing
<br>
same-domain spoofing can be fully realized.</p>
</blockquote></div>
<div style=3D"white-space:normal">
<p dir=3D"auto"><em>Any</em> domain owner? That is not a goal of any of m=
y domains.</p>
<p dir=3D"auto">A DMARC record should reflect the sending behavior of the=
 domain it=E2=80=99s associated with. If the domain, for any number of re=
asons, does not have the ability to authenticate all of its outgoing mail=
 in an aligned way, it should either publish p=3Dnone and leave it at tha=
t, or not publish a DMARC record at all (if it doesn=E2=80=99t want any r=
eports).</p>
<p dir=3D"auto">-Jim</p>
<p dir=3D"auto">P.S. What I think you are describing here is what I consi=
der the converse of a ratchet. A ratchet allows movement in one direction=
, not the other, and you seem to be talking about going from a p=3Dreject=
 policy back to something less strict if there is a problem.</p>

</div></div>
</body>
</html>

--=_MailMate_7526C109-35FA-430F-9B25-9E670783F132_=--


From nobody Sat Jul 17 05:38:29 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 CD5CD3A0C5B for <dmarc@ietfa.amsl.com>; Sat, 17 Jul 2021 05:38: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=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 2eZGkbZaJTUk for <dmarc@ietfa.amsl.com>; Sat, 17 Jul 2021 05:38:24 -0700 (PDT)
Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F9313A0C5A for <dmarc@ietf.org>; Sat, 17 Jul 2021 05:38:23 -0700 (PDT)
Received: by mail-ot1-x329.google.com with SMTP id h24-20020a9d64180000b029036edcf8f9a6so12850972otl.3 for <dmarc@ietf.org>; Sat, 17 Jul 2021 05:38:23 -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=BFA+FJ8Zp95DT3NPcOKe2o7T1ZoMQ891Pr+VW3EgzJk=; b=hlCLxEYpF5M9lHwDWlwhPbRwmVpcQc0p75lvZxOsepkkncvShofGhPYB6XoOT9Vehf qAQ1WAa/yFnFBRtxwVNlzLKSV3BFzV5sZmp+Dw0oeskN6qHYP76nuIMWDWbaTgVoZ/74 4ieSt1XMdTn7f1RtAxrZV/hq8JNhnJm1ToaRVFvy1nIi/f/VcWazXQvh7xgQ7ZAolR+n y/6GMVQDUBkdIVMgm3u84bdIZNad3f4P1/o5u2gJTXJkoqcfqUXScgY+yqQXA7Ktdw9V ZKDqQrdnbOCY8pAQKWJfVXNLnMYIegUkP0+DhXmQF51881mHCPe7OdixeF5I3lzUrqcq aUYw==
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=BFA+FJ8Zp95DT3NPcOKe2o7T1ZoMQ891Pr+VW3EgzJk=; b=qWM87vdRa4kJhZoRSb0fvQjjli9dM/BaRAq5G3IPwfutXpMdsYgsD+pxOisNwl51Zn dZ2mqAlANkmC808V2opTCv8/P/pMskcIsox4HoAfxVOPM8QqGWj5VEeEbGRz7zey+lO4 gwfSqeX44/bljXq2oBMjdLx/Gv1wSseVXSl/P9wY1b1YN5gN3ptiaLbVVyvvhlcnMx3Z 4iv04rxyNe7zzusKGwAYDcG4JJkc9ALQ6k9UIb2PRmUf47JB0u2z/GetQOkQkJHr7JC4 Qm3VFD2OeMThthmZS0VHa4F0dye3ZPkr4EhzSNOvjwvucMHWOXOqP3eMak6SZym/Q7js r5gw==
X-Gm-Message-State: AOAM530xI9qEJJtZnhS3UhWr7BshqSqbnnYgcT3qnKVeS2ZeJfXMULps 485S7MnDEc/CFpyiqN6DON1VDofkowEGT1U3vyOnM7Ia
X-Google-Smtp-Source: ABdhPJx713O0l1eQDgt6F84ynhlRrbOsW5kxlaqQ8Hjwiufir9RWWy7n3D9Y17Lltaqyuo8Y2q5DAuP1C16li40m+WU=
X-Received: by 2002:a9d:6f84:: with SMTP id h4mr12324386otq.240.1626525502515;  Sat, 17 Jul 2021 05:38:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <d80b0a14-0f4d-8266-8d42-8d9a6b02413d@tana.it> <CAH48ZfyLvECR_nwLmw6R6RnE4EZa8g_i7MJaF32d2qk4RBCKRA@mail.gmail.com> <1E1F7937-AFEC-4F5A-8A5A-229A99C94E8B@bluepopcorn.net> <CAH48ZfyTm1PSANTUmnqOy3aeiW4JHGbTsQ-m9xtSW9zFaCUZQA@mail.gmail.com>
In-Reply-To: <CAH48ZfyTm1PSANTUmnqOy3aeiW4JHGbTsQ-m9xtSW9zFaCUZQA@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 17 Jul 2021 08:38:13 -0400
Message-ID: <CAH48ZfzEWaFPUG4Gfc2ckpyUEq-8L9kEZZv+LwqJcW88=0y6=w@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cbad8c05c750faa4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/P0vjCBSGNQssncdOxzpR5IO3eV0>
Subject: [dmarc-ietf] Fwd:  Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jul 2021 12:38:29 -0000

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

The goal is to partition all incoming messages into two mutually exclusive
groups:   Those messages which originated under domain owner control, and
those which originated under domain owner control, and those which
originated outside domain owner control.   This requires two things:

- First, that at origination, credentials are in place so that a first-hop
MTA can reliably perform this partitioning.   I have a much longer
analysis, but the short version is that this requires an aligned and
verified DKIM signature on all messages.   There is no partial
participation, which is why the percentage notion needs to be discarded.
 Of course, fully authenticated messages are always detectable.  However,
in the absence of DKIM on all messages, the partitioning is not possible
because both domain owner and non-owner messages will both fail to be
authenticated.

- Secondly, the message addresses and the associated DKIM credential must
be preserved until the message is received.   We know that this is not the
case because forwarding with changes will break the DKIM signature.   The
absence of verification does not reliably indicate the absence of domain
owner
control, it can result from a domain owner message which was modified or a
non-owner message which was received in transit for any reason.

Consequently, we need three categories:
1) Messages which can be reliably attributed to the domain owner because
authentication passess.
2) Messages which can be reliably attributed to non-owners because of a
repudiation rule.
3) Messages which are ambiguous because they neither meet an authentication
rule nor meet a repudiation rule.

When we acknowledge this three-category reality, we have solved the mailing
list problem.   Mailing list messages can never be in category one.   They
belong in category 2.  The current DMARCv1 specification forces them into
category 3.   The two-possibility worldview creates the problem.   The
three-possibility worldview solves the problem.

I suggest these repudiation rules:

Rule 1:  The domain owner asserts that all messages from this domain will
originate with a verifiable DKIM signature.   If a message does not have an
aligned DKIM signature, or does not have a DNS public key available for the
scope ID, then the message originated outside domain owner control,  As I
have said, this is a mandatory first step to any policy being applied to
non-authenticated mail.

Rule 2:  The domain owner asserts that all messages from this domain will
originate with an SPF policy, including messages from email service
providers.   Results of SPF NONE or SPF NXDOMAIN indicate messages that are
outside domain owner control.

Rule 3:  The domain owner asserts that all messages from this domain will
have RFC5322.FROM addresses that "exist".   Messages that do not have FROM
addresses which "exist" have originated outside domain owner control.  The
definition of "Exists" is still being debated, and I have expressed strong
feelings about the right definition.

Rule 4:  The domain owner asserts that all messages from the domain will
originate with an initial ARC Set.   Messages which do not have an ARC Set
from the domain have originated outside domain owner control.  I am
inclined to include broken-chain ARC sets in this rule, but John would be a
better person to clarify this question

Everything that is not authenticated or repudiated is in category 2.   I
understand that category 2 includes a large number of messages.   These
messages require more analysis because the DMARC result is indeterminate.
 In most cases, this means that the next step is to put the message through
the full suite of content filters.   If the message is not blocked based on
content filters, then it may be desirable to do an in-depth analysis of the
message. Full header analysis is complex, ambiguous, subject to spoofing,
and very much outside of the capabilities of this document.

Note:  I am being careful to use "outside domain owner control" because
some such messages are very much wanted and should not be blocked.   Even
though such cases exist, the partitioning effort is indeed useful, because
it can be used to block some unwanted messages.  So "p=3Dreject" fails on
multiple levels:   It presumes that the domain owner knows that credentials
will be preserved until reception, which is false, and it assumes that
non-credentials messages should always be blocked, which is also false.
 "Pct=3D50" fails because it presumes that partial participation is possibl=
e,
and it presumes that a message evaluator will be willing to use a random
number generator to decide message fates.

Doug Foster


Doug Foster


On Fri, Jul 16, 2021 at 7:24 PM Jim Fenton <fenton@bluepopcorn.net> wrote:

> On 15 Jul 2021, at 18:07, Douglas Foster wrote:
>
> >> The aligned DKIM signature test can have three conclusions, not just
> two:
> >>
> >> =C2=B7         Fully Authenticated:    A signature is present, a DNS p=
ublic
> >> key is available, and the key can be used to verify the signature.
> >>
> >> =C2=B7         Provided:  A signature is present, and a DNS public key=
 is
> >> available, but the key cannot be used to validate the signature.
> >>
> >> =C2=B7         No Signature or No key:  A signature is not present or =
is
> >> present but the DNS public key is not available.
> >>
> >> If the domain owner indicates that all messages originate with a
> >> signature, then messages with =E2=80=9CNo Signature or No Key=E2=80=9D=
 are verifiably
> not
> >> from the domain owner and can be confidently repudiated.
>
> Why would =E2=80=9CProvided=E2=80=9D be handled any differently from =E2=
=80=9CNo signature or no
> key=E2=80=9D? An attacker can easily provide a signature for a message th=
ey are
> spoofing, and after observing some of that domain=E2=80=99s traffic will =
know what
> selector name to use that has a published public key.
>
> DKIM is very explicit about its results: either the signature verifies or
> it does not. There is no third case.
>
> -Jim
>

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><br><div dir=3D"ltr">The goal i=
s to partition all incoming messages into two mutually exclusive groups:=C2=
=A0 =C2=A0Those messages=C2=A0which originated under domain owner control, =
and those which originated under domain owner control, and those which orig=
inated outside domain owner control.=C2=A0 =C2=A0This requires two things:<=
div><br></div><div>- First, that at origination, credentials are in place s=
o that a first-hop MTA can reliably perform=C2=A0this partitioning.=C2=A0 =
=C2=A0I have a much longer analysis, but the short version is that this req=
uires an aligned and verified DKIM signature on all messages.=C2=A0 =C2=A0T=
here is no partial participation,=C2=A0which is why the percentage notion n=
eeds=C2=A0to be discarded.=C2=A0 =C2=A0Of course, fully authenticated messa=
ges are always detectable.=C2=A0 However, in the absence of DKIM on all mes=
sages, the partitioning is not possible because both domain owner and non-o=
wner messages will both fail to be authenticated.</div><div><br></div><div>=
- Secondly, the message addresses and the associated DKIM credential must b=
e preserved until the message is received.=C2=A0 =C2=A0We know that this is=
 not the case because=C2=A0forwarding with changes will break the DKIM sign=
ature.=C2=A0 =C2=A0The absence of verification does not reliably indicate t=
he absence of domain owner=C2=A0</div><div>control, it can result from a do=
main owner message which was modified or a non-owner message which was rece=
ived in transit for any reason.</div><div><br></div><div>Consequently, we n=
eed three categories:</div><div>1) Messages which can be reliably attribute=
d to the domain owner because authentication passess.</div><div>2) Messages=
 which can be reliably attributed to non-owners because of a repudiation ru=
le.</div><div>3) Messages which are ambiguous because they neither meet an =
authentication rule nor meet a repudiation rule.</div><div><br></div><div>W=
hen we acknowledge this three-category reality, we have solved the mailing =
list problem.=C2=A0 =C2=A0Mailing list messages can never be in category on=
e.=C2=A0 =C2=A0They belong in category 2.=C2=A0 The current DMARCv1 specifi=
cation forces them into category 3.=C2=A0 =C2=A0The two-possibility worldvi=
ew creates the problem.=C2=A0 =C2=A0The three-possibility worldview solves =
the problem.</div><div><br></div><div>I suggest these repudiation rules:</d=
iv><div><br></div><div>Rule 1:=C2=A0 The domain owner asserts that all mess=
ages from this domain will originate with a verifiable DKIM signature.=C2=
=A0 =C2=A0If a message does not have an aligned DKIM signature, or does not=
 have a DNS public key available for the scope ID, then the message origina=
ted outside domain owner control,=C2=A0 As I have said, this is a mandatory=
 first step to any policy being applied to non-authenticated mail.</div><br=
><div>Rule 2:=C2=A0 The domain owner asserts that all messages from this=C2=
=A0domain will originate with an SPF policy,=C2=A0including messages from e=
mail service providers.=C2=A0 =C2=A0Results of SPF NONE or SPF NXDOMAIN ind=
icate messages that are outside=C2=A0domain owner control.</div><div><br></=
div><div>Rule 3:=C2=A0 The domain owner asserts that all messages from this=
 domain will have RFC5322.FROM addresses that &quot;exist&quot;.=C2=A0 =C2=
=A0Messages that do not have FROM addresses which &quot;exist&quot; have or=
iginated outside domain owner control.=C2=A0 The definition of &quot;Exists=
&quot; is still being debated, and I have expressed strong feelings about t=
he right definition.<br></div><div><br></div><div>Rule 4:=C2=A0 The domain =
owner asserts that all messages from the domain will originate with an init=
ial ARC Set.=C2=A0 =C2=A0Messages which do not have an ARC Set from the dom=
ain have originated outside domain owner control.=C2=A0 I am inclined to in=
clude broken-chain ARC sets in this rule, but John would be a better person=
 to clarify this question</div><div><br></div><div>Everything that is not a=
uthenticated or repudiated is in category 2.=C2=A0 =C2=A0I understand that =
category 2 includes a large number of messages.=C2=A0 =C2=A0These messages =
require more analysis because the DMARC result is indeterminate.=C2=A0 =C2=
=A0In most cases, this means that the next step is to put the message throu=
gh the full suite of content filters.=C2=A0 =C2=A0If the message is not blo=
cked based on content filters, then it may be desirable to do an in-depth a=
nalysis of the message. Full header analysis is complex, ambiguous, subject=
 to spoofing, and very much outside of the capabilities of this document.<b=
r></div><div><br></div><div><div>Note:=C2=A0 I am being careful to use &quo=
t;outside domain owner control&quot; because some such messages are very mu=
ch wanted and should not be blocked.=C2=A0 =C2=A0Even though such cases exi=
st, the partitioning=C2=A0effort is indeed useful,=C2=A0because it can be u=
sed to block some unwanted=C2=A0messages.=C2=A0 So &quot;p=3Dreject&quot; f=
ails on multiple levels:=C2=A0 =C2=A0It presumes that the domain owner know=
s that credentials will be preserved until reception, which is false, and i=
t assumes that non-credentials messages should always be blocked, which is =
also false.=C2=A0 =C2=A0&quot;Pct=3D50&quot; fails because it presumes that=
 partial participation is possible, and it presumes that a message evaluato=
r will be willing to use a random number generator to decide message fates.=
</div><div><br></div><div>Doug Foster</div><div><br></div><br></div><div>Do=
ug Foster</div><div>=C2=A0=C2=A0</div></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jul 16, 2021 at 7:24 PM Jim F=
enton &lt;<a href=3D"mailto:fenton@bluepopcorn.net" target=3D"_blank">fento=
n@bluepopcorn.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">On 15 Jul 2021, at 18:07, Douglas Foster wrote:<br>
<br>
&gt;&gt; The aligned DKIM signature test can have three conclusions, not ju=
st two:<br>
&gt;&gt;<br>
&gt;&gt; =C2=B7=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Fully Authenticated:=C2=A0=
 =C2=A0 A signature is present, a DNS public<br>
&gt;&gt; key is available, and the key can be used to verify the signature.=
<br>
&gt;&gt;<br>
&gt;&gt; =C2=B7=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Provided:=C2=A0 A signatur=
e is present, and a DNS public key is<br>
&gt;&gt; available, but the key cannot be used to validate the signature.<b=
r>
&gt;&gt;<br>
&gt;&gt; =C2=B7=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0No Signature or No key:=C2=
=A0 A signature is not present or is<br>
&gt;&gt; present but the DNS public key is not available.<br>
&gt;&gt;<br>
&gt;&gt; If the domain owner indicates that all messages originate with a<b=
r>
&gt;&gt; signature, then messages with =E2=80=9CNo Signature or No Key=E2=
=80=9D are verifiably not<br>
&gt;&gt; from the domain owner and can be confidently repudiated.<br>
<br>
Why would =E2=80=9CProvided=E2=80=9D be handled any differently from =E2=80=
=9CNo signature or no key=E2=80=9D? An attacker can easily provide a signat=
ure for a message they are spoofing, and after observing some of that domai=
n=E2=80=99s traffic will know what selector name to use that has a publishe=
d public key.<br>
<br>
DKIM is very explicit about its results: either the signature verifies or i=
t does not. There is no third case.<br>
<br>
-Jim<br>
</blockquote></div>
</div></div>

--000000000000cbad8c05c750faa4--


From nobody Sat Jul 17 06:09:32 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A9933A0DFA for <dmarc@ietfa.amsl.com>; Sat, 17 Jul 2021 06:09:30 -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 JCgTQW-qd_Hk for <dmarc@ietfa.amsl.com>; Sat, 17 Jul 2021 06:09:22 -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 AC9143A0DF8 for <dmarc@ietf.org>; Sat, 17 Jul 2021 06:09:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1626527358; bh=zujC1ij6kLWGS6fTWVYM0+DNFELgB8PYbtHws24MNfE=; l=11007; h=To:Cc:References:From:Date:In-Reply-To; b=AoXF/66QsCBY9ESf73K1HyfnsEVRgWOlj0Tl88h72HmChq37Gi9gDf4qQbf5KxsJl MJSKbFPWE7QvxRI/xTuWmydMoTjljmV36QxFbKkX24qnltvUQGKgh8VN/T3uQ+OG8B EbkmbuSHTUerdMWYy1P0bfsqzIiqFGgB/TCPMbzH9O28PHv4Luk2iJWWG2a8s
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 00000000005DC028.0000000060F2D67E.00002E75; Sat, 17 Jul 2021 15:09:18 +0200
To: Todd Herr <todd.herr@valimail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <f45a2fb6-c907-feb9-fedd-4573f9685c0c@tana.it> <CAHej_8=-jUnQAs9yqhnC5-kOvKBWXL4DjHcsu=at-RF0VYxCtQ@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <9dd46972-0767-a48c-d401-a14b0c2a3e33@tana.it>
Date: Sat, 17 Jul 2021 15:09:18 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8=-jUnQAs9yqhnC5-kOvKBWXL4DjHcsu=at-RF0VYxCtQ@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/BIPJq4eld2lgNzP1DKPY66X31OI>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 17 Jul 2021 13:09:30 -0000

On Fri 16/Jul/2021 15:44:35 +0200 Todd Herr wrote:
> On Fri, Jul 16, 2021 at 5:32 AM Alessandro Vesely wrote:
>> On Tue 13/Jul/2021 20:09:45 +0200 Todd Herr wrote:
>>> On Tue, Jul 13, 2021 at 7:03 AM Douglas Foster wrote:
>>>
>>>
>>> draft-ietf-dmarc-dmarcbis-02 instead starts with this text:
>>>
>>>     pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
>>>        default is 100).  For the RFC5322.From domain to which the DMARC
>>>        record applies, the "pct" tag is the percentage of messages
>>>        producing a DMARC result of "fail" to which the Domain Owner
>>>        wishes its preferred handling policy be applied.
>>>
>>> Since the concept of applying DMARC policy to messages that produce a
>>> DMARC result of "pass" doesn't exist, it doesn't make sense to claim
>>> that "pct" applies to the entire mailstream.>>
>> Why not?  I'd say that a DMARC filter takes no action when dmarc=pass 
>> (except for setting Authentication-Results: and feedback data).  The
>> policy requests noop on pass, and it is applied indeed.>
> I will continue to maintain that it makes no sense to talk about the
> concept of applying DMARC policy to messages which pass DMARC validation
> checks, especially in the context of the 'pct' tag.
> 
> In RFC 7489, the definitions of "quarantine" and "reject" both speak of
> their application in terms of "email that fails the DMARC mechanism check".
> 
> So, for a DMARC record such as this:
> 
> _dmarc.foo.com IN TXT "v=DMARC1; p=quarantine; pct=X; rua=...."
> 
> I assert that the domain owner is requesting that X percent of the messages
> that fail the DMARC mechanism check be subjected to the "quarantine"
> policy.


This is a minor issue.  I just observed it is not necessary to pinpoint on what set to take the percentage.  The case that results in the easier wording should be used.


> To assert that the domain owner is instead asking only that DMARC
> validation checks be performed on X percent of the messages runs the very
> real risk of the pct mechanism being even less useful as a ratchet,
> especially when X is small, because that X% of the total mailstream might
> not contain any DMARC failures.


I never meant that.  The DMARC check has to performed in all cases.


> It occurs to me now that something like the following is considered a valid 
> DMARC record, and we should probably fix that:> 
> _dmarc.foo.com IN TXT "v=DMARC1; p=none; pct=25; rua=...."
> 
> The fix would be to describe the 'pct' tag as only valid with p= quarantine 
> or reject, because "p=none, pct=X" is just a nonsensical way of writing 
> "p=none; pct=100", because you're going to get "none" on all failures 
> regardless.

I agree it's quite nonsensical, except you can have p=none; sp=reject; pct=X, which makes sense.  However, it isn't worth to spend a paragraph of specification to declare such records invalid.  It is totally obvious how to treat such cases —it's a noop, similar to the policy to be applied on dmarc=pass.

I found various instances of such records, which I paste at the bottom of this message.


>>> Next, draft-ietf-dmarc-dmarcbis-02 contains a substantial rewrite
>>> of the Message Sampling section (now section 6.7.4) that goes to
>>> great lengths to attempt to show that the desired pct value
>>> really can't be counted on to be applied as asked for, and what
>>> might actually happen could vary widely from what's desired.
>>
>> I find that section excessively long and difficult.  It doesn't
>> mention the key point that the percentage is more and more exact as
>> the number of (failed) messages grows.  Indeed, pct=20 doesn't say
>> that the policy should apply to one of /the first five/ messages.>
> Please suggest alternate text.


I will.  I appreciate your mathematical digression, but I don't think dmarcbis is the appropriate kind of media to publish such kind of articles.


>> The last paragraph of Section 6.7.4.2 seems to say that pct affects
>> reporting:
>>
>>     *  "0" - A request that zero percent of messages producing a DMARC
>>        "fail" result have the specified policy applied.  While this is
>>        seemingly a non-sensical request, this value has been given
>>        special meaning by some mailbox providers when combined with
>>        certain "p=" values to alter DMARC processing and/or reporting for
>>        the domain publishing such a policy.
>>
>> I'd remove "and/or reporting".
>
> This section is an attempt to discuss the need for one to have a policy of
> "p=quarantine; pct=0" to get accurate reporting from Google in the past,
> and was mentioned during the last interim -
> https://datatracker.ietf.org/doc/minutes-interim-2021-dmarc-01-202105270900/
> 
> Please suggest alternate text.


Hm... an attempt could be as follows:


    *  "0" - A request that zero percent of messages producing a DMARC
       "fail" result have the specified policy applied.  While this is
       seemingly a non-sensical request, this value has an effect on
       some mailing lists or groups who rewrite the From: header field
       only if the author domain publishes a strict policy.  So having
       p=quarantine; pct=0 changes how mail mediators behave without
       affecting the actual treatment by the final receivers.

Of course, processing is different and the resulting aggregate reports change as a consequence.  Currently there are some variations on how to operate From: munging.  There should be a section on that topic, so the above paragraph could refer to it.


Now for p=none; pct=;  many records are expired, some are still current, some make sense, some don't.


MariaDB [mail]> SELECT domain, dmarc_rec, FROM_UNIXTIME(last_recv) AS date FROM domain WHERE dmarc_rec RLIKE 'p=none' AND dmarc_rec RLIKE 'pct=' AND NOT dmarc_rec RLIKE 'p=[rq]' order by date desc;
+---------------------------+------------------------------------------------+---------------------+
| domain                    | dmarc_rec                                      | date                |
+---------------------------+------------------------------------------------+---------------------+
| bluehost.com              | adkim=r; aspf=r; p=none; pct=10                | 2021-07-17 00:38:18 |
| mailerlite.com            | adkim=r; aspf=r; p=none; pct=5                 | 2021-07-16 13:47:29 |
| reverbia.it               | adkim=r; aspf=r; p=none; pct=1                 | 2021-07-14 11:01:12 |
| kernel.org                | adkim=r; aspf=r; p=none; pct=1                 | 2021-07-13 21:24:30 |
| crif.com                  | adkim=r; aspf=r; p=none; pct=25; fo=s          | 2021-07-06 14:28:33 |
| endurance.com             | adkim=r; aspf=r; p=none; pct=10                | 2021-07-04 04:56:51 |
| domain.com                | adkim=r; aspf=r; p=none; pct=10                | 2021-06-29 17:47:32 |
| constantcontact.com       | adkim=r; aspf=r; p=none; pct=10                | 2021-06-11 18:22:30 |
| asmallorange.com          | adkim=r; aspf=r; p=none; pct=10                | 2021-06-05 11:07:19 |
| netfacil.net.br           | adkim=r; aspf=r; p=none; sp=none; pct=5        | 2021-05-29 12:58:25 |
| xss.de                    | adkim=r; aspf=r; p=none; pct=1                 | 2021-05-20 23:35:57 |
| nic.cz                    | adkim=s; aspf=r; p=none; sp=none; pct=5; fo=1  | 2021-05-17 14:28:01 |
| oyabasket.com             | adkim=r; aspf=r; p=none; sp=none; pct=90; fo=0 | 2021-02-25 04:45:41 |
| ac-orleans-tours.fr       | adkim=r; aspf=s; p=none; sp=none; pct=1; fo=0  | 2021-02-25 00:20:17 |
| forgerock.com             | adkim=r; aspf=r; p=none; sp=none; pct=0        | 2021-02-24 13:22:35 |
| nw.tutto-business.it      | adkim=r; aspf=r; p=none; sp=none; pct=5; fo=0  | 2021-02-14 10:39:05 |
| nw.esperienza-italia.it   | adkim=r; aspf=r; p=none; sp=none; pct=5; fo=0  | 2021-02-13 12:09:45 |
| ticino.com                | adkim=r; aspf=r; p=none; pct=90                | 2021-02-04 14:50:44 |
| DENIC.DE                  | adkim=r; aspf=r; p=none; sp=none; pct=0; fo=0  | 2021-01-26 09:58:41 |
| uclouvain.be              | adkim=s; aspf=s; p=none; sp=none; pct=50; fo=1 | 2021-01-05 10:42:00 |
| vshosting.cz              | adkim=r; aspf=r; p=none; pct=1                 | 2020-08-11 18:05:14 |
| nw.graziepromo.com        | adkim=r; aspf=r; p=none; sp=none; pct=5; fo=0  | 2020-08-04 09:09:04 |
| xyonet.com                | adkim=r; aspf=r; p=none; pct=5; fo=0:1:d:s     | 2020-07-30 22:57:33 |
| anandbus.net              | adkim=r; aspf=r; p=none; sp=none; pct=20; fo=0 | 2020-06-10 23:59:42 |
| windstream.com            | adkim=r; aspf=r; p=none; sp=none; pct=5; fo=1  | 2020-04-27 15:13:16 |
| ipage.com                 | adkim=r; aspf=r; p=none; pct=10                | 2020-03-30 11:16:28 |
| packlink.com              | adkim=r; aspf=r; p=none; pct=60                | 2020-03-27 16:02:53 |
| hostgator.com             | adkim=r; aspf=r; p=none; pct=10                | 2020-02-10 06:04:43 |
| pasteur-cayenne.fr        | adkim=r; aspf=r; p=none; sp=none; pct=5        | 2019-12-27 04:27:44 |
| nw.mailzop.com            | adkim=r; aspf=r; p=none; sp=none; pct=5; fo=0  | 2019-12-22 16:04:05 |
| mediacombb.net            | adkim=r; aspf=r; p=none; sp=none; pct=0; fo=1  | 2019-12-15 04:42:23 |
| nw.kisend.com             | adkim=r; aspf=r; p=none; sp=none; pct=5; fo=0  | 2019-11-26 18:14:11 |
| nw.mailrogue.com          | adkim=r; aspf=r; p=none; sp=none; pct=5; fo=0  | 2019-11-21 20:34:34 |
| nw.mailcri.com            | adkim=r; aspf=r; p=none; sp=none; pct=5; fo=0  | 2019-10-15 15:40:06 |
| nw.keesend.com            | adkim=r; aspf=r; p=none; sp=none; pct=5; fo=0  | 2019-10-13 15:57:08 |
| maersk.com                | adkim=r; aspf=r; p=none; pct=1; fo=1           | 2019-07-17 09:03:42 |
| qlc.in                    | adkim=r; aspf=r; p=none; pct=5                 | 2019-06-04 00:21:26 |
| iran.ir                   | adkim=r; aspf=r; p=none; pct=50; fo=1          | 2019-02-12 09:29:27 |
| 0086.info                 | adkim=r; aspf=r; p=none; pct=5; fo=1           | 2019-02-03 17:30:23 |
| olivet.edu                | adkim=r; aspf=r; p=none; pct=5; fo=1           | 2019-02-01 19:17:07 |
| news.packlink.it          | adkim=r; aspf=r; p=none; pct=60                | 2018-08-01 11:53:01 |
| ucdavis.edu               | adkim=r; aspf=r; p=none; sp=none; pct=5; fo=1  | 2018-04-29 04:19:01 |
| anchus.com.ar             | adkim=r; aspf=r; p=none; sp=none; pct=1        | 2018-04-10 19:19:24 |
| junkemailfilter.com       | adkim=r; aspf=r; p=none; sp=none; pct=0        | 2018-02-02 21:47:05 |
| bnl.gov                   | adkim=r; aspf=r; p=none; pct=10                | 2018-01-24 02:12:25 |
| aqa.org.uk                | adkim=r; aspf=r; p=none; sp=none; pct=10       | 2018-01-24 01:01:06 |
| explorartdigital.com      | adkim=r; aspf=r; p=none; sp=none; pct=1        | 2018-01-16 17:13:23 |
| mail1.datongcloud.com     | adkim=r; aspf=r; p=none; pct=50                | 2018-01-12 18:25:53 |
| hulusungaitengahkab.go.id | adkim=r; aspf=r; p=none; pct=20                | 2018-01-01 04:08:33 |
| demmarkita2.com           | adkim=r; aspf=r; p=none; pct=20                | 2017-10-18 13:56:23 |
| opentext.com              | adkim=r; aspf=r; p=none; sp=none; pct=10; fo=s | 2017-09-28 22:43:18 |
| eu.org                    | adkim=r; aspf=r; p=none; sp=none; pct=10       | 2017-07-25 19:42:09 |
| ramosmirkin.com           | adkim=r; aspf=r; p=none; sp=none; pct=1        | 2017-07-23 12:00:18 |
| macsales.com              | adkim=r; aspf=r; p=none; pct=0                 | 2017-06-22 19:46:57 |
| opayq.com                 | adkim=r; aspf=r; p=none; pct=0                 | 2017-06-09 12:44:37 |
| mchsi.com                 | adkim=r; aspf=r; p=none; sp=none; pct=0; fo=1  | 2017-01-01 18:58:58 |
| lqfconos.com              | adkim=r; aspf=r; p=none; sp=none; pct=1        | 2016-10-24 20:00:38 |
| unimelb.edu.au            | adkim=r; aspf=r; p=none; sp=none; pct=10       | 2016-02-28 02:36:47 |
| waltermoreno.com          | adkim=r; aspf=r; p=none; sp=none; pct=1        | 2015-05-02 22:09:08 |
+---------------------------+------------------------------------------------+---------------------+
59 rows in set (0.088 sec)



Best
Ale
-- 




























From nobody Sun Jul 18 03:00:15 2021
Return-Path: <johnl@taugh.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 486493A18EC for <dmarc@ietfa.amsl.com>; Sun, 18 Jul 2021 03:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0yVv4EClsqIn for <dmarc@ietfa.amsl.com>; Sun, 18 Jul 2021 03:00:09 -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 24B8F3A18EA for <dmarc@ietf.org>; Sun, 18 Jul 2021 03:00:08 -0700 (PDT)
Received: (qmail 68920 invoked by uid 100); 18 Jul 2021 10:00:06 -0000
Date: 18 Jul 2021 09:59:44 -0000
Message-ID: <20210718095944.68919.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/Gd3R5rxGYfqogT7DSfelpoEhWrQ>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Jul 18 06:00:05 2021
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Jul 2021 10:00:14 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
 14 ( 100%) | 212570 ( 100%) | Total
  6 (42.9%) | 125740 (59.2%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  2 (14.3%) |  39726 (18.7%) | Todd Herr <todd.herr@valimail.com>
  2 (14.3%) |  23587 (11.1%) | Alessandro Vesely <vesely@tana.it>
  2 (14.3%) |  11524 ( 5.4%) | Jim Fenton <fenton@bluepopcorn.net>
  1 ( 7.1%) |   6847 ( 3.2%) | Steven M Jones <smj@crash.com>
  1 ( 7.1%) |   5146 ( 2.4%) | John Levine <johnl@taugh.com>


From nobody Mon Jul 19 03:59:25 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 23D913A2F41 for <dmarc@ietfa.amsl.com>; Mon, 19 Jul 2021 03:59:24 -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 kbvWZF-I2nGZ for <dmarc@ietfa.amsl.com>; Mon, 19 Jul 2021 03:59:19 -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 C2DEE3A2F3A for <dmarc@ietf.org>; Mon, 19 Jul 2021 03:59:19 -0700 (PDT)
Received: by mail-oi1-x229.google.com with SMTP id c197so20194223oib.11 for <dmarc@ietf.org>; Mon, 19 Jul 2021 03:59:19 -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=LXl4IW0/BeIuCsVwGj4aRzNHXdR7G4HZDpj3yM6kyhs=; b=Crgdpu5fAFNMt6/kvS7KTzM3eog2KAaBciYyJX+qZE6tMg+YFrfoB9seYfOffer7fN jba51o629q62+3OEEb79TMU9Y5c6wb3z0SW50uo/DDypXv5Mpc66as2SBntQgFqDGlVb 0f6EOwaHztI9awePEV8E61RZB34vJnG3AI+V55zPUPepfy1RbOjup0UPcq6wOKmX8vfH dYpreUcqF5Y2Uh6IE2AAEWzw6B0du6vRhjwMY3EIiGhW9my7V+rBlGiNZQYqNKIE3VUz GsTzwRIz2/DSlEERlQqpBznh6P+2Ki2qabgUhnv5FtbCZUCeVBk22lPHfDDuVjhpJOZ1 3b4Q==
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=LXl4IW0/BeIuCsVwGj4aRzNHXdR7G4HZDpj3yM6kyhs=; b=JIFJlEQsBFRRv60yNbBApat7MHsdjOVBNqSWM/5kPhz698MEMPl2pT7j1DHnXlzAeT x1rjJvco6rRAAmFKwCgT01Sn0G8mretCRX1kLPiUbIhr24muM7YoXlCSSTpJOPCh8wTM GP4JroMxm5Dny+AREc1YcAqnPzYxqAeuE8RHa6STWSPK1e9JlPiksVpdu3tFkAAHG2lr SU0rZ4yhkSRlJ1vm3Z3OT0XoDrgWmm9eykA9gqJgGpg7xQT3YiBgJ1yzAjOEh0naUsjA M6jmOUk3GI4FgNNyKAlXejDB4tJeXkhR9foeHAQ9vzdXP1ZeRh17ve7PTzT6CCUZ0q7I sWiQ==
X-Gm-Message-State: AOAM532A53yytkTdMzOWLdl3L9R7HmZ2RMkbP9/UlX7I9oh6hLatKs2k T/93PYx6q+7Xth84bKHWoJV0zgHnNwyuX1WDSms=
X-Google-Smtp-Source: ABdhPJyIXD619+0KnywrIeFSjDdMonSHtsfqtX/xfS9v1s0U4iHK8qgJZjd0prPaF2Ge4bby3jqhXQ2DQzbFLMQXY/4=
X-Received: by 2002:a05:6808:1153:: with SMTP id u19mr21664648oiu.20.1626692357900;  Mon, 19 Jul 2021 03:59:17 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com>
In-Reply-To: <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Mon, 19 Jul 2021 06:59:07 -0400
Message-ID: <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000026cd0a05c777d4a8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ZUeM79gEgQqChuHek9u9jLn-yRc>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 19 Jul 2021 10:59:24 -0000

--00000000000026cd0a05c777d4a8
Content-Type: text/plain; charset="UTF-8"

Todd, the new language has addressed my concerns about PCT.

As a message evaluator, PCT is an unreasonable request.   If I follow the
requested approach, it pretty much guarantees that I will block wanted
messages and allow unwanted messages.    I don't want to explain to a
C-level executive that a message was mishandled because "the random number
generator told me to do it."

PCT is also a significant data collection effort.   That collection effort
may represent a significant processing load, since every
non-authenticated record requires looking back over all received messages
in a chosen time period.   Obviously, that algorithm can be tuned, but the
tuning process is costly in time, labor, and stability risk.

I suppose that the issue here is that domain owners are concerned about the
message recipients who never send RUA reports.   Once enforcement is turned
on, SMTP reject and non-delivery reports provide feedback from more sources
(any source that does not discard silently).   The domain owner is unlikely
to get non-delivery reports from spam sources, so any notification about
messages that are blocked for DMARC-related reasons will be indications of
legitimate messages that were handled contrary to domain owner
preferences.   I understand the concern, I just don't see it as compatible
with my own security needs.

A partial solution lies in my proposal for an intermediate enforcement
option.   This option should be called "relaxed" mode, for consistency with
other standards.     The domain owner chooses whether
- SPF policy record is required in DNS,
- DKIM public key is required in DNS,
- From "existence" indicator is required in DNS, or
a domain-owner ARC Set is required in the message.
These are independently selectable enforcements; and they provide a domain
owner the opportunity to get reject and NDR information on a limited scale,
based on the feature selected and the weak nature of the test.

Domain owners who want to tolerate mailing list messages will stay in
relaxed mode permanently, and it provides more security than P=NONE.
Domain owners that want to block mailing list messages would eventually
switch to "strict", which is the same as our current P=REJECT.

Doug Foster




On Tue, Jul 13, 2021 at 2:10 PM Todd Herr <todd.herr=
40valimail.com@dmarc.ietf.org> wrote:

> On Tue, Jul 13, 2021 at 7:03 AM Douglas Foster <
> dougfoster.emailstandards@gmail.com> wrote:
>
>> I understand that under the current specification, PCT has been useful
>> because P=NONE with PCT=100 produces different results than QUARANTINE with
>> PCT=0.   This is an anomaly that I would hope we can fix, but if not, we
>> need to specify that the only valid settings are PCT=0 or PCT=100.   The
>> specification should force numbers between 1 and 99 to be interpreted as
>> either 0 or 100.
>>
>> The current PCT specification is fatally flawed because the denominator
>> is undefined and unstable.  Suppose that a domain owner concludes that most
>> but not all of his traffic will produce DMARC PASS.   Should the percentage
>> be based on message volume or Source IP counts?    Either way, the volume
>> distribution received by any single evaluator will be different than the
>> volume distribution sent out.
>>
>> But the larger problem is that the evaluator is performing a conditional
>> probability, because the policy is only applied to messages that produce
>> DMARC FAIL.    If there is no impersonation, an unauthenticated message has
>> a 100% probability of being legitimate.    The denominator is determined by
>> the volume of impersonation messages, not by the volume of legitimate
>> messages.   The percentage offered by the sending domain owner is useless.
>>
>> Next, assume that an accurate probability can be determined, and that 80%
>> of unauthenticated messages are legitimate and 20% are impersonations.
>> Does it make sense to apply that probability rule to
>> message disposition?    It will produce these results:
>>
>> Legitimate and DMARC ignored, message accepted = 80%*80% = 64% of total
>>
>> Legitimate and DMARC enforced, message blocked = 80%*20% = 16% of total
>>
>> Impersonation and DMARC ignored, message accepted = 20%*80% = 16% of total
>>
>> Impersonation and DMARC enforced, message blocked = 20%*20% = 4% of total
>>
>> Therefore, the correct decision is applied only 68% of the time, and the
>> wrong decision is applied 32% of the time.   This is unsatisfactory for
>> protecting against ransomware, and also unsatisfactory for reliably
>> delivering wanted messages.
>>
>> The actual volume of impersonating messages will be determined by the
>> spammer, not by the domain owner, so the whole notion of choosing a
>> percentage is flawed.    The domain owner does not have the information
>> needed to provide a usable percentage.   The message evaluator can only
>> determine the percentage by carefully examining many messages and
>> categorizing the source.  Once the source is categorized, guessing is no
>> longer necessary and the percentage is irrelevant.
>>
>>
>>
> I believe you'll find that your ideas, or at least sentiments quite
> similar to them, are captured in draft-ietf-dmarc-dmarcbis-02
>
> First, draft-ietf-dmarc-dmarcbis-02 makes a small but substantial change
> to the definition of the pct tag from what's currently in RFC 7489. Where
> RFC 7489 reads:
>
>    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.
>
>
> draft-ietf-dmarc-dmarcbis-02 instead starts with this text:
>
>    pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
>
>       default is 100).  For the RFC5322.From domain to which the DMARC
>
>       record applies, the "pct" tag is the percentage of messages
>
>       producing a DMARC result of "fail" to which the Domain Owner
>       wishes its preferred handling policy be applied.
>
> Since the concept of applying DMARC policy to messages that produce a
> DMARC result of "pass" doesn't exist, it doesn't make sense to claim that
> "pct" applies to the entire mailstream.
>
> Next, draft-ietf-dmarc-dmarcbis-02 contains a substantial rewrite of the
> Message Sampling section (now section 6.7.4) that goes to great lengths to
> attempt to show that the desired pct value really can't be counted on to be
> applied as asked for, and what might actually happen could vary widely from
> what's desired.
>
> https://datatracker.ietf.org/doc/draft-ietf-dmarc-dmarcbis/
>
>
> --
>
> *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.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr">Todd, the new language has=C2=A0addressed my concerns abou=
t PCT.<div><br></div><div>As a message evaluator, PCT is an unreasonable re=
quest.=C2=A0 =C2=A0If I follow the requested approach, it pretty much guara=
ntees that I will block wanted messages and allow unwanted messages.=C2=A0 =
=C2=A0 I don&#39;t want to explain to a C-level executive that a message wa=
s mishandled because &quot;the random number generator told me to do it.&qu=
ot;</div><div><br></div><div>PCT=C2=A0is also a significant data collection=
 effort.=C2=A0 =C2=A0That collection effort may represent a significant pro=
cessing load,=C2=A0since every non-authenticated=C2=A0record requires looki=
ng back over all received messages in a chosen time period.=C2=A0 =C2=A0Obv=
iously, that algorithm can be tuned,=C2=A0but the tuning process is costly =
in=C2=A0time,=C2=A0labor, and stability risk.</div><div><br></div><div>I su=
ppose that the issue here is that domain owners are concerned about the mes=
sage recipients who never send RUA reports.=C2=A0 =C2=A0Once enforcement is=
 turned on, SMTP reject and non-delivery reports provide feedback from more=
 sources (any source that does not discard silently).=C2=A0 =C2=A0The domai=
n owner is unlikely to get non-delivery reports from spam sources,=C2=A0so =
any notification about messages that are blocked for DMARC-related reasons =
will be indications of=C2=A0 legitimate messages that=C2=A0were handled con=
trary to domain owner preferences.=C2=A0 =C2=A0I understand the concern, I =
just don&#39;t see it as compatible with my own security needs.</div><div><=
br></div><div>A partial solution lies in my proposal for an intermediate en=
forcement option.=C2=A0 =C2=A0This option should be called &quot;relaxed&qu=
ot; mode, for consistency with other standards.=C2=A0 =C2=A0 =C2=A0The doma=
in owner chooses whether=C2=A0</div><div>- SPF policy record is required in=
 DNS,=C2=A0</div><div>- DKIM public key is required in DNS,=C2=A0</div><div=
>- From &quot;existence&quot; indicator is required in DNS, or=C2=A0</div><=
div>a domain-owner ARC Set is required in the message.=C2=A0 =C2=A0=C2=A0</=
div><div>These are independently selectable enforcements; and they provide =
a domain owner the opportunity to get reject and NDR information on a limit=
ed scale, based on the feature selected and the weak nature of the test.=C2=
=A0 =C2=A0=C2=A0</div><div><br></div><div>Domain owners who want to tolerat=
e mailing list messages will stay in relaxed mode permanently, and it provi=
des more security than P=3DNONE.=C2=A0 Domain owners that want to block mai=
ling=C2=A0list messages would eventually switch to &quot;strict&quot;, whic=
h is the same as our current P=3DREJECT.</div><div><br></div><div>Doug Fost=
er</div><div><br></div><div><br></div><div>=C2=A0 =C2=A0</div></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 1=
3, 2021 at 2:10 PM Todd Herr &lt;todd.herr=3D<a href=3D"mailto:40valimail.c=
om@dmarc.ietf.org">40valimail.com@dmarc.ietf.org</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=
=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-seri=
f"><span style=3D"font-family:Arial,Helvetica,sans-serif">On Tue, Jul 13, 2=
021 at 7:03 AM Douglas Foster &lt;<a href=3D"mailto:dougfoster.emailstandar=
ds@gmail.com" target=3D"_blank">dougfoster.emailstandards@gmail.com</a>&gt;=
 wrote:</span><br></div></div><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><p class=
=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-size:11pt;=
font-family:Calibri,sans-serif">I understand that under the current specifi=
cation, PCT has
been useful because P=3DNONE with PCT=3D100 produces different results than=
 QUARANTINE with PCT=3D0.=C2=A0=C2=A0 This is an anomaly that I would
hope we can fix, but if not, we need to specify that the only valid setting=
s
are PCT=3D0 or PCT=3D100.=C2=A0=C2=A0 The specification
should force numbers between 1 and 99 to be interpreted as either 0 or 100.=
 </p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">The current PCT specification is fa=
tally flawed because the
denominator is undefined and unstable.=C2=A0
Suppose that a domain owner concludes that most but not all of his traffic
will produce DMARC PASS.=C2=A0=C2=A0 Should the
percentage be based on message volume or Source IP counts?=C2=A0=C2=A0=C2=
=A0 Either way, the volume distribution received
by any single evaluator will be different than the volume distribution sent
out.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">But the larger problem is that the =
evaluator is performing a
conditional probability, because the policy is only applied to messages tha=
t
produce DMARC FAIL.=C2=A0=C2=A0=C2=A0 If there is no
impersonation, an unauthenticated message has a 100% probability of being
legitimate.=C2=A0=C2=A0=C2=A0 The denominator is
determined by the volume of impersonation messages, not by the volume of
legitimate messages.=C2=A0=C2=A0 The percentage
offered by the sending domain owner is useless.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Next, assume that an accurate proba=
bility can be determined,
and that 80% of unauthenticated messages are legitimate and 20% are
impersonations.=C2=A0=C2=A0 Does it make sense to
apply that probability rule to message=C2=A0disposition?=C2=A0=C2=A0=C2=A0
It will produce these results:</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Legitimate and DMARC ignored, messa=
ge accepted =3D 80%*80% =3D
64% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Legitimate and DMARC enforced, mess=
age blocked =3D 80%*20% =3D
16% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Impersonation and DMARC ignored, me=
ssage accepted =3D 20%*80%
=3D 16% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Impersonation and DMARC enforced, m=
essage blocked =3D 20%*20%
=3D 4% of total</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">Therefore, the correct decision is =
applied only 68% of the
time, and the wrong decision is applied 32% of the time.=C2=A0 =C2=A0This
is unsatisfactory for protecting against ransomware, and also unsatisfactor=
y
for reliably delivering wanted messages.</p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">The actual volume of impersonating =
messages will be
determined by the spammer, not by the domain owner, so the whole notion of
choosing a percentage is flawed.=C2=A0=C2=A0=C2=A0 The
domain owner does not have the information needed to provide a usable
percentage.=C2=A0=C2=A0 The message evaluator can
only determine the percentage by carefully examining many messages and
categorizing the source.=C2=A0 Once the source
is categorized, guessing is no longer necessary and the percentage is
irrelevant.</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></div></blockquote><d=
iv><br></div><div class=3D"gmail_default"><font face=3D"tahoma, sans-serif"=
>I believe you&#39;ll find that your ideas, or at least sentiments quite si=
milar to them, are captured in draft-ietf-dmarc-dmarcbis-02</font></div><di=
v class=3D"gmail_default"><font face=3D"tahoma, sans-serif"><br></font></di=
v><div class=3D"gmail_default"><font face=3D"tahoma, sans-serif">First, dra=
ft-ietf-dmarc-dmarcbis-02 makes a small but substantial change to the defin=
ition of the pct tag from what&#39;s currently in RFC 7489. Where RFC 7489 =
reads:</font></div><div class=3D"gmail_default"><pre><font face=3D"tahoma, =
sans-serif">   pct:  (plain-text integer between 0 and 100, inclusive; OPTI=
ONAL;
      default is 100).  Percentage of messages from the Domain Owner&#39;s
      mail stream to which the DMARC policy is to be applied.</font></pre><=
/div></div><div><font face=3D"tahoma, sans-serif"><br></font></div><div><fo=
nt face=3D"tahoma, sans-serif">draft-ietf-dmarc-dmarcbis-02<span class=3D"g=
mail_default"> instead starts with this text:</span></font></div><div><font=
 face=3D"tahoma, sans-serif"><br></font></div>





<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><span style=
=3D"font-variant-ligatures:no-common-ligatures"><font face=3D"tahoma, sans-=
serif"><span>=C2=A0 =C2=A0</span>pct:<span>=C2=A0 </span>(plain-text intege=
r between 0 and 100, inclusive; OPTIONAL;</font></span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><span style=
=3D"font-variant-ligatures:no-common-ligatures"><font face=3D"tahoma, sans-=
serif"><span>=C2=A0 =C2=A0 =C2=A0 </span>default is 100).<span>=C2=A0 </spa=
n>For the RFC5322.From domain to which the DMARC</font></span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><span style=
=3D"font-variant-ligatures:no-common-ligatures"><font face=3D"tahoma, sans-=
serif"><span>=C2=A0 =C2=A0 =C2=A0 </span>record applies, the &quot;pct&quot=
; tag is the percentage of messages</font></span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;line-height:normal;color:rgb(0,0,0)"><span style=
=3D"font-variant-ligatures:no-common-ligatures"><font face=3D"tahoma, sans-=
serif"><span>=C2=A0 =C2=A0 =C2=A0 </span>producing a DMARC result of &quot;=
fail&quot; to which the Domain Owner</font></span></p>
<div><font face=3D"tahoma, sans-serif"><span style=3D"font-variant-ligature=
s:no-common-ligatures;color:rgb(0,0,0)">=C2=A0 =C2=A0 =C2=A0=C2=A0</span><s=
pan style=3D"font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0)">w=
ishes its preferred handling policy be applied.</span></font></div><div><fo=
nt face=3D"tahoma, sans-serif"><br></font></div><div><span class=3D"gmail_d=
efault"><font face=3D"tahoma, sans-serif">Since the concept of applying DMA=
RC policy to messages that produce a DMARC result of &quot;pass&quot; doesn=
&#39;t exist, it doesn&#39;t make sense to claim that &quot;pct&quot; appli=
es to the entire mailstream.</font></span></div><div><span class=3D"gmail_d=
efault"><font face=3D"tahoma, sans-serif"><br></font></span></div><div><fon=
t face=3D"tahoma, sans-serif"><span class=3D"gmail_default">Next,=C2=A0</sp=
an>draft-ietf-dmarc-dmarcbis-02<span class=3D"gmail_default"> contains a su=
bstantial rewrite of the Message Sampling section (now section 6.7.4) that =
goes to great lengths to attempt to show that the desired pct value really =
can&#39;t be counted on to be applied as asked for, and what might actually=
 happen could vary widely from what&#39;s desired.</span></font></div><div>=
<font face=3D"tahoma, sans-serif"><br></font></div><blockquote style=3D"mar=
gin:0px 0px 0px 40px;border:none;padding:0px"><div><font face=3D"tahoma, sa=
ns-serif"><a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dmarc-dmar=
cbis/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-dmarc-=
dmarcbis/</a></font><span style=3D"font-family:tahoma,sans-serif"></span></=
div></blockquote><div><br></div>-- <br><div dir=3D"ltr"><span><p dir=3D"ltr=
" style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div sty=
le=3D"text-align:left"><span style=3D"vertical-align:baseline;white-space:p=
re-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></span><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font-fam=
ily:Arial"> | Technical Director, Standards and Ecosystem</span></div><span=
 style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small;font=
-family:Arial"><div style=3D"text-align:left"><span style=3D"vertical-align=
:baseline"><b>e:</b></span><span style=3D"vertical-align:baseline"> <a href=
=3D"mailto: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.41=
53</span><span></span></div><div style=3D"text-align:left"><img style=3D"wi=
dth: 175px; height: 43px;" src=3D"https://hosted-packages.s3-us-west-1.amaz=
onaws.com/Valimail+Logo.png"></div></span><p dir=3D"ltr" style=3D"backgroun=
d-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 information intended solely for the use of =
individual(s) authorized to receive it. If you are not an intended and auth=
orized recipient you are hereby notified of any use, disclosure, copying or=
 distribution of the information included in this transmission is prohibite=
d 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></d=
iv></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>

--00000000000026cd0a05c777d4a8--


From nobody Tue Jul 20 07:51:12 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA5693A2585 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 07:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtai9ceDy1gC for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 07:51:05 -0700 (PDT)
Received: from mail-lf1-f43.google.com (mail-lf1-f43.google.com [209.85.167.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 639743A2582 for <dmarc@ietf.org>; Tue, 20 Jul 2021 07:51:05 -0700 (PDT)
Received: by mail-lf1-f43.google.com with SMTP id u13so36157251lfs.11 for <dmarc@ietf.org>; Tue, 20 Jul 2021 07:51:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=sQblGZoR2iuXPTmkh+NPf+GxJ5gyRL1xEkQOZLHPzVc=; b=UnGRSDJY0PQbldW2kqCVAhVvpmLW7zYYbIEVyvuSVqRuvPD1YWp53xjA76M5OTYdFJ WwLcakR2ZfJP8YBlxp8yaunYeQcLrnqrEy+4hXmoBaKCbYqSvvCx0EPQbJTs0KP2VanF KeUtm/n68umGNX8EOBAZi489JhoS6AS4cvqttFVYZSfKF67uXuI+GjSBxeaSAq8L3XL2 D5/CYoww6H9HR3AOyJ+V3YI6xL77UxAkFmJFNZt9vnDq/Kzk5sRjAFQqcHrblLEgiJSC lbchjSuOW3ayQ2bm8MZ2+tF7//LHHbA6V6XAXa9NslT63jkTP3A4zTwGEqrb8ekLX7q4 8j2w==
X-Gm-Message-State: AOAM5325OH3y+9uJywIqa5iAuNWx6ZCMg//7x+186Nre8gUpo8BROUJm z/YZS5nubGixomr+CXZK7/c9l6Wig37Uuu3sE7k=
X-Google-Smtp-Source: ABdhPJy3qmHWZb9BWCRdjxadRO6DRV+K1EBOicyE21jTwgHYu7bwBHNf28nVVISXaNo0NUqsTYyqdxjWHRnXmMreF4I=
X-Received: by 2002:a19:6d06:: with SMTP id i6mr23570708lfc.295.1626792658075;  Tue, 20 Jul 2021 07:50:58 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <d80b0a14-0f4d-8266-8d42-8d9a6b02413d@tana.it> <CAH48ZfyLvECR_nwLmw6R6RnE4EZa8g_i7MJaF32d2qk4RBCKRA@mail.gmail.com> <1E1F7937-AFEC-4F5A-8A5A-229A99C94E8B@bluepopcorn.net> <CAH48ZfyTm1PSANTUmnqOy3aeiW4JHGbTsQ-m9xtSW9zFaCUZQA@mail.gmail.com> <CAH48ZfzEWaFPUG4Gfc2ckpyUEq-8L9kEZZv+LwqJcW88=0y6=w@mail.gmail.com>
In-Reply-To: <CAH48ZfzEWaFPUG4Gfc2ckpyUEq-8L9kEZZv+LwqJcW88=0y6=w@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 20 Jul 2021 10:50:46 -0400
Message-ID: <CALaySJJ2ZFML2neecfgAhvfk_1EuMNGw6DwchLmmWWpbDJC+Zw@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/3agS8RI5XWhCL9yW4SNsQrWZlKY>
Subject: Re: [dmarc-ietf] Fwd: Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 14:51:11 -0000

Doug, I think the issue here is that I disagree with your premise, so
the rest of the argument fails for me:

> The goal is to partition all incoming messages into two mutually exclusiv=
e groups:   Those messages which
> originated under domain owner control, and those which originated under d=
omain owner control, and those
> which originated outside domain owner control.   This requires two things=
:

I don't agree with the characterization of the second group.  I would
say that we are partitioning messages into these two groups:
- Those for which we can confirm that they originated in the domain
they say they did.
- Those for which we can not confirm that.

Note that the second of those is subtly different to your
characterization, in that there's a difference between knowing that
they did not originate in the domain... and not knowing whether they
did or didn't.  It has never been a claim of either DKIM or SPF that
we can know anything in particular about a message when validation
fails: all either of them tells us is that validation has failed.

As Jim says, DKIM is very clear about that, when it tells us to treat
a validation failure the same as an absent signature.  Any proposal
that tries to treat a signature that fails to validate in any special
way is a non-starter, as it violates DKIM.

Barry

On Sat, Jul 17, 2021 at 8:38 AM Douglas Foster
<dougfoster.emailstandards@gmail.com> wrote:
>
>
> The goal is to partition all incoming messages into two mutually exclusiv=
e groups:   Those messages which originated under domain owner control, and=
 those which originated under domain owner control, and those which origina=
ted outside domain owner control.   This requires two things:
>
> - First, that at origination, credentials are in place so that a first-ho=
p MTA can reliably perform this partitioning.   I have a much longer analys=
is, but the short version is that this requires an aligned and verified DKI=
M signature on all messages.   There is no partial participation, which is =
why the percentage notion needs to be discarded.   Of course, fully authent=
icated messages are always detectable.  However, in the absence of DKIM on =
all messages, the partitioning is not possible because both domain owner an=
d non-owner messages will both fail to be authenticated.
>
> - Secondly, the message addresses and the associated DKIM credential must=
 be preserved until the message is received.   We know that this is not the=
 case because forwarding with changes will break the DKIM signature.   The =
absence of verification does not reliably indicate the absence of domain ow=
ner
> control, it can result from a domain owner message which was modified or =
a non-owner message which was received in transit for any reason.
>
> Consequently, we need three categories:
> 1) Messages which can be reliably attributed to the domain owner because =
authentication passess.
> 2) Messages which can be reliably attributed to non-owners because of a r=
epudiation rule.
> 3) Messages which are ambiguous because they neither meet an authenticati=
on rule nor meet a repudiation rule.
>
> When we acknowledge this three-category reality, we have solved the maili=
ng list problem.   Mailing list messages can never be in category one.   Th=
ey belong in category 2.  The current DMARCv1 specification forces them int=
o category 3.   The two-possibility worldview creates the problem.   The th=
ree-possibility worldview solves the problem.
>
> I suggest these repudiation rules:
>
> Rule 1:  The domain owner asserts that all messages from this domain will=
 originate with a verifiable DKIM signature.   If a message does not have a=
n aligned DKIM signature, or does not have a DNS public key available for t=
he scope ID, then the message originated outside domain owner control,  As =
I have said, this is a mandatory first step to any policy being applied to =
non-authenticated mail.
>
> Rule 2:  The domain owner asserts that all messages from this domain will=
 originate with an SPF policy, including messages from email service provid=
ers.   Results of SPF NONE or SPF NXDOMAIN indicate messages that are outsi=
de domain owner control.
>
> Rule 3:  The domain owner asserts that all messages from this domain will=
 have RFC5322.FROM addresses that "exist".   Messages that do not have FROM=
 addresses which "exist" have originated outside domain owner control.  The=
 definition of "Exists" is still being debated, and I have expressed strong=
 feelings about the right definition.
>
> Rule 4:  The domain owner asserts that all messages from the domain will =
originate with an initial ARC Set.   Messages which do not have an ARC Set =
from the domain have originated outside domain owner control.  I am incline=
d to include broken-chain ARC sets in this rule, but John would be a better=
 person to clarify this question
>
> Everything that is not authenticated or repudiated is in category 2.   I =
understand that category 2 includes a large number of messages.   These mes=
sages require more analysis because the DMARC result is indeterminate.   In=
 most cases, this means that the next step is to put the message through th=
e full suite of content filters.   If the message is not blocked based on c=
ontent filters, then it may be desirable to do an in-depth analysis of the =
message. Full header analysis is complex, ambiguous, subject to spoofing, a=
nd very much outside of the capabilities of this document.
>
> Note:  I am being careful to use "outside domain owner control" because s=
ome such messages are very much wanted and should not be blocked.   Even th=
ough such cases exist, the partitioning effort is indeed useful, because it=
 can be used to block some unwanted messages.  So "p=3Dreject" fails on mul=
tiple levels:   It presumes that the domain owner knows that credentials wi=
ll be preserved until reception, which is false, and it assumes that non-cr=
edentials messages should always be blocked, which is also false.   "Pct=3D=
50" fails because it presumes that partial participation is possible, and i=
t presumes that a message evaluator will be willing to use a random number =
generator to decide message fates.
>
> Doug Foster
>
>
> Doug Foster
>
>
> On Fri, Jul 16, 2021 at 7:24 PM Jim Fenton <fenton@bluepopcorn.net> wrote=
:
>>
>> On 15 Jul 2021, at 18:07, Douglas Foster wrote:
>>
>> >> The aligned DKIM signature test can have three conclusions, not just =
two:
>> >>
>> >> =C2=B7         Fully Authenticated:    A signature is present, a DNS =
public
>> >> key is available, and the key can be used to verify the signature.
>> >>
>> >> =C2=B7         Provided:  A signature is present, and a DNS public ke=
y is
>> >> available, but the key cannot be used to validate the signature.
>> >>
>> >> =C2=B7         No Signature or No key:  A signature is not present or=
 is
>> >> present but the DNS public key is not available.
>> >>
>> >> If the domain owner indicates that all messages originate with a
>> >> signature, then messages with =E2=80=9CNo Signature or No Key=E2=80=
=9D are verifiably not
>> >> from the domain owner and can be confidently repudiated.
>>
>> Why would =E2=80=9CProvided=E2=80=9D be handled any differently from =E2=
=80=9CNo signature or no key=E2=80=9D? An attacker can easily provide a sig=
nature for a message they are spoofing, and after observing some of that do=
main=E2=80=99s traffic will know what selector name to use that has a publi=
shed public key.
>>
>> DKIM is very explicit about its results: either the signature verifies o=
r it does not. There is no third case.
>>
>> -Jim
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


From nobody Tue Jul 20 07:54:37 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0E813A259F for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 07:54:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id grK4YrMb-YKz for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 07:54:30 -0700 (PDT)
Received: from mail-lj1-f173.google.com (mail-lj1-f173.google.com [209.85.208.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6924C3A25A3 for <dmarc@ietf.org>; Tue, 20 Jul 2021 07:54:30 -0700 (PDT)
Received: by mail-lj1-f173.google.com with SMTP id t20so15659214ljd.2 for <dmarc@ietf.org>; Tue, 20 Jul 2021 07:54:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=hgCvt/nzWSXP4Deo1VcniCVJs7IacBEkL0iRUwjAf/8=; b=pxL5fajlkFiclE9vjjHdCYnfd6abX/fRR9CZ9N7BW48f6VtZsffvKLv0x9DsUVLryf 4SXoStbwHDZdxFY9HkxbxTyj5QiC4nKfH8shzV0e1eVg6zqhJ31qfi1DcYLFny302R3R FLKnFfT2PI8MXRawTtuiojf4pCKn7cU6AccTY8cuXxsau4/cr11GJvXtEWk1y7WEhiDz Ouc2mgGcKV9XEqI0yJcQTMoRZx0uKSeSfnJnXTeoWdIXH0fSs981CTHMlr/SW6QNNHeY KTQEbBW4+JNk4XuqZlvSPPmjW5fL1e+vx5fNHqvCy61x5yWUqp9SukLcKkp7S4kvOqNt xOGQ==
X-Gm-Message-State: AOAM530vCKKhOY8hosK/F+txefd/LziltHxYL6Rh0hRrTiCnYOOP5t60 lP+uOFGLcAmLmSLI61iVUA/iZUlbAzUQAkpbdTw=
X-Google-Smtp-Source: ABdhPJwGRe1SP9oRH70CSMujfk9Vy8sFGP+xE4Wfzp8Pl/wSMW9vKsT/PbWqIRKa2ZORzFoxjW8G5ChUYFJY98tNDi8=
X-Received: by 2002:a2e:9a09:: with SMTP id o9mr27274720lji.473.1626792867999;  Tue, 20 Jul 2021 07:54:27 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com>
In-Reply-To: <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 20 Jul 2021 10:54:16 -0400
Message-ID: <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/LnCwkhttpMFTwci0k1YBa9Zl86Y>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 14:54:36 -0000

Indeed: I see PCT as a feature that was put in early, in order to
allow us to experiment with things and ease into DMARC.  As we move to
a Proposed Standard version, I don't see a continuing need for such a
phase-in feature, and aggregate reporting covers the desire to reduce
reporting volume.  I would like to see us deprecate PCT entirely, and
remove the complexity and the misunderstandings that cause confusion
and unexpected results, at best, and that can cause interoperability
issues, at worst.

Barry

On Mon, Jul 19, 2021 at 6:59 AM Douglas Foster
<dougfoster.emailstandards@gmail.com> wrote:
>
> Todd, the new language has addressed my concerns about PCT.
>
> As a message evaluator, PCT is an unreasonable request.   If I follow the=
 requested approach, it pretty much guarantees that I will block wanted mes=
sages and allow unwanted messages.    I don't want to explain to a C-level =
executive that a message was mishandled because "the random number generato=
r told me to do it."
>
> PCT is also a significant data collection effort.   That collection effor=
t may represent a significant processing load, since every non-authenticate=
d record requires looking back over all received messages in a chosen time =
period.   Obviously, that algorithm can be tuned, but the tuning process is=
 costly in time, labor, and stability risk.
>
> I suppose that the issue here is that domain owners are concerned about t=
he message recipients who never send RUA reports.   Once enforcement is tur=
ned on, SMTP reject and non-delivery reports provide feedback from more sou=
rces (any source that does not discard silently).   The domain owner is unl=
ikely to get non-delivery reports from spam sources, so any notification ab=
out messages that are blocked for DMARC-related reasons will be indications=
 of  legitimate messages that were handled contrary to domain owner prefere=
nces.   I understand the concern, I just don't see it as compatible with my=
 own security needs.
>
> A partial solution lies in my proposal for an intermediate enforcement op=
tion.   This option should be called "relaxed" mode, for consistency with o=
ther standards.     The domain owner chooses whether
> - SPF policy record is required in DNS,
> - DKIM public key is required in DNS,
> - From "existence" indicator is required in DNS, or
> a domain-owner ARC Set is required in the message.
> These are independently selectable enforcements; and they provide a domai=
n owner the opportunity to get reject and NDR information on a limited scal=
e, based on the feature selected and the weak nature of the test.
>
> Domain owners who want to tolerate mailing list messages will stay in rel=
axed mode permanently, and it provides more security than P=3DNONE.  Domain=
 owners that want to block mailing list messages would eventually switch to=
 "strict", which is the same as our current P=3DREJECT.
>
> Doug Foster
>
>
>
>
> On Tue, Jul 13, 2021 at 2:10 PM Todd Herr <todd.herr=3D40valimail.com@dma=
rc.ietf.org> wrote:
>>
>> On Tue, Jul 13, 2021 at 7:03 AM Douglas Foster <dougfoster.emailstandard=
s@gmail.com> wrote:
>>>
>>> I understand that under the current specification, PCT has been useful =
because P=3DNONE with PCT=3D100 produces different results than QUARANTINE =
with PCT=3D0.   This is an anomaly that I would hope we can fix, but if not=
, we need to specify that the only valid settings are PCT=3D0 or PCT=3D100.=
   The specification should force numbers between 1 and 99 to be interprete=
d as either 0 or 100.
>>>
>>> The current PCT specification is fatally flawed because the denominator=
 is undefined and unstable.  Suppose that a domain owner concludes that mos=
t but not all of his traffic will produce DMARC PASS.   Should the percenta=
ge be based on message volume or Source IP counts?    Either way, the volum=
e distribution received by any single evaluator will be different than the =
volume distribution sent out.
>>>
>>> But the larger problem is that the evaluator is performing a conditiona=
l probability, because the policy is only applied to messages that produce =
DMARC FAIL.    If there is no impersonation, an unauthenticated message has=
 a 100% probability of being legitimate.    The denominator is determined b=
y the volume of impersonation messages, not by the volume of legitimate mes=
sages.   The percentage offered by the sending domain owner is useless.
>>>
>>> Next, assume that an accurate probability can be determined, and that 8=
0% of unauthenticated messages are legitimate and 20% are impersonations.  =
 Does it make sense to apply that probability rule to message disposition? =
   It will produce these results:
>>>
>>> Legitimate and DMARC ignored, message accepted =3D 80%*80% =3D 64% of t=
otal
>>>
>>> Legitimate and DMARC enforced, message blocked =3D 80%*20% =3D 16% of t=
otal
>>>
>>> Impersonation and DMARC ignored, message accepted =3D 20%*80% =3D 16% o=
f total
>>>
>>> Impersonation and DMARC enforced, message blocked =3D 20%*20% =3D 4% of=
 total
>>>
>>> Therefore, the correct decision is applied only 68% of the time, and th=
e wrong decision is applied 32% of the time.   This is unsatisfactory for p=
rotecting against ransomware, and also unsatisfactory for reliably deliveri=
ng wanted messages.
>>>
>>> The actual volume of impersonating messages will be determined by the s=
pammer, not by the domain owner, so the whole notion of choosing a percenta=
ge is flawed.    The domain owner does not have the information needed to p=
rovide a usable percentage.   The message evaluator can only determine the =
percentage by carefully examining many messages and categorizing the source=
.  Once the source is categorized, guessing is no longer necessary and the =
percentage is irrelevant.
>>>
>>>
>>
>> I believe you'll find that your ideas, or at least sentiments quite simi=
lar to them, are captured in draft-ietf-dmarc-dmarcbis-02
>>
>> First, draft-ietf-dmarc-dmarcbis-02 makes a small but substantial change=
 to the definition of the pct tag from what's currently in RFC 7489. Where =
RFC 7489 reads:
>>
>>    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.
>>
>>
>> draft-ietf-dmarc-dmarcbis-02 instead starts with this text:
>>
>>    pct:  (plain-text integer between 0 and 100, inclusive; OPTIONAL;
>>
>>       default is 100).  For the RFC5322.From domain to which the DMARC
>>
>>       record applies, the "pct" tag is the percentage of messages
>>
>>       producing a DMARC result of "fail" to which the Domain Owner
>>
>>       wishes its preferred handling policy be applied.
>>
>> Since the concept of applying DMARC policy to messages that produce a DM=
ARC result of "pass" doesn't exist, it doesn't make sense to claim that "pc=
t" applies to the entire mailstream.
>>
>> Next, draft-ietf-dmarc-dmarcbis-02 contains a substantial rewrite of the=
 Message Sampling section (now section 6.7.4) that goes to great lengths to=
 attempt to show that the desired pct value really can't be counted on to b=
e applied as asked for, and what might actually happen could vary widely fr=
om what's desired.
>>
>> https://datatracker.ietf.org/doc/draft-ietf-dmarc-dmarcbis/
>>
>>
>> --
>>
>> 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) autho=
rized to receive it. If you are not an intended and authorized recipient yo=
u are hereby notified of any use, disclosure, copying or distribution of th=
e information included in this transmission is prohibited and may be unlawf=
ul. Please immediately notify the sender by replying to this email and then=
 delete it from your system.
>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


From nobody Tue Jul 20 09:39:05 2021
Return-Path: <dcrocker@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A80E93A2A5C for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 09:39:03 -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 O3hbaV8puIbG for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 09:38:59 -0700 (PDT)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B11F3A2A58 for <dmarc@ietf.org>; Tue, 20 Jul 2021 09:38:59 -0700 (PDT)
Received: by mail-pf1-x432.google.com with SMTP id d12so20064779pfj.2 for <dmarc@ietf.org>; Tue, 20 Jul 2021 09:38:59 -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=gj64H0VzVuf4vuhMg1ZI5ZF84rcNmrwQTw+3Yn+a8YA=; b=OVKUdG9Ca/fBrnn2mFk7jGHUQFnV50vgkZVi80gYuxQnYzZgTQ7+FPptLF+yc95DKw W2Xi2VuR+mQHsS2Wv/4hvM1cOormFo4ApCB+uDKIFI8pNRvS4Ux/R9xlKj+xaN6Xgpn9 COAo3yGFbD0noWRTAQS6kcQQvfUKMg9BYUE8bm9pLh59u6fiMFDFwpaabn/JJ/436og0 ApuISdtVFclPnOxW9pTlVMn06n1wBQzZMpv7VtVAe0eyx7HWgghamQJYShbh9Nq7klkY mTEDCQhFxTb2+ouL4hvq3FvDTy5PaXBtF7Na0UtvqLMAPVut2I3A48vNZnGom64opCo6 2jUg==
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=gj64H0VzVuf4vuhMg1ZI5ZF84rcNmrwQTw+3Yn+a8YA=; b=Qc+1vXt81DXr5waKdAJeVH6aLsY4Q1A2rL2KYAb72AOeciEQgqVGwBhPW6jSIZZMX6 TSK6JEqIKV+tEAyMYVG9AKyOgDWit0iwOpwUgZ/caQDiOyVrEgXWdV49mICNZD3+dHlp tG5X+XW3m7ftJR/WUzC36pMUUeUqXj6N4w5cnOkjfziiHqcskgYIZMQirj52CiD7hcsa pKKdwFIN3AeL9Pnf2b8qwHbJsX97hS2PJm6COKY1eNnFv3RQRcLIG042OR67NPp83CjA DnCxuCywuXTRn665ivFsd6/Qls8jU3lA25xA8X0fi91zS9ky6Gcv/BZ3VatNNRhuifm8 8WDQ==
X-Gm-Message-State: AOAM532VoCt245xsWLKaTeOcdIoT30HzsuWV8KlE5Dif6AUDypGpAQqA l/Wkt/YIZjjXdXQb2Z+Ng8X9aRUHwXk=
X-Google-Smtp-Source: ABdhPJx17QIpH199PzLAxSRAnNOusPgFMjM0IP8tjI6XQpY2wNtEHI3uMJtKd58IFKdPFD7cDDG3RA==
X-Received: by 2002:a65:4386:: with SMTP id m6mr31223223pgp.430.1626799137475;  Tue, 20 Jul 2021 09:38:57 -0700 (PDT)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id h5sm23661447pfv.145.2021.07.20.09.38.56 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Jul 2021 09:38:56 -0700 (PDT)
To: IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <d80b0a14-0f4d-8266-8d42-8d9a6b02413d@tana.it> <CAH48ZfyLvECR_nwLmw6R6RnE4EZa8g_i7MJaF32d2qk4RBCKRA@mail.gmail.com> <1E1F7937-AFEC-4F5A-8A5A-229A99C94E8B@bluepopcorn.net> <CAH48ZfyTm1PSANTUmnqOy3aeiW4JHGbTsQ-m9xtSW9zFaCUZQA@mail.gmail.com> <CAH48ZfzEWaFPUG4Gfc2ckpyUEq-8L9kEZZv+LwqJcW88=0y6=w@mail.gmail.com> <CALaySJJ2ZFML2neecfgAhvfk_1EuMNGw6DwchLmmWWpbDJC+Zw@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <993a1ce5-50c6-3168-ffd6-98119a5cef27@gmail.com>
Date: Tue, 20 Jul 2021 09:38:56 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJ2ZFML2neecfgAhvfk_1EuMNGw6DwchLmmWWpbDJC+Zw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/jrOjPd3_dRHdNsk7pGvMzhlGWjY>
Subject: Re: [dmarc-ietf] Fwd: Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 16:39:04 -0000

On 7/20/2021 7:50 AM, Barry Leiba wrote:
> I don't agree with the characterization of the second group.  I would
> say that we are partitioning messages into these two groups:
> - Those for which we can confirm that they originated in the domain
> they say they did.
> - Those for which we can not confirm that.
>
> Note that the second of those is subtly different to your

Not sure it's that subtle, but am sure the difference is profoundly 
important.

A constant misunderstanding of efforts in this realm of effort is a 
belief that perfection is attainable.  It isn't.  Therefore any 
characterization needs to use language of approximations, estimations, 
heuristics and trade-offs.


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 Tue Jul 20 09:39:48 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 991673A2A61 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 09: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, 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 F-n10toRejb9 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 09:39:41 -0700 (PDT)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8D6F3A2A5E for <dmarc@ietf.org>; Tue, 20 Jul 2021 09:39:40 -0700 (PDT)
Received: by mail-pf1-x432.google.com with SMTP id i14so8020505pfd.5 for <dmarc@ietf.org>; Tue, 20 Jul 2021 09:39:40 -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=2CzREkdinWtnruRyF43VXnP5fr2L9ImsloC/v+HN+5k=; b=rM4VcKqFwBdkYIkFHIWBsSwERQTDPz2K3oTBQDSj28JJL47hFfxGXeoLmJAvJhgBy2 8kjoE5WtcfJg757tQOfvozxO9PhhdlZdUu7uw2yY+qhE4eQHf5/++oRz7jr4GDgfPsbA 72WZfPnvWcB1ecgUJ4afSkyder6xW7i+3+ZXfJMn+7XvuHgPyvBpNv+NAGs1NaJ68MrB e8IZx5UZd2idu07Lhb78GUz0HBhPSto/jAukqR8sCB3uGd+eQiiG2kxYaVPSSbHy6fDJ XWX6706IqHSMbOcYDAo/k1iA7uPk0kf7gDgLtZw/03w0X9NXXAwMJlQP8IdSDq2TLccx P7iQ==
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=2CzREkdinWtnruRyF43VXnP5fr2L9ImsloC/v+HN+5k=; b=Oga9ldePkgMDSfq/Wx6xij47eVlpRtRHCBtFpDMS1x+jnm5KgP/V3oWa/QVT8Hk3Hb 4Oy+YaWmH+oSadtxSzZlOWI/7ODEjcQD6ikaj4wCB4nw9TGHBgi0fwqPxcK6mTHucqPV /5p/XV3keXVTJOxlXlcukdH5r6h6P6mvDCIvCgOfkAOoXerqOT7oe+9cjwTq9C5O0twE L029qfdgIEArXAd5GVzonqNoa1xmagKc5OoKybeYEpuB6fyn/7iq5g3QIgovQlNBtdy5 Vd8IfmNxts/Gu3zBPmFI3dj6gejBC+MljX0L16MoPIjzi3fmyN7xXYGtBPRcocRGIXO7 7T4g==
X-Gm-Message-State: AOAM532CR6b3R7hhJyRAub0I0tEoqi3sebBHyvq9srn6iWL9U+eqxCpY eV5AqofxEi2G72qD2GzzaEpNXXy/3lw=
X-Google-Smtp-Source: ABdhPJxCi2tye8QEfmsLzwIAgwXAMgC+xBiV3zFFQjYAsSMWRc0Srtb8ff5a3DK/W+0+baD3jNNLBQ==
X-Received: by 2002:a63:593:: with SMTP id 141mr3632870pgf.133.1626799179784;  Tue, 20 Jul 2021 09:39:39 -0700 (PDT)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id ev20sm20279579pjb.43.2021.07.20.09.39.39 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Jul 2021 09:39:39 -0700 (PDT)
To: IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com>
Date: Tue, 20 Jul 2021 09:39:39 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@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/vkdUKDU4f8EDArcEDRYLPgXghdw>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 16:39:47 -0000

On 7/20/2021 7:54 AM, Barry Leiba wrote:
> I would like to see us deprecate PCT entirely,

+1

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 Tue Jul 20 10:17:11 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 E13713A2B73 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 10:17:09 -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_BLOCKED=0.001, 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 XBoobRBGRzw8 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 10:17:04 -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 B98B93A2B76 for <dmarc@ietf.org>; Tue, 20 Jul 2021 10:17:04 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id z25so36879qto.12 for <dmarc@ietf.org>; Tue, 20 Jul 2021 10:17:04 -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=A7jLkqLEuoX+EJG+XhyOMyMbT7NFkv6fzgybIeuNkeo=; b=JThIkO6LoFIu/+zhqxKgZqYiIbRBFtijBd/r49Nqk1zsZXld7sd2bVdb8pJ8ICFlzy ScrZ+TJSLCHFMTvajrDRYE6f/IeSKkXNwDQ6iUjT0UbbW4+F1ARzBohWvKT8DcxYL6rB YKM+xw6/jJUy4qUFcqO8BpTyzLwZ5jhvWpeHp3fqWiBRYWnaBD83p7NDymIzrevcZyJ8 Lxtpl5+lIEGu8usTILhCekTo9eOS8ePLofdPqc4UVnq+WsuzWukb5mFv/cgojM1N2Bnq HZWo5/60cMzYalFeXd0CxqRCE88eZZA+mbplhdLa7PfDVaH59tzBcXqWiopjvhlob2vO eJjw==
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=A7jLkqLEuoX+EJG+XhyOMyMbT7NFkv6fzgybIeuNkeo=; b=k/kQ3hNWXArWDA8pEGLHFaNw1TA+3+0GwLhfDl5huWJS9WiJeLnqKOREla1vHjyO+J zOCDmaPLguamWOVjLptjloHT4tYyWlQmQtsPyUZYdhOytFdZ7ULj4Zup7yBGXg+7dksg /p/leeOz0BMXTbgpePLkt2qN3oxmqwuAtmnH/TiIWl1vy3PvaSIpckGw9q6b7qk10mNp p5q+9/OLK/vNJ3D+RpgU71xARXLWAiF26/A1kLxtq8rjp8PdjAfBwqYzAilKn4ET82+y 6TO1RlC3efEdyglzD+90vME7TfJOu0oQ5oz1lyrTZus3t5rf0GNN2SlG9LM8sWRIcsSV FhLQ==
X-Gm-Message-State: AOAM533Q9BWwzk53qFeyKW48KrL/eMOHaBA4IMC2ZXqQ6nCvnohaLZSP qL61NMB5KW545+BxdInhd5FxRyjbk5C8MDXT76M=
X-Google-Smtp-Source: ABdhPJx4QsaII/VmxxlExiDz0wVp8NGYGq92Zf7DhGSaErTuHEC7goz6oDQs/KpMn2yGdIHMEC2gJtJXJflSQD+WFFc=
X-Received: by 2002:ac8:7f85:: with SMTP id z5mr27223286qtj.354.1626801422844;  Tue, 20 Jul 2021 10:17:02 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com>
In-Reply-To: <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com>
From: Dotzero <dotzero@gmail.com>
Date: Tue, 20 Jul 2021 13:16:52 -0400
Message-ID: <CAJ4XoYf0mE_1kY06J5Tuw3G5JySndqRPyu96uJjdWEWXgE0S+g@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000edc68b05c7913868"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ZI2OHHBNHwdE_tv8mFWT2OPfz2k>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 17:17:10 -0000

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

On Tue, Jul 20, 2021 at 12:39 PM Dave Crocker <dcrocker@gmail.com> wrote:

> On 7/20/2021 7:54 AM, Barry Leiba wrote:
> > I would like to see us deprecate PCT entirely,
>
> +1
>
> d/
>
> --
> Dave Crocker
> dcrocker@gmail.com
> 408.329.0791
>

+1

Michael Hammer

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 20, 2021 at 12:39 PM Dave=
 Crocker &lt;<a href=3D"mailto:dcrocker@gmail.com">dcrocker@gmail.com</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 7/2=
0/2021 7:54 AM, Barry Leiba wrote:<br>
&gt; I would like to see us deprecate PCT entirely,<br>
<br>
+1<br>
<br>
d/<br>
<br>
-- <br>
Dave Crocker<br>
<a href=3D"mailto:dcrocker@gmail.com" target=3D"_blank">dcrocker@gmail.com<=
/a><br>
408.329.0791<br></blockquote><div><br></div><div>+1</div><div><br></div><di=
v>Michael Hammer <br></div></div></div>

--000000000000edc68b05c7913868--


From nobody Tue Jul 20 11:52:31 2021
Return-Path: <me@junc.eu>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9359F3A2E29 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 11:52: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, 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=junc.eu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PhNWvM5bgp6A for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 11:52:23 -0700 (PDT)
Received: from mx.junc.eu (mx.junc.eu [172.105.72.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 687273A2E28 for <dmarc@ietf.org>; Tue, 20 Jul 2021 11:52:22 -0700 (PDT)
Received: from localhost.junc.eu (localhost.junc.eu [127.0.0.1]) by mx.junc.eu (Postfix) with SMTP id 6C77D80DD7 for <dmarc@ietf.org>; Tue, 20 Jul 2021 18:52:19 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junc.eu; i=@junc.eu; l=495; q=dns/txt; s=default; t=1626807139; h=from : subject : date : to; bh=wyB5slRVhlLFgBnlVh2iyHsDNoXBMWR0WfkvsnxB3hY=; b=YrNXsq6Hmg9D5If3ckCLqS6WaUCimYZjCPTHoZaNKGJjHH8VzMerl9CSEl21vxAYaFCki y8NBYObYav4VPkYQUxOOz59MLWPfAgJpg1xR+3EO0P4RII8bFhkvAsK7VaHmPijnR4jjrcU Go2e4iuTwnzUHaK+W6jwEXJRfN7Dxx3K8A9T7Pw8467vv5xXQprNbRwR0Ivwt3SznqUJYa1 gUsgMaOa5ZdTPVDlot9x2tSqb4dVXzO4BaN9jssIEkY7+Nf0YWXuC3zwsT0TXqc+UzhtTdL 8dSMqjOK+cBNZyYq/pNOSXFwFMgMCBBqoEOG6ZrHj3nfrHaaxL/qzXUCUfgA==
Received: from localhost.junc.eu (localhost.junc.eu [IPv6:::1]) by mx.junc.eu (Postfix) with ESMTPSA id 4C92180A94 for <dmarc@ietf.org>; Tue, 20 Jul 2021 18:52:19 +0000 (UTC)
MIME-Version: 1.0
Date: Tue, 20 Jul 2021 20:52:19 +0200
From: Benny Pedersen <me@junc.eu>
To: dmarc@ietf.org
In-Reply-To: <CAJ4XoYf0mE_1kY06J5Tuw3G5JySndqRPyu96uJjdWEWXgE0S+g@mail.gmail.com>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <CAJ4XoYf0mE_1kY06J5Tuw3G5JySndqRPyu96uJjdWEWXgE0S+g@mail.gmail.com>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <52d3b7d214499c20a490baa4c43a998d@junc.eu>
X-Sender: me@junc.eu
Organization: junc.eu
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/oSp-BVmmm3MoBC91HaFliCBAL_I>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 18:52:30 -0000

On 2021-07-20 19:16, Dotzero wrote:
> On Tue, Jul 20, 2021 at 12:39 PM Dave Crocker <dcrocker@gmail.com> 
> wrote:
>> On 7/20/2021 7:54 AM, Barry Leiba wrote:
>>> I would like to see us deprecate PCT entirely,
>> +1
> +1

if this was postfix it would not be accepted, old habist must stay to be 
backward compatible, sadly not all understand why

with all that changes it could end with no one uses this good software 
writed after c code i provided :(

hope for there LTS of it all


From nobody Tue Jul 20 13:13:28 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3CFD3A308A for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 13:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.638
X-Spam-Level: 
X-Spam-Status: No, score=-1.638 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvuw3urOG0HR for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 13:13:20 -0700 (PDT)
Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 928943A3086 for <dmarc@ietf.org>; Tue, 20 Jul 2021 13:13:20 -0700 (PDT)
Received: by mail-lj1-f182.google.com with SMTP id h4so18457ljo.6 for <dmarc@ietf.org>; Tue, 20 Jul 2021 13:13:20 -0700 (PDT)
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=lVei4KoS9tNAE9hi80XeLaw8Y0ntDMo+P3s3nrGFjMA=; b=lPz9BP8I1zFz+oWqiheGzuyBE0qJ3fq3KW/bHNPHLavkkHAsvfl/pT/XltAD3r+Jzl dNk+heVOUlCORQsepbsK6GcDUIHSNrHudjDmWfBACpit21112sNdrqpdqQzmMyjgRZTh C8FdvmddfZEIgCgMYC4mR8y9pf43/iAJmULssq0uHdfmEfWI1NIRatWRdU6OVpiSwZ8r LFfFOfV/0wnZSHiqzDlhZfVFDcoKUl7ylxiK0Db2sx1x6teeodYcwkUkU6nURWfSzr2p eY/utVYorb1KFDZh31QmeKGUdFimiUlH+6DY+M36OD6HqYgNwzT/JItatI9vGz2NfZBN tnMQ==
X-Gm-Message-State: AOAM531zZyeXyCcafK3jmtqIA0VUs+xtBfXJFdALL9VPZyCXCiOuxWOH N0dKxqIF4CHbANyn74dbtXXTYimsEdn1/03CwVo=
X-Google-Smtp-Source: ABdhPJyCA13iXuFvcNehKfql+0Sij6QLv+s7rBZrhFmPP/VwYKG4zxIEqiWRT/1EDL07kUWf1logQFtdFFO5HhY8Dnk=
X-Received: by 2002:a2e:8956:: with SMTP id b22mr22756245ljk.248.1626811998415;  Tue, 20 Jul 2021 13:13:18 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <CAJ4XoYf0mE_1kY06J5Tuw3G5JySndqRPyu96uJjdWEWXgE0S+g@mail.gmail.com> <52d3b7d214499c20a490baa4c43a998d@junc.eu>
In-Reply-To: <52d3b7d214499c20a490baa4c43a998d@junc.eu>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 20 Jul 2021 16:13:06 -0400
Message-ID: <CALaySJJJ-Nsi_hg=g1T6AdtAXEfnW-mHavLfb=5ppxbgRtVkVg@mail.gmail.com>
To: Benny Pedersen <me@junc.eu>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/LzUx94VPny868j4w924liT8Y2FI>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 20:13:26 -0000

One of the points of "deprecation" is that we don't eliminate it
entirely, but say that it's no longer used.  New implementations no
longer generate it, but implementations that are interested in
backward compatibility will still include support for it on receipt.

Eventually, when we see that its use is rare enough, the community
might move to no longer include support (no longer needing backward
compatibility).  But I expect that support on receipt would remain for
some time.

Barry

On Tue, Jul 20, 2021 at 2:52 PM Benny Pedersen <me@junc.eu> wrote:
>
> On 2021-07-20 19:16, Dotzero wrote:
> > On Tue, Jul 20, 2021 at 12:39 PM Dave Crocker <dcrocker@gmail.com>
> > wrote:
> >> On 7/20/2021 7:54 AM, Barry Leiba wrote:
> >>> I would like to see us deprecate PCT entirely,
> >> +1
> > +1
>
> if this was postfix it would not be accepted, old habist must stay to be
> backward compatible, sadly not all understand why
>
> with all that changes it could end with no one uses this good software
> writed after c code i provided :(
>
> hope for there LTS of it all
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


From nobody Tue Jul 20 14:04:38 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 1CAC13A3215 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 14:04:37 -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 nCrfl7G0-pME for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 14:04:32 -0700 (PDT)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 932353A3210 for <dmarc@ietf.org>; Tue, 20 Jul 2021 14:04:32 -0700 (PDT)
Received: by mail-qt1-x831.google.com with SMTP id q15so574408qtp.0 for <dmarc@ietf.org>; Tue, 20 Jul 2021 14:04:32 -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=WGDeUTFJDNR3UeyEzLbnqZ9+9HcZm+OV37akXMnQCC8=; b=Oznl/7Jc9qvZ+xd2GhoWriJFSAfvxPi45drAUWprJWArHLcFjWv+64/xiZXWppCo1H kKdFCvCQMJk5U5cvG+rm0GgIPbeco52i4dI61Gmjr2n8/74NQceHt2Pwd3biL/7pUcSA 3C4h8NjTAXdbuLmv/kyfJ57XTjvCpmIDeFUnSOwk06jYvtM6snxXX0bJIZ56TyoNx/7z c4YoMZhofHaEbC454o0E6YYaQMi7Q3Zw7xrgyosfomdA6s/TpnxdmrXkXKxPO4VQ+yfl YnngtU5qZKp/Z12vfke/jnF30496EkNmWiLh4N9ncrnV4aL+anicOHc/W/FuJaX12mDk ZMdA==
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=WGDeUTFJDNR3UeyEzLbnqZ9+9HcZm+OV37akXMnQCC8=; b=oInL9JuBPBM+4dVeuPhV+u7IASnrkv9t8611whLt4XoMJEH8flxS18vNumZF8BONKK LqouPiBvGVXVK7NIuAb23l+JP97FFFKC6oUw50FZW7qrEOWU7qQCgkFBjP9HT04bYE/0 7QbCewv2AdDKJ1hNOgnpPDLfgcYR/xpNx9db+ggOEX8X1nf7YO8nz/3RNZnbooltxrMr zmFrtKlYrFFc8+IEpWzaZ3lt+iXu5+XiMc5rkEedPoOU750dmt0Y/dTsUsZtJjLcSzlc RX+j5nfM6bLKqR981UO3k3MAsDHuLYJZxdgUI+LI2VPkbhib4q1W3aAVsX8y0+npJG+b gSyg==
X-Gm-Message-State: AOAM530UQW1r+QxmHok1/zCi5yZL7iTaHSUz58x9N9RVUEBRGhQwxmYC QmtQKPkqHkPZ4EdyOaUT75GR8ELXn5CmtA2zxoc=
X-Google-Smtp-Source: ABdhPJz3DHV6cIhsBIdnaTI3fuwgU1EyL5egeDinGGMNJqiDOhEE/PIqfwEaFlYzCGiXJDVFA2JGF2jUl5YPGf6N79E=
X-Received: by 2002:ac8:7f85:: with SMTP id z5mr28049715qtj.354.1626815070918;  Tue, 20 Jul 2021 14:04:30 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <CAJ4XoYf0mE_1kY06J5Tuw3G5JySndqRPyu96uJjdWEWXgE0S+g@mail.gmail.com> <52d3b7d214499c20a490baa4c43a998d@junc.eu> <CALaySJJJ-Nsi_hg=g1T6AdtAXEfnW-mHavLfb=5ppxbgRtVkVg@mail.gmail.com>
In-Reply-To: <CALaySJJJ-Nsi_hg=g1T6AdtAXEfnW-mHavLfb=5ppxbgRtVkVg@mail.gmail.com>
From: Dotzero <dotzero@gmail.com>
Date: Tue, 20 Jul 2021 17:04:20 -0400
Message-ID: <CAJ4XoYfMqMFd28axH_RiNHUHQB20yDKaYAEKK8PCerOP6WQ_SA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Benny Pedersen <me@junc.eu>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006addea05c7946607"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rRiIFfmo1WuFlc0BgNNKYQkaH5w>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 21:04:37 -0000

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

On Tue, Jul 20, 2021 at 4:13 PM Barry Leiba <barryleiba@computer.org> wrote:

> One of the points of "deprecation" is that we don't eliminate it
> entirely, but say that it's no longer used.  New implementations no
> longer generate it, but implementations that are interested in
> backward compatibility will still include support for it on receipt.
>
> Eventually, when we see that its use is rare enough, the community
> might move to no longer include support (no longer needing backward
> compatibility).  But I expect that support on receipt would remain for
> some time.
>
> Barry
>

As soon as we say deprecated, the justifications for backwards
compatibility become tenuous. If a sender has no reasonable expectation
that most validators will respect their request, why would they make such a
request (other than in ignorance). I think very few would argue that using
percent is a long term strategy for any given domain. Either percent is
useful or it is not.

Michael Hammer

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 20, 2021 at 4:13 PM Barry=
 Leiba &lt;<a href=3D"mailto:barryleiba@computer.org">barryleiba@computer.o=
rg</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=
">One of the points of &quot;deprecation&quot; is that we don&#39;t elimina=
te it<br>
entirely, but say that it&#39;s no longer used.=C2=A0 New implementations n=
o<br>
longer generate it, but implementations that are interested in<br>
backward compatibility will still include support for it on receipt.<br>
<br>
Eventually, when we see that its use is rare enough, the community<br>
might move to no longer include support (no longer needing backward<br>
compatibility).=C2=A0 But I expect that support on receipt would remain for=
<br>
some time.<br>
<br>
Barry<br></blockquote><div><br></div><div>As soon as we say deprecated, the=
 justifications for backwards compatibility become tenuous. If a sender has=
 no reasonable expectation that most validators will respect their request,=
 why would they make such a request (other than in ignorance). I think very=
 few would argue that using percent is a long term strategy for any given d=
omain. Either percent is useful or it is not.</div><div><br></div><div>Mich=
ael Hammer<br></div></div></div>

--0000000000006addea05c7946607--


From nobody Tue Jul 20 14:09:53 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 7384E3A3239 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 14:09:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=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.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.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=l8DOhRtZ; dkim=pass (2048-bit key) header.d=taugh.com header.b=hWnropXB
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p72bbRVarrSj for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 14:09:46 -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 A587A3A323F for <dmarc@ietf.org>; Tue, 20 Jul 2021 14:09:46 -0700 (PDT)
Received: (qmail 7668 invoked from network); 20 Jul 2021 21:09:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1df2.60f73b99.k2107; bh=g34db/7MWmKz1Cf6Jee2LGxSbi/DyxKQ0u8AwMXwkcM=; b=l8DOhRtZzRMvX0JzKVtrza7XR1+9rYOYsLIIwyfTC//TL1b3JehEyhwy0h/fge4nRaqF6BQa5jNTNzN1FZqE43iV8YjLmtJb0UslJkx0DSUhDSswVR8gFPEVkY3ofbCQaLCpYo8VSOyvIT8rtqiohWDFL3Lhr0TgWGuRnF4QEGTIdDfx0ABQcNiY5enbvAdRANjOYbaUNFFzw3wpjkjaJTaairDAYZaDEhV/uaYG63WK3DCUsHW/cemIJqwj1FEKX0izAF3rvANgqRV/Wbt+YMJ4JRbDGlVnXOYzWoUG6IoExI+vsnemW3isEm1CV1HHwSJzH6ML2mvc89ZgLRcO5w==
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=1df2.60f73b99.k2107; bh=g34db/7MWmKz1Cf6Jee2LGxSbi/DyxKQ0u8AwMXwkcM=; b=hWnropXBDEdQXMxWKnJ+MH2Ns5uX70Sb+ByH0W1Ky7LU6h4nUMTZqlhhHFflmu5bR86F6g58NM+XMCPWEOwu9hYTxMv9CaA7hNQejQmwMWzc/cgwQ4pyC0vII3A/fWv8U34o67YC7/JTPH2UYMxiD+YBbo7NcN3iVohF9erAsTpHW7tcgNni7JD2WHr+p1X6eFIfymywFFQhAlgHuDrfizuRIA1pySktyToQl2+1JXreRuHSHC594p88G3dt2tNY02nblZ1HmYAXB+Xi/GqDAc9anCmUBUj/KemOROsgwhpbQfbJunhdvUJKP49TKBp0OuzNynVTf8bzHJNoYze0yQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 20 Jul 2021 21:09:45 -0000
Received: by ary.qy (Postfix, from userid 501) id 7F04024C687D; Tue, 20 Jul 2021 17:09:43 -0400 (EDT)
Date: 20 Jul 2021 17:09:43 -0400
Message-Id: <20210720210944.7F04024C687D@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dotzero@gmail.com
In-Reply-To: <CAJ4XoYfMqMFd28axH_RiNHUHQB20yDKaYAEKK8PCerOP6WQ_SA@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/_sezrmYNVuLk_oue-LnVKkVzJmM>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 21:09:53 -0000

It appears that Dotzero  <dotzero@gmail.com> said:
>As soon as we say deprecated, the justifications for backwards
>compatibility become tenuous. If a sender has no reasonable expectation
>that most validators will respect their request, why would they make such a
>request (other than in ignorance). I think very few would argue that using
>percent is a long term strategy for any given domain. Either percent is
>useful or it is not.

Considering how little it's used, I think we have decided that it's not.

Has anyone ever used it the way originally anticipated, set it to 10% on Monday,
look for trouble, 20% on Tuesday, look for more trouble, ... ?

R's,
John


From nobody Tue Jul 20 14:10:40 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F65B3A3245 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 14:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KkopNDbTeMce for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 14:10:38 -0700 (PDT)
Received: from mail-lj1-f169.google.com (mail-lj1-f169.google.com [209.85.208.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22FE73A3016 for <dmarc@ietf.org>; Tue, 20 Jul 2021 14:10:37 -0700 (PDT)
Received: by mail-lj1-f169.google.com with SMTP id c23so186262ljr.8 for <dmarc@ietf.org>; Tue, 20 Jul 2021 14:10:37 -0700 (PDT)
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=xNQTRsKhemLTMLHo/IqNEa91TQGNmrK/vdlcFC9WHFA=; b=D+8SrBkAo6rPnZ3l3OVzSv74tlu4l32P9x10R0e0Qf1GXDtWUc0aXHMZfPV5/IWgoc m8WZhZuDRPqtjdSM5YYai4iP7j3zWBMwGyl9jh2geoWtd8xSUlzNx+nmHm5x77N5NWxU W3VmGvr+VLvETrtt1s9SCZ54RzUvLnL/0feY91nfG3wG/DdHBn4mcEPBOngOno/jkzmH 6AcLsjs46lSdjPtOWiUaSkTdJAXepEgrBMLjNkY614zLAvFRbbJjzhNXsQ7qqluPYkmN aLQhkJ56jsJzSODPPvwshdpWw+it3a1cdF530Q+djpPdM1GwcRBuEZ6ZXzLB7bredd74 wmig==
X-Gm-Message-State: AOAM532C0ZM1Vre/nn/7avJsm+YV7V6HmH27TY2R+pE9MJPzHpjhtcH5 2yjIs5tHXe4Osp2p3o4NQTJIJ1tvYevHJj3VJN8=
X-Google-Smtp-Source: ABdhPJxIpHff7dhLYo8D5bXJaa+bqF0pA6h0ulwDJfNiP1CORkfkKpdzg/kmIcU/GeOTH+0d72TJzm12X7B2ISNU5cc=
X-Received: by 2002:a2e:8116:: with SMTP id d22mr16636980ljg.113.1626815435341;  Tue, 20 Jul 2021 14:10:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <CAJ4XoYf0mE_1kY06J5Tuw3G5JySndqRPyu96uJjdWEWXgE0S+g@mail.gmail.com> <52d3b7d214499c20a490baa4c43a998d@junc.eu> <CALaySJJJ-Nsi_hg=g1T6AdtAXEfnW-mHavLfb=5ppxbgRtVkVg@mail.gmail.com> <CAJ4XoYfMqMFd28axH_RiNHUHQB20yDKaYAEKK8PCerOP6WQ_SA@mail.gmail.com>
In-Reply-To: <CAJ4XoYfMqMFd28axH_RiNHUHQB20yDKaYAEKK8PCerOP6WQ_SA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 20 Jul 2021 17:10:23 -0400
Message-ID: <CALaySJJ5fsVxyOcy7vSKx3u62=AzjovMzrPq6Bt_oNqRmbS=Og@mail.gmail.com>
To: Dotzero <dotzero@gmail.com>
Cc: Benny Pedersen <me@junc.eu>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/G7vOyJvqyGplDZDdhHv4EtaHppA>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 21:10:40 -0000

>> One of the points of "deprecation" is that we don't eliminate it
>> entirely, but say that it's no longer used.  New implementations no
>> longer generate it, but implementations that are interested in
>> backward compatibility will still include support for it on receipt.
>>
>> Eventually, when we see that its use is rare enough, the community
>> might move to no longer include support (no longer needing backward
>> compatibility).  But I expect that support on receipt would remain for
>> some time.
>
> As soon as we say deprecated, the justifications for backwards
> compatibility become tenuous. If a sender has no reasonable
> expectation that most validators will respect their request, why would
> they make such a request (other than in ignorance). I think very few
> would argue that using percent is a long term strategy for any given
> domain. Either percent is useful or it is not.

I don't understand what you're objecting to: the whole point of
deprecation is to tell the sender not to make the request.  Backward
compatibility is purely on the receiver -- are there still enough old
senders who haven't updated their software, such that it's worth
supporting PCT if I receive it... or are the consequences of my
ignoring it such that it doesn't matter?  That's up to the judgment of
the receivers.

If we deprecate it, compliant senders will simply stop sending it.
Which is what it seems that we want.

Barry


From nobody Tue Jul 20 14:22:52 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 457CD3A3266 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 14:22:50 -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, 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 wso4G3WCedeP for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 14:22:44 -0700 (PDT)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B4253A32B6 for <dmarc@ietf.org>; Tue, 20 Jul 2021 14:22:43 -0700 (PDT)
Received: by mail-pj1-x1029.google.com with SMTP id me13-20020a17090b17cdb0290173bac8b9c9so2752162pjb.3 for <dmarc@ietf.org>; Tue, 20 Jul 2021 14:22:43 -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=IhsZRjhks7L5Zs1yqLgKiYAvv07ksB7HOJ5iuqJnO0Q=; b=mpXaOlB0QfWy4LLNnm6GglU8n+1joIgzG3+wrXHajtMsffQn6lhmNpL//Q7abmiFnv HiBzkWwmCoh7Jv1h7BY2x7bqXB8v6J75LR1KQj6ijD2H3ZJQci/wKD9VgBLb2DQFKNzk B4S4KkPGYT5X5L3Kjm4WNBUcyzvalUWTiH7dvXrYqyW8cuAdzA7NZuzB16SojimGKV5w L0ldhItLuL7dScZlr0XjzBljFJU8HNcJj3Q07C8PAGYLYO4X7uMpTAG++O4+/mdR9kyJ TZrB/bjKZIDu+HG3EkNLJVntLLvgoEjUqnDIAkS8WS4z9v3fdlAy29PGvUYiYQwXk3Jl ubdA==
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=IhsZRjhks7L5Zs1yqLgKiYAvv07ksB7HOJ5iuqJnO0Q=; b=W2G87mTs5KygcsKHLnipFqXbf2eJCVYLELmx1/PVb5dhZPne8WopZc7Yk0PT2At5I/ JvGxaImMiNQo/dVB9+QaudmK8YmJ9J4LGrcmqG1H2Cs5h/9GTX64eDm4ZX646tGn+GY2 jJGUS4GCiAbre83CVbhxutT6dUNqXrwNnpiTFO9LBWSWE77Gm+k2xN5BTc0IkFOCEf2+ o5uJ5NVI8GObdBvBe07tOZnfczzixktdo1iecc6qU4EOQP04BspUxD7j1cV27d5I4faU vF5RDQz1evJ6t6qDLBJmIy/fb7sr4vwkoXch+R7RcPjeTrIIKhn70cL5xRYWHJsOERRz I1FA==
X-Gm-Message-State: AOAM530DsOhDErtOAl7coTlv55JW/I7kqMkbFLvjR+Q7zurIA515gTXV 4Fm1B0qL/KdoDpueG6B4Q4Q/7MgbQno=
X-Google-Smtp-Source: ABdhPJxNcZ2bsvJq7rhmPnyF35+BMnmTNyZoW3tFb1asnhTrH58lxj5J6D/5jzPg0KegKunh75DHZg==
X-Received: by 2002:a17:90a:b792:: with SMTP id m18mr32334419pjr.140.1626816162379;  Tue, 20 Jul 2021 14:22:42 -0700 (PDT)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id a23sm25668833pfa.16.2021.07.20.14.22.41 for <dmarc@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Jul 2021 14:22:41 -0700 (PDT)
To: IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <CAJ4XoYf0mE_1kY06J5Tuw3G5JySndqRPyu96uJjdWEWXgE0S+g@mail.gmail.com> <52d3b7d214499c20a490baa4c43a998d@junc.eu> <CALaySJJJ-Nsi_hg=g1T6AdtAXEfnW-mHavLfb=5ppxbgRtVkVg@mail.gmail.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <bf40d8ef-ee1e-3026-2017-6be909cc11f6@gmail.com>
Date: Tue, 20 Jul 2021 14:22:41 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJJ-Nsi_hg=g1T6AdtAXEfnW-mHavLfb=5ppxbgRtVkVg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/_AVfy5oN-DkFOJfgbE7nUYtKXbM>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 20 Jul 2021 21:22:50 -0000

On 7/20/2021 1:13 PM, Barry Leiba wrote:
> One of the points of "deprecation" is that we don't eliminate it
> entirely, but say that it's no longer used.  New implementations no
> longer generate it, but implementations that are interested in
> backward compatibility will still include support for it on receipt.
>
> Eventually, when we see that its use is rare enough, the community
> might move to no longer include suppor

This is a natural, and considerate, model.  In the Internet, I believe 
it also has been shown not to work.  Really.

If something is to be removed from a protocol, it needs to be removed.  
So, remove it.

If there is a concern about noting the removal, add an appendix that 
references the removed feature, explaining why it was removed, and 
citing the previous specification.

Do NOT make it 'deprecated'. Don't continue it's specification. Do NOT 
make its use optional.  Make its use a matter of private choice, beyond 
the four walls of the public protocol specification.

"Deprecated" makes things complicated and conditional.  Neither of those 
are protocol attributes to aspire to.

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 Tue Jul 20 19:04:24 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 C416E3A0C24 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 19:04:22 -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, HEADER_FROM_DIFFERENT_DOMAINS=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=K2ris5Wu; dkim=pass (2048-bit key) header.d=taugh.com header.b=fwhrmJT9
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MQEPg_eH5plE for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 19:04:16 -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 ACE053A0C1F for <dmarc@ietf.org>; Tue, 20 Jul 2021 19:04:16 -0700 (PDT)
Received: (qmail 61303 invoked from network); 21 Jul 2021 02:04:14 -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=ef74.60f7809e.k2107; bh=JcnX8IvLvvj73Gf4Y1wFmHf7i5KSOWftb3QI4h+u1j0=; b=K2ris5Wu8mvV6tPTIVMquQRlij5hrhUzz3QTQIaKD9FcRe+sbe7BIsGMIifJZ3T28V3fK04zIQldEVO3CSW7ooPokbTLz/CECauugayzX9NwU84PoPveZMyLow4dlVodKYLPeDddWcTaz4Pbaj6OSZ9v/EsbRF5CoHaJvAgNlpbhKPI6h8tInMMxHF/Wm+SaHKhuoMits9YITav39hCrHqaEV76huz47LD/RGzAUOgTgO4O/zdqJ+FZZfXdwHzeRjjctU5oLlJHxRYLQji1c4eAye1ilEudi8Si0pbdV93P4iacfiOYka0aHHPafoD2aAbdsdaohEQH5/1hRdmqsbg==
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=ef74.60f7809e.k2107; bh=JcnX8IvLvvj73Gf4Y1wFmHf7i5KSOWftb3QI4h+u1j0=; b=fwhrmJT9VPvLxRLJQmmh4JzclD+1Mh17kdrfEjqQ4Nl9cuyFikHqodIC/ebU9XurA5mpx7uThpfXBY3IbmQ9Yt2PGjJAZagd4SuBh5g+gphg6QEEmQJxECXEn7PsFP2xD9Bz7u18prVaz3/3f/xxobZQhilFpU+iFo7s3MN3mk4cB4u/APPH0LUp6WasuJPrwndLTWwAzfAQ5Avkh9oLrPFTl6vNh5AB3WVZW2Pzmd6F6PUBe4thlGXxmXx5LGD0XeDOiKgEnlU9apFgkOndgNR937bNybdcmezDjorGHQV++x8jIwMnv6JKOqoRJ0wHuXeRlXfh3VRAWdCTC9LCug==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 21 Jul 2021 02:04:14 -0000
Received: by ary.qy (Postfix, from userid 501) id D58EB24CA31F; Tue, 20 Jul 2021 22:04:13 -0400 (EDT)
Date: 20 Jul 2021 22:04:13 -0400
Message-Id: <20210721020413.D58EB24CA31F@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dcrocker@gmail.com
In-Reply-To: <bf40d8ef-ee1e-3026-2017-6be909cc11f6@gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/nrUx96uMyYQTuZgXzvQsY3YeHNo>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 02:04:23 -0000

It appears that Dave Crocker  <dcrocker@gmail.com> said:
>If something is to be removed from a protocol, it needs to be removed.  
>So, remove it.

Since you're supposed to ignore unknown tags in the DMARC record, that seems
straightforward enough.

I suppose we should have a Former DMARC Tags registry to prevent them
from being recycled with a different meaning.

R's,
John


From nobody Tue Jul 20 19:45:43 2021
Return-Path: <dcrocker@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 615D53A0D96 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 19:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level: 
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 qJpgIOdd3qSX for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 19:45:35 -0700 (PDT)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1C433A0D93 for <dmarc@ietf.org>; Tue, 20 Jul 2021 19:45:35 -0700 (PDT)
Received: by mail-pj1-x1036.google.com with SMTP id p5-20020a17090a8685b029015d1a9a6f1aso160431pjn.1 for <dmarc@ietf.org>; Tue, 20 Jul 2021 19:45: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=9LtueC7a4wCikptoeBy1XW0wNrjodFi9yFq6yrYazUE=; b=TqBCHhuF5O3N9x9qhF3uBC9EaUtW+DPAFC6nCXK0TZxRd/QzEdLOJAeDgWIXoqzZ1j ht+scm8lTalzKVu4G7agoFKil9KNTfXK0OVaxgddm97Qw6HOs9kpfGn1mIrMCHRxRUsi 2yTh83nTC654mCpiNkngVfxA/okOflbNYbbXo6tbQeZXX47LEFgYRJ8sdD3RSmZXgPJ6 QuR3YBYwo4QGDDKDSRMpbpwjC1uX2R0iuFE7QvxuIeCXy3slhvR11iTaqd+0SafmvA4l gWKueNSyvxYIMQW6R7Nyrwrdy4BiBfXpYCrwChEEzJSjXA3mrfHL84lq+fOZiT9+f+JO tTwA==
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=9LtueC7a4wCikptoeBy1XW0wNrjodFi9yFq6yrYazUE=; b=E2CkmR+mu77LlZbfL/yO3ThCoGG2IyvoZV2BeU9Jtkj0xzKUys5mzEXh1UF9/VnHoo 2O2awfJv63jwUMDQFNNTTVWO5AV0JBC+dBDVubnDs+W1YVXgfb6fkNUrvUQFt+zn+W91 fOPumlPs7KOGkg/0RmAd7sxSAXRwXWiplw1r45WtQhwLvFTzixnA5kd529oqrmR8cRYd WfngEWmqeWTp2ijWSbHsS6d+s02+SFbJ9gTBE82TAubGBaGdfnUvdGepIfTtvAd7tEwK UGJQu+f9q7FiX3K/5/vRg4hqCr6mKJaqEUcnFKUHNjbBeOrGTmgkt9OXgeO2cGo3PHEk 3vZQ==
X-Gm-Message-State: AOAM533tLpq7TzBo91n3i/mqSa91/cDUIif9WX4Qeq/GM8dye9Yo8/aX 35OXpjex4WYdmN9c5n+pcY6bSuEj61E=
X-Google-Smtp-Source: ABdhPJwx/63XTr0z6GPoM2ncIg9MOw+aLLR2ObM+aUQ8vP+2Nt6xvbeeEP86V0JyOIIeeAhWS7Hz4Q==
X-Received: by 2002:a17:90a:62ca:: with SMTP id k10mr31979974pjs.133.1626835533255;  Tue, 20 Jul 2021 19:45:33 -0700 (PDT)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id l65sm16307009pgl.32.2021.07.20.19.45.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Jul 2021 19:45:32 -0700 (PDT)
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210721020413.D58EB24CA31F@ary.qy>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <8a209f99-6409-2073-7daf-b3d80702d562@gmail.com>
Date: Tue, 20 Jul 2021 19:45:32 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <20210721020413.D58EB24CA31F@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/z1RnJqHsdL5c-l52LQXBHqYkXCo>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 02:45:41 -0000

On 7/20/2021 7:04 PM, John Levine wrote:
> I suppose we should have a Former DMARC Tags registry to prevent them
> from being recycled with a different meaning.


Or keep the current entry, changing the specification citation to NONE, 
or even just keep the existing one.

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 Tue Jul 20 20:47: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 E10DB3A104E for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 20:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=1, 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 IdWJaxsg813I for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 20:47:30 -0700 (PDT)
Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68B893A1047 for <dmarc@ietf.org>; Tue, 20 Jul 2021 20:47:30 -0700 (PDT)
Received: by mail-qv1-xf2d.google.com with SMTP id gh6so332743qvb.3 for <dmarc@ietf.org>; Tue, 20 Jul 2021 20:47:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=guKpx3+HuBp8dQHMF0ZiD1r2tQ6JUtDaHlzNa7B8d6w=; b=cMw1Wt3qwyTjyVZuMnJxumgrhUttv5mNVnR1YTbgS9UshC93DMOxeIIRCU9V90aA/O M1xybCOsl8iFcWEU8Q4cyr9fDsWPq76ep5riNOrD85u6CUXsANa5mlzkT1ikMB40adbY wDJeJnNs/ZV4YB0kY1p49JZchl7sp4LRKhcsj5eXVFnMUv4m0lzmKsQu4gOC5xaIZ8F2 5BGRsxaXTuBjnLoIB5mehB3KcwezC84CDu+uZJLn4xiYdNVqz1WYHPDxvVGYsGEcYDF5 tXNPqYux0qACwY4CXseb2OCd0mMwBxM9pbJRjVuzsbxeLGOuslUxFVvUHUZlDH9lVUas kJAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=guKpx3+HuBp8dQHMF0ZiD1r2tQ6JUtDaHlzNa7B8d6w=; b=fbCcQQOuRE5FzFJ5uG9Uu5iTL0Dis1OObV7E77UjmdQo0GpjBc4tjqSo1d4uuSJ3yl sf+SFnjcrCoujtq+O6tW/KuH+4q9SAvYQ9Nwp2b5NjGtojHLYtLHwi/6+oogB3+gDkil fWz2lnfiMlAoswfLU0YokCMdhBRrD9LO7G5A9fVI2ju7IMvPDRyx1MbDRiaCWwA4mLW2 XhLxxeqqrhzHaMJ6WyW/Wr+ncNvb/TM5nZU4dJ/xkJde2CgFsYrW7eezTgdbG+shujuu iZQcV3aXni84ShUHTq0T2LBUR8hzAIRZebAn6t8vd36a0Ph+P81+ygKEi81JDhLWTdKg rqTA==
X-Gm-Message-State: AOAM531/1MD6dG4AAiABpsm7WVY+2Z12aL28jErfZZZgh3Krv/nU5IHS FjKPOHy6bktPeuzj05KRRWQ3W5bbTNpiTA==
X-Google-Smtp-Source: ABdhPJykcq8/5odhI2FQDlNT8qgnGLqHaPn/fhW4j2NMcPb0Y5u8HwShY0BFftRX8hLN9yEncXphoQ==
X-Received: by 2002:a0c:f6c6:: with SMTP id d6mr34064370qvo.30.1626839248147;  Tue, 20 Jul 2021 20:47:28 -0700 (PDT)
Received: from smtpclient.apple (50-110-95-0.clbg.wv.frontiernet.net. [50.110.95.0]) by smtp.gmail.com with ESMTPSA id az37sm10392377qkb.91.2021.07.20.20.47.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Jul 2021 20:47:26 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: tjw ietf <tjw.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 20 Jul 2021 23:47:23 -0400
Message-Id: <317CD7F5-2724-4D91-999C-8B47E863E3FD@gmail.com>
References: <8a209f99-6409-2073-7daf-b3d80702d562@gmail.com>
Cc: John Levine <johnl@taugh.com>, dmarc@ietf.org
In-Reply-To: <8a209f99-6409-2073-7daf-b3d80702d562@gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
X-Mailer: iPhone Mail (18F72)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/I_wi1AlMNCoUusdX9FFI2Kh4nio>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 03:47:35 -0000

I like Dave=E2=80=99s idea here about leaving them changing their value to n=
one.=20



Sent from my iPhone

> On Jul 20, 2021, at 22:45, Dave Crocker <dcrocker@gmail.com> wrote:
>=20
> =EF=BB=BFOn 7/20/2021 7:04 PM, John Levine wrote:
>> I suppose we should have a Former DMARC Tags registry to prevent them
>> from being recycled with a different meaning.
>=20
>=20
> Or keep the current entry, changing the specification citation to NONE, or=
 even just keep the existing one.
>=20
> d/
>=20
> --=20
> Dave Crocker
> dcrocker@gmail.com
> 408.329.0791
>=20
> Volunteer, Silicon Valley Chapter
> Information & Planning Coordinator
> American Red Cross
> dave.crocker2@redcross.org
>=20
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


From nobody Tue Jul 20 21:26:09 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 694363A11D7 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 21:26:08 -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=PLT/h0Ai; dkim=pass (2048-bit key) header.d=taugh.com header.b=Lsp+ziVh
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IaTL3MNUDrL5 for <dmarc@ietfa.amsl.com>; Tue, 20 Jul 2021 21:26:01 -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 115BE3A11D5 for <dmarc@ietf.org>; Tue, 20 Jul 2021 21:26:00 -0700 (PDT)
Received: (qmail 77909 invoked from network); 21 Jul 2021 04:25:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:content-type:content-transfer-encoding:mime-version:subject:references:in-reply-to; s=13050.60f7a1d6.k2107; i=johnl-iecc.com@submit.iecc.com; bh=07QEazIawrwOd6X8usQX0b0F/2w4uE+GqKkicrnPdNA=; b=PLT/h0Ai+nIBHjZTo08xOWxTY5EWGST1nL6zIeQbL8le14dUdjJRYNfzNxzsbmbgDDTpZRFC8JNVpOVpossExJp5IxyfMPC4rj+328MF/gtK6//+7andfWQ9VonTbttqQkkBk1oXUqvW0yfL5fLupoRIJyGErvd1YdDuxaWWawKXm6TamfKy0x4U+4r6moNPz6WsU2thWOKdy4hNG/JsCczKBtv5wsNh9VtviGdQ84KGJmQ6v2AIXelLIRCRy8J08pB7CUIwkn3ME58qWhai2YZyUtoWC0CMMGdZTe7cfPOYWPtV1zEsMCTaHTZLjFzWaTmlKaQg2TZZgCJgvnAlrg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:content-type:content-transfer-encoding:mime-version:subject:references:in-reply-to; s=13050.60f7a1d6.k2107; olt=johnl-iecc.com@submit.iecc.com; bh=07QEazIawrwOd6X8usQX0b0F/2w4uE+GqKkicrnPdNA=; b=Lsp+ziVh9f/euQvG4bZnvLfFvx5Nm4bJWSWf6ECV0fwJTMZCH9obY6y6gt4aAHFLsyI8dw1BsxWf3MLVKDPPwjSa5SF35W7lkUA1Vko6HiS2LTwCkeK1q6C74KI2FF6QBM6PL4JtLwtURVlJ59H+TuqqNw6xL7+ZAs7JUZUQA0nvhfJonO5MmqdgtiIlPGrnZN2zkjEQrzJvf8LwLJ+ZrRKHio7kG0DxZ0gr8Lwbo87Y+TIaOWfripn8tZpE5CfT6exljmCVA14Kp9JMKByLtDEQ8en+sbTC0aL8wbyzZMKaC4nuAnKwj3wkmwOJnY23iWWjKTs346OrpU7IA8ALxg==
Received: from smtpclient.apple ([IPv6:2001:470:8d03:c0d:7ce3:f715:2a30:ef07]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-128-GCM AEAD, johnl@iecc.com) via TCP6; 21 Jul 2021 04:25:57 -0000
Date: 21 Jul 2021 00:25:56 -0400
Message-Id: <4D723EC0-0EF7-4D90-A4FA-8522AE96CA5C@taugh.com>
From: "John Levine" <johnl@taugh.com>
To: "tjw ietf" <tjw.ietf@gmail.com>
Cc: "Dave Crocker" <dcrocker@gmail.com>, dmarc@ietf.org
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
References: <317CD7F5-2724-4D91-999C-8B47E863E3FD@gmail.com>
In-Reply-To: <317CD7F5-2724-4D91-999C-8B47E863E3FD@gmail.com>
X-Mailer: iPad Mail (18F72)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/6cUnDpbtQlXduDkCrkbxqXIZHkE>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 04:26:08 -0000

Seems like a reasonable way to do it.

Please consider the environment before reading this message.
John Levine, johnl@taugh.com=20

> On Jul 20, 2021, at 23:47, tjw ietf <tjw.ietf@gmail.com> wrote:
>=20
> =EF=BB=BFI like Dave=E2=80=99s idea here about leaving them changing their=
 value to none.=20
>=20
>=20
>=20
> Sent from my iPhone
>=20
>>> On Jul 20, 2021, at 22:45, Dave Crocker <dcrocker@gmail.com> wrote:
>>>=20
>>> =EF=BB=BFOn 7/20/2021 7:04 PM, John Levine wrote:
>>> I suppose we should have a Former DMARC Tags registry to prevent them
>>> from being recycled with a different meaning.
>>=20
>>=20
>> Or keep the current entry, changing the specification citation to NONE, o=
r even just keep the existing one.
>>=20
>> d/
>>=20
>> --=20
>> Dave Crocker
>> dcrocker@gmail.com
>> 408.329.0791
>>=20
>> Volunteer, Silicon Valley Chapter
>> Information & Planning Coordinator
>> American Red Cross
>> dave.crocker2@redcross.org
>>=20
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>=20


From nobody Wed Jul 21 01:28:50 2021
Return-Path: <laura@wordtothewise.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22A593A0A20 for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 01:28: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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wordtothewise.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c1p1cnEeyS0g for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 01:28:42 -0700 (PDT)
Received: from mail.wordtothewise.com (mail.wordtothewise.com [104.225.223.158]) by ietfa.amsl.com (Postfix) with ESMTP id F26823A0A1C for <dmarc@ietf.org>; Wed, 21 Jul 2021 01:28:41 -0700 (PDT)
Received: from [192.168.0.227] (unknown [37.228.231.27]) by mail.wordtothewise.com (Postfix) with ESMTPSA id 701F39F149 for <dmarc@ietf.org>; Wed, 21 Jul 2021 01:28:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wordtothewise.com; s=aardvark; t=1626856120; bh=ws2B1Ag3oZC3eBd9nnz1kegtSTrrtDIErhF5Qm77XwI=; h=From:Subject:Date:References:To:In-Reply-To:From; b=pbdrjQCPzHfrob49DPq/w7UQJ25EL1+oKrBD12KTSx+/3b4nvaimd0qIYeZEkQ1P7 8T1UwHhyfZPeRTkIwCfUqelsF1xwmVltR7TIBlNCB0LnQ84bMTyBt9ekyzA1h083nb 5zG+Qv7coEyoiRQYiKmxYnUhhsTLrhiXdJ+LhGpM=
From: Laura Atkins <laura@wordtothewise.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_95B05281-CA3A-4723-934A-3D4A738239E7"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Wed, 21 Jul 2021 09:28:36 +0100
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com>
Message-Id: <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/F629nWfVogYQpo-rM_BbsNur7oo>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 08:28:48 -0000

--Apple-Mail=_95B05281-CA3A-4723-934A-3D4A738239E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

This is going to cause difficulties in deployment for a lot of companies =
and domains. Experience tells us that p=3Dquarantine pct=3D0 detects =
forwarders and other types systems that modify and break DMARC =
authentication. These systems are undetectable when p=3Dnone is in =
place.=20

I understand and support removing PCT 1 - 99, but think that removing =
pct=3D0 will make it even more difficult for companies to deploy DMARC.=20=


larua=20


> On 20 Jul 2021, at 17:39, Dave Crocker <dcrocker@gmail.com> wrote:
>=20
> On 7/20/2021 7:54 AM, Barry Leiba wrote:
>> I would like to see us deprecate PCT entirely,
>=20
> +1
>=20
> d/
>=20
> --=20
> Dave Crocker
> dcrocker@gmail.com
> 408.329.0791
>=20
> Volunteer, Silicon Valley Chapter
> Information & Planning Coordinator
> American Red Cross
> dave.crocker2@redcross.org
>=20
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc

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

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

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








--Apple-Mail=_95B05281-CA3A-4723-934A-3D4A738239E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><div =
class=3D"">This is going to cause difficulties in deployment for a lot =
of companies and domains. Experience tells us that p=3Dquarantine pct=3D0 =
detects forwarders and other types systems that modify and break DMARC =
authentication. These systems are undetectable when p=3Dnone is in =
place.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">I =
understand and support removing PCT 1 - 99, but think that removing =
pct=3D0 will make it even more difficult for companies to deploy =
DMARC.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">larua&nbsp;</div><br class=3D""><div><br class=3D""><blockquote=
 type=3D"cite" class=3D""><div class=3D"">On 20 Jul 2021, at 17:39, Dave =
Crocker &lt;<a href=3D"mailto:dcrocker@gmail.com" =
class=3D"">dcrocker@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">On =
7/20/2021 7:54 AM, Barry Leiba wrote:<br class=3D""><blockquote =
type=3D"cite" class=3D"">I would like to see us deprecate PCT =
entirely,<br class=3D""></blockquote><br class=3D"">+1<br class=3D""><br =
class=3D"">d/<br class=3D""><br class=3D"">-- <br class=3D"">Dave =
Crocker<br class=3D""><a href=3D"mailto:dcrocker@gmail.com" =
class=3D"">dcrocker@gmail.com</a><br class=3D"">408.329.0791<br =
class=3D""><br class=3D"">Volunteer, Silicon Valley Chapter<br =
class=3D"">Information &amp; Planning Coordinator<br class=3D"">American =
Red Cross<br class=3D"">dave.crocker2@redcross.org<br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">dmarc mailing list<br class=3D"">dmarc@ietf.org<br =
class=3D"">https://www.ietf.org/mailman/listinfo/dmarc<br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-ligatures: =
normal; font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><div =
class=3D"">--&nbsp;</div><div class=3D"">Having an Email Crisis? =
&nbsp;We can help! 800 823-9674&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Laura Atkins</div><div class=3D"">Word =
to the Wise</div><div class=3D""><a =
href=3D"mailto:laura@wordtothewise.com" =
class=3D"">laura@wordtothewise.com</a></div><div class=3D"">(650) =
437-0741<span class=3D"Apple-tab-span" style=3D"white-space: pre;">		=
</span></div><div class=3D""><br =
class=3D""></div></span></span></span></span></span></div><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;">Email Delivery Blog: <a =
href=3D"https://wordtothewise.com/blog" =
class=3D"">https://wordtothewise.com/blog</a><span =
class=3D"Apple-tab-span" style=3D"white-space: pre;">	=
</span></span></span></span></span></span></div></span></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_95B05281-CA3A-4723-934A-3D4A738239E7--


From nobody Wed Jul 21 04:03:38 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 D921F3A10D7 for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 04:03:36 -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 36f41GaZO7ek for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 04:03:35 -0700 (PDT)
Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5A7B3A10D6 for <dmarc@ietf.org>; Wed, 21 Jul 2021 04:03:29 -0700 (PDT)
Received: by mail-oi1-x22b.google.com with SMTP id t6so2508688oic.0 for <dmarc@ietf.org>; Wed, 21 Jul 2021 04:03:29 -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=ZvPy9LABIg82zesNDjRbHtDKaU+/eWvd3e5MyY+pdVE=; b=dwN0Xxp0rJH/EOLkm9G9LfMGKFSogdWQfEY949LSIbKG2K9npEK/8xar0qmWzZmDjB Ug/oHNhM5lsIVDJKIxgMphe3w53a+mrgXfgSJSjqJo6SxGcihgyHGsuaGoiOwgHUHt9B f9E7TXb8tyEUDAoQY4NsOhxlaSm62P9B8Y1GCAw5CDpFJDQISaeJkkHBiUltA6kvI2qc dc4S0hSlsvo+ekfH5sK9nZSdl1l8CU10YR6ytbb4coK/vgUHqYgPgXo8O/FgdQkamNAb ngOJAusx5iu1Hj2eWOFhjysJzHT05TyfzXaYeGsYaCluxdzF3c5XuFRDB31+4ojIU8oY JsrQ==
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=ZvPy9LABIg82zesNDjRbHtDKaU+/eWvd3e5MyY+pdVE=; b=d07DXhVzgTqPTh/hV6Fm9E6qxvjXnsO/uNKCVClOUFr8O3zwG9rF2H201pylQpJVvB dLvUkvaXj4Q4bRQ5CML72INkKWQChRv1LYGIl08SKX/t5tUUEgrMETI+7M4HV7uCsvKH L74WtKU96SQQ26NhhOQsgTrd38rfZfkD6g/lqc+DzqLY7vUPr9p420nkyO8WDxIlfK44 AdYTdA48dZ0En7vomzdCb5zCGZX8vtPtKBoZc9kfeG53rvtQWPWfXPzFa59m9X1NgKxx l9d7wj0VbaggpzoaFihxHGbvUsv1Yo7VadgxJjip5XMawH783uxQBa8bTOWsKMrXhKMv Wg3g==
X-Gm-Message-State: AOAM531PYaKSng/exOAepqpSoajKf16p2iRJhKf6h2I9XyoGOTnmDcBn j4jEFlR1LGipOzIJGkWdTGvW3MzAZdfWeiOfDts=
X-Google-Smtp-Source: ABdhPJzNlLIWTS4CXgGwLifHJxRrjgUDbXhbJDC7ZVVcr+jM+TuQuuAiPdHd1EjPvhZvdMkLeNJWTfVvmDyg/PvwVR4=
X-Received: by 2002:aca:af14:: with SMTP id y20mr2158217oie.73.1626865406878;  Wed, 21 Jul 2021 04:03:26 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <d80b0a14-0f4d-8266-8d42-8d9a6b02413d@tana.it> <CAH48ZfyLvECR_nwLmw6R6RnE4EZa8g_i7MJaF32d2qk4RBCKRA@mail.gmail.com> <1E1F7937-AFEC-4F5A-8A5A-229A99C94E8B@bluepopcorn.net> <CAH48ZfyTm1PSANTUmnqOy3aeiW4JHGbTsQ-m9xtSW9zFaCUZQA@mail.gmail.com> <CAH48ZfzEWaFPUG4Gfc2ckpyUEq-8L9kEZZv+LwqJcW88=0y6=w@mail.gmail.com> <CALaySJJ2ZFML2neecfgAhvfk_1EuMNGw6DwchLmmWWpbDJC+Zw@mail.gmail.com>
In-Reply-To: <CALaySJJ2ZFML2neecfgAhvfk_1EuMNGw6DwchLmmWWpbDJC+Zw@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 21 Jul 2021 07:03:16 -0400
Message-ID: <CAH48ZfxELhp+fHujdZzDADGz4MNoWsJLB7cU1d1cW065Xu8YBQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aca69d05c7a01e59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/tu0r-Tm9mskc9u8oA77u51-QqMk>
Subject: Re: [dmarc-ietf] Fwd: Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 11:03:37 -0000

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

Barry's comment:

I don't agree with the characterization of the second group.  I would
say that we are partitioning messages into these two groups:
- Those for which we can confirm that they originated in the domain
they say they did.
- Those for which we can not confirm that.


When we use P=3DREJECT, we assert that anything which cannot be confirmed i=
s
unacceptable.   That makes for two pretty disjoint groups.   If
Authentication is only to be used to validate a whitelisting decision, then
a one-sided test would be sufficient.   In practice, the primary use for
DMARCv1 is to block messages, and much of our discussion has been around
the unwanted disposition that this places on mailing lists.

DKIM treats an invalid signature as non-existent.   It also treats a DKIM
signature as fully optional.   DMARCv1 changes the rules to gather more
usable information from the message.    DMARCv1 with P=3DREJECT says that a
message which lacks authentication is unacceptable, and since any message
might be forwarded, it has effectively made DKIM non-optional..  So we have
already modified the interpretation of DKIM.

I have observed that IF the domain owner indicates that all messages
originate with DKIM signatures, then the presence of a signature is no
longer optional at the evaluation point.    As I have said previously, this
provides a valid basis for partitioning messages between verified,
ambiguous, and repudiated.   If you accept the premise that mailing list
messages should not always be repudiated, then nothing we have done up to
this point has provided a reliable way to repudiate.   I am saying that
this is a problem that we can fix.

Upward Compatibility


Yes, I have gone radical, and I am no longer willing to be limited by the
design limitations of DMARCv1.   While DMARCv1 was apparently a
great success for PayPal, I perceive it as a failure when implemented
generally:

=C2=B7         DMARCv1 has a significant problem with mailing lists, and th=
e
mailing list interest has been well represented in this group.   Until my
proposal, the mailing list problem remained poorly addressed, even with ARC=
.

=C2=B7         DMARCv1 has poor implementation support.   I remember someon=
e
presenting a statistic to this group that only 6% of DMARC policies are
enforceable (p=3Dreject or quarantine).    If this is even close to correct=
,
after 10 years of DMARCv1, it suggests a significant failure to capture the
affection of domain owners.



=C2=B7         DMARCv1 has poor product support.   Many lower-end email
filtering products do not implement DMARC at all, which is not terribly
surprising.   But several high-end solutions implement DMARC enforcement
within their filter for incoming mail, while implementing DMARC violations
within their secure webmail product for outbound mail.   In-between these
extremes are some products that implement DMARC without adequate exception
methods, so the first false positive will require the feature to be
disabled.



I am no longer prepared to put window dressing on DMARCv1.   We need
DMARCbis to have a better design.

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

<div dir=3D"ltr"><div>Barry&#39;s comment:</div><div><br></div><blockquote =
style=3D"margin:0 0 0 40px;border:none;padding:0px"><div>I don&#39;t agree =
with the characterization of the second group.=C2=A0 I would</div><div>say =
that we are partitioning messages into these two groups:</div><div>- Those =
for which we can confirm that they originated in the domain</div><div>they =
say they did.</div><div>- Those for which we can not confirm that.</div></b=
lockquote><div dir=3D"ltr"><br></div><div>When we use P=3DREJECT, we assert=
 that anything which cannot=C2=A0be confirmed is unacceptable.=C2=A0 =C2=A0=
That makes for two pretty disjoint groups.=C2=A0 =C2=A0If Authentication=C2=
=A0is only to be used to validate a whitelisting decision, then a one-sided=
 test would be sufficient.=C2=A0 =C2=A0In practice, the primary use for DMA=
RCv1 is to block messages, and much of our discussion has been around the u=
nwanted disposition that this places on mailing lists.</div><div><br></div>=
<div>DKIM treats an invalid signature as non-existent.=C2=A0 =C2=A0It also =
treats a DKIM signature as fully optional.=C2=A0 =C2=A0DMARCv1 changes the =
rules to gather more usable information=C2=A0from the message.=C2=A0 =C2=A0=
 DMARCv1 with P=3DREJECT says that a message which lacks authentication=C2=
=A0is unacceptable,=C2=A0and since any message might be forwarded, it has=
=C2=A0effectively made DKIM non-optional..=C2=A0 So we have already modifie=
d the interpretation of DKIM.</div><div><br></div><div>I have observed that=
 IF the domain owner indicates that all messages originate with DKIM signat=
ures, then the presence of a signature is no longer optional at the evaluat=
ion point.=C2=A0 =C2=A0 As I have said previously, this provides a valid ba=
sis for partitioning=C2=A0messages between verified, ambiguous, and repudia=
ted.=C2=A0 =C2=A0If you accept the premise that mailing list messages shoul=
d not always be repudiated, then nothing we have done up to this point has =
provided a reliable way to repudiate.=C2=A0 =C2=A0I am saying that this is =
a problem that we can fix.</div><div><br></div><div><span style=3D"font-fam=
ily:Calibri,sans-serif;font-size:11pt">Upward Compatibility</span><br></div=
><div>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif"><br></p><p class=3D"MsoNormal" styl=
e=3D"margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:Calibri=
,sans-serif">Yes, I have gone radical, and I am no longer willing to be lim=
ited by the design limitations of DMARCv1.=C2=A0 =C2=A0While DMARCv1 was ap=
parently a great=C2=A0success for PayPal, I perceive it as a failure when i=
mplemented generally:=C2=A0 =C2=A0=C2=A0</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>DMARCv1 has a significant problem with mailing lists,
and the mailing list interest has been well represented in this group.=C2=
=A0=C2=A0 Until my proposal, the mailing list problem
remained poorly addressed, even with ARC.<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>DMARCv1 has poor implementation support.=C2=A0=C2=A0 I rememb=
er someone presenting a statistic to
this group that only 6% of DMARC policies are enforceable (p=3Dreject or
quarantine).=C2=A0=C2=A0=C2=A0 If this is even close to
correct, after 10 years of DMARCv1, it suggests a significant failure to
capture the affection of domain owners.</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">=C2=A0=
</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>DMARCv1 has poor product support.=C2=A0=C2=A0 Many lower-end =
email filtering products do
not implement DMARC at all, which is not terribly surprising.=C2=A0=C2=A0 B=
ut several high-end solutions implement
DMARC enforcement within their filter for incoming mail, while implementing=
 DMARC
violations within their secure webmail product for outbound mail.=C2=A0=C2=
=A0 In-between these extremes are some products that implement
DMARC without adequate exception methods, so the first false positive will =
require
the feature to be disabled.</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">=C2=A0</=
p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 8pt;line-height:107%;font-si=
ze:11pt;font-family:Calibri,sans-serif">I am no longer prepared to put wind=
ow dressing on DMARCv1.=C2=A0=C2=A0 We need DMARCbis to have a better desig=
n.</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><div><br></div></di=
v>

--000000000000aca69d05c7a01e59--


From nobody Wed Jul 21 06:54:05 2021
Return-Path: <sfs@umn.edu>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65A3B3A1896 for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 06:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.396
X-Spam-Level: 
X-Spam-Status: No, score=-4.396 tagged_above=-999 required=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_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kU5iAOdJpKPR for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 06:53:58 -0700 (PDT)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEFFF3A1894 for <dmarc@ietf.org>; Wed, 21 Jul 2021 06:53:57 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id 4GVH9w3lWSz9vFK8 for <dmarc@ietf.org>; Wed, 21 Jul 2021 13:53:56 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YH70J2AzYEvc for <dmarc@ietf.org>; Wed, 21 Jul 2021 08:53:56 -0500 (CDT)
Received: from mail-lf1-f71.google.com (mail-lf1-f71.google.com [209.85.167.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id 4GVH9w0YMCz9vFJb for <dmarc@ietf.org>; Wed, 21 Jul 2021 08:53:55 -0500 (CDT)
DMARC-Filter: OpenDMARC Filter v1.3.2 mta-p8.oit.umn.edu 4GVH9w0YMCz9vFJb
DKIM-Filter: OpenDKIM Filter v2.11.0 mta-p8.oit.umn.edu 4GVH9w0YMCz9vFJb
Received: by mail-lf1-f71.google.com with SMTP id u2-20020ac248a20000b0290384997a48fcso423262lfg.21 for <dmarc@ietf.org>; Wed, 21 Jul 2021 06:53:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:from:date:message-id:subject:to; bh=96+DVc+cVWR4bz5Y5GPS98DPKuoO0aEM6SXkY8rl0wY=; b=KUfL7p8CxeIzK5d65BfriQwaJPUpaRK4xNY+FzEBjWBGqODffz4/CpV0RVXUBhvTYO gVIMzfjDjpP3gE3ESekLMamvsV7mv4SJRcJEFSkkdMLmcMeWPGR1aZv044Gucd32INId se8d+IaCItahcDCIvj1C9erOlCfj58J9SypwHNBvRQOpMJ/xmqtU3qSmIl3DRcf/7cnE 226Fl5wDj/HaKDfx+oocNYiN7jxDA2Az+5vce7hUgUveYeJQwxiyfAaByQ4VYynfeuG+ eIerRoPTTtHUbrBuIOe03XxlqDy08rItFKNKjROX5uGnb+6Kk52K0yX80zrqLG8OOdkV oFNg==
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=96+DVc+cVWR4bz5Y5GPS98DPKuoO0aEM6SXkY8rl0wY=; b=D3KLHg+VQDsz3Q5z0dAgr5cIt94ERkpn6UprGOjtuPhpgKlhddPwVbH2XuyDSb14op 7diU3uq/zF/GVvrE1bYsTFPMIBNdYKZsW7JX4o+qWVvwIg+bIwNWDfwhxMTVTCr258dB 1tz3dinq3Hl0WBfxEXGBtxaT9aSPQ7WAhRoWC5RGsdrlm6x/mC1ASd3cP4BJ2H67PGi4 06Ko+6/n6BVxHx4Qwk0sd1MQUJQadCIXsM7iIoTBevzWFpId5LErzoP4HpPgX1PMGn0b MhZPxjazgj30oHcJz6zPNvKsq+mezZmZVkWXxo7cKU9M9zWIRDwMQvX4VmD+C3zZ/XR/ xIFQ==
X-Gm-Message-State: AOAM533FuqMI0ytHd+rYccrJQfLiICKQwniRzDIyShSjO/nDEmu4N9OW ZV3swX+gAIzy/T8SbXrVMK+yBKZPkW0W5hfJzpGzqD0nbkLVUEvn1neSDZcWSDzzpJ8Zpdj3GYP XcT87wVp5nAccApHSGEHLrHKylQ==
X-Received: by 2002:a05:6512:3f17:: with SMTP id y23mr25398918lfa.406.1626875634000;  Wed, 21 Jul 2021 06:53:54 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJwn/LIlPa5rBNvWBCkMpIsJtcMFw4b8vaCg/A7/vHJCcrrBFEFrJFQFwSMVCL5fdhqHF+vb8d/tsg6btTLSecY=
X-Received: by 2002:a05:6512:3f17:: with SMTP id y23mr25398885lfa.406.1626875633354;  Wed, 21 Jul 2021 06:53:53 -0700 (PDT)
MIME-Version: 1.0
From: Steve Siirila <sfs@umn.edu>
Date: Wed, 21 Jul 2021 08:53:42 -0500
Message-ID: <CAFAdyFoN2D0rg3Lfxq8amkAZbRXz=3uWz_DPnxzqLJr4__WR-w@mail.gmail.com>
To: dmarc@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003861e005c7a280b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/bEdk1uJjeUAbtAJcaSqX_QnuK3o>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 13:54:04 -0000

--0000000000003861e005c7a280b8
Content-Type: text/plain; charset="UTF-8"

At the University of Minnesota we used p=quarantine,pct=0 as a transition
between p=none and p=quarantine,pct=100 as it causes header "From:" to be
rewritten on DMARC-aware mailing list servers.  I agree with Laura Atkins
that removing pct=0 will make DMARC implementation more difficult for some
organizations.

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

<div dir=3D"ltr">At the University of Minnesota we used p=3Dquarantine,pct=
=3D0 as a transition between p=3Dnone and p=3Dquarantine,pct=3D100 as it ca=
uses header &quot;From:&quot; to be rewritten on DMARC-aware mailing list s=
ervers.=C2=A0 I agree with Laura Atkins that removing pct=3D0 will make DMA=
RC implementation more difficult for=C2=A0some organizations.</div>

--0000000000003861e005c7a280b8--


From nobody Wed Jul 21 10:19:46 2021
Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD5563A1FE3 for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:19:44 -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, HEADER_FROM_DIFFERENT_DOMAINS=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=IMB1sTTC; dkim=pass (2048-bit key) header.d=taugh.com header.b=f57vo9JQ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZYTAFz1MMZWK for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:19:39 -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 E721B3A1FDB for <dmarc@ietf.org>; Wed, 21 Jul 2021 10:19:37 -0700 (PDT)
Received: (qmail 87184 invoked from network); 21 Jul 2021 17:19:30 -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=1548d.60f85722.k2107; bh=303jEarxMOzWy2mK7Ti8qFOJHCqWwF+fN9rdHh8FKqw=; b=IMB1sTTC4rtnxJNUVdaDTEtfs73tmDbLN6345oV/6eKh1we47I+gQ8O6pp40tP0vFR+t3zzAbAqpyshxSUfSG6N3o+eJ00VY9TaIHEqwnUea9kAgJIn8kSXhTH5oJipbzr/NfOoc3wLgS7DTALNiS2OnWaFhtKmDbmR4Iz7vjMKexbovWVmoPBmIF4cjYQRAN8e4LfRz2/Fhw5++y+yadia14/rKX4Ti118LWFBwe0DUkv16Gzxi/Y5MFXkfJeX+9P72L/twO6An80aqZE6+KD+ZbhLWor/eAEyv9VzksSouVIZB8aid2XJ/2AZzF5BNx6to+5BpilU1nHnUeSBXJA==
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=1548d.60f85722.k2107; bh=303jEarxMOzWy2mK7Ti8qFOJHCqWwF+fN9rdHh8FKqw=; b=f57vo9JQ1BHoNbPqeXS7dwH95CECx+efkrpK2Aw0WKCQOgXl0gVdPkuDztf1lguTt6tBmufbBPc5nAFd0CM9/YC05uNqYCakY7MDfDQQ9KtXwTyITvccwdXjepM+H4zb8eqd+tHjWGeeoJHRHgbXZWX6fT01mB/6LD7Zf6QyGhpYbG9hZNQ1NdyebK07huGrrkhOEnD3VyKkKoskq6iIX8z6HVU3We7UpzuUw/X5rx5F6H1bJwzDp8Ffp/1/MVAmBx0KdOlWNL52HhYFo0VuCT8Ji7FWRPDNLpTU8xYHIpzyWyV3Rpd716aFKvDkwmalgAWyXrqs4BbHglbi/xi/3Q==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 21 Jul 2021 17:19:30 -0000
Received: by ary.qy (Postfix, from userid 501) id A9FA824CEF91; Wed, 21 Jul 2021 13:19:28 -0400 (EDT)
Date: 21 Jul 2021 13:19:28 -0400
Message-Id: <20210721171929.A9FA824CEF91@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: laura@wordtothewise.com
In-Reply-To: <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/UgH2XIyGY4kN0vazaVQuZKYBbj0>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 17:19:45 -0000

It appears that Laura Atkins  <laura@wordtothewise.com> said:
>-=-=-=-=-=-
>
>This is going to cause difficulties in deployment for a lot of companies and domains. Experience tells us that p=quarantine pct=0 detects forwarders
>and other types systems that modify and break DMARC authentication. These systems are undetectable when p=none is in place. 

I can see how that would be useful to help debug your mailing list software but it's not so clear
how you use it as a sender.

Is the idea that you see a bunch of fails in the report that look like lists, then turn on pct=0
and see if they go away?

I suppose we could leave pct=0 as a hint to forwarders to turn on their DMARC evasion hacks.

R's,
John


From nobody Wed Jul 21 10:24:46 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 8BEAE3A2029 for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:24:44 -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 0uXJZV2NjWLH for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:24:38 -0700 (PDT)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0D6A3A202B for <dmarc@ietf.org>; Wed, 21 Jul 2021 10:24:38 -0700 (PDT)
Received: by mail-pl1-x630.google.com with SMTP id p17so1282493plf.12 for <dmarc@ietf.org>; Wed, 21 Jul 2021 10:24:38 -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=vZt95Oj5LN9h9uTGCeSaCfhOdhDOwlUXoE+piRHNM68=; b=q8qapAlK5fZXbYO4oybjockrJplXwi3b7rWYJMM/MQduAkzcT7TZjWn/kBeVqMsKHq TBwtFmQqGRcpTXpW3mpI2Fq3faBv+pkBVLlG+wnpZoG712t1mhobxKFVdF5a8vAbjH73 5NQVNMeSkmXSOkDrG88fSMAAw1bOeKKywh1jlsRRQuQ/ovjypXXUXz3S8PKDdLNADzr/ oPXRKhF5cFCvX1ig2TKAiPOflId2u50oSBKw3a9w4EjehqaRsqDUZi35xHQnplq8XZVi y7xt2khIC7AXkEpisgA5EnrqoJI784VelMz9bDjN0E1lLrXzw1tS2hnePslpHamM9Vul wXPg==
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=vZt95Oj5LN9h9uTGCeSaCfhOdhDOwlUXoE+piRHNM68=; b=ezXYVszsBodmK2s0zjQ3flI94q+QG3U9OIjs0nHZj+XU5a6RrVKwwjtzS5/z7ASZIM U/nVhY9QvgWK0AK6hYVHfR7HY6e7AvPIe1O7UC6QmU28XxCJ2atPHMD8ZvLDcvP7TrAE irL/YqB6GYMI8Tpn0kZfg+v0IZOwV0rH9cyA/8WK1iOh2e2hvIJyPRyRKVcHZZOZ4kxR V+/uk4Q50XeJmAV63bxfqY++kEkeimtsaTWVu+7OyfvpwLKIS4j6P4uPq9DKJzWKZ4Qh Xyy7EuMEPT4DYDuh4kR0e2Ay9KqHsCDYOuXFK9jexiEvFyGDbFytMX6C4FShcXEJtk/U +CSA==
X-Gm-Message-State: AOAM533jXlh9tzevcXX23iWRXBsyoZnmOQjbdpPTBfunU2vCF2J4IcIu TD7xgWbEGSjrOQwC76/poiHKUiVI41Q=
X-Google-Smtp-Source: ABdhPJy+vxxU6jVheK4K7SjdS87C1ClhJ4NLtD2PC3eYg4VuPjHsX5s4nJQ607jyM6BiCYBzxTS3Ww==
X-Received: by 2002:a17:90a:74c8:: with SMTP id p8mr4866800pjl.70.1626888277790;  Wed, 21 Jul 2021 10:24:37 -0700 (PDT)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net. [24.130.62.181]) by smtp.gmail.com with ESMTPSA id a23sm28502377pfa.16.2021.07.21.10.24.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 21 Jul 2021 10:24:37 -0700 (PDT)
To: Laura Atkins <laura@wordtothewise.com>, IETF DMARC WG <dmarc@ietf.org>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.com>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <80374a84-6298-c45b-3fad-256bebd4f903@gmail.com>
Date: Wed, 21 Jul 2021 10:24:35 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/NhYBuvH9iyauUFJWS6jtB9UUTgI>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 17:24:45 -0000

On 7/21/2021 1:28 AM, Laura Atkins wrote:
> This is going to cause difficulties in deployment for a lot of 
> companies and domains. Experience tells us that p=quarantine pct=0 
> detects forwarders and other types systems that modify and break DMARC 
> authentication. These systems are undetectable when p=none is in place. 

How is this 'detection' actually used?  That is, what is then done 
differently?


On 7/21/2021 10:19 AM, John Levine wrote:
> I suppose we could leave pct=0 as a hint to forwarders to turn on their DMARC evasion hacks.

Why doesn't seeing DMARC as seeing that it isn't p=none outght to 
suffice for that?


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 Wed Jul 21 10:26:34 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 BBD0F3A204F for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, PDS_OTHER_BAD_TLD=1.999, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 BpFzNe_YSfAE for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:26:26 -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 17D3E3A204A for <dmarc@ietf.org>; Wed, 21 Jul 2021 10:26:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1626888382; bh=/Ft3Uahuv6LSQHyUvvRG5TevEiaY3uJRi3Ff83d61uo=; l=8112; h=To:References:From:Date:In-Reply-To; b=ADy3IZ7KnL0oEZ129SODkNYeJF+7rgFHmSQUK4zEd6nsn4nxX0NZ2Xi+bJK8HDkbw m3jcU9kL3ruD/cshgMf84sTO1/ozlHaEh9QpoXRatvwPCJH03qv/oiEY2MKLeNeJZ2 irzr0pKKMjIQyJ/aiyEHx0i4A2wnsQsREhrQX/ea47GccHA4/D264q+9Uwbvo
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 00000000005DC008.0000000060F858BD.000075E3; Wed, 21 Jul 2021 19:26:21 +0200
To: dmarc@ietf.org
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <859c3867-9c1f-a3a4-9705-73d3fb9f7f64@tana.it>
Date: Wed, 21 Jul 2021 19:26:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.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/t-4Zv_DyEYzkSllT-wOAU1H1VK8>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 17:26:33 -0000

On Wed 21/Jul/2021 10:28:36 +0200 Laura Atkins wrote:
> [deprecate PCT entirely] is going to cause difficulties in deployment for a
> lot of companies and domains. Experience tells us that p=quarantine pct=0
> detects forwarders and other types systems that modify and break DMARC
> authentication. These systems are undetectable when p=none is in place.

+1, although some DMARC records in the wild betray a poor understanding of how it works, pct is a useful ratchet and we should keep it.


> I understand and support removing PCT 1 - 99, but think that removing pct=0 
> will make it even more difficult for companies to deploy DMARC.


My main objection to removing pct 1-99 is that it would make for a nasty wording, not to mention the hassle of backward compatibility.  (Didn't we say we're not going to make DMARCv2?)

Indeed, since pct=100 is the default, what would we use for pct=0?  Just-kidding=1?

In addition, since I cash domain data and have a sample of 121,329 domain records, 5,980 (~4.9%) of which have a DMARC record, I can try to answer the question that John asked yesterday at 5pm.  Some domains do seem to evolve their pct.  I found 214 domains having a two-digit pct.  It is only ~3.6% of DMARC records, but, if you concede any statistical relevance to my data, it proves that the pct feature is more or less as important to DMARC as DMARC itself is important to email in general.  That is, by domain numbers, even if it is not so important, oversimplifying feels like throwing the baby out with the bathwater.

Of those 214 domains experimenting with pct, 115 (~53.7%) did not change it yet, 51 (~23.8%) failed to serve a DMARC record, 43 (~20%) raised it to full percentage, and 5 (~2.3%) played other changes.  Change details are as follows, newest to oldest:

umn.edu                       had      pct=0  on 2021-07-21 15:54:31,  now    pct=100
constantcontact.com           had     pct=10  on 2021-07-21 05:30:27,  now    pct=100
nannyjob.co.uk                had     pct=50  on 2021-07-20 21:06:47,  now    default
mailerlite.com                had      pct=5  on 2021-07-20 16:48:01,  now    pct=100
kernel.org                    had      pct=1  on 2021-07-18 20:25:34,  now    default
db.com                        had     pct=15  on 2021-07-14 16:12:38,  now     pct=25
developers.italia.it          had      pct=5  on 2021-07-13 19:19:45,  now    default
revfr.today                   had     pct=30  on 2021-07-12 16:29:08,  now  not found
caser.today                   had     pct=30  on 2021-07-12 05:31:20,  now  not found
ericsson.com                  had      pct=0  on 2021-07-08 10:53:37,  now    default
crif.com                      had     pct=25  on 2021-07-06 14:28:33,  now    default
p-a-finbergadvisor.com        had      pct=1  on 2021-06-10 11:10:28,  now    default
economiasviluppo.com          had      pct=1  on 2021-06-07 22:07:50,  now    default
medody.com                    had     pct=40  on 2021-05-22 15:19:27,  now  not found
pafinberg.net                 had      pct=1  on 2021-05-21 09:07:51,  now    default
xss.de                        had      pct=1  on 2021-05-20 23:35:57,  now    default
paddle.com                    had      pct=5  on 2021-05-02 15:39:05,  now    pct=100
dnswl.org                     had     pct=25  on 2021-04-27 19:50:49,  now    default
rusoil.net                    had      pct=1  on 2021-04-22 20:35:12,  now    default
qa.jcb.co.jp                  had     pct=50  on 2021-03-12 17:58:04,  now    default
rni.com.pk                    had      pct=0  on 2021-03-11 04:00:07,  now  not found
cloudflare.com                had     pct=25  on 2021-03-08 17:50:09,  now    pct=100
nw.mailzaap.com               had      pct=5  on 2021-02-22 17:58:45,  now  not found
nw.risparmisubito.it          had      pct=5  on 2021-02-14 07:53:21,  now  not found
nw.promopremium.eu            had      pct=5  on 2021-02-13 14:54:37,  now  not found
nw.scontiok.com               had      pct=5  on 2020-12-15 16:05:54,  now  not found
hw.ac.uk                      had      pct=5  on 2020-11-30 17:32:15,  now    default
karta.website                 had     pct=30  on 2020-11-25 04:55:33,  now  not found
veicolimilano.it              had      pct=1  on 2020-10-07 02:02:26,  now    default
jagoanhosting.com             had     pct=80  on 2020-09-25 02:42:44,  now    default
vshosting.cz                  had      pct=1  on 2020-08-11 18:05:14,  now    default
techno-digm.com               had      pct=1  on 2020-08-05 08:45:36,  now  not found
nw.graziepromo.com            had      pct=5  on 2020-08-04 09:09:04,  now  not found
outreach.rehab4addiction.uk   had     pct=50  on 2020-07-31 10:09:39,  now     pct=20
xyonet.com                    had      pct=5  on 2020-07-30 22:57:33,  now    default
hanoi.gov.vn                  had     pct=20  on 2020-06-17 01:54:54,  now    default
silvanaeditoriale.it          had     pct=50  on 2020-05-08 17:22:06,  now     pct=25
hale.com.hk                   had     pct=90  on 2020-02-26 14:37:42,  now  not found
pasteur-cayenne.fr            had      pct=5  on 2019-12-27 04:27:44,  now     pct=90
nw.mailrogue.com              had      pct=5  on 2019-11-21 20:34:34,  now    default
delivery-571.info             had     pct=40  on 2019-11-10 12:31:25,  now  not found
opensystems.co.bw             had     pct=60  on 2019-10-17 01:26:10,  now  not found
pafinberg.com                 had     pct=20  on 2019-10-09 17:29:32,  now    default
efaxreceive.xyz               had     pct=40  on 2019-09-23 15:58:07,  now  not found
gameview.my                   had     pct=20  on 2019-09-18 07:58:00,  now  not found
nationizable.icu              had     pct=40  on 2019-09-02 17:16:37,  now  not found
designifican.icu              had     pct=40  on 2019-08-09 20:02:11,  now  not found
maersk.com                    had      pct=1  on 2019-07-17 09:03:42,  now    default
mebnet.net                    had     pct=20  on 2019-06-28 04:33:46,  now    default
qlc.in                        had      pct=5  on 2019-06-04 00:21:26,  now    default
primefinance.com              had     pct=15  on 2019-05-23 18:48:43,  now    default
corrlinks.com                 had     pct=25  on 2019-02-21 10:51:27,  now    default
0086.info                     had      pct=5  on 2019-02-03 17:30:23,  now  not found
studio-im.com                 had      pct=5  on 2019-01-24 13:39:42,  now  not found
crowdselector.eu              had     pct=40  on 2018-11-06 12:06:59,  now  not found
eehmke.de                     had     pct=25  on 2018-10-16 13:52:43,  now    default
learningcompass.ga            had     pct=50  on 2018-07-24 16:00:08,  now  not found
women.it                      had      pct=2  on 2018-05-30 17:48:18,  now  not found
ucdavis.edu                   had      pct=5  on 2018-04-29 04:19:01,  now    default
nasaprolifeone.com            had     pct=30  on 2018-02-20 03:30:01,  now  not found
korrumpedia.org               had     pct=30  on 2018-02-17 00:56:57,  now  not found
nasaprolifeadmin.com          had     pct=30  on 2018-02-15 23:59:32,  now  not found
campaniaorlreaders.com        had     pct=30  on 2018-02-15 22:47:03,  now  not found
campaniaorlreader.com         had     pct=30  on 2018-02-15 18:18:45,  now  not found
emailepost.com                had     pct=30  on 2018-02-15 14:36:54,  now  not found
servicepost.net               had     pct=30  on 2018-02-14 05:46:13,  now  not found
ipostica.com                  had     pct=30  on 2018-02-14 03:02:30,  now  not found
postaname.net                 had     pct=30  on 2018-02-13 16:48:51,  now  not found
nasaprolife.com               had     pct=30  on 2018-02-13 14:01:46,  now  not found
nuovoemail.net                had     pct=30  on 2018-02-13 12:38:22,  now  not found
postaspa.com                  had     pct=30  on 2018-02-07 04:22:28,  now  not found
polinpdg.ac.id                had     pct=10  on 2018-02-06 03:06:29,  now  not found
popularanimal.net             had     pct=30  on 2018-01-24 19:31:14,  now  not found
bnl.gov                       had     pct=10  on 2018-01-24 02:12:25,  now    pct=100
mail1.datongcloud.com         had     pct=50  on 2018-01-12 18:25:53,  now  not found
hulusungaitengahkab.go.id     had     pct=20  on 2018-01-01 04:08:33,  now    default
haladzhi.com.ua               had     pct=30  on 2017-11-24 01:59:41,  now  not found
demmarkita2.com               had     pct=20  on 2017-10-18 13:56:23,  now  not found
lada-date-brides.com          had     pct=30  on 2017-10-11 05:13:01,  now  not found
know.kiev.ua                  had     pct=30  on 2017-10-09 14:10:39,  now  not found
opentext.com                  had     pct=10  on 2017-09-28 22:43:18,  now    default
modernposta.net               had     pct=30  on 2017-09-25 15:29:03,  now  not found
stratoplan.ru                 had      pct=5  on 2017-09-18 04:56:28,  now    default
etc-brainwork-sev.com         had     pct=30  on 2017-09-12 21:52:19,  now  not found
aabl.in                       had     pct=50  on 2017-08-27 15:41:27,  now  not found
voxel.larrylarson.com.br      had      pct=5  on 2017-08-24 17:25:42,  now  not found
framestore.com                had      pct=6  on 2017-08-23 10:09:28,  now    pct=100
eu.org                        had     pct=10  on 2017-07-25 19:42:09,  now    default
terradox.ro                   had      pct=5  on 2017-07-03 07:35:55,  now  not found
macsales.com                  had      pct=0  on 2017-06-22 19:46:57,  now    pct=100
opayq.com                     had      pct=0  on 2017-06-09 12:44:37,  now     pct=10
ipoggioli.site                had      pct=0  on 2017-03-08 12:21:11,  now  not found
td-gratis.ru                  had     pct=25  on 2016-11-20 00:05:54,  now  not found
lqfconos.com                  had      pct=1  on 2016-10-24 20:00:38,  now    default
systemcentral.net             had      pct=1  on 2016-09-16 16:01:07,  now    default
spectranet.in                 had     pct=50  on 2016-03-14 11:38:23,  now  not found
unimelb.edu.au                had     pct=10  on 2016-02-28 02:36:47,  now    default
savages.com                   had      pct=5  on 2015-11-23 19:50:55,  now    default
waltermoreno.com              had      pct=1  on 2015-05-02 22:09:08,  now  not found


Best
Ale
-- 
























From nobody Wed Jul 21 10:26:58 2021
Return-Path: <laura@wordtothewise.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9797B3A2062 for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:26:56 -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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wordtothewise.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OYoyM_siwWB1 for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:26:50 -0700 (PDT)
Received: from mail.wordtothewise.com (mail.wordtothewise.com [104.225.223.158]) by ietfa.amsl.com (Postfix) with ESMTP id 624513A2097 for <dmarc@ietf.org>; Wed, 21 Jul 2021 10:26:49 -0700 (PDT)
Received: from [192.168.0.227] (unknown [37.228.231.27]) by mail.wordtothewise.com (Postfix) with ESMTPSA id 38DC09F149 for <dmarc@ietf.org>; Wed, 21 Jul 2021 10:26:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wordtothewise.com; s=aardvark; t=1626888408; bh=A31Y20EbMiI8vVDC1M8LYSBcSoBHGIZDGJvEjjjetHY=; h=From:Subject:Date:References:To:In-Reply-To:From; b=C6NMohGaWC4Mq8iFFA8Jpi0ydsbmY8+d9zt37iJ+t0orx5NdnBQtN5k0Z/7aB2YFv no2N7yNcGrp5Uwrq4zwz6KzHk6A6LL9vri+x02bayDpKjD9DoHYRyIcWyrtlLhMwE8 FyFW3hYpCS3hCKpYLcFi1IKeqhXLyKYfULPNNUuk=
From: Laura Atkins <laura@wordtothewise.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5C6C6477-A042-4141-990E-1A15CCF23D76"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Wed, 21 Jul 2021 18:26:46 +0100
References: <20210721171929.A9FA824CEF91@ary.qy>
To: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <20210721171929.A9FA824CEF91@ary.qy>
Message-Id: <0C2D8AE5-6411-476A-BAAD-2FDC6DFD5CE5@wordtothewise.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VzJski5NGo8ak3TGkl65nvSAzrE>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 17:26:57 -0000

--Apple-Mail=_5C6C6477-A042-4141-990E-1A15CCF23D76
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 21 Jul 2021, at 18:19, John Levine <johnl@taugh.com> wrote:
>=20
> It appears that Laura Atkins  <laura@wordtothewise.com> said:
>> -=3D-=3D-=3D-=3D-=3D-
>>=20
>> This is going to cause difficulties in deployment for a lot of =
companies and domains. Experience tells us that p=3Dquarantine pct=3D0 =
detects forwarders
>> and other types systems that modify and break DMARC authentication. =
These systems are undetectable when p=3Dnone is in place.=20
>=20
> I can see how that would be useful to help debug your mailing list =
software but it's not so clear
> how you use it as a sender.
>=20
> Is the idea that you see a bunch of fails in the report that look like =
lists, then turn on pct=3D0
> and see if they go away?

We discussed this on the phone call. We=E2=80=99ve discussed this on the =
list. You can see the summary of the notes from the call in the message =
from Barry with the subject line [dmarc-ietf] Notes from DMARC interim =
teleconference, 27 May 2021. You can also review the list archives for =
previous discussions of this and why pct=3D0 is important for =
deployment.=20

laura=20

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

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

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








--Apple-Mail=_5C6C6477-A042-4141-990E-1A15CCF23D76
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 21 Jul 2021, at 18:19, John Levine &lt;<a =
href=3D"mailto:johnl@taugh.com" class=3D"">johnl@taugh.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">It appears that Laura Atkins &nbsp;&lt;<a =
href=3D"mailto:laura@wordtothewise.com" =
class=3D"">laura@wordtothewise.com</a>&gt; said:<br class=3D""><blockquote=
 type=3D"cite" class=3D"">-=3D-=3D-=3D-=3D-=3D-<br class=3D""><br =
class=3D"">This is going to cause difficulties in deployment for a lot =
of companies and domains. Experience tells us that p=3Dquarantine pct=3D0 =
detects forwarders<br class=3D"">and other types systems that modify and =
break DMARC authentication. These systems are undetectable when p=3Dnone =
is in place. <br class=3D""></blockquote><br class=3D"">I can see how =
that would be useful to help debug your mailing list software but it's =
not so clear<br class=3D"">how you use it as a sender.<br class=3D""><br =
class=3D"">Is the idea that you see a bunch of fails in the report that =
look like lists, then turn on pct=3D0<br class=3D"">and see if they go =
away?<br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>We discussed this on the phone call. We=E2=80=99ve =
discussed this on the list. You can see the summary of the notes from =
the call in the message from Barry with the subject line&nbsp;<span =
style=3D"color: rgba(0, 0, 0, 0.85); font-family: &quot;Helvetica =
Neue&quot;;" class=3D"">[dmarc-ietf] Notes from DMARC interim =
teleconference, 27 May 2021. You can also review the list archives for =
previous discussions of this and why pct=3D0 is important for =
deployment.&nbsp;</span></div><div><span style=3D"color: rgba(0, 0, 0, =
0.85); font-family: &quot;Helvetica Neue&quot;;" class=3D""><br =
class=3D""></span></div><div><span style=3D"color: rgba(0, 0, 0, 0.85); =
font-family: &quot;Helvetica Neue&quot;;" =
class=3D"">laura&nbsp;</span></div></div><br class=3D""><div class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px; font-family: Helvetica; font-size: 12px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal;"><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><div =
class=3D"">--&nbsp;</div><div class=3D"">Having an Email Crisis? =
&nbsp;We can help! 800 823-9674&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Laura Atkins</div><div class=3D"">Word =
to the Wise</div><div class=3D""><a =
href=3D"mailto:laura@wordtothewise.com" =
class=3D"">laura@wordtothewise.com</a></div><div class=3D"">(650) =
437-0741<span class=3D"Apple-tab-span" style=3D"white-space: pre;">		=
</span></div><div class=3D""><br =
class=3D""></div></span></span></span></span></span></div><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;">Email Delivery Blog: <a =
href=3D"https://wordtothewise.com/blog" =
class=3D"">https://wordtothewise.com/blog</a><span =
class=3D"Apple-tab-span" style=3D"white-space: pre;">	=
</span></span></span></span></span></span></div></span></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_5C6C6477-A042-4141-990E-1A15CCF23D76--


From nobody Wed Jul 21 10:30:41 2021
Return-Path: <laura@wordtothewise.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91E5A3A209A for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:30:33 -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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wordtothewise.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32cwwBxv1TVr for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:30:27 -0700 (PDT)
Received: from mail.wordtothewise.com (mail.wordtothewise.com [104.225.223.158]) by ietfa.amsl.com (Postfix) with ESMTP id 712F53A2087 for <dmarc@ietf.org>; Wed, 21 Jul 2021 10:30:27 -0700 (PDT)
Received: from [192.168.0.227] (unknown [37.228.231.27]) by mail.wordtothewise.com (Postfix) with ESMTPSA id 65E7A9F149; Wed, 21 Jul 2021 10:30:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wordtothewise.com; s=aardvark; t=1626888626; bh=sAnLEfaIQdrN8/51JOnhb74af7KXhU+jAmSGOhZ/LL4=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=AbtOqwZrggHeC0EU3rmvsxLX8iphEthYvDeKOUKByH9Ak6rUJopVvABnfVOCqa2UW w3gmb18yUv0aHxywRC6RvqiJZNFL6sSADDpg5CCRSoh02jF3YKBK4FAZqIvKHMMCdY B5N/A3Zf9U0l9yujGZxzg7z9iMuSPs+N6mG9txB4=
From: Laura Atkins <laura@wordtothewise.com>
Message-Id: <CD892072-EE38-4073-80B0-E354E0C2B61A@wordtothewise.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_89B538A1-5CC7-4064-9E59-9792CB6E1772"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Wed, 21 Jul 2021 18:30:23 +0100
In-Reply-To: <80374a84-6298-c45b-3fad-256bebd4f903@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
To: Dave Crocker <dcrocker@gmail.com>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.com> <80374a84-6298-c45b-3fad-256bebd4f903@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/3HXzsrse2_tzOYuQIyu02ialtgg>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 17:30:39 -0000

--Apple-Mail=_89B538A1-5CC7-4064-9E59-9792CB6E1772
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 21 Jul 2021, at 18:24, Dave Crocker <dcrocker@gmail.com> wrote:
>=20
> On 7/21/2021 1:28 AM, Laura Atkins wrote:
>> This is going to cause difficulties in deployment for a lot of =
companies and domains. Experience tells us that p=3Dquarantine pct=3D0 =
detects forwarders and other types systems that modify and break DMARC =
authentication. These systems are undetectable when p=3Dnone is in =
place.=20
>=20
> How is this 'detection' actually used?  That is, what is then done =
differently?

Please review the list archives for previous discussion of why p=3D0 is =
important.=20

The part of the message you clipped indicates I was specifically =
commenting on removing pct=3D0, which group consensus from May 27 says =
we keep. If it=E2=80=99s possible to remove 1 - 99 that gets a +1 from =
me.

> On 7/21/2021 10:19 AM, John Levine wrote:
>> I suppose we could leave pct=3D0 as a hint to forwarders to turn on =
their DMARC evasion hacks.
>=20
> Why doesn't seeing DMARC as seeing that it isn't p=3Dnone outght to =
suffice for that?

There was a long discussion on this list at the end of 2020 describing =
why pct=3D0 is an important step in deployment.=20

laura=20

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

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

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








--Apple-Mail=_89B538A1-5CC7-4064-9E59-9792CB6E1772
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 21 Jul 2021, at 18:24, Dave Crocker &lt;<a =
href=3D"mailto:dcrocker@gmail.com" class=3D"">dcrocker@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">On 7/21/2021 1:28 AM, Laura Atkins wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D"">This is going to cause =
difficulties in deployment for a lot of companies and domains. =
Experience tells us that p=3Dquarantine pct=3D0 detects forwarders and =
other types systems that modify and break DMARC authentication. These =
systems are undetectable when p=3Dnone is in place. <br =
class=3D""></blockquote><br class=3D"">How is this 'detection' actually =
used?&nbsp; That is, what is then done differently?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>Please =
review the list archives for previous discussion of why p=3D0 is =
important.&nbsp;</div><div><br class=3D""></div><div>The part of the =
message you clipped indicates I was specifically commenting on removing =
pct=3D0, which group consensus from May 27 says we keep. If it=E2=80=99s =
possible to remove 1 - 99 that gets a +1 from me.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">On 7/21/2021 10:19 AM, John Levine wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D"">I suppose we could leave =
pct=3D0 as a hint to forwarders to turn on their DMARC evasion hacks.<br =
class=3D""></blockquote><br class=3D"">Why doesn't seeing DMARC as =
seeing that it isn't p=3Dnone outght to suffice for that?<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>There =
was a long discussion on this list at the end of 2020 describing why =
pct=3D0 is an important step in deployment.&nbsp;</div><div><br =
class=3D""></div><div>laura&nbsp;</div></div><br class=3D""><div =
class=3D"">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D""><div style=3D"color: rgb(0, 0, 0); =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-ligatures: =
normal; font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-caps: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><div =
class=3D"">--&nbsp;</div><div class=3D"">Having an Email Crisis? =
&nbsp;We can help! 800 823-9674&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Laura Atkins</div><div class=3D"">Word =
to the Wise</div><div class=3D""><a =
href=3D"mailto:laura@wordtothewise.com" =
class=3D"">laura@wordtothewise.com</a></div><div class=3D"">(650) =
437-0741<span class=3D"Apple-tab-span" style=3D"white-space: pre;">		=
</span></div><div class=3D""><br =
class=3D""></div></span></span></span></span></span></div><div =
style=3D"word-wrap: break-word;" class=3D""><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px; color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-caps: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; =
widows: 2; word-spacing: 0px;">Email Delivery Blog: <a =
href=3D"https://wordtothewise.com/blog" =
class=3D"">https://wordtothewise.com/blog</a><span =
class=3D"Apple-tab-span" style=3D"white-space: pre;">	=
</span></span></span></span></span></span></div></span></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></body></html>=

--Apple-Mail=_89B538A1-5CC7-4064-9E59-9792CB6E1772--


From nobody Wed Jul 21 10:42:10 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16C4F3A210A for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:42:09 -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 EYPdBQWqAYlk for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 10:42:03 -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 5D7263A2101 for <dmarc@ietf.org>; Wed, 21 Jul 2021 10:42:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1626889319; bh=WCHqwPDW6cPjEBNG9ySXf3YF5NFCvPRWuqJ2wHlLK5c=; l=627; h=To:References:From:Date:In-Reply-To; b=C4LyJo0bSMRffYBnkhO5rXkQnUTw2Yf9+v12oGlNpdaMVPlAVj/+Vz+hbjFvIXFWx 7v3HW+TJjbhLjxkPN3FFrwj+0bxGVM8MFSqpSK0euwJU5Du6HpkaXZT71vIVeXad5y 4I165Xhs8+UJ6dKJmhfb/7q+nkj4XF8DAWuTlclTHki6+Bma4o30GbqIR6KIy
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 00000000005DC008.0000000060F85C67.000077F9; Wed, 21 Jul 2021 19:41:59 +0200
To: dmarc@ietf.org
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.com> <80374a84-6298-c45b-3fad-256bebd4f903@gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <96633d7e-7e7a-3012-9765-41f12872beab@tana.it>
Date: Wed, 21 Jul 2021 19:41:59 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <80374a84-6298-c45b-3fad-256bebd4f903@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/5RQIDCkIOs1mtUVzSyykMfypC3w>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 17:42:09 -0000

On Wed 21/Jul/2021 19:24:35 +0200 Dave Crocker wrote:
> On 7/21/2021 10:19 AM, John Levine wrote:
>> I suppose we could leave pct=0 as a hint to forwarders to turn on their DMARC 
>> evasion hacks.
> 
> Why doesn't seeing DMARC as seeing that it isn't p=none ought to suffice for 
> that?


Some lists operate the evasion hack, a.k.a. From: munging, only if the sender 
has p=quarantine or p=reject, some do it unconditionally, some only if the mail 
is outbound, some only if the receiver is mail.ru.  Behavior doesn't seem to be 
settled yet.

We should add a section on From: munging in the spec.


Best
Ale
-- 











From nobody Wed Jul 21 11:05:53 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 ABB173A2229 for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 11:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level: 
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 S4CGlAbjw26S for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 11:05:46 -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 717733A2223 for <dmarc@ietf.org>; Wed, 21 Jul 2021 11:05:46 -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=7ROYC9fSZPVEScRDAxnGAnwCV0duXZRM/0+xG9bcjpA=; b=Q94HHkaRJANo6g9G3XPajpoDe owfqC1wTu0JkZE30n4CNPCCnHHmr+Z3y1zRhyEyAAr2OwLzGwxE00w2osq9gj9KUDWlBvzlp+q3CR M7YKgqN42I7c7cXirbULM0CI4AeTy3LCxkRrgmu/MOLLp6KLnfsYC5BEckEDwdGMbKdLGkfmZ/b/i Umro5Yhtm5ik+0NFWWoxqSMkBj3iTBDQUWWqbPVxMI3F4FZqZ51zl+wH+aJslr+t4furomJWmiSNb alNySP5S4pXn59eeqXj7N6ZjDjqNbcOS++H1qfHGFpFcif217XH2hd2uL21CZyGdtRaOKq/nPkQuN /MPNm/iLw==;
Received: from dynamic-2a01-0c23-708c-4c00-8542-10d9-9af7-8c35.c23.pool.telefonica.de ([2a01:c23:708c:4c00:8542:10d9:9af7:8c35]) by mail.swznet.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <mail@wander.science>) id 1m6GbG-00076V-Ee for dmarc@ietf.org; Wed, 21 Jul 2021 20:05:43 +0200
To: dmarc@ietf.org
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.com> <80374a84-6298-c45b-3fad-256bebd4f903@gmail.com> <96633d7e-7e7a-3012-9765-41f12872beab@tana.it>
From: =?UTF-8?Q?Matth=c3=a4us_Wander?= <mail@wander.science>
Message-ID: <ee8556f0-2cfd-135a-b09e-92285f6628b2@wander.science>
Date: Wed, 21 Jul 2021 20:05:41 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <96633d7e-7e7a-3012-9765-41f12872beab@tana.it>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms080707070204080806020708"
X-SA-Exim-Connect-IP: 2a01:c23:708c:4c00:8542:10d9:9af7:8c35
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/5dJssCR3M7ZCXQsnFS7UvGOiUQQ>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 18:05:52 -0000

This is a cryptographically signed message in MIME format.

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

Alessandro Vesely wrote on 2021-07-21 19:41:
> Some lists operate the evasion hack, a.k.a. From: munging, only if the =

> sender has p=3Dquarantine or p=3Dreject, some do it unconditionally, so=
me=20
> only if the mail is outbound, some only if the receiver is mail.ru. =20
> Behavior doesn't seem to be settled yet.
>=20
> We should add a section on From: munging in the spec.

It's explained as mitigation in RFC7960:
<https://datatracker.ietf.org/doc/html/rfc7960#section-4.1.3.1>

What's seems to be missing is a recommendation to not change DMARC=20
validation behavior subject to p=3D or other conditions. A conditional=20
validation makes p=3Dnone less useful for monitoring of potential deliver=
y=20
problems.

Regards,
Matt


--------------ms080707070204080806020708
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
DxcNMjEwNzIxMTgwNTQxWjAvBgkqhkiG9w0BCQQxIgQgOOBMwYAYyZigQlMOt+QYsfMT+PGU
2AgRlWHGmzqnd7wwbAYJKoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAEC
MAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzAN
BggqhkiG9w0DAgIBKDCBzQYJKwYBBAGCNxAEMYG/MIG8MIGkMQswCQYDVQQGEwJVUzERMA8G
A1UECBMISWxsaW5vaXMxEDAOBgNVBAcTB0NoaWNhZ28xITAfBgNVBAoTGFRydXN0d2F2ZSBI
b2xkaW5ncywgSW5jLjEsMCoGA1UEAxMjVHJ1c3R3YXZlIFMvTUlNRSBTSEEyNTYgQ0EsIExl
dmVsIDExHzAdBgkqhkiG9w0BCQEWEGNhQHRydXN0d2F2ZS5jb20CEwb+/2M8pAx1sjrlBRDx
rmd75C0wgc8GCyqGSIb3DQEJEAILMYG/oIG8MIGkMQswCQYDVQQGEwJVUzERMA8GA1UECBMI
SWxsaW5vaXMxEDAOBgNVBAcTB0NoaWNhZ28xITAfBgNVBAoTGFRydXN0d2F2ZSBIb2xkaW5n
cywgSW5jLjEsMCoGA1UEAxMjVHJ1c3R3YXZlIFMvTUlNRSBTSEEyNTYgQ0EsIExldmVsIDEx
HzAdBgkqhkiG9w0BCQEWEGNhQHRydXN0d2F2ZS5jb20CEwb+/2M8pAx1sjrlBRDxrmd75C0w
DQYJKoZIhvcNAQEBBQAEggEAXBPDbOqybhbcE/+SOSGXGeHr9QipVeTYNgy1rL60Y4Nygqlx
Bpjh+UcNQHEROGifQ8zv7+h+CtiOtEqqKhDS6DJsrAgqxUqucJtOwV78KUyU01tce0MrBGEZ
6GqFcLhBClyVZdroW0DLWkgzuNldo7YC7OWNnUT+GScRMXKWVqDTzcURE7PpEdMsjLSeVVLO
2otcrLv8Jlqu2Y/fo/2n+rz1e2Q11faJxKHPNdojD639JeLSU/PJFlx/+0rWimiUy9uvR7+d
s5vd3TanCo5q3AIl5+vs7FsDfDqP78dSYg4xVKNr6EaZfrYqjpd7WhXSZhhFcm3FcqbMPJ40
g+7sCQAAAAAAAA==
--------------ms080707070204080806020708--


From nobody Wed Jul 21 12:00:48 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43F073A25CF for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 12:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I89KHhBrmjUz for <dmarc@ietfa.amsl.com>; Wed, 21 Jul 2021 12:00:38 -0700 (PDT)
Received: from mail-lf1-f44.google.com (mail-lf1-f44.google.com [209.85.167.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B5373A26A1 for <dmarc@ietf.org>; Wed, 21 Jul 2021 12:00:27 -0700 (PDT)
Received: by mail-lf1-f44.google.com with SMTP id y42so4715310lfa.3 for <dmarc@ietf.org>; Wed, 21 Jul 2021 12:00:27 -0700 (PDT)
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=KknaKavPl63u5u5BJlXp7DPl27/iq2od+2d3/Q1uAro=; b=LfJzQ8E6SB8gLFZ70ewAYhy+b9qJvKci9f14S5m1VR9Vjt5CYw7TJQEhkDbLlq87/3 fexwRue1/H/UNXpXbtI5dGCeG3LTIKAGHMXO7rYVpwtNOWQIFV0gvsiTDWXveoBIwqP3 GWJOu8FwycRWI1iX03avZT6HdqojKiZSDwxLkMjyMjx+hNcBWfrIYBH7J/Bo0AxXEDRb RUq4KUm2pjob2GeLX8ZWge3Ow8+f4fAMVyYixHXNQmUfP8LDHy2WKk22HOC+LjrLTHKh jr5KagWlzBaXKxSelGLFZ37wRTmfv7vEiTvzjFhaBzqttcdKn8BrYpfIYXc5v9QW/wgk Rgqw==
X-Gm-Message-State: AOAM530zuTEd3YOQL5NCqlIG3gRoGeYo8RfEiDxqLqCrfycIKR6a71Rq XaNd5awBXZBHc0rPVnbAXG8xRjaEGyPT59uMnE4=
X-Google-Smtp-Source: ABdhPJx9o49QF98VrNLbwXM4Z7fHNWV4pKrTQOp6h1I53m4PFTHUUAga4/Cc4vdmvGk3p8XpMTKYWu2aGymlxX70AmA=
X-Received: by 2002:ac2:44ad:: with SMTP id c13mr25788595lfm.377.1626894024208;  Wed, 21 Jul 2021 12:00:24 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <d80b0a14-0f4d-8266-8d42-8d9a6b02413d@tana.it> <CAH48ZfyLvECR_nwLmw6R6RnE4EZa8g_i7MJaF32d2qk4RBCKRA@mail.gmail.com> <1E1F7937-AFEC-4F5A-8A5A-229A99C94E8B@bluepopcorn.net> <CAH48ZfyTm1PSANTUmnqOy3aeiW4JHGbTsQ-m9xtSW9zFaCUZQA@mail.gmail.com> <CAH48ZfzEWaFPUG4Gfc2ckpyUEq-8L9kEZZv+LwqJcW88=0y6=w@mail.gmail.com> <CALaySJJ2ZFML2neecfgAhvfk_1EuMNGw6DwchLmmWWpbDJC+Zw@mail.gmail.com> <CAH48ZfxELhp+fHujdZzDADGz4MNoWsJLB7cU1d1cW065Xu8YBQ@mail.gmail.com>
In-Reply-To: <CAH48ZfxELhp+fHujdZzDADGz4MNoWsJLB7cU1d1cW065Xu8YBQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 21 Jul 2021 15:00:12 -0400
Message-ID: <CALaySJ+5i6vcii=YTTMQbr5gcdNSmOjNDp6ox8nK+izJDAe2_A@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/vPcrUQHJ083qjxfVS-D6jjSO44U>
Subject: Re: [dmarc-ietf] Fwd: Priming the Pump for Discussion - Ratchets
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 21 Jul 2021 19:00:47 -0000

>> I don't agree with the characterization of the second group.  I would
>> say that we are partitioning messages into these two groups:
>> - Those for which we can confirm that they originated in the domain
>> they say they did.
>> - Those for which we can not confirm that.
>
> When we use P=REJECT, we assert that anything which cannot be
> confirmed is unacceptable.   That makes for two pretty disjoint
> groups.   If Authentication is only to be used to validate a
> whitelisting decision, then a one-sided test would be sufficient.   In
> practice, the primary use for DMARCv1 is to block messages, and much
> of our discussion has been around the unwanted disposition that this
> places on mailing lists.

Indeed; there is definitely a problem between DMARC's p=reject and
mailing lists.

> DKIM treats an invalid signature as non-existent.   It also treats a
> DKIM signature as fully optional.   DMARCv1 changes the rules to
> gather more usable information from the message.    DMARCv1 with
> P=REJECT says that a message which lacks authentication is
> unacceptable, and since any message might be forwarded, it has
> effectively made DKIM non-optional..  So we have already modified the
> interpretation of DKIM.

Here, again, I disagree with your premise: we have not modified the
interpretation of DKIM.  Senders still decide whether to sign with
DKIM or not, and you're correct that it's a poor quality deployment to
use p=reject (or even quarantine) without also deploying DKIM signing.
But the interpretation has not changed: a valid DKIM signature still
means the same as it always did, and the absence of a valid DKIM
signature still means the same as well.  We have not created -- and
must not create -- an additional state that has been proscribed for a
number of good reasons.

> I have observed that IF the domain owner indicates that all messages
> originate with DKIM signatures, then the presence of a signature is no
> longer optional at the evaluation point.    As I have said previously,
> this provides a valid basis for partitioning messages between
> verified, ambiguous, and repudiated.   If you accept the premise that
> mailing list messages should not always be repudiated, then nothing we
> have done up to this point has provided a reliable way to repudiate.
> I am saying that this is a problem that we can fix.

It does not provide such a valid basis.  With your proposal, any
attacker can move her message from "repudiated" to "ambiguous" simply
by attaching a fake DKIM signature that she knows will never validate.
That alone is a reason this plan won't work.

> Yes, I have gone radical, and I am no longer willing to be limited by
> the design limitations of DMARCv1.

I think that's a fine approach, but it has to come with proposals that
do not violate the other protocols that we're relying on.

Barry


From nobody Thu Jul 22 11:32:17 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2A4A3A0D10 for <dmarc@ietfa.amsl.com>; Thu, 22 Jul 2021 11:32:15 -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 70ukcxCkhlcF for <dmarc@ietfa.amsl.com>; Thu, 22 Jul 2021 11:32:10 -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 63CA33A0D17 for <dmarc@ietf.org>; Thu, 22 Jul 2021 11:32:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1626978721; bh=ZOcMmHAdDuR7Qkne6MTv0k0hGI5PjqNgUVFDKY0glZM=; l=2449; h=To:References:From:Date:In-Reply-To; b=A4AWM9FL6jlmA0CHxUbyRZRzdOle6irJ+Hk/kTHMQcnCI0kI4uhhIHoylaJdTx+lY nOe866g0JCgLUxDihXlrwoRZL9uOi4/2Fn1AbPhDw3DypXue/0093Ig+eF5frxr9py NbXG4KHgHF2Bm+XN80rJhWXrV5xbv8GtDX2KE/XrQC9IeE9OO37JavvrRV8vE
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.0000000060F9B9A1.0000552D; Thu, 22 Jul 2021 20:32:01 +0200
To: dmarc@ietf.org
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.com> <80374a84-6298-c45b-3fad-256bebd4f903@gmail.com> <96633d7e-7e7a-3012-9765-41f12872beab@tana.it> <ee8556f0-2cfd-135a-b09e-92285f6628b2@wander.science>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <96988b78-3f5e-6e7c-a92e-66a59fc4beaf@tana.it>
Date: Thu, 22 Jul 2021 20:32:01 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <ee8556f0-2cfd-135a-b09e-92285f6628b2@wander.science>
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/fIaSfoxAvAHopEQKKVsdCHOEAbE>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 22 Jul 2021 18:32:16 -0000

On Wed 21/Jul/2021 20:05:41 +0200 Matthäus Wander wrote:
> Alessandro Vesely wrote on 2021-07-21 19:41:
>> Some lists operate the evasion hack, a.k.a. From: munging, only if the sender 
>> has p=quarantine or p=reject, some do it unconditionally, some only if the 
>> mail is outbound, some only if the receiver is mail.ru. Behavior doesn't seem 
>> to be settled yet.
>>
>> We should add a section on From: munging in the spec.
> 
> It's explained as mitigation in RFC7960:
> <https://datatracker.ietf.org/doc/html/rfc7960#section-4.1.3.1>
> 
> What's seems to be missing is a recommendation to not change DMARC validation 
> behavior subject to p= or other conditions. A conditional validation makes 
> p=none less useful for monitoring of potential delivery problems.


I agree that it's easier to deal with From: munging when it's done uniformly on 
all messages.  However, I'm not sure whether to actually RECOMMEND to do so.

How about something more or less like the following?

     *Mailing Lists*

     Mailing lists are characterized by changing the bounce address
     (RFC5321.MailFrom) on forwarding, see SMTP ([RFC5321]).  Described in
     Internet Mail Architecture ([RFC5598]) as a kind of Mediators, several
     mailing lists do additional changes that break most original DKIM
     signatures.  Before DMARC, this wasn't a problem.  As DMARC becomes more
     widely supported and generic mailbox providers public strict DMARC
     policies, mitigation as described in Interoperability Issues between DMARC
     and Indirect Email Flows ([RFC7960]) becomes necessary.

     We RECOMMEND that mailing list managers (MLMs) change the From: address
     (RFC5322.From) in order to become the owner of the main DMARC identifier.
     For example, if the incoming message has:

         From: Original Author <user@example.com>

     then the forwarded message SHOULD change it, for example like so:

         From: Original Author via list-tag <whatever@list.example.org>

     See [RFC7960] for a full explanation of whys and hows.

     For uniform behavior, MLMs are better off applying the same mitigation
     technique irrespective of the current content of any DMARC records.
     However, some MLMs are known to decide whether to apply that change or
     not based on the existence of an author's domain DMARC record and the
     value of the "p" tag therein.  In any case, MLMs MUST NOT consider the
     value of the "pct" tag in order to make such decision.


Best
Ale
-- 





















From nobody Thu Jul 22 11:51: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 373293A0DCF for <dmarc@ietfa.amsl.com>; Thu, 22 Jul 2021 11:51:19 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.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=OGtn/gfU; dkim=pass (2048-bit key) header.d=taugh.com header.b=eosv5W9f
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWEhyPTrOlnv for <dmarc@ietfa.amsl.com>; Thu, 22 Jul 2021 11:51: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 5E54D3A0DC9 for <dmarc@ietf.org>; Thu, 22 Jul 2021 11:51:13 -0700 (PDT)
Received: (qmail 29406 invoked from network); 22 Jul 2021 18:51:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=72dc.60f9be1b.k2107; bh=1Pv0Gk44ketb4iavqepy3GlDUfJ3wN2wQhctH/C7vgE=; b=OGtn/gfUyRyYnNLYCvhHE5KVfqQ6HO+ZHMtFiuW0XUx/XPQqZLVI25ulg6XQ8IKLnaagscL+W+reR/BP1r9uZOPnWaiPpCNAA3gRpH3gT3okhP0wF1Puuv7J15btpfiNbPudi6aigkmdH1FyOqrl1EZI+bcnVvslwF9NdJH/BwJOW2CJrXBUgvkgPSyd3yXDzet70T3g8diXYIkjM5eP4XhrLrNC0MrraR5tMHiwA141+XmqHikJQ8VX65MyYO6N/nQ8XEaaIeGx6t8n9mmE8BtqDthtdBWbZgCXYSZFIjQSkLmU6KsHXJaBlCudUyiz5vUtJD5VGBLF3YaKZ6eEUg==
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=72dc.60f9be1b.k2107; bh=1Pv0Gk44ketb4iavqepy3GlDUfJ3wN2wQhctH/C7vgE=; b=eosv5W9ftuwCfye8Bd2YtYW4cLplRpZkMHg2EVUfu2VDEAQYZ45tGk5XYXfkEfueL1lzBe1cFXR8lrG4fQ8Q58aJZU5pabb5oonzU2VrADU82MKstX1eP0fq4fhhqNKomZflig398woeLstkQEmLVIYvk2ObwSoKSDnw1LbLxtUnv7z2xpBRqhIsxmC1njNsEv44XxfYFj5y+yXpBHFhSYiIjk0xtK6KDNfysS88zSnY7SNyFsO/Y9PODcW2pjmK4FAC5HMdybLMbAYcycWRlDsZgSr5TRMikYWkO/U3EAebMpWVDQcsNov6XeH6yHOUEwyTi3e+DOdqg+VYdV6Kdw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 22 Jul 2021 18:51:06 -0000
Received: by ary.qy (Postfix, from userid 501) id 15C9F24DEDF0; Thu, 22 Jul 2021 14:51:05 -0400 (EDT)
Date: 22 Jul 2021 14:51:05 -0400
Message-Id: <20210722185106.15C9F24DEDF0@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <96988b78-3f5e-6e7c-a92e-66a59fc4beaf@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/CyaralOwISAmaQ4wHCcb547lMwg>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 22 Jul 2021 18:51:19 -0000

It appears that Alessandro Vesely  <vesely@tana.it> said:
>On Wed 21/Jul/2021 20:05:41 +0200 Matthäus Wander wrote:
>> Alessandro Vesely wrote on 2021-07-21 19:41:
>>> Some lists operate the evasion hack, a.k.a. From: munging, only if the sender 
>>> has p=quarantine or p=reject, some do it unconditionally, some only if the 
>>> mail is outbound, some only if the receiver is mail.ru. Behavior doesn't seem 
>>> to be settled yet.
>>>
>>> We should add a section on From: munging in the spec.
>> 
>> It's explained as mitigation in RFC7960:
>> <https://datatracker.ietf.org/doc/html/rfc7960#section-4.1.3.1>
>> 
>> What's seems to be missing is a recommendation to not change DMARC validation 
>> behavior subject to p= or other conditions. A conditional validation makes 
>> p=none less useful for monitoring of potential delivery problems.
>
>I agree that it's easier to deal with From: munging when it's done uniformly on 
>all messages.

Lists change messages in all sorts of ways, not just for DMARC, and if
you want to try to unmunge them (mostly a losing battle in my
experience) you end up with an ever growing list of patterns and
replacements.

>  However, I'm not sure whether to actually RECOMMEND to do so.

That's simple: no.  I can't imagine why we would expect list operators to take list
management instructions from the people who screwed up their lists in the first place.

Also remember that ARC is supposed eventually to remove the need for anti-DMARC munging.

R's,
John


From nobody Thu Jul 22 11:57:04 2021
Return-Path: <dilyan.palauzov@aegee.org>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F21A3A0E04 for <dmarc@ietfa.amsl.com>; Thu, 22 Jul 2021 11:56:53 -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, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=aegee.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xOfnIuZJp8xk for <dmarc@ietfa.amsl.com>; Thu, 22 Jul 2021 11:56:48 -0700 (PDT)
Received: from mail.aegee.org (mail.aegee.org [144.76.142.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 992E93A0DE9 for <dmarc@ietf.org>; Thu, 22 Jul 2021 11:56:47 -0700 (PDT)
Authentication-Results: mail.aegee.org/16MIuhbn1472910; auth=pass (LOGIN) smtp.auth=didopalauzov@aegee.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1626980204; i=dkim+MSA-tls@aegee.org; bh=Xis4aNmRkftOMaW7Qr7njN2qQucVes95c4q6glX7dCM=; h=Subject:From:To:Date:In-Reply-To:References; b=qS7nJ7w9hHjTPoTncLtzdc73BS1tjVizTtgLXA+9HbYZQrj3TsILMKy2jo4W/4Mua VX1J1mSKOSPa2c3lC+bR6j9HpslwkQqUokS/rCLM6Ni9Nn9W9GfB804p8Ypm2cyviX /sD+0594oX62PKnSj9sLd0JKGiuCtlHKm1pk8oDhxfoOhM7MZVj8z7vPSLHV8ilVXg brp26P1H89ruZ2LlkcJRmqWtVd0PtLylKLFKxFvACKzwEdob70ZT1XCyvzjP5xvzH0 2wRxrRcVvy11oBUAlLAeks7r6LAE9C/lgDT6g9xaxLPa5WNhMaNUj++9anxGwFJU/j IcCrYQtzJ9BtJPoVQyHWCLrupdOU3AdkCm41oKfbRO8lKJFfUbB91D1ssoC4vx2W+u bDJkFBSmxhHZn2xAgtxUwWkn2RSNc6DfAWzohbKn9wdpL900zBLYLV8z07C0hINX5s 4dAMPxKTG8Rdkh2O7YvibSgIjMfG7W1nXrueioN+Y3EmPU+73H+6n4WujpJjIsqe50 Y55G5b+Kh1EVGvVnVN2/Y6+Lce/M2jWUQng9LFaqxT7MxQsWpSf9W17ECYfaduVkZ1 Kn4LG0nCFshAZHyALnn+21ex/xHFURsZOkQ4CwKFqYn/OsYo8q1xs0wxyP0g2T+Hp6 zTCtD8tGhdIOFAhOuKZg0wNs=
Authentication-Results: mail.aegee.org/16MIuhbn1472910; dkim=none
Received: from [192.168.0.199] (87.118.146.153.topnet.bg [87.118.146.153] (may be forged)) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id 16MIuhbn1472910 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 22 Jul 2021 18:56:43 GMT
Message-ID: <0d6c75754507d828cc42238edbe74c1c950d3d38.camel@aegee.org>
From: =?UTF-8?Q?=D0=94=D0=B8=D0=BB=D1=8F=D0=BD_?= =?UTF-8?Q?=D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2?= <dilyan.palauzov@aegee.org>
To: Alessandro Vesely <vesely@tana.it>, dmarc@ietf.org
Date: Thu, 22 Jul 2021 21:56:42 +0300
In-Reply-To: <96988b78-3f5e-6e7c-a92e-66a59fc4beaf@tana.it>
References: <CAHej_8=yvgXP2WgHayhGU2Hg2E0RcNgZBFjfw1cM-qKWkTG-+w@mail.gmail.com> <CAH48Zfys9cwTskjjdeJ14Y-wDBuqLseDEEiNvwC9BonLAwMyVw@mail.gmail.com> <CAHej_8mTF7DFwDiCHBq_mK40E+vuFS6iB+MQ3Co3pS=ZdqXkcg@mail.gmail.com> <CAH48ZfwUAfwG93ZOoFp+Xbor-chZ-X0Pbd9OGdAs3mxsTFHxEw@mail.gmail.com> <CALaySJJwS=OvWZypbfTHsdjSLeMNFaq5TM7De0MrQO32fz-cHg@mail.gmail.com> <99d648e3-9f72-393a-a16e-225e340a8152@gmail.com> <AD1B50E9-8B8D-42E2-8BF6-818456D7505D@wordtothewise.com> <80374a84-6298-c45b-3fad-256bebd4f903@gmail.com> <96633d7e-7e7a-3012-9765-41f12872beab@tana.it> <ee8556f0-2cfd-135a-b09e-92285f6628b2@wander.science> <96988b78-3f5e-6e7c-a92e-66a59fc4beaf@tana.it>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.41.2 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/g2pcdJHBB-6747qUKZk_OjP8IK0>
Subject: Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 22 Jul 2021 18:57:03 -0000

Hello Ale,

please explain why this recommendation is done …

On Thu, 2021-07-22 at 20:32 +0200, Alessandro Vesely wrote:
> 
> How about something more or less like the following?
>      For uniform behavior, MLMs are better off applying the same
> mitigation
>      technique irrespective of the current content of any DMARC
> records.
>      However, some MLMs are known to decide whether to apply that
> change or
>      not based on the existence of an author's domain DMARC record and
> the
>      value of the "p" tag therein.  In any case, MLMs MUST NOT consider
> the
>      value of the "pct" tag in order to make such decision.
by appending:

The reason is, that operators can verify the correct setup, before
switching to a strict DMARC policy.  After installing “pct=0;p=reject"
the domain owner can verify by reading the aggregate reports that 100%
of the messages from the owned domain have aligned DKIM.  (Otherwise
MLM-NOT-mаngled messages will be reported as failed, too).


See also the last paragraph of 
https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-dmarcbis-02#section-6.7.4.2
Shortcomings of the "pct" Tag
>>>
   *  "0" - A request that zero percent of messages producing a DMARC
      "fail" result have the specified policy applied.  While this is
      seemingly a non-sensical request, this value has been given
      special meaning by some mailbox providers when combined with
      certain "p=" values to alter DMARC processing and/or reporting
for
      the domain publishing such a policy.
<<<

I think this paragraph needs to be changed.  Proposed new wording:

*  "0" - A request that zero percent of messages producing a DMARC
"fail" result have the specified policy applied.  While this is
seemingly a nonsensical request, MLM modifying the message shall
rewrite the From: header in this case.  This way the initial domain
owners, by evaluating aggregate reports, can verify, that their setup
is correct, before enforcing strict DMARC policy.

Greetings
  Дилян


From nobody Thu Jul 22 12:23:21 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C34463A0112 for <dmarc@ietfa.amsl.com>; Thu, 22 Jul 2021 12:23:19 -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 W-6iEqZytu8v for <dmarc@ietfa.amsl.com>; Thu, 22 Jul 2021 12:23:13 -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 AB0363A0100 for <dmarc@ietf.org>; Thu, 22 Jul 2021 12:23:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1626981784; bh=/yDMzNt1wA7gIbFX3Xe0tw/2XCEvpPKC6uJZjYrcjJA=; l=2177; h=To:References:From:Date:In-Reply-To; b=CldHFd6j3gvgH17Ih7I5MGCvU6pv/RkVJJECOLGqovOKxEsRtJ8o8MNXOUnNJWET9 8MkeI52zE+q61HONu+EaL/XRbKqRqmUKlH4xKA3sAty9EHLs9UK/xU+rHNTv6w5q6/ jwIvCFvy5oi0irXLEDDnNoYiNdoezCGN+or73FKFxlcyzt4asigetGZYLOFiw
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 00000000005DC042.0000000060F9C598.00005AE2; Thu, 22 Jul 2021 21:23:04 +0200
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210722185106.15C9F24DEDF0@ary.qy>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <8b90752d-d4ea-e242-4c59-1b340f9bc400@tana.it>
Date: Thu, 22 Jul 2021 21:23:04 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <20210722185106.15C9F24DEDF0@ary.qy>
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/MfqGWZP5KlcrY4QNhLU1sLAU9Uc>
Subject: Re: [dmarc-ietf] From: munging, was Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 22 Jul 2021 19:23:20 -0000

On Thu 22/Jul/2021 20:51:05 +0200 John Levine wrote:
> It appears that Alessandro Vesely  <vesely@tana.it> said:
>>On Wed 21/Jul/2021 20:05:41 +0200 Matthäus Wander wrote:
>>> Alessandro Vesely wrote on 2021-07-21 19:41:
>>>> Some lists operate the evasion hack, a.k.a. From: munging, only if the sender 
>>>> has p=quarantine or p=reject, some do it unconditionally, some only if the 
>>>> mail is outbound, some only if the receiver is mail.ru. Behavior doesn't seem 
>>>> to be settled yet.
>>>>
>>>> We should add a section on From: munging in the spec.
>>> 
>>> It's explained as mitigation in RFC7960:
>>> <https://datatracker.ietf.org/doc/html/rfc7960#section-4.1.3.1>
>>> 
>>> What's seems to be missing is a recommendation to not change DMARC validation 
>>> behavior subject to p= or other conditions. A conditional validation makes 
>>> p=none less useful for monitoring of potential delivery problems.
>>
>>I agree that it's easier to deal with From: munging when it's done uniformly on 
>>all messages.
> 
> Lists change messages in all sorts of ways, not just for DMARC, and if
> you want to try to unmunge them (mostly a losing battle in my
> experience) you end up with an ever growing list of patterns and
> replacements.


Yeah, for example X-Mailman-Original-DKIM-Signature.  It still seems to be 
manageable, though.


>>  However, I'm not sure whether to actually RECOMMEND to do so.
> 
> That's simple: no.  I can't imagine why we would expect list operators to take list
> management instructions from the people who screwed up their lists in the first place.


:-)

Yet, From: munging itself resulted from cooperation between dmarcers and MLM 
people, didn't it?


> Also remember that ARC is supposed eventually to remove the need for anti-DMARC munging.


What I imagine can happen is that receivers who can work out how to trust ARC 
will unmunge messages based on Original-From:, Author:, or similar field when 
ARC validates it.  Unmunging based on undoing list changes is an alternative. 
Neither method seems to reliably work every time for every one.  Therefore, 
From: munging is going to stay.


Best
Ale
-- 














From nobody Thu Jul 22 12:51:38 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 AC0AC3A07D2 for <dmarc@ietfa.amsl.com>; Thu, 22 Jul 2021 12:51:37 -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=omPiEEDB; dkim=pass (2048-bit key) header.d=taugh.com header.b=fC0VmoD4
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0NretbDgTIk9 for <dmarc@ietfa.amsl.com>; Thu, 22 Jul 2021 12:51:31 -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 9EFBB3A07D0 for <dmarc@ietf.org>; Thu, 22 Jul 2021 12:51:31 -0700 (PDT)
Received: (qmail 48224 invoked from network); 22 Jul 2021 19:51:28 -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=bc5b.60f9cc40.k2107; bh=IZrvsgjvNnV0W7BZbetQgFIb0bvFd14JBhi6LXKcSjE=; b=omPiEEDBJ2pQO70DiHlIMGCnFIoXJ1Y+B+GEyqDO0IwPZzuxW5KZ2p+6N+8WhKPBsbk0ee2dqQhnptAOSznYzBqIGdKWfppv+Ij/LsaqItptV7E51vS839mSorPa7ArEmkahWVXbue41Z0W0S4rzn5U1hn0VZ1CTdPGLgHOCjAzX4fIMWkYtZvQg9EsK+oD/xPEegAdOtGJZKGVhFU8v8Njz20QxAvZKp2zzI34b7S+Dv/hbORRsjGku154p56cxPFo9OtUmx7GOnqOuAHSxRcuRD1Er43dqdaK+oOPA+ogCk5YPWtFCnZqHGOCpbdzQlImvuoKpSGEjYaFZF1I+fQ==
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=bc5b.60f9cc40.k2107; bh=IZrvsgjvNnV0W7BZbetQgFIb0bvFd14JBhi6LXKcSjE=; b=fC0VmoD4hxJbdANnBNgnLMRzGXQ3aKB5Wc0ZHoA3A9daGiisq4OtP7oDQclqXAK52+QyeAUziKLxhmnuhXEUeUpYpEC/moiKHYJ7J1hQWtpJCD+K8IDBcaykxuMcTR02D7s/6Njh3SbQarPd54P2P45QWopf8CvoX9ekbHjKJYhJAzGCarkH/xk0A/eAei8JTxSCfvj9Y6Qx6zQ1l2sPnybv/MSZiTplHjTHVCmcZ1aR3PxCsUJhocfpaYOumz9NJOyU9h/tL/isZ8WUTDjNg+hCjXaALy7MrOcr3pLVzEqR0RQG4eL/3XaFJ5nYsbPJfA6Mp5FLs2GhYYcOxGoIJw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 22 Jul 2021 19:51:28 -0000
Received: by ary.qy (Postfix, from userid 501) id 532BE24DFA1C; Thu, 22 Jul 2021 15:51:25 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 7B6C824DF9FE; Thu, 22 Jul 2021 15:51:25 -0400 (EDT)
Date: 22 Jul 2021 15:51:25 -0400
Message-ID: <88e9cce0-5510-7818-275-525ab5fc97ff@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: <8b90752d-d4ea-e242-4c59-1b340f9bc400@tana.it>
References: <20210722185106.15C9F24DEDF0@ary.qy> <8b90752d-d4ea-e242-4c59-1b340f9bc400@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/hh0LZHRK_aWh-wE6O8lLIpCjhfc>
Subject: Re: [dmarc-ietf] From: munging, was Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 22 Jul 2021 19:51:38 -0000

On Thu, 22 Jul 2021, Alessandro Vesely wrote:
>>>  However, I'm not sure whether to actually RECOMMEND to do so.
>> That's simple: no.

> Yet, From: munging itself resulted from cooperation between dmarcers and MLM 
> people, didn't it?

No, it came from AOL and Yahoo unilateraly using DMARC to outsource the 
cost of their security breaches, with the entirely predictable (and 
predicted) effect of breaking every mailing list in the world.  List 
operators had to scramble and come up with some hack to mitigate the 
damage when I became clear that AOL and Yahoo did not care.

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


From nobody Fri Jul 23 03:08:30 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 724903A10E9 for <dmarc@ietfa.amsl.com>; Fri, 23 Jul 2021 03:08:28 -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 GBFz-H0v7bzC for <dmarc@ietfa.amsl.com>; Fri, 23 Jul 2021 03:08: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 15BFE3A10E7 for <dmarc@ietf.org>; Fri, 23 Jul 2021 03:08:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1627034896; bh=SI2bPUMXaOumjdxWTMyi9WZKBwdU0rB2qBcXWVJkXe0=; l=948; h=To:References:From:Date:In-Reply-To; b=CXGqm+QKxqu2tlGPahNHJiKVYIMgb0f0TnOiFEDsQccpnuXhOtMkDIswjEmzKgQXh cBx7tYJFXD3oe9A7MIhnUswXEPeE2FR6ntisCOYKHwx+fBkpoJJ4d9NTLlfBBSbm+F PptEGIuK6EjvVnR8anjg91cUcY56WTjtE6BBcfQwXM1x+V7jEO9VH+41HBE35
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC0CB.0000000060FA9510.000002E3; Fri, 23 Jul 2021 12:08:16 +0200
To: John R Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20210722185106.15C9F24DEDF0@ary.qy> <8b90752d-d4ea-e242-4c59-1b340f9bc400@tana.it> <88e9cce0-5510-7818-275-525ab5fc97ff@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <128283c2-2607-ecf1-b261-3839a52383e1@tana.it>
Date: Fri, 23 Jul 2021 12:08:16 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <88e9cce0-5510-7818-275-525ab5fc97ff@taugh.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PtLaT9Wf_tPwJI9fyB1qtetfPH8>
Subject: Re: [dmarc-ietf] From: munging, was Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 23 Jul 2021 10:08:29 -0000

On Thu 22/Jul/2021 21:51:25 +0200 John R Levine wrote:
> On Thu, 22 Jul 2021, Alessandro Vesely wrote:
>>>>  However, I'm not sure whether to actually RECOMMEND to do so.
>>> That's simple: no.
>> Yet, From: munging itself resulted from cooperation between dmarcers and MLM 
>> people, didn't it?
> 
> No, it came from AOL and Yahoo unilaterally using DMARC to outsource the cost of 
> their security breaches, with the entirely predictable (and predicted) effect 
> of breaking every mailing list in the world.  List operators had to scramble 
> and come up with some hack to mitigate the damage when I became clear that AOL 
> and Yahoo did not care.


That certainly was the efficient cause of the trouble.  But you must remember 
that the possible solutions were discussed on this list with MLM participants a 
few years ago.  For example:

https://mailarchive.ietf.org/arch/msg/dmarc/KvSFv66Mz8UipXQ0477UgO5WKio/


Best
Ale
-- 












From nobody Fri Jul 23 05:23:12 2021
Return-Path: <me@junc.eu>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B60C3A16A2 for <dmarc@ietfa.amsl.com>; Fri, 23 Jul 2021 05:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level: 
X-Spam-Status: No, score=-4.4 tagged_above=-999 required=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_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=junc.eu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LaiqwUUzCnhf for <dmarc@ietfa.amsl.com>; Fri, 23 Jul 2021 05:23:04 -0700 (PDT)
Received: from mx.junc.eu (mx.junc.eu [172.105.72.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B23453A16A0 for <dmarc@ietf.org>; Fri, 23 Jul 2021 05:23:03 -0700 (PDT)
Received: from localhost.junc.eu (localhost.junc.eu [127.0.0.1]) by mx.junc.eu (Postfix) with SMTP id 468337FA9C for <dmarc@ietf.org>; Fri, 23 Jul 2021 12:23:01 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junc.eu; i=@junc.eu; l=725; q=dns/txt; s=default; t=1627042981; h=from : subject : date : to; bh=aaGQyTj7LAS4HVN6BZfIMRR4e09reKlbE9wEMp4X0vg=; b=phg2t+PkpfnOOKMQRIJlRGGFJpTYI7EFZixG43LfPSrKxHhwPaL2ycTSvD8R3QW2LxeUi dC1qLLXF1LRYZLZkTyy6bXHdDomK0kYDpMl+JmEh6Nsf598m2wvypSjM35M6p6FseoMtS6F 42zg1RvfmPcTIMv/YDk1Lm8ddcwXoA4ZYeh/ilBI0kfm/aB2uRIFbvfDst1leHSGAL32Ydj gzVtKHLHSlH2xOrUaMIHik4VSMU2ix8RtzKfrLlqoqYvOeq0Tt9SaRNh4rb2kD8cXb8w2sh ss5Lmsabn9YbyNW5Zr42y/G6DnLfiCAiOUk22EA65SGaSMOi/Cm/NDGIE+Qw==
Received: from localhost.junc.eu (localhost.junc.eu [IPv6:::1]) by mx.junc.eu (Postfix) with ESMTPSA id 252D87FA8A for <dmarc@ietf.org>; Fri, 23 Jul 2021 12:23:01 +0000 (UTC)
MIME-Version: 1.0
Date: Fri, 23 Jul 2021 14:23:01 +0200
From: Benny Pedersen <me@junc.eu>
To: dmarc@ietf.org
In-Reply-To: <128283c2-2607-ecf1-b261-3839a52383e1@tana.it>
References: <20210722185106.15C9F24DEDF0@ary.qy> <8b90752d-d4ea-e242-4c59-1b340f9bc400@tana.it> <88e9cce0-5510-7818-275-525ab5fc97ff@taugh.com> <128283c2-2607-ecf1-b261-3839a52383e1@tana.it>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <324e6035bd8909039f0d16242a2f403f@junc.eu>
X-Sender: me@junc.eu
Organization: junc.eu
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/M6HKN-G-31VbOedvKeKB9r2TlBU>
Subject: Re: [dmarc-ietf] From: munging, was Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 23 Jul 2021 12:23:10 -0000

On 2021-07-23 12:08, Alessandro Vesely wrote:

> https://mailarchive.ietf.org/arch/msg/dmarc/KvSFv66Mz8UipXQ0477UgO5WKio/

all this is solved if maillists stop dkim signing of non origination 
postings and only do the arc sealing so all dmarc testers can see 
originating spf, dkim pass

take sendgrid, thay forwarded netflix phishing emails, and thay belived 
dmarc protected there ignorance to some kind out off there services

never trust a forwarding server that does there own dkim signing, period

dmarc needs openARC testing to all above to work, then maillist can 
break maillists to there own stupid needs without breaking dkim cant be 
verified on dmarc recipient servers

hope the best for the future


From nobody Sat Jul 24 03:23:26 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 14DBE3A35A7 for <dmarc@ietfa.amsl.com>; Sat, 24 Jul 2021 03:23: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, 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 TfKDXlnHOIDN for <dmarc@ietfa.amsl.com>; Sat, 24 Jul 2021 03:23:20 -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 D13763A3511 for <dmarc@ietf.org>; Sat, 24 Jul 2021 03:23:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1627122191; bh=YGkoI75WlSY/2Dnl28nLSPHOIS4QonOtVEUzt3Yl53Y=; l=1090; h=To:References:From:Date:In-Reply-To; b=BNFEhOdZUjDiRFfasl5vXqgjJXPc1KBKGW625KXWxQFzocLbDDuwYWcTUIeQeFUou FeZkGrAcg57TkVfIEVBKZ1k4dq14C/F2A34GcnxUZlxH4O575+MTuT6Ri1VJnLXc6U xSMNDH8/8ppIU/80bIO3WlwGnJ5JX0oQL5Dw+Vurl/oBW7QPZfLxmIUE42lvV
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 00000000005DC0E2.0000000060FBEA0F.000020FF; Sat, 24 Jul 2021 12:23:11 +0200
To: dmarc@ietf.org
References: <20210722185106.15C9F24DEDF0@ary.qy> <8b90752d-d4ea-e242-4c59-1b340f9bc400@tana.it> <88e9cce0-5510-7818-275-525ab5fc97ff@taugh.com> <128283c2-2607-ecf1-b261-3839a52383e1@tana.it> <324e6035bd8909039f0d16242a2f403f@junc.eu>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <74841b3d-29e6-d54f-47b8-652a2f1eb5b9@tana.it>
Date: Sat, 24 Jul 2021 12:23:11 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <324e6035bd8909039f0d16242a2f403f@junc.eu>
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/JZCISXLEk8jhHfsO-GHpMXuAfdY>
Subject: Re: [dmarc-ietf] From: munging, was Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 24 Jul 2021 10:23:25 -0000

On Fri 23/Jul/2021 14:23:01 +0200 Benny Pedersen wrote:
> On 2021-07-23 12:08, Alessandro Vesely wrote:
> 
>> https://mailarchive.ietf.org/arch/msg/dmarc/KvSFv66Mz8UipXQ0477UgO5WKio/
> 
> all this is solved if maillists stop dkim signing of non origination postings 
> and only do the arc sealing so all dmarc testers can see originating spf, dkim 
> pass


ARC doesn't exclude DKIM.  Actually, the latter has a larger use base and it 
would be an error to stop supporting it.


> take sendgrid, thay forwarded netflix phishing emails, and thay belived dmarc 
> protected there ignorance to some kind out off there services
> 
> never trust a forwarding server that does there own dkim signing, period


We always knew that verified authenticity wouldn't imply trust, irrespective of 
forwarding.


> dmarc needs openARC testing to all above to work, then maillist can break 
> maillists to there own stupid needs without breaking dkim cant be verified on 
> dmarc recipient servers


ARC is not a part of DMARC, despite the acronym being a substring.


Best
Ale
-- 


















From nobody Sun Jul 25 03:00:15 2021
Return-Path: <johnl@taugh.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 909BE3A236E for <dmarc@ietfa.amsl.com>; Sun, 25 Jul 2021 03:00:14 -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 t1luxYqqxUXW for <dmarc@ietfa.amsl.com>; Sun, 25 Jul 2021 03:00:09 -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 552113A236D for <dmarc@ietf.org>; Sun, 25 Jul 2021 03:00:09 -0700 (PDT)
Received: (qmail 9478 invoked by uid 100); 25 Jul 2021 10:00:06 -0000
Date: 25 Jul 2021 09:59:44 -0000
Message-ID: <20210725095944.9477.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/IUmVjix-DtuFDVWhfAn_54kbjDk>
Subject: [dmarc-ietf] Messages from the dmarc list for the week ending Sun Jul 25 06:00:05 2021
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Jul 2021 10:00:15 -0000

   Count    |      Bytes     |  Who
------------+----------------+-------
 36 ( 100%) | 284522 ( 100%) | Total
  7 (19.4%) |  33265 (11.7%) | John Levine <johnl@taugh.com>
  6 (16.7%) |  40245 (14.1%) | Alessandro Vesely <vesely@tana.it>
  5 (13.9%) |  42204 (14.8%) | Barry Leiba <barryleiba@computer.org>
  5 (13.9%) |  29279 (10.3%) | Dave Crocker <dcrocker@gmail.com>
  3 ( 8.3%) |  47345 (16.6%) | Laura Atkins <laura@wordtothewise.com>
  2 ( 5.6%) |  40772 (14.3%) | Douglas Foster <dougfoster.emailstandards@gmail.com>
  2 ( 5.6%) |  13484 ( 4.7%) | Dotzero <dotzero@gmail.com>
  2 ( 5.6%) |   8692 ( 3.1%) | Benny Pedersen <me@junc.eu>
  1 ( 2.8%) |  11040 ( 3.9%) | Matthäus Wander <mail@wander.science>
  1 ( 2.8%) |   6710 ( 2.4%) | Дилян Палаузов <dilyan.palauzov@aegee.org>
  1 ( 2.8%) |   6036 ( 2.1%) | Steve Siirila <sfs@umn.edu>
  1 ( 2.8%) |   5450 ( 1.9%) | tjw ietf <tjw.ietf@gmail.com>


From nobody Sun Jul 25 10:28: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 6ED203A32D9 for <dmarc@ietfa.amsl.com>; Sun, 25 Jul 2021 10:28: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, 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 nVHUUgjVLEpG for <dmarc@ietfa.amsl.com>; Sun, 25 Jul 2021 10:28:25 -0700 (PDT)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 077FA3A32D8 for <dmarc@ietf.org>; Sun, 25 Jul 2021 10:28:24 -0700 (PDT)
Received: by mail-ot1-x32b.google.com with SMTP id v8-20020a0568301bc8b02904d5b4e5ca3aso6739016ota.13 for <dmarc@ietf.org>; Sun, 25 Jul 2021 10:28: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=mlbltPa0d4xAzAE+TP7h1p8vbwAHxPCXD4JN2k0/vTs=; b=M3FDxCqJivoU+dwIflFVWnTd9KpupC6qGFl2UiMtNrRT/uT/IAZnvs/ojRJcC8d2MJ hZIyoruF+/1A7d/SRizTh2R6dMwKFZ3jEmgHZSLizK8ShrVhigf08NiPom6nnBWzUhD5 MUeCCKkBf7+oJaGFFH8apsIBNGtgpKjl5x7A9eNAP3RutpWtUDvzpd0y7tJqUteRK/gS ReErX5iP+6qRBkPrK5FC0h2+njdPpPpyWF+DKpwQhwV6KPa2hViuw+K/RM+wdIjDQQ83 F6xvA8NOpQ6YiNDmQ/b7Q2o2+FY5eNGRzmmBz8m5uXS4+q1jVQyHe9J2hBaKU9pC+RA8 MWew==
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=mlbltPa0d4xAzAE+TP7h1p8vbwAHxPCXD4JN2k0/vTs=; b=QIp9WkenW3E9bapK6f9rn/dnhqg5EtNpEvy5HomxmEjyb0BwrmNWxzsQZ5+nAZSQuB QFZ++THjHIl39ElTfvlgIuyQMvrD3kSKaX5cOz5APv+4vVNIlzVwh7chYnh1ECVs1PMj vpcxPkDyV/gKwrsphxYsMGXVSmBEAW0ehde45/loYY77aIS0UMcjWHhQv5ydZ2JQsu0B lv/9iTXCYhM6QdBjtcHt7L/UNZAJVa5rwFyY1hExmKf/Oz44ji+su/JycEOVc0+g54rw qEQZzrlC1v1VeyppRwNNPnspBXMd7cI1Tdvts7nssLiH+fVStlBX++uyCxFSAHcm2OxJ nPiQ==
X-Gm-Message-State: AOAM530YWHTzIeUhfJqFP3Am0O42CXQa0FqOyhWSTzrzhaUsPcKfocBb IZrWf70e+T9gcG2FjP4WfTRQYwDKz2UJLbyE+9/TqaQANnk=
X-Google-Smtp-Source: ABdhPJzIqKu+eK+h6Na344Fo6VGvivx/WTZt7A65DIcgsbS+xeKnSQG3jaKCvl8PSYl2IVZ601obnKnfrJBkMNYm9AQ=
X-Received: by 2002:a9d:6f84:: with SMTP id h4mr9778869otq.240.1627234102796;  Sun, 25 Jul 2021 10:28:22 -0700 (PDT)
MIME-Version: 1.0
References: <20210722185106.15C9F24DEDF0@ary.qy> <8b90752d-d4ea-e242-4c59-1b340f9bc400@tana.it> <88e9cce0-5510-7818-275-525ab5fc97ff@taugh.com> <128283c2-2607-ecf1-b261-3839a52383e1@tana.it> <324e6035bd8909039f0d16242a2f403f@junc.eu> <74841b3d-29e6-d54f-47b8-652a2f1eb5b9@tana.it>
In-Reply-To: <74841b3d-29e6-d54f-47b8-652a2f1eb5b9@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sun, 25 Jul 2021 13:28:12 -0400
Message-ID: <CAH48ZfxHe6GGGvuv6qkOvyVz3xhemdFK5MDNBo9zCsoGjx-VHQ@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a9e6c305c7f5f6f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ATYdvPjXLdkS_Ut7Dvm891Z0Gfs>
Subject: Re: [dmarc-ietf] From: munging, was Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 25 Jul 2021 17:28:27 -0000

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

>
> Ale said:
>
"ARC is not a part of DMARC, despite the acronym being a substring."

Is this really true?  Some time ago, the chairs said that ARC was the
candidate solution to the mailing list problem, and that DMARCbis would not
fly without a mailing list solution.  More recently, we seem to be
proceeding with a plan to leave the based design of DMARCv1 untouched, with
all of its limitations.   So perhaps the politics have changed.

I have tried to fall in love with ARC, without success.   I have not seen
anyone describe an algorithm for parsing an ARC chain to draw a
conclusion, although the effort seems to require an extraordinary amount of
software development and processing effort.  Having the outlines of this
algorithm seems important, if we expect both implementers and evaluators
for ARC.

But even with an algorithm, the goal seems elusive.  Since any liar can
start an ARC chain and insert a set of unverifiable A-R assertions, it
seems that trusting an ARC set requires prior knowledge of whom to trust,
and when that information is available, ARC chain evaluation becomes
redundant.

Doug Foster

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">Ale said:<br></blockquote><div>&quot;ARC is not a part o=
f DMARC, despite the acronym being a substring.&quot;</div><div><br></div><=
div>Is this really true?=C2=A0 Some time ago, the chairs said that ARC was =
the candidate solution to the mailing list problem, and that DMARCbis would=
 not fly without a mailing list solution.=C2=A0 More recently, we seem to b=
e proceeding with a plan to leave the based=C2=A0design of DMARCv1 untouche=
d, with all of its limitations.=C2=A0 =C2=A0So perhaps the politics have ch=
anged.</div><div><br></div><div>I have tried to fall in love with ARC,=C2=
=A0without=C2=A0success.=C2=A0 =C2=A0I have not seen anyone describe an=C2=
=A0algorithm for parsing an ARC chain to draw a conclusion,=C2=A0although=
=C2=A0the effort seems to require an extraordinary amount of software devel=
opment and processing effort.=C2=A0 Having the outlines of this algorithm s=
eems important, if we expect both implementers and evaluators for ARC.=C2=
=A0 =C2=A0</div><div><br></div><div>But even with an algorithm, the goal se=
ems elusive.=C2=A0 Since any liar can start an ARC chain and insert a set o=
f unverifiable A-R assertions, it seems that trusting=C2=A0an ARC set requi=
res prior knowledge of whom to trust, and when that information is availabl=
e, ARC chain evaluation becomes redundant.</div><div><br></div><div>Doug Fo=
ster</div></div></div>

--000000000000a9e6c305c7f5f6f2--


From nobody Mon Jul 26 01:38:11 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1170A3A2109 for <dmarc@ietfa.amsl.com>; Mon, 26 Jul 2021 01:38:10 -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 SmQPfHuGSgGc for <dmarc@ietfa.amsl.com>; Mon, 26 Jul 2021 01:38:05 -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 22A703A1C10 for <dmarc@ietf.org>; Mon, 26 Jul 2021 01:38:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1627288680; bh=fa96hHyJbCrZKF7f3Mt8Yj2RLiYZAWO+oXpZvcFeN78=; l=1593; h=To:Cc:References:From:Date:In-Reply-To; b=AJqg38uu+mYD9MGoAbbwFu4/LznfmkWiN44ovI8cLIeoALh307vSZ6+Ki/5dM1iRc z/xhRcYmAPnhCVkw1tyDTXjjvpIJ1p4YFXXuzac19uUWSZoSBvzg1UXqisFJv/Kghr WkotBFMbpQI6r594WkW1e32aZe3+3+CVX66h7GXk1ZYu4SGigtD1dSp0utb9C
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 00000000005DC008.0000000060FE7468.00003DE7; Mon, 26 Jul 2021 10:38:00 +0200
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
References: <20210722185106.15C9F24DEDF0@ary.qy> <8b90752d-d4ea-e242-4c59-1b340f9bc400@tana.it> <88e9cce0-5510-7818-275-525ab5fc97ff@taugh.com> <128283c2-2607-ecf1-b261-3839a52383e1@tana.it> <324e6035bd8909039f0d16242a2f403f@junc.eu> <74841b3d-29e6-d54f-47b8-652a2f1eb5b9@tana.it> <CAH48ZfxHe6GGGvuv6qkOvyVz3xhemdFK5MDNBo9zCsoGjx-VHQ@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <51862153-274c-09df-4690-983470a30131@tana.it>
Date: Mon, 26 Jul 2021 10:38:00 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfxHe6GGGvuv6qkOvyVz3xhemdFK5MDNBo9zCsoGjx-VHQ@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/GGnYQzThFEN21HLNFs4GuqmhP3Q>
Subject: Re: [dmarc-ietf] From: munging, was Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 26 Jul 2021 08:38:10 -0000

On Sun 25/Jul/2021 19:28:12 +0200 Douglas Foster wrote:
>     Ale said:
> 
>> "ARC is not a part of DMARC, despite the acronym being a substring."
> 
> Is this really true?  Some time ago, the chairs said that ARC was the candidate 
> solution to the mailing list problem, and that DMARCbis would not fly without a 
> mailing list solution.


The mailing list solution that seems to be emerging is From: munging.  There 
are other possibilities, see Section 4.1.3.3 of rfc7960.  A MLM needs to adopt 
a solution that works for all subscribers, not only for the ones whose 
receivers implement DKIM or some other solution-specific protocol.

There are several ways to munge From: in order to minimize end-user 
inconveniences.  Among these, there are cooperative methods that allow 
receivers to unmunge From: on delivery.  The MLM munges From:, which works for 
all, but some of the receivers restore the original From: value based on 
additional authentication techniques.  ARC is one such technique.  MLM 
transformation reversion is another one.

Are such additional authentication techniques, that help repairing DMARC 
damage, themselves part of DMARC?  In a proper sense they're not, in some other 
sense however they have to be.  For example, for questions concerning DMARC 
reports:

* It has been established that ARC data is part of aggregate reports, but it's 
not clear what data is to be included in which reports.

* In what cases should results of MLM transformation reversion be included in 
the aggregate reports destined to the original author domain?


Best
Ale
-- 


















From nobody Mon Jul 26 09:06:52 2021
Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB1463A1BB3 for <dmarc@ietfa.amsl.com>; Mon, 26 Jul 2021 09:06:50 -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, HEADER_FROM_DIFFERENT_DOMAINS=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=ioioLuib; dkim=pass (2048-bit key) header.d=taugh.com header.b=hQugsnvu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c3cnyy2iKy-2 for <dmarc@ietfa.amsl.com>; Mon, 26 Jul 2021 09:06:45 -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 915FC3A1BB2 for <dmarc@ietf.org>; Mon, 26 Jul 2021 09:06:45 -0700 (PDT)
Received: (qmail 55003 invoked from network); 26 Jul 2021 16:06:43 -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=d6d8.60fedd93.k2107; bh=MOR05ygOLSIHL+qoerSwG+1TKp9J1XoZPvp5eOcjBLw=; b=ioioLuibewekmHKezlrbDZxGxTAF/4BAWRGSaUOXc33pKOJ2Se/EE54x1t7a8awcVtOlhh7ku7PDesIe0PnKciWQ+IjYXuCbMZQbEZscKrOTiNjD8MBKwrYoy2qOgE3RUWSQ9Wv6GgrjX5NK2bNdDlTew3kaSEkAY+3ZIeH5FlHvGRTzSG3RnyuE/VNuBT1H0cBC2kMkJAOI1pwfITrGq0lGuB4EBDBl8T8nLN7Yc9UC29ETpt849VOEwVYz/mBRpbr/asYZpAvOWi52xZArHrxTDVcjOApNXacL3bLqbS1D8GF0aYjBQkxpXYlxrdZjvROr+Awe9PfTQxptYkqn+A==
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=d6d8.60fedd93.k2107; bh=MOR05ygOLSIHL+qoerSwG+1TKp9J1XoZPvp5eOcjBLw=; b=hQugsnvuuoWQhi9gpm980a27ui0faij3Fgr49eXe0tZFynD+BuMK4F7MBB2vT7CXdvZTtXgGHH84+V2Kf9n/be0pvsT4wzT4RyqmpjLqLKF3xa1jAr9IWyclkOtJO7W02TU31R/Qxm8/8X9enFeWxqbQcEjg8sR8SP2Nwq6XO4KBj6E75Jcna29y6Uo2/XXN1J3GRV76wau13t6rZr9Q8Wnj2FBQP1mdpJXE6FTEX6HLOnNY79VOtmnak62YYBbv3rvYiAN7NRmLHM+iNVhYg0hd/qT4w8Dl7wn+Iwos40qiWErLeXhTFXIelixtxOUf87Y/bYT8mloSBRUE47kGpQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 26 Jul 2021 16:06:43 -0000
Received: by ary.qy (Postfix, from userid 501) id F16622502E24; Mon, 26 Jul 2021 12:06:41 -0400 (EDT)
Date: 26 Jul 2021 12:06:41 -0400
Message-Id: <20210726160641.F16622502E24@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dougfoster.emailstandards@gmail.com
In-Reply-To: <CAH48ZfxHe6GGGvuv6qkOvyVz3xhemdFK5MDNBo9zCsoGjx-VHQ@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/as5YKqj_dVhY1E1-DOz7H-Sc7Rk>
Subject: Re: [dmarc-ietf] From: munging, was Ratchets - Disallow PCT 1-99
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 26 Jul 2021 16:06:51 -0000

It appears that Douglas Foster  <dougfoster.emailstandards@gmail.com> said:
>But even with an algorithm, the goal seems elusive.  Since any liar can
>start an ARC chain and insert a set of unverifiable A-R assertions, it
>seems that trusting an ARC set requires prior knowledge of whom to trust,

Yes, that's a problem although in practice, the big mail providers have their
own data to know where the real lists are, and small providers don't get list
mail from all that many sources so it's not too painful to make a manual list.

>and when that information is available, ARC chain evaluation becomes >redundant.

No.  Please review the endless previous discussions of this issue.

R's,
John


From nobody Mon Jul 26 13:34:54 2021
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F19C3A088A; Mon, 26 Jul 2021 13:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Fkk2P-NshGMb; Mon, 26 Jul 2021 13:34:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A3713A087C; Mon, 26 Jul 2021 13:34:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E277AF406F3; Mon, 26 Jul 2021 13:34:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dmarc@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210726203425.E277AF406F3@rfc-editor.org>
Date: Mon, 26 Jul 2021 13:34:25 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/KuhfF6nFrTto_5049R6Qrjl87po>
Subject: [dmarc-ietf] =?utf-8?q?RFC_9091_on_Experimental_Domain-Based_Mes?= =?utf-8?q?sage_Authentication=2C_Reporting=2C_and_Conformance_=28DMARC=29?= =?utf-8?q?_Extension_for_Public_Suffix_Domains?=
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 26 Jul 2021 20:34:49 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9091

        Title:      Experimental Domain-Based Message Authentication, 
                    Reporting, and Conformance (DMARC) Extension for Public 
                    Suffix Domains 
        Author:     S. Kitterman,
                    T. Wicinski, Ed.
        Status:     Experimental
        Stream:     IETF
        Date:       July 2021
        Mailbox:    scott@kitterman.com,
                    tjw.ietf@gmail.com
        Pages:      14
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dmarc-psd-15.txt

        URL:        https://www.rfc-editor.org/info/rfc9091

        DOI:        10.17487/RFC9091

Domain-based Message Authentication, Reporting, and Conformance
(DMARC), defined in RFC 7489, 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.

This document is a product of the Domain-based Message Authentication, Reporting & Conformance Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Fri Jul 30 13:07:03 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 244323A0DC5 for <dmarc@ietfa.amsl.com>; Fri, 30 Jul 2021 13:07:02 -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=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 tdy4wsa3lTp6 for <dmarc@ietfa.amsl.com>; Fri, 30 Jul 2021 13:06:56 -0700 (PDT)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFC283A0DC2 for <dmarc@ietf.org>; Fri, 30 Jul 2021 13:06:56 -0700 (PDT)
Received: by mail-qk1-x72d.google.com with SMTP id x3so10595199qkl.6 for <dmarc@ietf.org>; Fri, 30 Jul 2021 13:06:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:from:date:message-id:subject:to; bh=bo4XhG+xJdPexmZGzTvgW38Nr8zZoHVhAU87dBjy3ig=; b=OufuVisHYTGaxwPfPGdczknBBgiNozF9a1LQg9Heqo2YY0QwuiF+6K8XjuJp7N7jEd cCcxq5jWzwijXzV5YmClS+7PFIjhbnqgZTWToRDc7QlEebxX8JjwrRnrdM0t2/G/FNzK yvDnBzaXcnADmojD1axowuGwfxQaL3YMxEBBb88j9ypkjEV1QGtdmuSHrnBQ1qwYZYNF 32u/M4eQ/ETT/LdSA1ILRsCGJcDXIItmJTlWyuIOdnDCVhq34eRQeuTVcS55IuhM7VQN dGmWqx84M9AGWx3w5OqZCan9xpnpkskbbvxX1WKBgWIlF1RybhfAYNri6YhA/F3gyPj4 jbFw==
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=bo4XhG+xJdPexmZGzTvgW38Nr8zZoHVhAU87dBjy3ig=; b=IZX8sCu8uyGmn4Eq3VHbBopy0Vv2D56K94ra2C6zJamiIntQ78moU8CYckpDj+9A5P diWn97+o2R12Oml8GPveLasLSlU4MsizDD4QLTSjA+mXcYX8/YJwKqorPukRm8ZDCtsk kHZFVw5i9VE1tzbUObb1XTk56f6VsYzhWi8wxS5dfiKGYpG0md0T2UvSslH0b5/NUZTk il4B1QrqB+0/LNlMQOPFBnWt1GlH56AzIckKrHWJ3qVr2SKpWHpiLDhTf7HXr24QeOlM DndVomMbNcrictLsEE4VqCZe2+ZXr5nfafvgxBr6O5OJ+BwUxyt1LixVxQydHgpUTknc o6Kg==
X-Gm-Message-State: AOAM532Bg4rwNiBheL5ej3of/A3kfke15E5Szx1jIU810G64+Agy6BJP cGn+FA94lBeYliJfqShZU2ghJmtnXDqxVVKRrUxt99UNmBynHQ==
X-Google-Smtp-Source: ABdhPJxrueZjzOm1mNUCpCHKj+oMRVi28+YhWtfngypYhv1WMUvsCXeyPba3MqCdLxBrDjylrQyxTyiQLNo237i8SLU=
X-Received: by 2002:a05:620a:14b7:: with SMTP id x23mr4096051qkj.387.1627675615420;  Fri, 30 Jul 2021 13:06:55 -0700 (PDT)
MIME-Version: 1.0
From: Todd Herr <todd.herr@valimail.com>
Date: Fri, 30 Jul 2021 16:06:39 -0400
Message-ID: <CAHej_8m4W_k_r9SV6reNJA7aMGFCkK451tjvQGtrPNwRtJwC8A@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ddf5e805c85cc2c8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/w3EijF9NovG0ht9dUWyZa_rdkME>
Subject: [dmarc-ietf] Some Proposed Language for a New pct Tag Defintion
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 30 Jul 2021 20:07:02 -0000

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

Following on to the recent discussion about the pct tag, and specifically
the disallowing of any values other than 0 and 100, I propose the following
text and look forward to your comments:

   pct:  (plain-text integer; OPTIONAL; default is 100).  For the

      RFC5322.From domain to which the DMARC record applies, the "pct"

      tag is the percentage of messages producing a DMARC result of

      "fail" to which the Domain Owner wishes its preferred handling

      policy be applied.  However, this MUST NOT be applied to the

      DMARC-generated reports, all of which must be sent and received

      unhindered.  Possible values are as follows:


      0:  A request that zero percent of messages producing a DMARC

         "fail" result have the specified policy applied.  While this is

         seemingly a non-sensical request, this value has been given

         special meaning by some mailbox providers and intermediaries

         when combined with "p=" values other than "none".  In those

         cases, in can result in changes to message handling, and/or

         DMARC reporting for the domain publishing such a policy.  In

         some instances of altered reporting, it is possible that the

         altered reports may reveal intermediaries whose handling of the

         domain owners' mail could cause it to produce a DMARC result of

         "fail" when it reaches its final destination.


      100:  The default, in which a request is made that every message

         that produces a DMARC "fail" result will be subject to

         application of the specified policy.

I'll check on this thread on Monday to see where things stand...

-- 

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

--000000000000ddf5e805c85cc2c8
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">Following on to the recent discussion about the pct tag, and spe=
cifically the disallowing of any values other than 0 and 100, I propose the=
 following text and look forward to your comments:<br clear=3D"all"></div><=
div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><br></d=
iv><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">





<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>pct:<span class=3D"gmail-Apple-converted-s=
pace">=C2=A0 </span>(plain-text integer; OPTIONAL; default is 100).<span cl=
ass=3D"gmail-Apple-converted-space">=C2=A0 </span>For 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 =C2=A0 </span>RFC5322.From domain to which the D=
MARC record applies, the &quot;pct&quot;</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 =C2=A0 </span>tag is the percentage of messages =
producing a DMARC result 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 =C2=A0 </span>&quot;fail&quot; to which the Doma=
in Owner wishes its preferred handling</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 =C2=A0 </span>policy be applied.<span class=3D"g=
mail-Apple-converted-space">=C2=A0 </span>However, this MUST NOT be applied=
 to 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 =C2=A0 </span>DMARC-generated reports, all of wh=
ich must be sent and received</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 =C2=A0 </span>unhindered.<span class=3D"gmail-Ap=
ple-converted-space">=C2=A0 </span>Possible values are as follows:</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 =C2=A0 </span>0:<span class=3D"gmail-Apple-conve=
rted-space">=C2=A0 </span>A request that zero percent of messages producing=
 a DMARC</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 =C2=A0 =C2=A0 =C2=A0 </span>&quot;fail&quot; resu=
lt have the specified policy applied.<span class=3D"gmail-Apple-converted-s=
pace">=C2=A0 </span>While this is</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 =C2=A0 =C2=A0 =C2=A0 </span>seemingly a non-sensi=
cal request, this value has been given</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 =C2=A0 =C2=A0 =C2=A0 </span>special meaning by so=
me mailbox providers and intermediaries</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 =C2=A0 =C2=A0 =C2=A0 </span>when combined with &q=
uot;p=3D&quot; values other than &quot;none&quot;.<span class=3D"gmail-Appl=
e-converted-space">=C2=A0 </span>In those</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 =C2=A0 =C2=A0 =C2=A0 </span>cases, in can result =
in changes to message handling, and/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 =C2=A0 =C2=A0 =C2=A0 </span>DMARC reporting for t=
he domain publishing such a policy.<span class=3D"gmail-Apple-converted-spa=
ce">=C2=A0 </span>In</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 =C2=A0 =C2=A0 =C2=A0 </span>some instances of alt=
ered reporting, it is possible that 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 =C2=A0 =C2=A0 =C2=A0 </span>altered reports may r=
eveal intermediaries whose handling of 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 =C2=A0 =C2=A0 =C2=A0 </span>domain owners&#39; ma=
il could cause it to produce a DMARC result 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 =C2=A0 =C2=A0 =C2=A0 </span>&quot;fail&quot; when=
 it reaches its final destination.</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 =C2=A0 </span>100:<span class=3D"gmail-Apple-con=
verted-space">=C2=A0 </span>The default, in which a request is made that ev=
ery message</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 =C2=A0 =C2=A0 =C2=A0 </span>that produces a DMARC=
 &quot;fail&quot; result will be subject 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 =C2=A0 =C2=A0 =C2=A0 </span>application of the sp=
ecified policy.</span></p></div><div><br></div><div><div class=3D"gmail_def=
ault" style=3D"font-family:tahoma,sans-serif">I&#39;ll check on this thread=
 on Monday to see where things stand...</div><br></div>-- <br><div dir=3D"l=
tr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><span><p d=
ir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p=
><div style=3D"text-align:left"><span style=3D"vertical-align:baseline;whit=
e-space:pre-wrap;font-size:small;font-family:Arial"><b>Todd Herr</b></span>=
<span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:small=
;font-family:Arial"> | Technical Director, Standards and Ecosystem</span></=
div><span style=3D"vertical-align:baseline;white-space:pre-wrap;font-size:s=
mall;font-family:Arial"><div style=3D"text-align:left"><span style=3D"verti=
cal-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@val=
imail.com</a> </span></div></span><span><div><span><b>m:</b></span><span> 7=
03.220.4153</span><span></span></div><div style=3D"text-align:left"><img st=
yle=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"back=
ground-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.66=
67px;white-space:pre-wrap">This email and all data transmitted with it cont=
ains confidential and/or proprietary information intended solely for the us=
e of individual(s) authorized to receive it. If you are not an intended and=
 authorized recipient you are hereby notified of any use, disclosure, copyi=
ng or distribution of the information included in this transmission is proh=
ibited and may be unlawful. Please immediately notify the sender by replyin=
g to this email and then delete it from your system.</span></font></p></spa=
n></div></div>

--000000000000ddf5e805c85cc2c8--


From nobody Fri Jul 30 17:13:14 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 33DD73A18D9 for <dmarc@ietfa.amsl.com>; Fri, 30 Jul 2021 17:13:12 -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 f6hsxJrRJSl3 for <dmarc@ietfa.amsl.com>; Fri, 30 Jul 2021 17:13:07 -0700 (PDT)
Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 556253A18D8 for <dmarc@ietf.org>; Fri, 30 Jul 2021 17:13:07 -0700 (PDT)
Received: by mail-ot1-x329.google.com with SMTP id c2-20020a0568303482b029048bcf4c6bd9so11316016otu.8 for <dmarc@ietf.org>; Fri, 30 Jul 2021 17:13:07 -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=OSRFb/MbqHONMLMOMgub1Yql4pCIkE75ZkUfsepk+hA=; b=benJzqDql44gHzGESRX5VinTzl0gqwRD5t6jnHlXHQ4KSYSqUI0KjOCqX3SjdpXNUd Y/0F+ULehPes0tUNLzJYPzNLyGN2N3SB7+kow/cvWqgPE772NKlBudH2TUNBP1DCDAYg mLQuf1Cdq3rZ5fgHG41q/HD6VsaUQPsFAvkOW4c2JJtBga/1rLkweUtOelxW1iaidLZW ZVrCwRsQQ1IHgmZvHfbZu6xlZcibNaI4N1fdIL5jT3B5iqeRhCuL1xix0TB9NrJZ1BoR Tn75JEze0IHiRKsP+puUcfFQ4GtbFhu/QIfhdTX4QOodKRFDdqzjnMoNEE0AGWvTWlZH jRiw==
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=OSRFb/MbqHONMLMOMgub1Yql4pCIkE75ZkUfsepk+hA=; b=kE0MmeQX1eWNyh/gWwuLm+9yF2UmY/Sa9UxnitDUkMhJm0ckgRkPIP1L15RsM3rQq3 QV9owKc2N4l89ji9irVON09RAfJbSDfvFqdMRDLx4JZnSIHTDDhpawXVpqfiJ+vsvPc7 o04Q5b+D6QtFeKrlHMkhOPxmDTuB8rtID6oNEu3NHxv7LoBYhRDFEvSWCvxZ3HVPH6D1 BNo3h6MXOoElDpog3f5k+0HLTY2lZ2/x/HbVBoqC5gEeVywsR/eqi8ArD8CylzZRnivT p/p/+XsFuCGEV9u8ZTgrlrNAp9hIlzeywHKMaOw3KdM/Ga6o951U81JszHhUo4UKwXnb G/Ag==
X-Gm-Message-State: AOAM532OKqdAbEDzHK091YudNrCKSjGRp3ykJklT+UVW0tihDBRQ4oWd eO678VH3utqw9dtw1mzWKB0LGI2iAUlE2NXr6i4=
X-Google-Smtp-Source: ABdhPJy17ZumLzSknNigNyLU4aFzlYRBIGZ5rkcDAu2iRm3mJn9lGwlb2Vo/6GSdxNZwOz18Ke+ajgagRW997m7SqqE=
X-Received: by 2002:a9d:6f84:: with SMTP id h4mr4219509otq.240.1627690386165;  Fri, 30 Jul 2021 17:13:06 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8m4W_k_r9SV6reNJA7aMGFCkK451tjvQGtrPNwRtJwC8A@mail.gmail.com>
In-Reply-To: <CAHej_8m4W_k_r9SV6reNJA7aMGFCkK451tjvQGtrPNwRtJwC8A@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Fri, 30 Jul 2021 20:12:56 -0400
Message-ID: <CAH48Zfz91SHxGNc6YZ8d_=_yf=Y-iJoZDm_t_ybBv2yfbJPPRg@mail.gmail.com>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000045916905c8603385"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ueRwxN4pnNjQf5ByikaVHe0h8UY>
Subject: Re: [dmarc-ietf] Some Proposed Language for a New pct Tag Defintion
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 31 Jul 2021 00:13:13 -0000

--00000000000045916905c8603385
Content-Type: text/plain; charset="UTF-8"

This language addresses my original concern.

You have a typo at this point:
... cases, in can result in...
and of course it should read
...cases, it can result in...

Since PCT is being removed, I would like to provide something for domain
owners that are struggling to complete implementation safely.   I think
what they would most appreciate would be for recipients to use SMTP
extended result enhanced status codes.   Others have already defined
appropriate codes to communicate whether or not a message passes
authentication, and how.

Unfortunately, it seems the extended status codes have very limited
deployment.   When I searched my recent history, I could only find codes
2.0.0 and 2.6.0, which communicate nothing incremental.

Would it be reasonable to add language saying that we RECOMMEND that
evaluators use extended status codes, for both accepted and rejected
messages, to indicate the message authentication status?   We could
highlight the codes that are particularly relevant to this need.

Doug Foster

On Fri, Jul 30, 2021 at 4:07 PM Todd Herr <todd.herr=
40valimail.com@dmarc.ietf.org> wrote:

> Following on to the recent discussion about the pct tag, and specifically
> the disallowing of any values other than 0 and 100, I propose the following
> text and look forward to your comments:
>
>    pct:  (plain-text integer; OPTIONAL; default is 100).  For the
>
>       RFC5322.From domain to which the DMARC record applies, the "pct"
>
>       tag is the percentage of messages producing a DMARC result of
>
>       "fail" to which the Domain Owner wishes its preferred handling
>
>       policy be applied.  However, this MUST NOT be applied to the
>
>       DMARC-generated reports, all of which must be sent and received
>
>       unhindered.  Possible values are as follows:
>
>
>       0:  A request that zero percent of messages producing a DMARC
>
>          "fail" result have the specified policy applied.  While this is
>
>          seemingly a non-sensical request, this value has been given
>
>          special meaning by some mailbox providers and intermediaries
>
>          when combined with "p=" values other than "none".  In those
>
>          cases, in can result in changes to message handling, and/or
>
>          DMARC reporting for the domain publishing such a policy.  In
>
>          some instances of altered reporting, it is possible that the
>
>          altered reports may reveal intermediaries whose handling of the
>
>          domain owners' mail could cause it to produce a DMARC result of
>
>          "fail" when it reaches its final destination.
>
>
>       100:  The default, in which a request is made that every message
>
>          that produces a DMARC "fail" result will be subject to
>
>          application of the specified policy.
>
> I'll check on this thread on Monday to see where things stand...
>
> --
>
> *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.
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr"><div>This language addresses my original concern.</div><di=
v><br></div>You have a typo at this point:<div>... cases, in can result in.=
..<br></div><div>and of course it should read</div><div>...cases, it can re=
sult in...<br></div><div><br></div><div>Since PCT is being removed, I would=
 like to provide something for domain owners that are struggling to complet=
e implementation safely.=C2=A0 =C2=A0I think what they would most appreciat=
e would be for recipients to use SMTP extended result enhanced status codes=
.=C2=A0 =C2=A0Others have already defined appropriate codes to communicate =
whether or not a message passes authentication, and how.</div><div><br></di=
v><div>Unfortunately, it seems the extended status codes have very limited =
deployment.=C2=A0 =C2=A0When I searched my recent history, I could only fin=
d codes 2.0.0 and 2.6.0, which communicate nothing incremental.=C2=A0 =C2=
=A0=C2=A0</div><div><br></div><div>Would it be reasonable to add language s=
aying that we RECOMMEND that evaluators use extended status codes, for both=
 accepted and rejected messages, to indicate the message authentication sta=
tus?=C2=A0 =C2=A0We could highlight the codes that are particularly relevan=
t to this need.</div><div><br></div><div>Doug Foster</div></div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jul 30, 2=
021 at 4:07 PM Todd Herr &lt;todd.herr=3D<a href=3D"mailto:40valimail.com@d=
marc.ietf.org">40valimail.com@dmarc.ietf.org</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"><div dir=3D"ltr"><div class=3D"=
gmail_default" style=3D"font-family:tahoma,sans-serif">Following on to the =
recent discussion about the pct tag, and specifically the disallowing of an=
y values other than 0 and 100, I propose the following text and look forwar=
d to your comments:<br clear=3D"all"></div><div class=3D"gmail_default" sty=
le=3D"font-family:tahoma,sans-serif"><br></div><div class=3D"gmail_default"=
 style=3D"font-family:tahoma,sans-serif">





<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0 =C2=A0</span>pct:<span>=C2=A0 </span>(plain-text integer=
; OPTIONAL; default is 100).<span>=C2=A0 </span>For the</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0 =C2=A0 =C2=A0 </span>RFC5322.From domain to which the DM=
ARC record applies, the &quot;pct&quot;</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0 =C2=A0 =C2=A0 </span>tag is the percentage of messages p=
roducing a DMARC result of</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0 =C2=A0 =C2=A0 </span>&quot;fail&quot; to which the Domai=
n Owner wishes its preferred handling</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0 =C2=A0 =C2=A0 </span>policy be applied.<span>=C2=A0 </sp=
an>However, this MUST NOT be applied to the</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0 =C2=A0 =C2=A0 </span>DMARC-generated reports, all of whi=
ch must be sent and received</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0 =C2=A0 =C2=A0 </span>unhindered.<span>=C2=A0 </span>Poss=
ible values are as follows:</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0);min-height:13px"><span style=3D"font-variant-ligatures=
:no-common-ligatures"></span><br></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0 =C2=A0 =C2=A0 </span>0:<span>=C2=A0 </span>A request tha=
t zero percent of messages producing a DMARC</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>&quot;fail&quot; resul=
t have the specified policy applied.<span>=C2=A0 </span>While this is</span=
></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>seemingly a non-sensic=
al request, this value has been given</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>special meaning by som=
e mailbox providers and intermediaries</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>when combined with &qu=
ot;p=3D&quot; values other than &quot;none&quot;.<span>=C2=A0 </span>In tho=
se</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>cases, in can result i=
n changes to message handling, and/or</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>DMARC reporting for th=
e domain publishing such a policy.<span>=C2=A0 </span>In</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>some instances of alte=
red reporting, it is possible that the</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>altered reports may re=
veal intermediaries whose handling of the</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>domain owners&#39; mai=
l could cause it to produce a DMARC result of</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>&quot;fail&quot; when =
it reaches its final destination.</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0);min-height:13px"><span style=3D"font-variant-ligatures=
:no-common-ligatures"></span><br></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0 =C2=A0 =C2=A0 </span>100:<span>=C2=A0 </span>The default=
, in which a request is made that every message</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>that produces a DMARC =
&quot;fail&quot; result will be subject to</span></p>
<p style=3D"margin:0px;font-variant-numeric:normal;font-variant-east-asian:=
normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Me=
nlo;color:rgb(0,0,0)"><span style=3D"font-variant-ligatures:no-common-ligat=
ures"><span>=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 </span>application of the spe=
cified policy.</span></p></div><div><br></div><div><div class=3D"gmail_defa=
ult" style=3D"font-family:tahoma,sans-serif">I&#39;ll check on this thread =
on Monday to see where things stand...</div><br></div>-- <br><div dir=3D"lt=
r"><span><p dir=3D"ltr" style=3D"line-height:1.656;margin-top:0pt;margin-bo=
ttom: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 He=
rr</b></span><span style=3D"vertical-align:baseline;white-space:pre-wrap;fo=
nt-size:small;font-family:Arial"> | Technical Director, Standards and Ecosy=
stem</span></div><span style=3D"vertical-align:baseline;white-space:pre-wra=
p;font-size:small;font-family:Arial"><div style=3D"text-align:left"><span s=
tyle=3D"vertical-align:baseline"><b>e:</b></span><span style=3D"vertical-al=
ign:baseline"> <a href=3D"mailto: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-pack=
ages.s3-us-west-1.amazonaws.com/Valimail+Logo.png"></div></span><p dir=3D"l=
tr" 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 trans=
mitted with it contains confidential and/or proprietary information intende=
d solely for the use of individual(s) authorized to receive it. If you are =
not an intended and authorized recipient you are hereby notified of any use=
, disclosure, copying or distribution of the information included in this t=
ransmission is prohibited and may be unlawful. Please immediately notify th=
e sender by replying to this email and then delete it from your system.</sp=
an></font></p></span></div></div>
_______________________________________________<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>

--00000000000045916905c8603385--


From nobody Sat Jul 31 02:40:07 2021
Return-Path: <vesely@tana.it>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CBE73A1F89 for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 02:40:05 -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 CjLex4KuwZg3 for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 02:40:00 -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 D65193A1F88 for <dmarc@ietf.org>; Sat, 31 Jul 2021 02:39:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1627724395; bh=EkbRYrkjO+eKZlzbFJtqSxcVnhmOgSUKb7qVKjN1PBw=; l=1690; h=To:References:From:Date:In-Reply-To; b=CYJzFgkpVNkAKgC6O+5SiwHVdffQGUUpCiDH9LOBq+dyPEGyYCws03D3A/5Hom4wG QlHzClMHvD3Y4XdoVkYGTWbvdsh67udCa0OfkHYhxb1dC48ey4aGR6xS9SnHvu9zmI 4zd7TxvOmJp6wIllNQs9MIEKLnG2RFuULlDu4EI6ahCVFftU4zBzZoVvVZjHq
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.0000000061051A6A.00001470; Sat, 31 Jul 2021 11:39:54 +0200
To: dmarc@ietf.org
References: <CAHej_8m4W_k_r9SV6reNJA7aMGFCkK451tjvQGtrPNwRtJwC8A@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <6e96de62-f387-bb42-a5da-0b7f74674a02@tana.it>
Date: Sat, 31 Jul 2021 11:39:54 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAHej_8m4W_k_r9SV6reNJA7aMGFCkK451tjvQGtrPNwRtJwC8A@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/GaMHnw2qCl5SggK3GP-qvCD0z8Y>
Subject: Re: [dmarc-ietf] Some Proposed Language for a New pct Tag Defintion
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 31 Jul 2021 09:40:05 -0000

On Fri 30/Jul/2021 22:06:39 +0200 Todd Herr wrote:
> Following on to the recent discussion about the pct tag, and specifically the 
> disallowing of any values other than 0 and 100, I propose the following text 
> and look forward to your comments:


I still dislike this limitation.  I previously showed that users seem to change 
pct= with some salt.  In addition, how should implementations amend their code? 
  What shall a receiver do if it finds intermediate values of pct?

I'd keep allowing intermediate values.  Substitute /Possible values are as 
follows:/ with /RECOMMENDED values are as follows:/.

For case 0:

YOUR TEXT:
      0:  A request that zero percent of messages producing a DMARC
          "fail" result have the specified policy applied.  While this is
          seemingly a non-sensical request, this value has been given
          special meaning by some mailbox providers and intermediaries
          when combined with "p=" values other than "none".  In those
          cases, in can result in changes to message handling, and/or
          DMARC reporting for the domain publishing such a policy.  In
          some instances of altered reporting, it is possible that the
          altered reports may reveal intermediaries whose handling of the
          domain owners' mail could cause it to produce a DMARC result of
          "fail" when it reaches its final destination.

MY PROPOSED ALTERNATIVE:
      0:  A request that messages producing a DMARC "fail" result never
          have the specified policy applied.  The special meaning of
          this value is to have mailing lists which discriminate message
          handling by author's domain policy apply From: munging
          (see [Section X.Y.Z]) while final receivers still apply no
          policy.


Best
Ale
-- 















From nobody Sat Jul 31 02:55:43 2021
Return-Path: <dilyan.palauzov@aegee.org>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A945D3A2009; Sat, 31 Jul 2021 02:55: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, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=aegee.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JRcZ4fs0aDdF; Sat, 31 Jul 2021 02:55:36 -0700 (PDT)
Received: from mail.aegee.org (mail.aegee.org [144.76.142.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9F553A2007; Sat, 31 Jul 2021 02:55:35 -0700 (PDT)
Authentication-Results: mail.aegee.org/16V9tP8p3586715; auth=pass (LOGIN) smtp.auth=didopalauzov@aegee.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1627725326; i=dkim+MSA-tls@aegee.org; bh=shmCHY9tXPjbvSo3IsHO0sB3aoYLIAwaTzVvG3zuY9Q=; h=Subject:From:To:Date:In-Reply-To:References; b=jkrBaCvQVKmOD7q9il0OSadUvbhnegaXzoY3taHDy8D8AHXua1CP+WESLBIyq/IEE EMd7RFlO34KZ2aqJZgfEZN9EF4CaW9A1ZjjU0npGm+dEsH5tEcyfZ59at6ACaaz4Fv lfp+HcrpFLmxU+G5tmt13VXPmtVRjZKipHQTXIfleh+vw9DKVz4F1J8zvlQfo9YES3 Rp15FQPenpguIofr5lASSEIDw4jhHXjRJLX5zru3lHH1+kRvl65ZwJISc1RAanqgyE JpDgbug/tPtXzKxqyADK44bpGi5bIPDagDQi0b/ft2fCi8KtZ+gdadMQIeSHnHkLhO TvPLLtS1/DuHyiBN16VZziEizA+dAE+hmHY7484BNzD5NrA8V+jWttDzddrK9e3JPA BcZ9QbfIq+W/zcMfvlpIvEcY+1ulbAVSJYou9ialgcMiaFjPNYFpRjHX8ZqaY9xCT3 U/pFkjeVt24jCJZH7RI8O2Wfdkju8O2s6hBavnMKOb5PW5pKpFlPLylZfOrwJD3gQu k1m9GyUov/QT+ZLA+7MmdaBU47NfXBPudjP0fbSygBts9naxEIKWq+F8TCnC7f6mA4 nO5Ow5/tknMqDDtPnhbBfiOiGyUv0lBD8/jjDPFdm/gncp5YkqF9TTIobOOd/LLQnn 9gHHnRgUaGQdEa6kG0+BnjPY=
Authentication-Results: mail.aegee.org/16V9tP8p3586715; dkim=none
Received: from [192.168.0.199] (87.118.146.153.topnet.bg [87.118.146.153] (may be forged)) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id 16V9tP8p3586715 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 31 Jul 2021 09:55:26 GMT
Message-ID: <433a654b1f4f9371282772a634a2c0894aec8dae.camel@aegee.org>
From: =?UTF-8?Q?=D0=94=D0=B8=D0=BB=D1=8F=D0=BD_?= =?UTF-8?Q?=D0=9F=D0=B0=D0=BB=D0=B0=D1=83=D0=B7=D0=BE=D0=B2?= <dilyan.palauzov@aegee.org>
To: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
Date: Sat, 31 Jul 2021 12:55:25 +0300
In-Reply-To: <CAHej_8m4W_k_r9SV6reNJA7aMGFCkK451tjvQGtrPNwRtJwC8A@mail.gmail.com>
References: <CAHej_8m4W_k_r9SV6reNJA7aMGFCkK451tjvQGtrPNwRtJwC8A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.41.2 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rTlNLnISdyqaRSM3dVTeivBTRKI>
Subject: Re: [dmarc-ietf] Some Proposed Language for a New pct Tag Defintion
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 31 Jul 2021 09:55:41 -0000

Hello,

for me this wording of pct=0 is not clear enough, why the value is
necessary.  Why the value is necessary can be explained by:

When seeing pct=0 mail intermediaries should munge the From: header. 
This allows mail operators to detect problems with DMARC deployment,
before strict DMARC policy is applied.

Greetings
  Дилян

On Fri, 2021-07-30 at 16:06 -0400, Todd Herr wrote:
> Following on to the recent discussion about the pct tag, and
> specifically the disallowing of any values other than 0 and 100, I
> propose the following text and look forward to your comments:
> 
>    pct:  (plain-text integer; OPTIONAL; default is 100).  For the
>       RFC5322.From domain to which the DMARC record applies, the
> "pct"
>       tag is the percentage of messages producing a DMARC result of
>       "fail" to which the Domain Owner wishes its preferred handling
>       policy be applied.  However, this MUST NOT be applied to the
>       DMARC-generated reports, all of which must be sent and received
>       unhindered.  Possible values are as follows:
> 
>       0:  A request that zero percent of messages producing a DMARC
>          "fail" result have the specified policy applied.  While this
> is
>          seemingly a non-sensical request, this value has been given
>          special meaning by some mailbox providers and intermediaries
>          when combined with "p=" values other than "none".  In those
>          cases, in can result in changes to message handling, and/or
>          DMARC reporting for the domain publishing such a policy.  In
>          some instances of altered reporting, it is possible that the
>          altered reports may reveal intermediaries whose handling of
> the
>          domain owners' mail could cause it to produce a DMARC result
> of
>          "fail" when it reaches its final destination.
> 
>       100:  The default, in which a request is made that every
> message
>          that produces a DMARC "fail" result will be subject to
>          application of the specified policy.
> 
> I'll check on this thread on Monday to see where things stand...
> 
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


From nobody Sat Jul 31 11:28:11 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 728C33A13E3 for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 11:28:00 -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 Mxfe0_BJc4pd for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 11:27:58 -0700 (PDT)
Received: from mail-vk1-xa30.google.com (mail-vk1-xa30.google.com [IPv6:2607:f8b0:4864:20::a30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A95E03A13D1 for <dmarc@ietf.org>; Sat, 31 Jul 2021 11:27:58 -0700 (PDT)
Received: by mail-vk1-xa30.google.com with SMTP id d15so2746369vka.13 for <dmarc@ietf.org>; Sat, 31 Jul 2021 11:27:58 -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=iCOBbJpeUpTcLuNQ5yYH2zuprS23ipJ7qKI+rDwpGEs=; b=TEACR1fwqocvL94Hda7bZtbe4SXBCDnjMrUDsoiw7ZCp/jJU8dlUsoVR5QsFwneiqg rcqkPjjYpPayw3NILGrg9LU+YyGw2Aq0qx3TUPWVJLg4/UAabSv8cN55WEV0YyYf8VdI W/E9mx0mKuS//iKo6V2hjelzNKPzCMlncjWNIPA1hLJZ5rMeQQpLHiDDjXzxLEAY2/ex pK26KFzR2fbO4GHltNCR6jwDmuHxLFzV8DG85ro7hkYiZrtOtEBa3yMTbRTReBeKKfm/ xJjEBmVKNlaw6u0POXlLnIj7qozBQpKNLcwSwb/SqR+teBrPzujTV4FeKJdctNvPbOnk JAgA==
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=iCOBbJpeUpTcLuNQ5yYH2zuprS23ipJ7qKI+rDwpGEs=; b=DhSexhDYmHCA4D0CD/Rp9Ju77H6l3+pOdzjG9J2ZHdRNs+SIjwECqbtbvV1viKLpR2 rQ7F6iWLv+SB9ov4k2zdcmj+6S5jWUJLATCBhjCWV9QT95zlSD6AlpPA0Z+MCP/BnJP/ QXOI6Ld3psMDYgO3lq4xof4jt5GbhMmjwL89ZHz6hLB+Xorjnr38rwJ/xWAst4takjDe RY912ww2ADWn9gQ8D++E/RPVoXZ4vuNc9jgph/V+EYLI+a2/6PYfCdyoPFdnLmoZp1xz rkmwX7oEfVc2L3yMhf3UxMWhq8P8X8qKQq14W2ljCasbDdGsBGI0Np3RPBe7g61m7cmy MDhQ==
X-Gm-Message-State: AOAM532qxchfhsEwtIOEAwZvyc/bqTJKmafvr/npXiZ1romOc+JfEXCu 41Kuktix+1VGrSMe+cFxrZNqsH/M/HsHm064rNs=
X-Google-Smtp-Source: ABdhPJydPpCYe/JjI9RQ0D9egK2LwgzZgVSNgAP+qfM1tMJ5e30unMs/vkJvSUkoV3Rm24U435HW539acIjFbek9324=
X-Received: by 2002:a1f:a687:: with SMTP id p129mr5271857vke.13.1627756076370;  Sat, 31 Jul 2021 11:27:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8m4W_k_r9SV6reNJA7aMGFCkK451tjvQGtrPNwRtJwC8A@mail.gmail.com> <CAH48Zfz91SHxGNc6YZ8d_=_yf=Y-iJoZDm_t_ybBv2yfbJPPRg@mail.gmail.com>
In-Reply-To: <CAH48Zfz91SHxGNc6YZ8d_=_yf=Y-iJoZDm_t_ybBv2yfbJPPRg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sat, 31 Jul 2021 11:27:45 -0700
Message-ID: <CAL0qLwb114xmTg7Qe5wAg2q316ih4x7RpS8WAomdnjsWDyd0Uw@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b68ea705c86f7e68"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/kx-1gl8R1_Xw5_N7nNH78YZ0XEI>
Subject: Re: [dmarc-ietf] Some Proposed Language for a New pct Tag Defintion
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 31 Jul 2021 18:28:10 -0000

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

On Fri, Jul 30, 2021 at 5:13 PM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> Unfortunately, it seems the extended status codes have very limited
> deployment.   When I searched my recent history, I could only find codes
> 2.0.0 and 2.6.0, which communicate nothing incremental.
>

Indeed; I would like to understand what 2.6.0 is meant to convey.  As I
read the IANA registry entries, "2" means success but "6" means there was a
media type error.

Would it be reasonable to add language saying that we RECOMMEND that
> evaluators use extended status codes, for both accepted and rejected
> messages, to indicate the message authentication status?   We could
> highlight the codes that are particularly relevant to this need.
>

I'm not sure about RECOMMENDED, but reminding readers of this mechanism for
providing additional information seems at least harmless to me.

If we say RECOMMENDED, I'd be inclined to think we should say something
about both producers of these codes and consumers of them, to encourage
interoperability.  There's no point in making a strong push toward
generating them if nobody has any incentive to do something with them when
they're observed.

-MSK

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

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jul 30, 2021 at 5:13 PM Douglas F=
oster &lt;<a href=3D"mailto:dougfoster.emailstandards@gmail.com">dougfoster=
.emailstandards@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Unfort=
unately, it seems the extended status codes have very limited deployment.=
=C2=A0 =C2=A0When I searched my recent history, I could only find codes 2.0=
.0 and 2.6.0, which communicate nothing incremental.=C2=A0 </div></blockquo=
te><div><br></div><div>Indeed; I would like to understand what 2.6.0 is mea=
nt to convey.=C2=A0 As I read the IANA registry entries, &quot;2&quot; mean=
s success but &quot;6&quot; means there was a media type error.<br></div><d=
iv> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr">Would it be reasonable to add language saying that we RECOMMEND that =
evaluators use extended status codes, for both accepted and rejected messag=
es, to indicate the message authentication status?=C2=A0 =C2=A0We could hig=
hlight the codes that are particularly relevant to this need.</div></blockq=
uote><div><br></div><div>I&#39;m not sure about RECOMMENDED, but reminding =
readers of this mechanism for providing additional information seems at lea=
st harmless to me.</div><div><br></div><div>If we say RECOMMENDED, I&#39;d =
be inclined to think we should say something about both producers of these =
codes and consumers of them, to encourage interoperability.=C2=A0 There&#39=
;s no point in making a strong push toward generating them if nobody has an=
y incentive to do something with them when they&#39;re observed.</div><div>=
<br></div><div>-MSK</div></div></div>

--000000000000b68ea705c86f7e68--


From nobody Sat Jul 31 13:24:37 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 E08F73A0D43 for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 13:24: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, HEADER_FROM_DIFFERENT_DOMAINS=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=iecc.com header.b=azvtOsCO; dkim=pass (2048-bit key) header.d=taugh.com header.b=qm93h6MU
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HSPXDQiZH-Vr for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 13:24:30 -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 9614B3A0D71 for <dmarc@ietf.org>; Sat, 31 Jul 2021 13:24:30 -0700 (PDT)
Received: (qmail 23505 invoked from network); 31 Jul 2021 20:24:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=5bce.6105b17b.k2107; bh=er1Wpgfnx/yXm3S+6mJtj6PvWYMYkKYOGPXKnxT2B+g=; b=azvtOsCODkFk1z5HpWiehO+Dr89RdaJBRS35zjZnKCi/EF0BQmQ5KhDGAi/cfoMI5Ra2E2ESDHjW0ABGQ/tbjMO7hFQqC3ynV4n85FiKH3DfPfpQdsgaVEHPpuSOCcdmcrAzYhhxGqudsBx722lDKDxp8q8fitAHHUf8IJtJaFHiL/DoHuWWOKOHYq0b/ISuJSKu2aOl/a4VgfCnWQz+PPMHligZVkIw/794Rm6SjU/H6ChSO/7ZOfzcP+YujHxSx2F7gQsdZKzDH+4LcnrbCsnws3U8hLd9YXkXxioXFoaB7O654kUszgtYbW4Li7RbtzKI3e6FA3mQhnc64CQC5Q==
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=5bce.6105b17b.k2107; bh=er1Wpgfnx/yXm3S+6mJtj6PvWYMYkKYOGPXKnxT2B+g=; b=qm93h6MUQ4DIFKLR5BQ8OH8jNbf6XOuhbZW1UI0BM+lg8STlSyyYn9CQoRbDo60aqqpr9g5asiXBiUP0GEHqiarS5MqtiBv5D6mATvA/NRrByeoMWA2BEfN7LHo1+32JhQx9fGdS4qmnrIVeqLQnXm3cOwzBIchHTvrW5Kb5OOUfyCWBipEJ/E2icFSVS6XWP+bOft7bHqYrAqvYff3+m+DWVzDLSef+++36cjYhwPBIs2Jw/7sScJpkO2XPWG82+dlV8Wp/HzRsUHMhP/7lH0QRkIODAAoq0FNiJdqWko6jgnuHp/1FCEXTa65zwobXLPmTafWLsXXi4ByfKYTCXw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 31 Jul 2021 20:24:27 -0000
Received: by ary.qy (Postfix, from userid 501) id CE9FD2566204; Sat, 31 Jul 2021 16:24:25 -0400 (EDT)
Date: 31 Jul 2021 16:24:25 -0400
Message-Id: <20210731202426.CE9FD2566204@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: superuser@gmail.com
In-Reply-To: <CAL0qLwb114xmTg7Qe5wAg2q316ih4x7RpS8WAomdnjsWDyd0Uw@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/_bBJcl0n7p4PUfJxV4qJR0I9fn4>
Subject: Re: [dmarc-ietf] not enhanced status codes Some Proposed Language for a New pct Tag Defintion
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 31 Jul 2021 20:24:36 -0000

It appears that Murray S. Kucherawy  <superuser@gmail.com> said:
>Indeed; I would like to understand what 2.6.0 is meant to convey.  As I
>read the IANA registry entries, "2" means success but "6" means there was a
>media type error.

I think it's supposed to mean "I accepted your message but I wouldn't have if I were
enforcing DMARC p=none".

Since this would be a gift to spammers trying to probe and evade filters, I find it
very unlikely anyone would implement it, so no.

R's,
John


From nobody Sat Jul 31 13:38:52 2021
Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F37C3A1A6D for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 13:38:50 -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, HEADER_FROM_DIFFERENT_DOMAINS=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=iecc.com header.b=gxddiDY2; dkim=pass (2048-bit key) header.d=taugh.com header.b=iJRO+cig
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2skyktyZinO for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 13:38:46 -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 21A623A1A6B for <dmarc@ietf.org>; Sat, 31 Jul 2021 13:38:45 -0700 (PDT)
Received: (qmail 26687 invoked from network); 31 Jul 2021 20:38:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=683d.6105b4d5.k2107; bh=0Q83lWSymbIuPYLfvfErw0Sqn/fjbP7q88X8zzVvXEw=; b=gxddiDY2w+BRKQZ0XDkJOC/JxTWzuMVsAtQbrig4/muL1JwLA5ZEYtCPAa+VSMhFlQinO77hi/9YvJlY2rV7VF/f68Sh0fn61ivpSr4lfXqynmOfKAzobdjEfYsZmB3YBl1+1ZPwBG/JDxLugzJaTp2UrLp8cYdgnhaCeRnvkA8p5nBq6HSR2JT7NezquBkGD0pd4/U/kI+XaBb2iU9qQzJiTBzHLuc/VVVlXx/ieJTIhsNWX3szf9jSTp8j2FaL6nQhX0pMVjE7Wf9drn2k8tEE+Pszw92u4jtG9IPSvnFiBiMYon1Y4cPU47gPPi2EeFaxfRaUancYEbJPrLITIg==
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=683d.6105b4d5.k2107; bh=0Q83lWSymbIuPYLfvfErw0Sqn/fjbP7q88X8zzVvXEw=; b=iJRO+cigs6qDOu6V1lMrnEPPG3UI0Vs+6ILI3RQsIxIZssyxXOigXafrUgw4X/fZd6Uw807S+jW9XgLzxRYof9BVKBd5RHDp97fuakdaKaGmn6uHHIFJaU/jlRygIPwwStUXNr/UVv30V3yD1uyqBl5Zw6ZBw89vIhAzztFoVrmQrQ33arxrfJ8OzQkKSmvlJKfKXT9sqhaCxZa9vFvmUONREY0g8T2nM9sVLkPFQxKMI6QYBWT/My8A9nkBKl3lHge1JKylXSGFg0s+IZBoIOePAzBOP184KLKnuATCSGUP3EhBhEJKTjF6V+Zlt3cdJinUnCPdFokuXicrYyTyQQ==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 31 Jul 2021 20:38:44 -0000
Received: by ary.qy (Postfix, from userid 501) id 1DBB42566507; Sat, 31 Jul 2021 16:38:41 -0400 (EDT)
Date: 31 Jul 2021 16:38:41 -0400
Message-Id: <20210731203844.1DBB42566507@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: todd.herr@valimail.com
In-Reply-To: <CAHej_8m4W_k_r9SV6reNJA7aMGFCkK451tjvQGtrPNwRtJwC8A@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/shBDb5ZH1R14FvEigS8cNtmkcq8>
Subject: Re: [dmarc-ietf] Some Proposed Language for a New pct Tag Defintion
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 31 Jul 2021 20:38:51 -0000

I'd make it a lot simpler:

   pct:  (plain-text integer; OPTIONAL; default is 100).  For the
      RFC5322.From domain to which the DMARC record applies, the "pct"
      tag describes what receivers are requested to to do with unaligned messages.
      This parameter does not affect the generation of DMARC reports.  Possible values are as follows:

      0:  A request to not apply the policy, but for message forwarders
          to do whatever message rewriting they do that is intended to avoid
          sending DMARC unaligned mail.

      100:  The default, a request to apply the policy as specified.

      Any other value: results are undefined.

It makes no sense to say anything about how DMARC reports are received, they're received however they 
are.  If there were some way to give them a free pass, whaddaya know, spam would start looking
like DMARC reports.

The way this is written, p=none pct=0 requests rewriting, which I don't think is wrong.  It doesn't mean
anything else now.

R's,
John


From nobody Sat Jul 31 16:47:29 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 DDD9A3A20D2 for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 16:47:27 -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 OJw5semBrG7S for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 16:47:23 -0700 (PDT)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98CDF3A20D1 for <dmarc@ietf.org>; Sat, 31 Jul 2021 16:47:23 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id 61-20020a9d0d430000b02903eabfc221a9so13831745oti.0 for <dmarc@ietf.org>; Sat, 31 Jul 2021 16:47:23 -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=xrCp0G26yAZK3pxvojQd4aB/13nzLogHid3xZmZhBE0=; b=CMZn3QGo0oO5oXHtykyqpYzr3x1x0sWIiHkNdT7hpWfKJu8L0c1b2thlVrE2mquCYV mU1lLpRlM+Nwc2Y2hfx54nZN/Lp6lwq0cYvMv4HTZWWmT7sRR2Vit2EPF8xcCL9a2UnQ r39o8BgQPnqFyeA4kLgPCu/t0V9kXYJCK+Sz4coe0nW4bYDkjJk9J0b6P0FcDMZ8r4ML VtbozuRH/E8bzy+ioNCbldGEz2NDtUYeARSprUkHI+i/ytOazv3ajN22IyTD3Lf0FWCw F5jhXgrM5tBXbMp5VLP8JTu/f5rAwT/qSlCrKq6CBAt4kLKsIPUBGU8EYnlicEYRcNXo SAuw==
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=xrCp0G26yAZK3pxvojQd4aB/13nzLogHid3xZmZhBE0=; b=ZQdjJ2nlO4QWZGAn9Wi8r6ObLimEgrh6GXiZ2H83U7SLZ+dNdVFO/Qx0587RPwDs6+ 7yZZ9ciJfGY3gtsLz+m5CCX44+/oMqRSS3s5T+hpHAEwKhBiwU/7tcEGF1J5QFq3hsL1 5Q/X00GCJLFcVGvmNMn9bseJJWn6xDyEe3IB7CxM+Tb90RRk0F+yOCwsKduE6GWXoi73 0VJrnreFv67UhRLd3a/hMDxHmADaSrUcMzgotRuDWquEYybGdxnNuOYiNolX8tdm3epT UB2jEfE2P3M5zXJOg0wiTUCov1JGZlND57jL+CiZOuo9dLLDc+BdA/ECVTtU0vX9YNpD 0QHg==
X-Gm-Message-State: AOAM533C9+U1gr/3PDgeemKTcvTpUliHQWnUwKdBl4hBovMZAJCxEcns zzBPf3Xx0XEjkx4yBPgGObvEbmi14cZyFYDhvMNUkWnvFjE=
X-Google-Smtp-Source: ABdhPJz3KguDwDlKTvpUSB1G1Zxrj2wvTTXJN5571Am8isRjTFr2CahUjnWur9b/JDIaxJH6G97WdU+Z+/rYgqZ1Dno=
X-Received: by 2002:a05:6830:4429:: with SMTP id q41mr7052956otv.284.1627775242159;  Sat, 31 Jul 2021 16:47:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8m4W_k_r9SV6reNJA7aMGFCkK451tjvQGtrPNwRtJwC8A@mail.gmail.com> <6e96de62-f387-bb42-a5da-0b7f74674a02@tana.it>
In-Reply-To: <6e96de62-f387-bb42-a5da-0b7f74674a02@tana.it>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 31 Jul 2021 19:47:12 -0400
Message-ID: <CAH48ZfzjQxRzqpGD9GqgeJcJ25V1cA3ke-x-N-bxO9--Lm4NUQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000154a8605c873f595"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/1wvJ43fWtCft09IdZPD6UioLRXs>
Subject: Re: [dmarc-ietf] Some Proposed Language for a New pct Tag Defintion
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 31 Jul 2021 23:47:28 -0000

--000000000000154a8605c873f595
Content-Type: text/plain; charset="UTF-8"

Ale, I understand your concern but I don't know that it can be solved.

My core objection is the partial-enforcement algorithm.   I cannot believe
that it would be wise for me, or any other receiver, to implement that
algorithm.   However, DMARCv1 was written with a presumed requirement for
participating recipients to follow that algorithm.

Given my expectations around actual recipient behavior, it seems
unreasonable to tell domain owners to expect a different set of behaviors
than what will actually occur.  I do not want to mislead.

During evaluation, my practice will be to treat any value other than 100 as
equal to zero, because it means that the sender does not have enough
confidence in his situation to be able to provide me with useful
information.   It does not mean that I will ignore the sender
authentication failure.

In the face of ambiguity, the only way to get a correct disposition is to
collect more data.    If I had more time, I would quarantine all
unauthenticated mail until I could determine whether the sender should be
authenticated by local policy or blacklisted by local policy.   In
practice, I quarantine some messages and let some messages through, then
periodically go back and adjust my policies after reviewing actual message
details.

Doug Foster

On Sat, Jul 31, 2021 at 5:40 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Fri 30/Jul/2021 22:06:39 +0200 Todd Herr wrote:
> > Following on to the recent discussion about the pct tag, and
> specifically the
> > disallowing of any values other than 0 and 100, I propose the following
> text
> > and look forward to your comments:
>
>
> I still dislike this limitation.  I previously showed that users seem to
> change
> pct= with some salt.  In addition, how should implementations amend their
> code?
>   What shall a receiver do if it finds intermediate values of pct?
>
> I'd keep allowing intermediate values.  Substitute /Possible values are as
> follows:/ with /RECOMMENDED values are as follows:/.
>
> For case 0:
>
> YOUR TEXT:
>       0:  A request that zero percent of messages producing a DMARC
>           "fail" result have the specified policy applied.  While this is
>           seemingly a non-sensical request, this value has been given
>           special meaning by some mailbox providers and intermediaries
>           when combined with "p=" values other than "none".  In those
>           cases, in can result in changes to message handling, and/or
>           DMARC reporting for the domain publishing such a policy.  In
>           some instances of altered reporting, it is possible that the
>           altered reports may reveal intermediaries whose handling of the
>           domain owners' mail could cause it to produce a DMARC result of
>           "fail" when it reaches its final destination.
>
> MY PROPOSED ALTERNATIVE:
>       0:  A request that messages producing a DMARC "fail" result never
>           have the specified policy applied.  The special meaning of
>           this value is to have mailing lists which discriminate message
>           handling by author's domain policy apply From: munging
>           (see [Section X.Y.Z]) while final receivers still apply no
>           policy.
>
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr">Ale, I understand your concern but I don&#39;t know that i=
t can be solved.<div><br></div><div>My core objection is the partial-enforc=
ement=C2=A0algorithm.=C2=A0 =C2=A0I cannot believe that it would be wise fo=
r me, or any other receiver, to implement that algorithm.=C2=A0 =C2=A0Howev=
er, DMARCv1 was written with a presumed requirement for participating recip=
ients to follow that algorithm.<div><br></div><div>Given my expectations ar=
ound actual recipient behavior, it seems unreasonable to tell domain owners=
 to expect a different=C2=A0set of behaviors than what will actually=C2=A0o=
ccur.=C2=A0 I do not want to mislead.</div><div><br></div><div>During evalu=
ation, my practice will be to treat any value other than 100 as equal to ze=
ro, because it means that the sender does not have enough confidence in his=
 situation to be able to provide me with useful information.=C2=A0 =C2=A0It=
 does not mean that I will ignore the sender authentication failure.</div><=
div><br></div><div>In the face of ambiguity, the only way to get a correct =
disposition is to collect more data.=C2=A0 =C2=A0 If I had more time, I wou=
ld quarantine all unauthenticated mail until I could determine whether the =
sender should be authenticated by local policy or blacklisted by local poli=
cy.=C2=A0 =C2=A0In practice, I quarantine some messages and let some messag=
es through, then periodically go back and adjust my policies after reviewin=
g actual message details.=C2=A0</div><div><br></div><div>Doug Foster=C2=A0<=
/div></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Sat, Jul 31, 2021 at 5:40 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 sol=
id rgb(204,204,204);padding-left:1ex">On Fri 30/Jul/2021 22:06:39 +0200 Tod=
d Herr wrote:<br>
&gt; Following on to the recent discussion about the pct tag, and specifica=
lly the <br>
&gt; disallowing of any values other than 0 and 100, I propose the followin=
g text <br>
&gt; and look forward to your comments:<br>
<br>
<br>
I still dislike this limitation.=C2=A0 I previously showed that users seem =
to change <br>
pct=3D with some salt.=C2=A0 In addition, how should implementations amend =
their code? <br>
=C2=A0 What shall a receiver do if it finds intermediate values of pct?<br>
<br>
I&#39;d keep allowing intermediate values.=C2=A0 Substitute /Possible value=
s are as <br>
follows:/ with /RECOMMENDED values are as follows:/.<br>
<br>
For case 0:<br>
<br>
YOUR TEXT:<br>
=C2=A0 =C2=A0 =C2=A0 0:=C2=A0 A request that zero percent of messages produ=
cing a DMARC<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;fail&quot; result have the specifi=
ed policy applied.=C2=A0 While this is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 seemingly a non-sensical request, this v=
alue has been given<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 special meaning by some mailbox provider=
s and intermediaries<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 when combined with &quot;p=3D&quot; valu=
es other than &quot;none&quot;.=C2=A0 In those<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 cases, in can result in changes to messa=
ge handling, and/or<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 DMARC reporting for the domain publishin=
g such a policy.=C2=A0 In<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 some instances of altered reporting, it =
is possible that the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 altered reports may reveal intermediarie=
s whose handling of the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 domain owners&#39; mail could cause it t=
o produce a DMARC result of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;fail&quot; when it reaches its fin=
al destination.<br>
<br>
MY PROPOSED ALTERNATIVE:<br>
=C2=A0 =C2=A0 =C2=A0 0:=C2=A0 A request that messages producing a DMARC &qu=
ot;fail&quot; result never<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 have the specified policy applied.=C2=A0=
 The special meaning of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 this value is to have mailing lists whic=
h discriminate message<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 handling by author&#39;s domain policy a=
pply From: munging<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (see [Section X.Y.Z]) while final receiv=
ers still apply no<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 policy.<br>
<br>
<br>
Best<br>
Ale<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>

--000000000000154a8605c873f595--


From nobody Sat Jul 31 17:42: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 6BE733A230C for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 17:42: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, 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 ZujTEatJdlnS for <dmarc@ietfa.amsl.com>; Sat, 31 Jul 2021 17:42:21 -0700 (PDT)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32EE63A2309 for <dmarc@ietf.org>; Sat, 31 Jul 2021 17:42:21 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id h63-20020a9d14450000b02904ce97efee36so3187675oth.7 for <dmarc@ietf.org>; Sat, 31 Jul 2021 17:42:21 -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=kAWn+ObgshbwIvNWkZaYJ0t7NoSzKzqzXZLYRCteFy0=; b=H3wjNKXa0/yRJ/EeYQM4e0x2bAQ9T7dWgHJrZDQUo7R/duVw6FrPO5sVVRZIce6iAX CQMZOpcvc9gRgwwMKMEUVn9NrKO9Ca8qKAiJU3/nmvtj3EIvSHrr/oZf+Z+FOvKnV7hP 7WSo1cpzi+T056WM6Orh/yyCwzHjCacBRfLCNQVCPDBWcepgsrA88PFEYWYS3mrzhURA 9Flp4d9jvSrJPf1q+fVpdCoYfLW+4t3PDkCSMlN7G2kG1bwNzVJmW9WVa2tABqIg9ZUs NkLwfm6FwO9zGzcC6spF0rTycPHBDY7xQS2AnP4iPiSFVyswTPnxA61nNMCOzwDyaAZK ICfw==
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=kAWn+ObgshbwIvNWkZaYJ0t7NoSzKzqzXZLYRCteFy0=; b=RmFAzVUbrqk22qSF8pnu6PxXkS/d1wKggiGDwA41ATztQlGZZ6oGIC7QRfFZyTH8nr Gr2vFqGv35IgMLc0fQv9mXX1NOrJhqzc59xLRiCsMwP1JFkaTssj13TC9/AsJxT+n7SA igqHpCpYnCJpbp6/TndGacJyOa0AMrYJhpwhjcDBggOyNcKaptNi2a7prh6MMtNG31vU jf7wK4NJ/9nQVihi2DndlqSnysGknxYcyBOHujGaa9b4Jw8GqcrOUFayeWzp7RsffPFG 900ZfPSxLN0KMIdZAWOe28WRaw9N2cygwZ68KZ7PI/vVem2mlYcm6pr6JLhzDGez8kaO FVjg==
X-Gm-Message-State: AOAM530+PXSs+CsQ3HsWyDSDByhMOv64gyt3qV0YqrGHjDGDWWQ9mBpT wEtm4T4CVtQw9VjxsKfqAk+6vhCVh4E+ytkOnbLW2njt
X-Google-Smtp-Source: ABdhPJyCl6KvdhkWN0IYeApCJk55PFP60I8ln5CAIupKyoJJ4nrwD0ZBFn6t7yQv5pIa1awPCqfbj4Jko2r6HSkQdrI=
X-Received: by 2002:a9d:7010:: with SMTP id k16mr6895572otj.298.1627778539719;  Sat, 31 Jul 2021 17:42:19 -0700 (PDT)
MIME-Version: 1.0
References: <CAL0qLwb114xmTg7Qe5wAg2q316ih4x7RpS8WAomdnjsWDyd0Uw@mail.gmail.com> <20210731202426.CE9FD2566204@ary.qy>
In-Reply-To: <20210731202426.CE9FD2566204@ary.qy>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Sat, 31 Jul 2021 20:42:09 -0400
Message-ID: <CAH48ZfwOegnX=3NCPxOOQ3oGK2muj=CLSDSNQ5fA-CFFq80taQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a20fbe05c874b986"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/KWy3BoQ3TjaR7SRAEXhMqvSYuLM>
Subject: Re: [dmarc-ietf] not enhanced status codes Some Proposed Language for a New pct Tag Defintion
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@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, 01 Aug 2021 00:42:26 -0000

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

2.6.0 really is a mystery to me.  The domain under study uses p=reject and
is getting 100% authenticated in the RUA reports, so it does not fit John's
theory.

I always get 2.6.0 from outlook.com servers and a few other destinations.
 So perhaps it is just their version of "OK so far, but I may block you
later in the evaluation process."

I would be interested if anyone else has data on extended status codes.  If
it seems too off-topic for the whole group, you can send to me directly.

Doug


On Sat, Jul 31, 2021 at 4:24 PM John Levine <johnl@taugh.com> wrote:

> It appears that Murray S. Kucherawy  <superuser@gmail.com> said:
> >Indeed; I would like to understand what 2.6.0 is meant to convey.  As I
> >read the IANA registry entries, "2" means success but "6" means there was
> a
> >media type error.
>
> I think it's supposed to mean "I accepted your message but I wouldn't have
> if I were
> enforcing DMARC p=none".
>
> Since this would be a gift to spammers trying to probe and evade filters,
> I find it
> very unlikely anyone would implement it, so no.
>
> R's,
> John
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>

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

<div dir=3D"ltr"><div>2.6.0 really is a mystery to me.=C2=A0 The domain und=
er study uses p=3Dreject and is getting 100% authenticated in the RUA repor=
ts,=C2=A0so it does not fit John&#39;s theory.</div><div><br></div><div>I a=
lways get 2.6.0 from <a href=3D"http://outlook.com">outlook.com</a> servers=
 and a few other destinations.=C2=A0 =C2=A0So perhaps it is just their vers=
ion of &quot;OK so far, but I may block you later in the evaluation=C2=A0pr=
ocess.&quot;=C2=A0</div><div><br></div><div>I would be interested if anyone=
 else has data on extended status codes.=C2=A0 If it seems too off-topic fo=
r=C2=A0the=C2=A0whole group, you can send to me directly.</div><div><br></d=
iv><div>Doug</div><div><br></div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Sat, Jul 31, 2021 at 4:24 PM John Levin=
e &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;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">It appears that Mur=
ray S. Kucherawy=C2=A0 &lt;<a href=3D"mailto:superuser@gmail.com" target=3D=
"_blank">superuser@gmail.com</a>&gt; said:<br>
&gt;Indeed; I would like to understand what 2.6.0 is meant to convey.=C2=A0=
 As I<br>
&gt;read the IANA registry entries, &quot;2&quot; means success but &quot;6=
&quot; means there was a<br>
&gt;media type error.<br>
<br>
I think it&#39;s supposed to mean &quot;I accepted your message but I would=
n&#39;t have if I were<br>
enforcing DMARC p=3Dnone&quot;.<br>
<br>
Since this would be a gift to spammers trying to probe and evade filters, I=
 find it<br>
very unlikely anyone would implement it, so no.<br>
<br>
R&#39;s,<br>
John<br>
<br>
_______________________________________________<br>
dmarc mailing list<br>
<a href=3D"mailto:dmarc@ietf.org" target=3D"_blank">dmarc@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dmarc" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dmarc</a><br>
</blockquote></div>

--000000000000a20fbe05c874b986--

