Re: [dmarc-ietf] Header munging, not ARC, can solve the mailing list problem

On 6/13/20 8:17 PM, Dave Crocker wrote: > On 6/13/2020 7:53 PM, Jim Fenton wrote: >> Alas, others do, > > Other groups do all sorts of things.  They once mandated OSI, for > example. > > Please explain how that is relevant, here and now. The WG needs to consider the operational impact of DMARC

Re: [dmarc-ietf] why ARC

In article you write: >-=-=-=-=-=- >> > ARC lets the recipient look back and retroactively do the filtering >> > the list didn't. >> >> The concern about the creator of an ARC chain spoofing the purported >> origin of a message is valid. > >By "creator" do you mean "initiator" (aka, the source

Re: [dmarc-ietf] why ARC

On 6/14/2020 10:25 AM, Kurt Andersen (b) wrote: On Fri, Jun 12, 2020 at 5:52 PM Dave Crocker > wrote: > ARC lets the recipient look back and retroactively do the filtering > the list didn't. The concern about the creator of an ARC chain spoofing the

Re: [dmarc-ietf] why ARC

On Fri, Jun 12, 2020 at 5:52 PM Dave Crocker wrote: > > > ARC lets the recipient look back and retroactively do the filtering > > the list didn't. > > The concern about the creator of an ARC chain spoofing the purported > origin of a message is valid. > By "creator" do you mean "initiator"

[dmarc-ietf] DMARC Policy Boundary Conditions - making DMARC protocol complete.

When we look at DKIM and the DMARC protocol by exposing the boundary conditions of the protocol, it helps with laying the groundwork for a protocol-complete model. DKIM has three possible signature states: - NONE (no valid signature) - 1PS (1st party valid signature, Author.domain ==

Re: [dmarc-ietf] Header munging, not ARC, can solve the mailing list problem

On Sunday, June 14, 2020 5:24:42 AM EDT devel2...@baptiste-carvello.net wrote: > Le 13/06/2020 à 17:19, Douglas E. Foster a écrit : > > About this comment > > > > If you teach users that "Joe User by Random Intermediary" is the same > > as "Joe User", this expectation is doomed.> > >

Re: [dmarc-ietf] Header munging, not ARC, can solve the mailing list problem

On Fri, Jun 12, 2020 at 5:06 PM Scott Kitterman wrote: > > On June 12, 2020 11:33:13 PM UTC, "Kurt Andersen (b)" > wrote: > >I would like to understand what you mean by: > > > >On Fri, Jun 12, 2020 at 1:02 AM Alessandro Vesely > >wrote: > > > >> . . . ARC chains can be forged. > > Not sure

Re: [dmarc-ietf] Header munging, not ARC, can solve the mailing list problem

Le 13/06/2020 à 17:19, Douglas E. Foster a écrit : About this comment If you teach users that "Joe User by Random Intermediary" is the same as "Joe User", this expectation is doomed. Based on the response to my previous post, "Trained User" is not a meaningful concept, for purposes of