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.

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

change CE behaviour only when threshold > 1 #277

Merged
merged 3 commits into from
Mar 4, 2024
Merged
Changes from 1 commit
Commits
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
11 changes: 8 additions & 3 deletions draft-ietf-quic-ack-frequency.md
Original file line number Diff line number Diff line change
Expand Up @@ -412,9 +412,14 @@ a Reordering Threshold of 2.

## Expediting Explicit Congestion Notification (ECN) Signals {#congestion}

An endpoint SHOULD send an immediate acknowledgment when a packet marked
with the ECN Congestion Experienced (CE) {{?RFC3168}} codepoint in the IP
header is received and the previously received packet was not marked CE.
If the Ack-Eliciting Threshold is larger than 1, an endpoint SHOULD send
an immediate acknowledgement when a packet marked with the ECN Congestion
Experienced (CE) {{?RFC3168}} codepoint in the IP header is received and
the previously received packet was not marked CE. From there on, if multiple
CE-marked packets are received in a row or only non-CE-marked packet received,
the endpoint resumes to sending acknowledgements based on the Ack-Eliciting
mirjak marked this conversation as resolved.
Show resolved Hide resolved
Threshold or max_ack_delay. That means only when a transition from non-CE-marked
to CE-marked occurs an immediate acknowledgement is sent.
mirjak marked this conversation as resolved.
Show resolved Hide resolved

mirjak marked this conversation as resolved.
Show resolved Hide resolved
Doing this 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
Expand Down
Loading