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.

Sign up for GitHub

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

Jump to bottom

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

Merged
merged 2 commits into from Aug 15, 2018
Merged

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

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3c5ae7b
use the 'no outstanding' rule to defer idle timeout
martinthomson Aug 13, 2018
3526d34
Fixup idle timeout with no use of 'outstanding'
martinthomson Aug 15, 2018
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
10 changes: 7 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2499,9 +2499,13 @@ A connection that remains idle for longer than the advertised idle timeout (see
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, or the first packet sent after the last
received packet. The latter condition ensures that initiating new activity
postpones a 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. 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