Skip to main content

Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access
RFC 8314

Revision differences

Document history

Date By Action
2018-04-16
(System) Received changes through RFC Editor sync (added Errata tag)
2018-01-31
(System)
Received changes through RFC Editor sync (created alias RFC 8314, changed title to 'Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email …
Received changes through RFC Editor sync (created alias RFC 8314, changed title to 'Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access', changed abstract to 'This specification outlines current recommendations for the use of Transport Layer Security (TLS) to provide confidentiality of email traffic between a Mail User Agent (MUA) and a Mail Submission Server or Mail Access Server.  This document updates RFCs 1939, 2595, 3501, 5068, 6186, and 6409.', changed pages to 26, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-01-31, changed IESG state to RFC Published, created updates relation between draft-ietf-uta-email-deep and RFC 1939, created updates relation between draft-ietf-uta-email-deep and RFC 2595, created updates relation between draft-ietf-uta-email-deep and RFC 3501, created updates relation between draft-ietf-uta-email-deep and RFC 5068, created updates relation between draft-ietf-uta-email-deep and RFC 6186, created updates relation between draft-ietf-uta-email-deep and RFC 6409)
2018-01-31
(System) RFC published