-
Notifications
You must be signed in to change notification settings - Fork 204
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
ack_delay in the first Handshake and 1RTT packet #3981
Closed
Closed
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
9090e42
ack_delay in the first Handshake and 1RTT packet
ianswett 311d22d
Update draft-ietf-quic-transport.md
ianswett 9ed9536
Update draft-ietf-quic-recovery.md
ianswett 2226fe7
Update draft-ietf-quic-recovery.md
ianswett cb6f4c7
Update draft-ietf-quic-recovery.md
ianswett 73ec359
Update draft-ietf-quic-recovery.md
ianswett File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -348,11 +348,11 @@ latency at the peer or loss of previous ACK frames. Any delays beyond the | |
peer's max_ack_delay are therefore considered effectively part of path delay and | ||
incorporated into the smoothed_rtt estimate. | ||
|
||
The first ACK frame in the Handshake and ApplicationData packet number spaces can | ||
be greatly delayed due to a lack of decryption keys at the time they're received. | ||
For these two ACK frames, the max_ack_delay MAY be ignored if the sender chooses. | ||
Note that if there are no prior RTT samples, ignoring max_ack_delay has no | ||
impact. | ||
The first ACK frame in the Handshake and ApplicationData packet number spaces | ||
can be greatly delayed due to a lack of decryption keys at the time they're | ||
received. For these two ACK frames, the max_ack_delay MAY be ignored if the | ||
sender chooses. If the delayed ACK frame is the first RTT sample, ignoring | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The last sentence reads as imperative, but it's more of a "Note that if the delayed" |
||
max_ack_delay has no impact. | ||
|
||
When adjusting an RTT sample using peer-reported acknowledgement delays, an | ||
endpoint: | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
It's not really the first, but any packets that are buffered, right?
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.
Sure, though hopefully you're processing all buffered packets before sending an ACK.