References from draft-pep-email
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 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
BCP 205 |
Improving Awareness of Running Code: The Implementation Status Section References Referenced by |
Best Current Practice | informatively references | |
draft-birk-pep |
pretty Easy privacy (pEp): Privacy by Default References Referenced by |
normatively references | ||
draft-birk-pep-trustwords |
IANA Registration of Trustword Lists: Guide, Template and IANA Considerations References Referenced by |
informatively references | ||
draft-marques-pep-email |
pretty Easy privacy (pEp): Email Formats and Protocols References Referenced by |
informatively references | ||
draft-marques-pep-handshake |
pretty Easy privacy (pEp): Contact and Channel Authentication through Handshake References Referenced by |
normatively references | ||
draft-marques-pep-rating |
pretty Easy privacy (pEp): Mapping of Privacy Rating References Referenced by |
normatively references | ||
draft-melnikov-iana-reg-forwarded |
IANA Registration of Content-Type Header Field Parameter 'forwarded' References Referenced by |
normatively references | ||
draft-pep-keysync |
pretty Easy privacy (pEp): Key Synchronization Protocol (KeySync) References Referenced by |
informatively references | ||
FYI 36 |
Internet Security Glossary, Version 2 References Referenced by |
Informational | 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 3156 |
MIME Security with OpenPGP References Referenced by |
Proposed Standard | normatively references | |
RFC 4880 |
OpenPGP Message Format References Referenced by |
Proposed Standard | normatively references | |
RFC 4949 |
Internet Security Glossary, Version 2 References Referenced by |
Informational | normatively references | |
RFC 5322 |
Internet Message Format References Referenced by |
Draft Standard | normatively references | |
RFC 7435 |
Opportunistic Security: Some Protection Most of the Time References Referenced by |
Informational | normatively references | |
RFC 7942 |
Improving Awareness of Running Code: The Implementation Status Section References Referenced by |
Best Current Practice | informatively references | |
RFC 8551 |
Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification References Referenced by |
Proposed Standard | informatively references |