Lines Matching refs:stream
39 * Note: There is no crypto stream for the 0-RTT EL.
40 * crypto[QUIC_PN_SPACE_APP] is the 1-RTT crypto stream.
64 implemented because only one stream is supported. However, packets being
69 void SSL_set_priority(SSL *stream, uint32_t priority);
70 uint32_t SSL_get_priority(SSL *stream);
82 - SSTREAM: manages application stream data for transmission.
83 - QUIC_STREAM_MAP: Maps stream IDs to QUIC_STREAM objects and tracks which
92 - Connection and stream-level TXFC and RXFC instances.
97 Each application or crypto stream has a SSTREAM object for the sending part.
98 This manages the buffering of data written to the stream, frees that data when
105 The TX packetiser queries the QUIC stream map for a list of active streams
114 stream) are represented by SSTREAM instances. The TX packetiser queries SSTREAM
168 The packetiser interacts with connection and stream-level TXFC and RXFC
170 control frames, and with TXFC instances to know how much stream data it is
254 - Active Stream: A stream which has data or flow control frames ready for
271 | 0x08 | stream 0x08 | | | ✓ | ✓ | | | …
272 | 0x09 | stream 0x09 | | | ✓ | ✓ | | | …
273 | 0x0A | stream 0x0A | | | ✓ | ✓ | | | …
274 | 0x0B | stream 0x0B | | | ✓ | ✓ | | | …
275 | 0x0C | stream 0x0C | | | ✓ | ✓ | | | …
276 | 0x0D | stream 0x0D | | | ✓ | ✓ | | | …
277 | 0x0E | stream 0x0E | | | ✓ | ✓ | | | …
278 | 0x0F | stream 0x0F | | | ✓ | ✓ | | | …
361 ============================ ] priority group, repeats per stream
425 application-level stream data. As such these frames can usually be expected to
433 streams. We refer to this as stream scheduling. There are many strategies that
436 stream scheduling further below.
450 contain only a stream ID and integer value used for flow control, so they are
452 stream, and because they are small and have no risk of stealing too many bytes
454 corresponding `STREAM` frames for a given stream ID.
456 - `RESET_STREAM`, `STOP_SENDING`: These terminate a given stream ID and thus are
457 also associated with a stream. They are also small. As such, we consider these
458 higher priority than both `STREAM` frames and the stream-level flow control
468 - `CRYPTO`: These frames generate the logical crypto stream, which is a logical
470 handshake and management purposes. As such, the crypto stream is viewed as
472 `CRYPTO` frames outcompete all application stream-related frames if need be,
493 packet of room for stream data.
501 For the purposes of stream budgeting, we consider all bytes of STREAM frames,
502 stream-level flow control frames, RESET_STREAM and STOP_SENDING frames to
512 portion of the packet to each stream.
524 if a packet is lost, typically only a single stream is held up.
531 the next active stream every n packets (where n ≥ 1).
533 - A sequential (SEQ) strategy in which a stream keeps being transmitted
540 completing transmission of one stream before beginning the next. However, it
554 Thus, we choose what active stream to select to fill in a packet on a
555 revolving round robin basis, moving to the next stream in the round robin
556 every `n` packets. If the available data in the active stream is not enough to
557 fill a packet, we do also move to the next stream, so IRPM can still occur in
560 When we fill a packet with a stream, we start with any applicable `RESET_STREAM`
561 or `STOP_SENDING` frames, followed by stream-level flow control frames if
567 for one stream, then a `STREAM` frame for another, then another `STOP_SENDING`
568 frame for another stream, etc.)
643 - The crypto stream, a bidirectional byte stream abstraction provided
644 to the handshake layer. There is one crypto stream for each of the Initial,
646 which is to say the 0-RTT EL has no crypto stream of its own.)
