RFC 7817: Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols

In plain English — editorial summary, not part of the RFC

This document describes the Transport Layer Security (TLS) server identity verification procedure for SMTP Submission, IMAP, POP, and ManageSieve clients. It replaces Section 2.4 (Server Identity Check) of RFC 2595 and updates Section 4.1 (Processing After the STARTTLS Command) of RFC 3207, Section 11.1 (STARTTLS Security Considerations) of RFC 3501, and Section 2.2.1 (Server Identity Check) of RFC 5804.

Document record

Document ID

RFC7817

Published

March 2016

Authors

A. Melnikov

Status

PROPOSED STANDARD

Stream

IETF

Area

sec

Pages

13

Also known as

—

Updates:

RFC 2595, RFC 3207, RFC 3501, RFC 5804

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC7817

Topics

• SMTP
• Submission
• IMAP
• POP
• ManageSieve

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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

  January 2018

• RFC 6186Use of SRV Records for Locating Email Submission/Access ServicesUpdated

  March 2011

• RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated

  August 2009

• RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent

  August 2009

• RFC 7672SMTP Security via Opportunistic DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS)Current

  October 2015

• RFC 7636Proof Key for Code Exchange by OAuth Public ClientsCurrent

  September 2015

• RFC 8689SMTP Require TLS OptionCurrent

  November 2019

• RFC 7888IMAP4 Non-synchronizing LiteralsCurrent

  May 2016

Also filed under

• PROPOSED STANDARD
• 2016
• IETF stream
• sec area