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

Remove SHOULD for 1 ACK/RTT recommendation #210

Closed
wants to merge 3 commits into from
Closed

Conversation

mirjak
Copy link
Contributor

@mirjak mirjak commented Jul 10, 2023

This PR is basically reverting to some old text to remove the SHOULD here. See further discussion in issue #168

This PR is basically reverting to some old text to remove the SHOULD here. See further discussion in issue #168
Copy link
Collaborator

@ianswett ianswett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a big fan of needed, but this is fine by me.

draft-ietf-quic-ack-frequency.md Outdated Show resolved Hide resolved
draft-ietf-quic-ack-frequency.md Outdated Show resolved Hide resolved
To limit the consequences of reduced acknowledgement frequency, a sender
SHOULD cause a receiver to send an acknowledgement at least once per RTT if
there are unacknowledged ack-eliciting packets in flight.
To enable a sender to respond to potential network congestion in a timely
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually don't think this is the only reason, there's also to avoid being unnecessarily CWND limited.

ianswett added a commit that referenced this pull request Jul 10, 2023
@gorryfair
Copy link
Contributor

I think this is wrong, and we need to keep the SHOULD. RFC8961 (2b) also says as much about the feedback timer:
"observations SHOULD be taken and incorporated into the RTO at least once per RTT or as frequently as data is exchanged in cases where that happens less frequently than once per RTT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants