A new Request for Comments is now available in online RFC libraries.
BCP 195
RFC 9852
Title: New Protocols Using TLS Must Require TLS 1.3
Author: R. Salz,
N. Aviram
Status: Best Current Practice
Stream: IETF
Date: July 2026
Mailbox: [email protected],
[email protected]
Pages: 7
Updates: RFC 9325
I-D Tag: draft-ietf-uta-require-tls13-12
URL: https://www.rfc-editor.org/info/rfc9852
DOI: 10.17487/RFC9852
TLS 1.3 is widely used, has had comprehensive security proofs, and improves
both security and privacy deficiencies in TLS 1.2. Therefore, new protocols
that use TLS must require TLS 1.3. As DTLS 1.3 is not widely available or
deployed, this prescription does not pertain to DTLS (in any DTLS version); it
pertains to TLS only.
This document updates RFC 9325. It discusses post-quantum cryptography and the
security and privacy improvements in TLS 1.3 as the rationale for the update.
This document is a product of the Using TLS in Applications Working Group of
the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
