Either way, I think Todd raises a valid point. Given the near identical
context of the language, the asserted intent should be consistent for
both, dependent on MUST NOT or SHOULD NOT consensus.
In my eyes as a consumer of the document output, I would probably be
asking the same clarifying questions of the WG about these two sections
in the future, because they're not consistent.
- Mark Alley
On 2/29/2024 1:47 PM, Scott Kitterman wrote:
Okay. I think 8.6 is the one in error. You see how this is going to go, right?
Scott K
On February 29, 2024 7:45:15 PM UTC, Todd
Herr<[email protected]> wrote:
It is not my intent here to relitigate any issues.
Rather, I believe that the text in 7.6 is wrong, likely due to an oversight
on my part when the new text in 8.6 was published, and I just want to
confirm that 7.6 is indeed wrong.
On Thu, Feb 29, 2024 at 2:10 PM Scott Kitterman<[email protected]>
wrote:
In what way is this a new issue that has not already been argued to death
in the WG? I think for WGLC, we've already done this. We will, no doubt
get to have this conversation during the IETF last call, but for the
working group, this strikes me as exactly the type of relitigation of
issues we've been counseled to avoid.
Scott K
On February 29, 2024 6:54:57 PM UTC, Todd Herr <todd.herr=
[email protected]> wrote:
Colleagues,
I've been reading DMARCbic rev -30 today with a plan to collect the first
set of minor edits and I came across a sentence that I believe goes beyond
minor, so wanted to get a sanity check.
Section 7.6, Domain Owner Actions, ends with the following sentence:
In particular, this document makes explicit that domains for
general-purpose email MUST NOT deploy a DMARC policy of p=reject.
I don't believe this to be true, however. Rather, Section 8.6,
Interoperability Considerations, says SHOULD NOT on the topic (e.g., "It
is
therefore critical that domains that host users who might post messages to
mailing lists SHOULD NOT publish p=reject")
Section 7.6 therefore should be updated to read "domains for
general-purpose email SHOULD NOT deploy a DMARC policy of p=reject", yes?
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
--
- Mark Alley
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
