Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field

[Seth Blank <[e-mail]>]

On Sat, Sep 26, 2020 at 3:50 PM Scott Kitterman <[e-mail]>
wrote:

> Is the context in terms of the protocol specified by RFC 7489?
>

Yes.


> That may sound like a silly question, but I think fundamentally if "DMARC"
> is
> just an input to a filter or if "DMARC" is a protocol to reject/quarantine
> email that meets certain policy criteria makes a big difference in how
> some of
> these questions are addressed.
>

The goal of DMARCbis is to take the independent stream informational RFC
7489 and drive it to an IETF stream standards track document that
represents IETF consensus. So this work is explicitly around DMARC as a
protocol that describes how a domain owner transmits its policy for mail
that does not authenticate to a mail receiver.

Further, our charter takes the usefulness of DMARC in its current form as
table stakes, and (to paraphrase) primarily focuses our discussion around
addressing limitations or operational concerns of the protocol.

One of the primary limitations of DMARC is when mail transits through a
forwarder that breaks authentication. For DMARC to go standards track, this
issue must be addressed. Currently ARC is the approved experiment from
Phase 2 of our Charter.

Seth, as Chair