Recommendations for use of TLS by Electronic Mail Access Protocols
draft-moore-email-tls-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Keith Moore | ||
| Last updated | 2014-04-24 (Latest revision 2013-10-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo requires support for Transport Layer Security (TLS) in all electronic mail user agents (MUAs) and the servers with which they communicate when using standard protocols, including Interactive Message Access Protocol (IMAP), Post Office Protocol (POP) and the variant of the Simple Message Transfer Protocol (SMTP) used in message submission. It also requires support for TLS in mail protocol servers provided by electronic mail service providers, and encourages mail service providers to migrate to requiring TLS for all interaction with their servers. In addition, this memo details specific recommendations for implementation and use of TLS with electronic mail protocols used in interactions between MUAs and mail service providers. Use of TLS with SMTP for message relaying is described in a separate document, and not in scope for this document. The recommendations in this memo do not replace the functionality of, and are not intended as a substitute for, end-to-end encryption of electronic mail.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)