References from draft-melnikov-jmap-smime-sender-extensions-alt
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 |
|---|---|---|---|---|
| draft-ietf-lamps-e2e-mail-guidance |
Guidance on End-to-End E-mail Security
References Referenced by |
Informational | normatively references | |
| draft-ietf-lamps-header-protection |
Header Protection for Cryptographically Protected E-mail
References Referenced by |
Proposed Standard | normatively references | |
| RFC 1847 |
Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
References Referenced by |
Proposed Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8550 |
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Certificate Handling
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8551 |
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8620 |
The JSON Meta Application Protocol (JMAP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8621 |
The JSON Meta Application Protocol (JMAP) for Mail
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9404 |
JSON Meta Application Protocol (JMAP) Blob Management Extension
References Referenced by |
Proposed Standard | informatively references |