References from RFC 2530
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 |
Reference | ||
| BCP 31 |
References Referenced by |
Reference | ||
| RFC 1893 |
Enhanced Mail System Status Codes
References Referenced by |
Proposed Standard | Possible Reference | |
| RFC 1894 |
An Extensible Message Format for Delivery Status Notifications
References Referenced by |
Proposed Standard | Reference | |
| RFC 2034 |
SMTP Service Extension for Returning Enhanced Error Codes
References Referenced by |
Proposed Standard | Reference | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Reference | |
| RFC 2234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Proposed Standard | Reference | |
| RFC 2298 |
An Extensible Message Format for Message Disposition Notifications
References Referenced by |
Proposed Standard | Reference | |
| RFC 2506 |
Media Feature Tag Registration Procedure
References Referenced by |
Best Current Practice | Reference | |
| RFC 2533 |
A Syntax for Describing Media Feature Sets
References Referenced by |
Proposed Standard | Reference |