References from draft-melnikov-email-draft-and-release
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 90 |
References Referenced by |
normatively references | ||
| RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by |
Draft Standard | 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 | normatively references | |
| RFC 3864 |
Registration Procedures for Message Header Fields
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Internet Standard | normatively references | |
| RFC 5322 |
Internet Message Format
References Referenced by |
Draft Standard | normatively references | |
| RFC 6532 |
Internationalized Email Headers
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7912 |
Message Authorizing Email Header Field and Its Use for the Draft and Release Procedure
References Referenced by |
Informational | normatively references | |
| RFC 8098 |
Message Disposition Notification
References Referenced by |
Internet Standard | normatively references | |
| RFC 8255 |
Multiple Language Content Type
References Referenced by |
Proposed Standard | normatively references | |
| STD 68 |
References Referenced by |
normatively references | ||
| STD 85 |
References Referenced by |
normatively references |