File formats:

Also available: XML file for editing

 

Status:

INFORMATIONAL

Authors:

D. K. Gillmor, Ed.
A. Melnikov, Ed.
B. Hoeneisen, Ed.

Stream:

IETF

Source:

lamps (sec)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9787

Discuss this RFC: Send questions or comments to the mailing list spasm@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9787

Abstract

End-to-end cryptographic protections for email messages can provide useful security. However, the standards for providing cryptographic protection are extremely flexible. That flexibility can trap users and cause surprising failures. This document offers guidance for Mail User Agent (MUA) implementers to help mitigate those risks and to make end-to-end email simple and secure for the end user. It provides a useful set of vocabulary as well as recommendations to avoid common failures. It also identifies a number of currently unsolved usability and interoperability problems.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.