From 7d5426c703d24a8a6867db4900a5a02f78619379 Mon Sep 17 00:00:00 2001 From: Neil Horman Date: Wed, 29 Jan 2025 14:44:13 -0500 Subject: [PATCH] Move handling of connection close frames to QUIC FUTURE MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit There is a corner case in handling connection close frames for which RFC guidance is unclear. Given that, move addressing it to QUIC FUTURE Fixes openssl/project#1075 Reviewed-by: Matt Caswell Reviewed-by: Saša Nedvědický (Merged from https://github.com/openssl/openssl/pull/26593) --- ssl/quic/quic_txp.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ssl/quic/quic_txp.c b/ssl/quic/quic_txp.c index 9ff0e5aee5d..1d74637ffaa 100644 --- a/ssl/quic/quic_txp.c +++ b/ssl/quic/quic_txp.c @@ -1469,7 +1469,8 @@ static int txp_should_try_staging(OSSL_QUIC_TX_PACKETISER *txp, * This is not a major concern for clients, since if a client has a 1-RTT EL * provisioned the server is guaranteed to also have a 1-RTT EL provisioned. * - * TODO(QUIC SERVER): Revisit this when server support is added. + * TODO(QUIC FUTURE): Revisit this when when have reached a decision on how + * best to implement this */ if (*conn_close_enc_level > enc_level && *conn_close_enc_level != QUIC_ENC_LEVEL_1RTT) -- 2.47.2