[TLS] Why has Hybrid key exchange in TLS 1.3 expired?

Wang Guilin <Wang.Guilin@huawei.com> Fri, 05 April 2024 06:21 UTC

Return-Path: <Wang.Guilin@huawei.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE389C14F6A7 for <tls@ietfa.amsl.com>; Thu, 4 Apr 2024 23:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.893
X-Spam-Level:
X-Spam-Status: No, score=-6.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id prJJaMM4Jg_E for <tls@ietfa.amsl.com>; Thu, 4 Apr 2024 23:21:12 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A85D0C14F6BA for <tls@ietf.org>; Thu, 4 Apr 2024 23:21:11 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4V9pCc287vz6J7Zc for <tls@ietf.org>; Fri, 5 Apr 2024 14:16:28 +0800 (CST)
Received: from lhrpeml100002.china.huawei.com (unknown [7.191.160.241]) by mail.maildlp.com (Postfix) with ESMTPS id 800861400DC for <tls@ietf.org>; Fri, 5 Apr 2024 14:21:08 +0800 (CST)
Received: from sinpeml100005.china.huawei.com (7.188.195.10) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Fri, 5 Apr 2024 07:21:07 +0100
Received: from sinpeml500005.china.huawei.com (7.188.193.102) by sinpeml100005.china.huawei.com (7.188.195.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Fri, 5 Apr 2024 14:21:06 +0800
Received: from sinpeml500005.china.huawei.com ([7.188.193.102]) by sinpeml500005.china.huawei.com ([7.188.193.102]) with mapi id 15.01.2507.035; Fri, 5 Apr 2024 14:21:05 +0800
From: Wang Guilin <Wang.Guilin@huawei.com>
To: "tls@ietf.org" <tls@ietf.org>
Thread-Topic: Why has Hybrid key exchange in TLS 1.3 expired?
Thread-Index: AdqHIOfy6fr1rbu5Ru6bx3+CqGYsaA==
Date: Fri, 05 Apr 2024 06:21:05 +0000
Message-ID: <1cd90f1e224849949f9b537b76462af2@huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.194.120.72]
Content-Type: multipart/alternative; boundary="_000_1cd90f1e224849949f9b537b76462af2huaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/qe51U1okE0D82UYoretwqM7tmL4>
Subject: [TLS] Why has Hybrid key exchange in TLS 1.3 expired?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2024 06:21:15 -0000

Dear all,

It seems that I have missed some updated info about the following TLS WG document.

Hybrid key exchange in TLS 1.3
draft-ietf-tls-hybrid-design-09
https://datatracker.ietf.org/doc/draft-ietf-tls-hybrid-design/

I thought that it was the main approach for TLS PQ migration. However, it has expired now. Why?

Thanks,

Guilin