Lines Matching +full:negative +full:- +full:phase

52 **DISPATCH:** Refers to the QUIC-specific dispatch code in `ssl_lib.c`. This
59 **Event Leader:** The QSO which is is the top-level QSO in a hierarchy of QSOs,
62 design](server/quic-server-api.md).
66 **FIFD:** Frame-in-flight dispatcher. Ties together the CFQ and TXPIM to handle
69 **FIFM:** Frame-in-flight manager. Tracks frames in flight until their
77 **Key epoch:** Non-negative number designating a generation of QUIC keys used to
81 **Key Phase:** Key phase bit in QUIC packet headers. See RFC 9000.
87 **KP:** See Key Phase.
99 **Locally-initiated:** Refers to a QUIC stream which was initiated by the local
131 **MSMT:** Multi-stream multi-thread. Refers to a type of multi-stream QUIC usage
134 **MSST:** Multi-stream single-thread. Refers to a type of multi-stream QUIC
153 This may be a QCSO or a QLSO. See [the server API design](server/quic-server-api.md).
200 wrapping libssl TLS code to implement the QUIC-specific aspects of QUIC TLS.
215 the top-level object of a QUIC event and I/O processing domain. Owns zero or
239 **Remotely-initiated:** Refers to a QUIC stream which was initiated by the
242 **RIO:** Reactive I/O subsystem. Refers to the generic, non-QUIC specific parts
260 budget should be generated. Exists in both connection-level and stream-level
264 has a flipped Key Phase bit, meaning the peer has initiated a key update.
296 peer. Exists in both connection-level and stream-level instances.
299 TX direction by flipping the Key Phase bit in an outgoing packet. A TXKU can be
305 **TXP:** TX packetiser. This is responsible for generating yet-unencrypted
315 **TX/RX v. Send/Receive:** The terms *TX*  and *RX* are used for *network-level*
316 communication, whereas *send* and *receive* are used for application-level
329 **URXE:** Unprocessed RX entry. Structure containing yet-undecrypted received