On Wed, Jul 5, 2017 at 4:36 PM, Seth Blank <[email protected]> wrote:
> The *only* intent here is to report back services that break > authentication to the domain owner in a DMARC report. As such, the selector > disambiguates services (especially when there are multiple hops, some of > which might have the same d=) and allows a reporter to make a clear > determination to a report consumer of where authentication failed so that a > service can be properly configured in SPF or with DKIM. > Are we talking about adding this to the DMARC reports or to A-R? Both have been suggested in this thread. I believe you're specifically talking about DMARC reports, and I have less of a concern with those. On the other hand, adding them to A-R makes less sense because that's got users partly in mind, and I don't think a user would care too much what selector is being used in a DKIM signature. Explicitly discouraging development of reputation based on an s=/d= pairing would be an added bonus. -MSK
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
