From 5633a323df5a533e003163b9f556a476b9f9df45 Mon Sep 17 00:00:00 2001 From: Hugo Landau Date: Tue, 23 May 2023 12:23:05 +0100 Subject: [PATCH] QUIC Glossary: TXKU, RXKU, KU Reviewed-by: Tomas Mraz Reviewed-by: Matt Caswell Reviewed-by: Paul Dale (Merged from https://github.com/openssl/openssl/pull/21029) --- doc/designs/quic-design/glossary.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/designs/quic-design/glossary.md b/doc/designs/quic-design/glossary.md index 0a45cdc027..1f947ef37d 100644 --- a/doc/designs/quic-design/glossary.md +++ b/doc/designs/quic-design/glossary.md @@ -82,6 +82,8 @@ may be maintained at a given time. See `quic_record_rx.h` for details. **KS:** See Keyslot. +**KU:** Key update. See also TXKU, RXKU. + **Locally-initiated:** Refers to a QUIC stream which was initiated by the local application rather than the remote peer. @@ -188,6 +190,10 @@ provides indication of when flow control frames increasing a peer's flow control budget should be generated. Exists in both connection-level and stream-level instances. +**RXKU:** RX key update. The detected condition whereby a received packet +has a flipped Key Phase bit, meaning the peer has initiated a key update. +Causes a solicited TXKU. See also TXKU. + **RXL:** RXE list. See RXE. **RCMPPL:** The number of bytes left in a packet whose payload we are currently @@ -213,6 +219,11 @@ Owned by the QTX. **TXFC:** TX flow control. This determines how much can be transmitted to the peer. Exists in both connection-level and stream-level instances. +**TXKU:** TX key update. This refers to when a QTX signals a key update for the +TX direction by flipping the Key Phase bit in an outgoing packet. A TXKU can be +either spontaneous (locally initiated) or in solicited (in response to receiving +an RXKU). See also RXKU. + **TXL:** TXE list. See TXE. **TXP:** TX packetiser. This is responsible for generating yet-unencrypted -- GitLab