Deprecation of use of TLS 1.1 for Email Submission and Access
draft-ietf-uta-tls-for-email-04

Document Type Active Internet-Draft (uta WG)
Last updated 2020-02-07 (latest revision 2020-01-23)
Replaces draft-lvelvindron-tls-for-email
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Valery Smyslov
Shepherd write-up Show (last changed 2020-01-15)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date On agenda of 2020-02-20 IESG telechat
Needs 5 more YES or NO OBJECTION positions to pass.
Responsible AD Alexey Melnikov
Send notices to Valery Smyslov <valery@smyslov.net>
IANA IANA review state IANA OK - No Actions Needed
Network Working Group                                      L. Velvindron
Internet-Draft                                             cyberstorm.mu
Updates: 8314 (if approved)                                   S. Farrell
Intended status: Standards Track                  Trinity College Dublin
Expires: July 26, 2020                                  January 23, 2020

     Deprecation of use of TLS 1.1 for Email Submission and Access
                    draft-ietf-uta-tls-for-email-04

Abstract

   This specification updates current recommendation for the use of
   Transport Layer Security (TLS) protocol to provide confidentiality of
   email between a Mail User Agent (MUA) and a Mail Submission Server or
   Mail Access Server.  This document updates RFC8314.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 26, 2020.

Copyright Notice

   Copyright (c) 2020 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
   (https://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.

Velvindron & Farrell      Expires July 26, 2020                 [Page 1]
Internet-Draft                TLS For Email                 January 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   2
   3.  Updates to RFC8314  . . . . . . . . . . . . . . . . . . . . .   2
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Informative References  . . . . . . . . . . . . . . . . .   4
     7.2.  Normative References  . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   [RFC8314] defines the minimum recommended version for TLS as version
   1.1.  Due to the deprecation of TLS 1.1 in
   [I-D.ietf-tls-oldversions-deprecate], this recommendation is no
   longer valid.  Therefore this document updates [RFC8314] so that the
   minimum version for TLS is TLS 1.2.

2.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119] when they
   appear in ALL CAPS.  These words may also appear in this document in
   lower case as plain English words, absent their normative meanings.

3.  Updates to RFC8314

   OLD:

   "4.1.  Deprecation of Services Using Cleartext and TLS Versions Less
   Than 1.1"

   NEW:

   "4.1.  Deprecation of Services Using Cleartext and TLS Versions Less
   Than 1.2"

   OLD

   "As soon as practicable, MSPs currently supporting Secure Sockets
   Layer (SSL) 2.x, SSL 3.0, or TLS 1.0 SHOULD transition their users to
   TLS 1.1 or later and discontinue support for those earlier versions
   of SSL and TLS."

Velvindron & Farrell      Expires July 26, 2020                 [Page 2]
Internet-Draft                TLS For Email                 January 2020

   NEW:

   "As soon as practicable, MSPs currently supporting Secure Sockets
   Layer (SSL) 2.x, SSL 3.0, TLS 1.0 or TLS 1.1 SHOULD transition their
   users to TLS 1.2 or later and discontinue support for those earlier
   versions of SSL and TLS."

   OLD:

   In Section 4.1, the text should be revised from: "It is RECOMMENDED
   that new users be required to use TLS version 1.1 or greater from the
   start.  However, an MSP may find it necessary to make exceptions to
   accommodate some legacy systems that support only earlier versions of
   TLS or only cleartext."

   NEW:

   "It is RECOMMENDED that new users be required to use TLS version 1.2
Show full document text