References from draft-ordogh-spam-reporting-using-imap-kleansed
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | informatively references | |
| RFC 3462 |
The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages
References Referenced by |
Draft Standard | informatively references | |
| RFC 3501 |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4467 |
Internet Message Access Protocol (IMAP) - URLAUTH Extension
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references | |
| RFC 5965 |
An Extensible Format for Email Feedback Reports
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6430 |
Email Feedback Report Type Value: not-spam
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6449 |
Complaint Feedback Loop Operational Recommendations
References Referenced by |
Informational | informatively references | |
| RFC 6965 |
MPLS Transport Profile (MPLS-TP) Applicability: Use Cases and Design
References Referenced by |
Informational | informatively references |