References from RFC 5463
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 | 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 5229 |
Sieve Email Filtering: Variables Extension
References Referenced by |
Proposed Standard | informatively 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 | informatively references | |
RFC 5232 |
Sieve Email Filtering: Imap4flags Extension
References Referenced by |
Proposed Standard | informatively references | |
RFC 5233 |
Sieve Email Filtering: Subaddress Extension
References Referenced by |
Proposed Standard | informatively references | |
RFC 5235 |
Sieve Email Filtering: Spamtest and Virustest Extensions
References Referenced by |
Proposed Standard | informatively references |