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

[Brandon Long <[e-mail]>]

On Fri, Aug 14, 2020 at 12:09 PM Jim Fenton <[e-mail]> wrote:

> On 8/10/20 12:04 PM, Tim Wicinski wrote:
>
>
> During IETF 108, the chairs realized that there was interest in Dave's
> RFC5322.Sender draft.
>
> This starts a Call for Adoption for draft-crocker-dmarc-sender
>
> I do not support adoption of this draft as a working group document for
> different reasons than I have seen expressed by others on the list.
>
> If the Sender header field is to be used by DMARC in the manner described
> in this draft, it should be an integral part of the DMARCbis specification
> rather than a separate extension to it. In other words, this should be an
> issue on the DMARC WG issue tracker rather than a working group draft (and
> presumably eventual RFC). There are enough different combinations of
> originators and receivers that might use Sender (which the chart in Section
> 2 begins to describe) that we don't need the ongoing ambiguity of whether
> the receiver does or does not implement this as an extension.
>

+1

If DMARC wasn't experimental, maybe I could see adding it separately, but
this seems like a fairly fundamental change and shouldn't just be a
bolt-on... especially since as written this appears to undermine the
existing DMARC.. ie if DMARC is "apply this policy to these messages" and
this addition says "nah, don't apply them to some of those messages".

Brandon