References from draft-ietf-lamps-e2e-mail-guidance
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 |
|---|---|---|---|---|
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3156 |
MIME Security with OpenPGP
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3274 |
Compressed Data Content Type for Cryptographic Message Syntax (CMS)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 4289 |
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4880 |
OpenPGP Message Format
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5322 |
Internet Message Format
References Referenced by |
Draft Standard | informatively references | |
| RFC 5355 |
Threats Introduced by Reliable Server Pooling (RSerPool) and Requirements for Security in Response to Threats
References Referenced by |
Informational | informatively references | |
| RFC 6376 |
DomainKeys Identified Mail (DKIM) Signatures
References Referenced by |
Internet Standard | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8551 |
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification
References Referenced by |
Proposed Standard | normatively references |