[TLS] Re: RFC 9954 on Hybrid Key Exchange in TLS 1.3

Sean Turner <[email protected]> Wed, 15 Jul 2026 18:51:34 -0400
Newsgroups gmane.ietf.tls
Message-ID <[email protected]>
Congrats to all that participated in the development of this RFC!

Cheers,
spt

> On Jul 15, 2026, at 18:22, [email protected] wrote:
> 
> A new Request for Comments is now available in online RFC libraries.
> 
>        RFC 9954
> 
>        Title:      Hybrid Key Exchange in TLS 1.3
>        Author:     D. Stebila,
>                    S. Fluhrer,
>                    S. Gueron
>        Status:     Informational
>        Stream:     IETF
>        Date:       July 2026
>        Mailbox:    [email protected],
>                    [email protected],
>                    [email protected]
>        Pages:      18
> 
> 
>        I-D Tag:    draft-ietf-tls-hybrid-design-16
> 
>        URL:        https://www.rfc-editor.org/info/rfc9954
> 
>        DOI:        10.17487/RFC9954
> 
> Hybrid key exchange refers to using multiple key exchange algorithms simultaneously and combining the result with the goal of providing security even if a way is found to defeat the encryption for all but one of the component algorithms. It is motivated by the transition to post-quantum cryptography. This document provides a construction for hybrid key exchange in the Transport Layer Security (TLS) protocol version 1.3.
> 
> This document is a product of the Transport Layer Security Working Group of the IETF.
> 
> INFORMATIONAL: This memo provides information for the Internet community.
> It does not specify an Internet standard of any kind. 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]

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