Congrats to all who participated in the development of this RFC!

spt

> On Jul 11, 2026, at 12:06, [email protected] wrote:
> 
> A new Request for Comments is now available in online RFC libraries.
> 
>        RFC 9846
> 
>        Title:      The Transport Layer Security (TLS) Protocol Version 1.3
>        Author:     E. Rescorla
>        Status:     Proposed Standard
>        Stream:     IETF
>        Date:       July 2026
>        Mailbox:    [email protected]
>        Pages:      137
>        Updates:    RFC 5705, RFC 6066
>        Obsoletes:  RFC 5077, RFC 5246, RFC 6961, RFC 7627, RFC 8422, RFC 8446
> 
> 
>        I-D Tag:    draft-ietf-tls-rfc8446bis-14
> 
>        URL:        https://www.rfc-editor.org/info/rfc9846
> 
>        DOI:        10.17487/RFC9846
> 
> This document specifies version 1.3 of the Transport Layer Security (TLS) 
> protocol. TLS allows client/server applications to communicate over the 
> Internet in a way that is designed to prevent eavesdropping, tampering, and 
> message forgery.
> 
> This document obsoletes RFC 8446, which specified TLS 1.3. This document 
> obsoletes RFC 5246 (specifying TLS 1.2) and RFCs 5077, 6961, 7627, and 8422, 
> all of which pertain to TLS 1.2 or earlier, and updates RFCs 5705 and 6066. 
> This document also specifies new requirements for TLS 1.2 implementations.
> 
> This document is a product of the Transport Layer Security Working Group of 
> the IETF.
> 
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol 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
> 
> _______________________________________________
> TLS mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to