Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify Ack-Eliciting Threshold of 0 and 1 #313

Merged
merged 4 commits into from
Feb 6, 2025
Merged

Clarify Ack-Eliciting Threshold of 0 and 1 #313

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2ebe1cc
Clarify Ack-Eliciting Threshold of 0 and 1
mirjak Jan 27, 2025
04f9d29
Update draft-ietf-quic-ack-frequency.md
mirjak Jan 27, 2025
afab66c
editorial remark by Ian
mirjak Feb 6, 2025
82be5d0
Apply suggestions from code review
mirjak Feb 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion draft-ietf-quic-ack-frequency.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -453,7 +453,14 @@ the endpoint resumes sending acknowledgements based on the Ack-Eliciting
Threshold or max_ack_delay. Therefore, CE-marking only triggers an immediate
acknowledgement when there is a transition from non-CE-marked to CE-marked.

Doing this maintains the peer's response time to congestion events, while also
If the Ack-Eliciting Threshold is 0, every ack-eliciting packet is immediately
acknowledged, CE marked or not. If the Ack-Eliciting Threshold
is 1, the default behavior as specified in RFC9000 applies, which recommends to
immediately acknowledge all packets marked with CE (see
{{Section 13.2.1 of QUIC-TRANSPORT}}).

Acknowledging the first CE marked packet immediately maintains
the peer's response time to congestion events, while also
reducing the ACK rate compared to {{Section 13.2.1 of QUIC-TRANSPORT}} during
extreme congestion or when peers are using DCTCP {{?RFC8257}} or other
congestion controllers (e.g. {{?I-D.ietf-tsvwg-aqm-dualq-coupled}}) that mark
Expand Down
Loading