External failure recipients
03External ruf destinations use the aggregate specification’s destination-verification procedure with the failure-report tag.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 5 ↗
RFC 9991 · § 5EXAMPLE
3 / 3
03
Stop unauthorized delivery
Do not send to an external recipient that has not authorized it.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Use RFC 9990 §4 with ruf substituted for rua.
- Use RFC 9990 §4 with ruf substituted for rua.
- An external recipient must authorize reports.
- This prevents arbitrary domains from forcing sensitive reports onto an unwilling destination.
Examples are illustrative. Read the exact policy, reporting, and privacy rules in the linked current specification.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy