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

Use the 'no outstanding' rule to defer idle timeout #1652

Merged
merged 2 commits into from
Aug 15, 2018
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -2501,9 +2501,11 @@ draining state when the idle timeout expires.
Each endpoint advertises their own idle timeout to their peer. The idle timeout
starts from the last packet received. In order to ensure that initiating new
activity postpones an idle timeout, an endpoint restarts this timer when sending
a packet if there are no other packets outstanding. This condition only applies
to packets that contain other than ACK or PADDING frames; those packets could
remain outstanding longer and prevent the timeout from being extended.
a packet. An endpoint does not postpone the idle timeout if another packet has
been sent containing frames other than ACK or PADDING, and that other packet has
not been acknowledged or declared lost. Packets that contain only ACK or
PADDING frames are not acknowledged until an endpoint has other frames to send,
so they could prevent the timeout from being refreshed.

The value for an idle timeout can be asymmetric. The value advertised by an
endpoint is only used to determine whether the connection is live at that
Expand Down