On Tue 11/Aug/2026 18:59:58 +0200 Murray S. Kucherawy wrote:
On Tue, Aug 11, 2026 at 4:30 AM Alessandro Vesely <[email protected]> wrote:
Accurate reputation development improves the quality of service you can
provide. Accordingly, individual operators (of varying sizes) develop and
keep this reputation entirely within their systems, and as far as I know it
is never shared.
Yes, that reputation systems are usually unique to the organizations operating
them was already anticipated in draft-jones-arc-usage in 2015. Although the
same document also envisages reputation service providers.
Likewise, the "parallel trust infrastructure" is not really
explained. What exactly is that infrastructure? These concepts are
implicitly
assumed by the RFC, not explicitly defined. So, if we use them to explain
ARC's failure, we have to say what they are supposed to be.
Yeah, that would probably be a good idea for this one.
Here's a possible outline of what a "trust infrastructure" might mean:
A full trust architecture encompasses a range of actors and
activities, to enable an end-to-end service for creating, exchanging,
and consuming trust-related information. One component of that is a
query mechanism, to permit retrieval of a reputation.
https://datatracker.ietf.org/doc/html/rfc7070
Is this the kind of infrastructure that the draft says ARC required? If so,
given that dkim-reputation.org was already dead and RFCs 7070-7073 apparently
had little deployment, why was it reasonable in 2015-2019 to expect such an
infrastructure to support ARC? If not, then it is unclear what "parallel trust
infrastructure" the I-D is referring to, or what role that infrastructure
played in ARC's lack of success.
Best
Ale
--
_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]