Hi,
This is a major new version, addressing (to the best of our knowledge) all
pending review comments, primarily from IESG members. Do let us know if we
missed anything.
>From the change log:
Addressed IESG feedback, ARTART review by Cullen Jennings, and TSVART review by
Magnus Westerlund.
Improved the rationale for still recommending TLS 1.2.
Specified TLS 1.3 as a MUST for new transport protocols and a SHOULD for new
application protocols.
Clarified TLS-only vs. dynamic upgrade for non-HTTP protocols.
Clarified distinction between implementation and deployment.
Clarified applicability to QUIC.
Further specified what to do on reaching the confidentiality limit or integrity
limit.
Added a note about post-quantum cryptography.
Improved the text about Encrypted Client Hello.
Thanks, and have a great IETF week!
Yaron
On 7/24/22, 18:21, "[email protected] on behalf of
[email protected]" <[email protected] on behalf of
[email protected]> wrote:
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Using TLS in Applications WG of the IETF.
Title : Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security (DTLS)
Authors : Yaron Sheffer
Peter Saint-Andre
Thomas Fossati
Filename : draft-ietf-uta-rfc7525bis-10.txt
Pages : 45
Date : 2022-07-24
Abstract:
Transport Layer Security (TLS) and Datagram Transport Layer Security
(DTLS) are used to protect data exchanged over a wide range of
application protocols, and can also form the basis for secure
transport protocols. Over the years, the industry has witnessed
several serious attacks on TLS and DTLS, including attacks on the
most commonly used cipher suites and their modes of operation. This
document provides the latest recommendations for ensuring the
security of deployed services that use TLS and DTLS. These
recommendations are applicable to the majority of use cases.
An earlier version of this document was published as RFC 7525 when
the industry was in the midst of its transition to TLS 1.2. Years
later this transition is largely complete and TLS 1.3 is widely
available. This document updates the guidance given the new
environment and obsoletes RFC 7525. In addition, the document
updates RFC 5288 and RFC 6066 in view of recent attacks.
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-uta-rfc7525bis/
There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-uta-rfc7525bis-10.html
A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-uta-rfc7525bis-10
Internet-Drafts are also available by rsync at
rsync.ietf.org::internet-drafts
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
