Abuse and recipient controls
05Failure reporting can be abused as an amplification or disclosure path.
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§ 8.1 ↗
RFC 9991 · § 8.1EXAMPLE
3 / 3
03
Retain diagnostic value safely
Do not let feedback become an unbounded message-content leak.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Destination verification does not remove all denial-of-service risks.
- Destination verification does not remove all denial-of-service risks.
- Report generation and processing need operational safeguards.
- Domain owners and receivers must account for disclosure, storage, and untrusted input.
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