-
Notifications
You must be signed in to change notification settings - Fork 205
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
Prohibit PADDING in response to ACK #3104
Conversation
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.
Some editorial suggestions, including improving the existing text.
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.
LGTM. Though all the "non-ACK-eliciting packets" is a bit of a mouth full.
draft-ietf-quic-transport.md
Outdated
it sends an ACK frame. | ||
one ACK-frame-only packet in response to receiving an ack-eliciting packet. An | ||
endpoint MUST NOT send a non-ack-eliciting packet in response to a non-ack- | ||
eliciting packet, even if there are packet gaps which precede the received |
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.
A nit: Though this hyphenation looks sane when presented this way, it won't be guaranteed to render nicely. It might appear as non-ack- eliciting
(note the extra space). I think that you should remove the wrapping on the hyphen.
Fixing #3100