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

Fix circular reference to kInitialRtt #3614

Merged
merged 2 commits into from Apr 30, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 4 additions & 3 deletions draft-ietf-quic-recovery.md
Expand Up @@ -533,8 +533,9 @@ previous RTT is available, the initial RTT SHOULD be set to 333ms, resulting in
a 1 second initial timeout, as recommended in {{?RFC6298}}.

A connection MAY use the delay between sending a PATH_CHALLENGE and receiving a
PATH_RESPONSE to set the initial RTT (see kInitialRtt in {{pto-handshake}})
for a new path, but the delay SHOULD NOT be considered an RTT sample.
PATH_RESPONSE to set the initial RTT (see kInitialRtt in
{{constants-of-interest}}) for a new path, but the delay SHOULD NOT be
considered an RTT sample.

Prior to handshake completion, when few to none RTT samples have been
generated, it is possible that the probe timer expiration is due to an
Expand Down Expand Up @@ -987,7 +988,7 @@ time_sent:
: The time the packet was sent.


## Constants of interest
## Constants of Interest {#constants-of-interest}

Constants used in loss recovery are based on a combination of RFCs, papers, and
common practice.
Expand Down