References from rfc5436
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 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2368 |
The mailto URL scheme
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3834 |
Recommendations for Automatic Responses to Electronic Mail
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5228 |
Sieve: An Email Filtering Language
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5229 |
Sieve Email Filtering: Variables Extension
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5321 |
Simple Mail Transfer Protocol
References Referenced by |
Draft Standard | informatively references | |
| RFC 5322 |
Internet Message Format
References Referenced by |
Draft Standard | normatively references | |
| RFC 5435 |
Sieve Email Filtering: Extension for Notifications
References Referenced by |
Proposed Standard | normatively references |