-
Notifications
You must be signed in to change notification settings - Fork 18
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
Gorry's editorial comments #296
Conversation
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One suggestion and one Question, but otherwise LG
draft-ietf-quic-ack-frequency.md
Outdated
@@ -145,7 +145,7 @@ endpoint performance in the following ways: | |||
- Sending UDP datagrams is very CPU intensive on some platforms. A data | |||
receiver can decrease its CPU usage by reducing the number of | |||
acknowledgement-only packets sent. Experience shows that this | |||
reduction can be critical for high bandwidth connections. | |||
reduction can be critical for high-rate connections. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm unsure what this means, but I can see why bandwidth may not be exactly correct. What about "high packet rate connections."?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
packet rate is fine also
Thanks!