Lines Matching refs:packet
99 the packet it was sent in was acknowledged, and can return the data for
121 sent and schedules them into a packet.
132 The packetiser will attempt to maximise the number of bytes in a packet.
138 the packet being filled. Once the wait is finished, the packets will be sent
151 the per-packet information recorded by the TXPIM to track which frames are
152 contained within a packet which was lost or acknowledged, and generates
156 1. When a packet is sent, the packetiser informs the FIFD, which also informs
158 2. When a packet is ACKed, the FIFD notifies applicable SSTREAMs and the CFQ
160 3. When a packet is lost, the FIFD notifies the TX packetiser of any frames
161 which were in the lost packet for which the Regenerate strategy is
171 allowed to send in a packet.
212 bytes we can put in a UDP packet. This is derived from the applicable PMTU.
213 This is also the maximum size of a single QUIC packet if we place only one
214 packet in a datagram. The MDPL may vary based on both local source IP and
218 and serialized QUIC packet in bytes in some given context. Typically
222 bytes we can put in the payload of a QUIC packet. This is related to
227 another QUIC packet into the same datagram as one or more previous
232 the payload of another QUIC packet which is to be coalesced with one or
234 this is the room we have left for another packet payload.
236 - Remaining CMPPL (RCMPPL): The number of bytes left in a packet whose payload
242 accomplished with a single packet, but we may need to add PADDING frames
243 to the final packet added to a datagram in this case.
245 - Minimum Packet Length (MinPL): The minimum serialized packet length we
246 are using while serializing a given packet. May often be 0. Used to meet
251 which must be placed into a packet payload in order to meet the MinPL
252 minimum size when the packet is encoded.
319 For `C`, `N` and `P`, the entire packet must consist of only frames with the
320 marking for the packet to qualify for it. For example, a packet with an ACK
385 - `PING`: The `PING` frame is encoded as a single byte. It is used to make a packet
389 a. we have been asked to ensure the packet is ACK-eliciting, and
390 b. we do not have any other ACK-eliciting frames in the packet.
395 the packet is ACK-eliciting and we do not know for sure up front if we will
396 add any other ACK-eliciting packet, we must reserve one byte of our CMPPL
400 - We have been asked to ensure a packet is ACK-eliciting and the CMPPL is
401 1000 (we are coalescing with another packet).
417 will only ever be at most one per packet, there is no risk of them
424 - `STREAM`: This is the bread and butter of a QUIC packet, and contains
426 consume most of our packet's payload budget. We must generally assume that
430 can be sent in a single packet.
442 have serialized all other frame types, we can reserve the rest of the packet
479 single packet and are thus ultimately limited by the MPPL. However, these
493 packet of room for stream data.
497 **Stream budgeting.** When it is time to add STREAM frames to a packet under
511 streams exceeds the Streams Budget for the packet, allocate an equal
512 portion of the packet to each stream.
515 streams exceeds the Streams Budget for the packet, try to fill the packet
520 probably due to a clear downside: if a packet is lost and it contains data for
524 if a packet is lost, typically only a single stream is held up.
547 to packet loss in typical networks occurring in small durations affecting small
549 will be affected by packet loss and held up on average. However, implementing
554 Thus, we choose what active stream to select to fill in a packet on a
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`
581 Initial packet. (If there are multiple packets in the datagram, the padding
582 does not necessarily need to be part of the Initial packet itself.) This
588 packet.
595 about enforcing the amplification limit in terms of precise packet sizes.
596 Rather, they just use it to determine if they can send another packet, but not
597 to determine what size that packet must be. Implementations with 'precise'
614 We handle the need for different kinds of packet via a notion of “archetypes”.
634 packet; or rather, it would be more accurate to say that the TX packetiser
635 decides what ELs need a packet generating. Many resources are instantiated per
636 EL, and can only be managed using a packet of that EL, therefore a datagram will
639 needs to produce a packet for each EL, and concatenating the resulting packets.
651 frame sent in an Initial packet, etc.
662 - For each EL in E, construct a packet bearing in mind the Remaining CMPPL
678 ### Restricting packet sizes
687 limit to be imposed on a given packet.
