11 application to be signalled as an error code value by QUIC. See QUIC RFCs
18 **Bidi:** Abbreviation of bidirectional, referring to a QUIC bidirectional
32 **CMPL:** The maximum number of bytes left to serialize another QUIC packet into
34 the total size of all previous packets already serialized into to the same
38 another QUIC packet which is to be coalesced with one or more previous QUIC
42 **CSM:** Connection state machine. Refers to some aspects of a QUIC channel. Not
47 **DEMUX:** The demuxer routes incoming packets to the correct connection QRX by
52 **DISPATCH:** Refers to the QUIC-specific dispatch code in `ssl_lib.c`. This
53 dispatches calls to libssl public APIs to the APL.
61 **FIFD:** Frame-in-flight dispatcher. Ties together the CFQ and TXPIM to handle
72 **Key epoch:** Non-negative number designating a generation of QUIC keys used to
78 **Keyslot**: A set of cryptographic state used to encrypt or decrypt QUIC
79 packets by a QRX or QTX. Due to the QUIC key update mechanism, multiple keyslots
88 **LCID:** Local CID. Refers to a CID which will be recognised as identifying a
91 **LCIDM:** Local CID Manager. Tracks LCIDs which have been advertised to a peer.
94 **Locally-initiated:** Refers to a QUIC stream which was initiated by the local
101 due to different path MTUs.
104 certain number of bytes. This does not need to be accomplished with a single
105 packet, but we may need to add PADDING frames to the final packet added to a
109 given packet. May often be 0. Used to meet MinDPL requirements, and thus equal
110 to MinDPL minus the length of any packets we have already encoded into the
114 payload in order to meet the MinPL minimum size when the packet is encoded.
117 serialized QUIC packet in bytes in some given context. Typically equal to the
121 QUIC packet. This is related to the MDPL by the size of the encoded header and
122 the size of any AEAD authentication tag which will be attached to the
125 **MSMT:** Multi-stream multi-thread. Refers to a type of multi-stream QUIC usage
128 **MSST:** Multi-stream single-thread. Refers to a type of multi-stream QUIC
131 **NCID:** New Connection ID. Refers to a QUIC `NEW_CONNECTION_ID` frame.
133 **Numbered CID:** Refers to a Connection ID which has a sequence number assigned
134 to it. All CIDs other than Initial ODCIDs and Retry ODCIDs have a sequence
138 packet sent by a client, and is used to generate the secrets for encrypting
154 which helps to unwrap an SSL object pointer (a QCSO or QSSO) into the relevant
157 **QRL:** QUIC record layer. Refers collectively to the QRX and QTX.
166 IDs to those objects. Allows iteration of active streams.
170 **QSSO:** QUIC Stream SSL Object. This is an SSL object which is subsidiary to a
175 wrapping libssl TLS code to implement the QUIC-specific aspects of QUIC TLS.
180 to a QUIC connection. Ties together other components and provides connection
181 handling and state machine implementation. Belongs to a `QUIC_PORT` representing
182 a UDP socket/BIO, which in turn belongs to a `QUIC_ENGINE`. Owns some number of
186 connection in the APL. It internally corresponds to a `QUIC_CHANNEL` object in
194 **QUIC_PORT:** Internal object in the QUIC core implementation corresponding to
196 associated with it and belongs to a `QUIC_ENGINE`.
200 an API object. As such, a `QUIC_CONNECTION` is to a `QUIC_CHANNEL` what a
201 `QUIC_XSO` is to a `QUIC_STREAM`.
203 **RCID:** Remote CID. Refers to a CID which has been provided to us by a peer
207 **RCIDM:** Remote CID Manager. Tracks RCIDs which have been provided to us by a
211 the frame from canonical data sources without having to store a copy of the
214 **Remotely-initiated:** Refers to a QUIC stream which was initiated by the
217 **RIO:** Reactive I/O subsystem. Refers to the generic, non-QUIC specific parts
220 **RSTREAM:** Receive stream. Internal receive buffer management object used to
223 **RTT:** Round trip time. Time for a datagram to reach a given peer and a reply
224 to reach the local machine, assuming the peer responds immediately.
230 processing. Stored in a queue known as the RXL. These structures belong to a
233 **RXFC:** RX flow control. This determines how much a peer may send to us and
254 **SSTREAM:** Send stream. Internal send buffer management object used to store
255 data which has been passed to libssl for sending but which has not yet been
269 **TXFC:** TX flow control. This determines how much can be transmitted to the
272 **TXKU:** TX key update. This refers to when a QTX signals a key update for the
274 either spontaneous (locally initiated) or in solicited (in response to receiving
280 packets and passing them to a QTX for encryption and transmission. It must
281 decide how to spend the space available in a datagram.
285 is needed to facilitate retransmission of frames if the packets they are in
291 communication. An application *sends*  on a stream (causing data to be appended
292 to a *send stream buffer*, and that data is eventually TX'd by the TXP and QTX.)
294 **Uni:** Abbreviation of unidirectional, referring to a QUIC unidirectional
297 **Unnumbered CID:** Refers to a CID which does not have a sequence number
298 associated with it and therefore cannot be referred to by a `NEW_CONNECTION_ID`

Last Index update Mon Nov 25 20:08:26 UTC 2024

Dedicated to & Maintained by Room-11