diff options
| author | Vladimir Homutov <vl@nginx.com> | 2020-10-23 17:08:50 +0300 |
|---|---|---|
| committer | Vladimir Homutov <vl@nginx.com> | 2020-10-23 17:08:50 +0300 |
| commit | 83d7a949e8af4b89bc8b41e89b50dcfe819837dd (patch) | |
| tree | db1cd410cb77e13ca6f2df443071dedbaff1b6cb /src/misc/ngx_cpp_test_module.cpp | |
| parent | b92e59691869120c55f56d721710d7de28836c05 (diff) | |
| download | nginx-83d7a949e8af4b89bc8b41e89b50dcfe819837dd.tar.gz nginx-83d7a949e8af4b89bc8b41e89b50dcfe819837dd.tar.bz2 | |
QUIC: optimized acknowledgement generation.
For application level packets, only every second packet is now acknowledged,
respecting max ack delay.
13.2.1 Sending ACK Frames
In order to assist loss detection at the sender, an endpoint SHOULD
generate and send an ACK frame without delay when it receives an ack-
eliciting packet either:
* when the received packet has a packet number less than another
ack-eliciting packet that has been received, or
* when the packet has a packet number larger than the highest-
numbered ack-eliciting packet that has been received and there are
missing packets between that packet and this packet.
13.2.2. Acknowledgement Frequency
A receiver SHOULD send an ACK frame after receiving at least two
ack-eliciting packets.
Diffstat (limited to 'src/misc/ngx_cpp_test_module.cpp')
0 files changed, 0 insertions, 0 deletions