References from RFC 5260
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 | ||
| BCP 78 |
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2822 |
Internet Message Format
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3339 |
Date and Time on the Internet: Timestamps
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3501 |
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5228 |
Sieve: An Email Filtering Language
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5230 |
Sieve Email Filtering: Vacation Extension
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5231 |
Sieve Email Filtering: Relational Extension
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references | |
| STD 11 |
References Referenced by |
Possible Reference | ||
| STD 68 |
References Referenced by |
normatively references |