<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-lamps-e2e-mail-guidance" target="https://datatracker.ietf.org/doc/html/draft-ietf-lamps-e2e-mail-guidance-14">
   <front>
      <title>Guidance on End-to-End E-mail Security</title>
      <author initials="D. K." surname="Gillmor" fullname="Daniel Kahn Gillmor">
         <organization>American Civil Liberties Union</organization>
      </author>
      <author initials="B." surname="Hoeneisen" fullname="Bernie Hoeneisen">
         <organization>pEp Foundation</organization>
      </author>
      <author initials="A." surname="Melnikov" fullname="Alexey Melnikov">
         <organization>Isode Ltd</organization>
      </author>
      <date month="February" day="1" year="2024" />
      <abstract>
	 <t>   End-to-end cryptographic protections for e-mail 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 implementers to help mitigate those risks, and to
   make end-to-end e-mail 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-lamps-e2e-mail-guidance-14" />
   
</reference>
