[~] Fix #730: Detect persistent congestion from lost packet intervals - #947
Draft
Yanmei-Liu wants to merge 2 commits into
Draft
Yanmei-Liu wants to merge 2 commits into
Yanmei-Liu wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mechanism
Detect persistent congestion from the sending-time span of lost ack-eliciting
packets after an RTT sample, independently of PTO count, per
RFC 9002 Sections 7.6.1–7.6.2.
Retained per-path history checks intervening acknowledgments across packet
number spaces, including recycled ACK-only packets and direct path probes.
Bounded history keeps the newest suffix when full and clears potentially
truncated ACK-range evidence; existing cwnd and RTT reset behavior is preserved.
Fixes: #730
Validation Cases
CONTRIBUTING.md