Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000245661D
Original Publication Date: 2016-Mar-01
Included in the Prior Art Database: 2016-Mar-25
Document File: 26 page(s) / 30K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Melnikov: AUTHOR

Abstract

Use of TLS by SMTP Submission, IMAP, POP, and ManageSieve clients is described in [RFC3207], [RFC3501], [RFC2595], and [RFC5804], respectively. Each of the documents describes slightly different rules for server certificate identity verification (or doesn't define any rules at all). In reality, email client and server developers implement many of these protocols at the same time, so it would be good to define modern and consistent rules for verifying email server identities using TLS.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 9% of the total text.

Internet Engineering Task Force (IETF)                       A. Melnikov Request for Comments: 7817                                     Isode Ltd Updates: 2595, 3207, 3501, 5804                               March 2016 Category: Standards Track ISSN: 2070-1721

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

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7817.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

 Melnikov                     Standards Track                    [Page 1]
 RFC 7817           TLS Server Identity Check for Email        March 2016

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Conventions Used in This Document . . . . . . . . . . . . . .   3

   3.  Email Server Certificate Verification Rules . . . . . . . . .   3

   4.  Compliance Checklist for Certification Authorities  . . . . .   5

     4.1.  Notes on Handling of Delegated Email Services by

           Certification Authorities . . . . . . . . . . . . . . . .   5

   5.  Compliance Chec...