Lines Matching +full:packet +full:- +full:based
44 * (other than the 0-RTT EL). Note that the `tls` SSL object is not "owned"
106 * crypto_send[QUIC_PN_SPACE_APP] is the 1-RTT crypto stream. There is no
107 * 0-RTT crypto stream.
114 * Client: The DCID used in the first Initial packet we transmit as a client.
115 * Server: The DCID used in the first Initial packet the client transmitted.
121 * Server: If this channel is created in response to an init packet sent
122 * after the server has sent a retry packet to do address validation, this
123 * field stores the original connection id from the first init packet sent
128 * Client: The SCID found in the first Initial packet from the server.
135 * Client only: The SCID found in an incoming Retry packet we handled.
167 * Temporary staging area to store information about the incoming packet we
218 * Override packet count threshold at which we do a spontaneous TXKU.
219 * Usually UINT64_MAX in which case a suitable value is chosen based on AEAD
241 * Deadline at which we should send an ACK-eliciting packet to ensure
261 * QTX key epoch is greater than 0. Once a packet we sent with a PN p (p >=
275 * State tracking. QUIC connection-level state is best represented based on
278 * state of the connection's lifecycle, but more fine-grained conditions of
280 * doc/designs/quic-design/connection-state-machine.md. We are in the Open
287 * Have we received at least one encrypted packet from the peer?
294 * Have we successfully processed any packet, including a Version
295 * Negotiation packet? If so, further Version Negotiation packets should be
301 * Have we sent literally any packet yet? If not, there is no point polling
330 * At our option, we may also take acknowledgement of any 1-RTT packet
336 * We are sending Initial packets based on a Retry. This means we definitely
365 * While in TERMINATING - CLOSING, set when we should generate a connection
385 * Have we sent an ack-eliciting packet since the last successful packet