--- 1/draft-ietf-uta-tls-for-email-00.txt 2019-03-07 01:13:10.941502586 -0800 +++ 2/draft-ietf-uta-tls-for-email-01.txt 2019-03-07 01:13:10.953502878 -0800 @@ -1,19 +1,19 @@ Network Working Group L. Velvindron Internet-Draft cyberstorm.mu Updates: 8314 (if approved) S. Farrell Intended status: Standards Track Trinity College Dublin -Expires: May 30, 2019 November 26, 2018 +Expires: September 8, 2019 March 7, 2019 Use of TLS for Email Submission and Access - draft-ietf-uta-tls-for-email-00 + draft-ietf-uta-tls-for-email-01 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 @@ -23,47 +23,48 @@ 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 May 30, 2019. + This Internet-Draft will expire on September 8, 2019. Copyright Notice - Copyright (c) 2018 IETF Trust and the persons identified as the + Copyright (c) 2019 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. 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 + 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. @@ -86,27 +87,26 @@ "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: "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." + 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: @@ -165,30 +166,34 @@ 4. IANA Considerations None of the proposed measures have an impact on IANA. 5. Security Considerations The purpose of this document is to document updated recommendations for using TLS with Email services. Those recommendations are based on [I-D.ietf-tls-oldversions-deprecate]. -6. References +6. Acknowledgement -6.1. Informative References + The authors would like to thank Vittorio Bertola for his feedback. + +7. References + +7.1. Informative References [RFC4346] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.1", RFC 4346, DOI 10.17487/RFC4346, April 2006, . -6.2. Normative References +7.2. Normative References [I-D.ietf-tls-oldversions-deprecate] Moriarty, K. and S. Farrell, "Deprecating TLSv1.0 and TLSv1.1", draft-ietf-tls-oldversions-deprecate-01 (work in progress), November 2018. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, .