--- 1/draft-ietf-tls-oldversions-deprecate-05.txt 2020-01-06 08:13:14.004690168 -0800 +++ 2/draft-ietf-tls-oldversions-deprecate-06.txt 2020-01-06 08:13:14.056691496 -0800 @@ -1,76 +1,76 @@ Internet Engineering Task Force K. Moriarty Internet-Draft Dell EMC Updates: 8465 8422 8261 7568 7562 7525 S. Farrell 7507 7465 7030 6750 6749 6739 Trinity College Dublin - 6460 6084 6083 6367 6347 6176 June 20, 2019 - 6042 6012 5878 5734 5469 5456 - 5422 5415 5364 5281 5263 5238 - 5216 5158 5091 5054 5049 5024 - 5023 5019 5018 4992 4976 4975 - 4964 4851 4823 4791 4785 4744 - 4743 4732 4712 4681 4680 4642 - 4616 4582 4540 4531 4513 4497 - 4279 4261 4235 4217 4168 4162 - 4111 4097 3983 3943 3903 3887 - 3871 3856 3767 3749 3656 3568 - 3552 3501 3470 3436 3329 3261 - (if approved) + 6614 6460 6084 6083 6367 6347 January 6, 2020 + 6176 6042 6012 5878 5734 5469 + 5456 5422 5415 5364 5281 5263 + 5238 5216 5158 5091 5054 5049 + 5024 5023 5019 5018 4992 4976 + 4975 4964 4851 4823 4791 4785 + 4744 4743 4732 4712 4681 4680 + 4642 4616 4582 4540 4531 4513 + 4497 4279 4261 4235 4217 4168 + 4162 4111 4097 3983 3943 3903 + 3887 3871 3856 3767 3749 3656 + 3568 3552 3501 3470 3436 3329 + 3261 (if approved) Intended status: Best Current Practice -Expires: December 22, 2019 +Expires: July 9, 2020 Deprecating TLSv1.0 and TLSv1.1 - draft-ietf-tls-oldversions-deprecate-05 + draft-ietf-tls-oldversions-deprecate-06 Abstract This document, if approved, formally deprecates Transport Layer - Security (TLS) versions 1.0 [RFC2246] and 1.1 [RFC4346] and moves + Security (TLS) versions 1.0 (RFC 2246) and 1.1 (RFC 4346) and moves these documents to the historic state. These versions lack support for current and recommended cipher suites, and various government and industry profiles of applications using TLS now mandate avoiding these old TLS versions. TLSv1.2 has been the recommended version for IETF protocols since 2008, providing sufficient time to transition away from older versions. Products having to support older versions increase the attack surface unnecessarily and increase opportunities for misconfigurations. Supporting these older versions also requires additional effort for library and product maintenance. This document also deprecates Datagram TLS (DTLS) version 1.0 - [RFC6347] (but not DTLS version 1.2, and there is no DTLS version - 1.1). + (RFC6347), but not DTLS version 1.2, and there is no DTLS version + 1.1. This document updates many RFCs that normatively refer to TLSv1.0 or TLSv1.1 as described herein. This document also updates RFC 7525 and hence is part of BCP195. 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 December 22, 2019. + This Internet-Draft will expire on July 9, 2020. Copyright Notice - Copyright (c) 2019 IETF Trust and the persons identified as the + 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 @@ -94,24 +94,23 @@ 10.2. Informative References . . . . . . . . . . . . . . . . . 16 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 1. Introduction Transport Layer Security (TLS) versions 1.0 [RFC2246] and 1.1 [RFC4346] were superceded by TLSv1.2 [RFC5246] in 2008, which has now itself been superceded by TLSv1.3 [RFC8446]. It is therefore timely - to further deprecate these old versions. The expectation is that - TLSv1.2 will continue to be used for many years alongside TLSv1.3. + to further deprecate these old versions. - The primary technical reasons for deprecating these versions include: + Technical reasons for deprecating these versions include: o They require implementation of older cipher suites that are no longer desirable for cryptographic reasons, e.g. TLSv1.0 makes TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA mandatory to implement o Lack of support for current recommended cipher suites, especially using AEAD ciphers which are not supported prior to TLSv1.2. Note: registry entries for no-longer-desirable ciphersuites remain in the registries, but many TLS registries are being updated through [RFC8447] which denotes such entries as "not recommended." o Integrity of the handshake depends on SHA-1 hash @@ -131,42 +130,45 @@ offerings. 1.1. RFCs Updated This document updates the following RFCs that normatively reference TLSv1.0 or TLSv1.1 or DTLS1.0. The update is to obsolete usage of these older versions. Fallback to these versions are prohibited through this update. [RFC8465] [RFC8422] [RFC8261] [RFC7568] [RFC7562] [RFC7525] [RFC7507] - [RFC7465] [RFC6750] [RFC6749] [RFC6739] [RFC6460] [RFC6084] [RFC6083] - [RFC6367] [RFC6176] [RFC6042] [RFC6012] [RFC5878] [RFC5734] [RFC5469] - [RFC5456] [RFC5422] [RFC5415] [RFC5364] [RFC5281] [RFC5263] [RFC5238] + [RFC7465] [RFC7030] [RFC6750] [RFC6749] [RFC6739] [RFC6460] [RFC6084] + [RFC6083] [RFC6367] [RFC6176] [RFC6042] [RFC6012] [RFC5878] [RFC5734] + [RFC5469] [RFC5456] [RFC5422] [RFC5415] [RFC5364] [RFC5281] [RFC5263] + [RFC5238] [RFC5216] [RFC5158] [RFC5091] [RFC5054] [RFC5049] [RFC5024] - [RFC5216] [RFC5158] [RFC5091] [RFC5054] [RFC5049] [RFC5024] [RFC5023] - [RFC5019] [RFC5018] [RFC4992] [RFC4976] [RFC4975] [RFC4964] [RFC4851] - [RFC4823] [RFC4791] [RFC4785] [RFC4744] [RFC4743] [RFC4732] [RFC4712] - [RFC4681] [RFC4680] [RFC4642] [RFC4616] [RFC4582] [RFC4540] [RFC4531] - [RFC4513] [RFC4497] [RFC4279] [RFC4261] [RFC4235] [RFC4217] [RFC4168] - [RFC4162] [RFC4111] [RFC4097] [RFC3983] [RFC3943] [RFC3903] [RFC3887] - [RFC3871] [RFC3856] [RFC3767] [RFC3749] [RFC3656] [RFC3568] [RFC3552] - [RFC3501] [RFC3470] [RFC3436] [RFC3329] [RFC3261] + [RFC5023] [RFC5019] [RFC5018] [RFC4992] [RFC4976] [RFC4975] [RFC4964] + [RFC4851] [RFC4823] [RFC4791] [RFC4785] [RFC4744] [RFC4743] [RFC4732] + [RFC4712] [RFC4681] [RFC4680] [RFC4642] [RFC4616] [RFC4582] [RFC4540] + [RFC4531] [RFC4513] [RFC4497] [RFC4279] [RFC4261] [RFC4235] [RFC4217] + [RFC4168] [RFC4162] [RFC4111] [RFC4097] [RFC3983] [RFC3943] [RFC3903] + [RFC3887] [RFC3871] [RFC3856] [RFC3767] [RFC3749] [RFC3656] [RFC3568] + [RFC3552] [RFC3501] [RFC3470] [RFC3436] [RFC3329] [RFC3261] In addition these RFCs normatively refer to TLSv1.0 or TLSv1.1 and have been obsoleted: [RFC5101] [RFC5081] [RFC5077] [RFC4934] [RFC4572] [RFC4507] [RFC4492] [RFC4366] [RFC4347] [RFC4244] [RFC4132] [RFC3920] [RFC3734] [RFC3588] [RFC3546] [RFC3489] [RFC3316] In the case of [RFC4642], that has already been updated by [RFC8143] which makes an overlapping, but not quite the same, update as this document. + [RFC6614] has a requirement for TLSv1.1 although only makes an + informative reference to [RFC4346]. + This document updates DTLS [RFC6347]. 1.2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. @@ -323,25 +325,25 @@ 7. Security Considerations This document deprecates two older protocol versions for security reasons already described. The attack surface is reduced when there are a smaller number of supported protocols and fallback options are removed. 8. Acknowledgements Thanks to those that provided usage data, reviewed and/or improved - this document, including: David Benjamin, David Black, Viktor - Dukhovni, Julien Elie, Gary Gapinski, Alessandro Ghedini, Jeremy - Harris, Russ Housley, Hubert Kario, John Mattsson, Eric Mill, Yoav - Nir, Andrei Popov, Eric Rescorla, Yaron Sheffer, Robert Sparks, - Martin Thomson, Loganaden Velvindron, https://github.com/yaleman, and + this document, including: David Benjamin, David Black, Alan DeKok, + Viktor Dukhovni, Julien Elie, Gary Gapinski, Alessandro Ghedini, + Jeremy Harris, James Hodgkinson, Russ Housley, Hubert Kario, John + Mattsson, Eric Mill, Yoav Nir, Andrei Popov, Eric Rescorla, Yaron + Sheffer, Robert Sparks, Martin Thomson, Loganaden Velvindron, and Jakub Wilk. [[Note to RFC editor: At least Julien Elie's name above should have an accent on the first letter of the surname. Please fix that and any others needing a similar fix if you can, I'm not sure the tooling I have now allows that.]] 9. IANA Considerations [[This memo includes no request to IANA.]] @@ -692,20 +694,25 @@ [RFC6749] Hardt, D., Ed., "The OAuth 2.0 Authorization Framework", RFC 6749, DOI 10.17487/RFC6749, October 2012, . [RFC6750] Jones, M. and D. Hardt, "The OAuth 2.0 Authorization Framework: Bearer Token Usage", RFC 6750, DOI 10.17487/RFC6750, October 2012, . + [RFC7030] Pritikin, M., Ed., Yee, P., Ed., and D. Harkins, Ed., + "Enrollment over Secure Transport", RFC 7030, + DOI 10.17487/RFC7030, October 2013, + . + [RFC7465] Popov, A., "Prohibiting RC4 Cipher Suites", RFC 7465, DOI 10.17487/RFC7465, February 2015, . [RFC7507] Moeller, B. and A. Langley, "TLS Fallback Signaling Cipher Suite Value (SCSV) for Preventing Protocol Downgrade Attacks", RFC 7507, DOI 10.17487/RFC7507, April 2015, . [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, @@ -872,20 +879,25 @@ 2011, . [RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347, January 2012, . [RFC6460] Salter, M. and R. Housley, "Suite B Profile for Transport Layer Security (TLS)", RFC 6460, DOI 10.17487/RFC6460, January 2012, . + [RFC6614] Winter, S., McCauley, M., Venaas, S., and K. Wierenga, + "Transport Layer Security (TLS) Encryption for RADIUS", + RFC 6614, DOI 10.17487/RFC6614, May 2012, + . + [RFC7457] Sheffer, Y., Holz, R., and P. Saint-Andre, "Summarizing Known Attacks on Transport Layer Security (TLS) and Datagram TLS (DTLS)", RFC 7457, DOI 10.17487/RFC7457, February 2015, . [RFC8143] Elie, J., "Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)", RFC 8143, DOI 10.17487/RFC8143, April 2017, . @@ -899,20 +911,33 @@ . [RFC8447] Salowey, J. and S. Turner, "IANA Registry Updates for TLS and DTLS", RFC 8447, DOI 10.17487/RFC8447, August 2018, . Appendix A. Change Log [[RFC editor: please remove this before publication.]] + From draft-ietf-tls-oldversions-deprecate-05 to draft-ietf-tls- + oldversions-deprecate-06: + + o Fixed "yaleman" ack. + o Added RFC6614 to UPDATEs list. + o per preliminary AD review: + + * Remove references from abstract + * s/primary technical reasons/technical reasons/ + * Add rfc7030 to 1.1 + * verified that all the RFCs in the (massive:-) Updates meta-data + are mentioned in section 1.1 (I think appropriately;-) + From draft-ietf-tls-oldversions-deprecate-04 to draft-ietf-tls- oldversions-deprecate-05: o Removed references to goverment related deprecation statements: US, Canada, and Germany. NIST documentation rationale remains as a reference describing the relevent RFCs and justification. From draft-ietf-tls-oldversions-deprecate-02 to draft-ietf-tls- oldversions-deprecate-03: