The “MUST” in this section is consistent with the aggregate reporting document.
Todd Herr Some Guy in VA LLC [email protected] 703-220-4153 On Sun, Sep 21, 2025 at 17:11 Steven M Jones <[email protected]> wrote: > On 9/5/25 9:08 PM, Steven M Jones wrote: > > Next section up for review: > > 5. > <https://www.ietf.org/archive/id/draft-ietf-dmarc-failure-reporting-14.html#section-5>Verifying > External Destinations > <https://www.ietf.org/archive/id/draft-ietf-dmarc-failure-reporting-14.html#name-verifying-external-destinat> > > This section introduces a requirement ("MUST") that, for sending failure > reports to an "external destination" (e.g. a destination that is not the > Organization Domain), the report generator must follow the Verifying > External Destinations procedure from the Aggregate Reporting document. > > The second paragraph ends with a reference to "potential privacy issues." > If that's not sufficient, I'd recommend a modification like, "potential > privacy issues, examples of which are included in Section 7." > > > Any concerns? > > Just noting that no concerns were raised in over two weeks, so I take it > that no changes are needed here. > > --S. > > > _______________________________________________ > dmarc mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
