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

Three times PTOs allows PTO to expire #4084

Merged
merged 5 commits into from Sep 10, 2020
Merged
Changes from 1 commit
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
5 changes: 2 additions & 3 deletions draft-ietf-quic-transport.md
Expand Up @@ -2222,8 +2222,7 @@ defined in {{QUIC-RECOVERY}} is RECOMMENDED. That is:
~~~

This timeout allows for multiple PTOs to expire prior to failing path
validation, allowing for at least one path validation to be lost before
declaring failure.
validation, ensuring one packet loss does not cause path validation failure.
ianswett marked this conversation as resolved.
Show resolved Hide resolved

Note that the endpoint might receive packets containing other frames on the new
path, but a PATH_RESPONSE frame with appropriate data is required for path
Expand Down Expand Up @@ -2708,7 +2707,7 @@ ensures that connections are not closed after new activity is initiated.
To avoid excessively small idle timeout periods, endpoints MUST increase the
idle timeout period to be at least three times the current Probe Timeout (PTO).
This allows for multiple PTOs to expire prior to idle timeout, allowing for at
least one path packet to be lost timing out the connection.
least one packet to be lost prior to idle timeout.


### Liveness Testing
Expand Down