Use of TLS for Email Submission and Access
draft-lvelvindron-tls-for-email-02

Document Type Active Internet-Draft (individual)
Last updated 2018-10-15
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      L. Velvindron
Internet-Draft                                             cyberstorm.mu
Updates: 8314 (if approved)                                   S. Farrell
Intended status: Standards Track                  Trinity College Dublin
Expires: April 18, 2019                                 October 15, 2018

               Use of TLS for Email Submission and Access
                   draft-lvelvindron-tls-for-email-02

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 April 18, 2019.

Copyright Notice

   Copyright (c) 2018 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 April 18, 2019                 [Page 1]
Internet-Draft                TLS For Email                 October 2018

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.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Informative References  . . . . . . . . . . . . . . . . .   4
     6.2.  Normative References  . . . . . . . . . . . . . . . . . .   4
   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."

   NEW:

Velvindron & Farrell     Expires April 18, 2019                 [Page 2]
Internet-Draft                TLS For Email                 October 2018

   "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.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
   or greater from the start.  However, an MSP may find it necessary to
Show full document text