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

Rework idle timeout definition #2346

Merged
merged 3 commits into from Jan 22, 2019
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
8 changes: 4 additions & 4 deletions draft-ietf-quic-transport.md
Expand Up @@ -2242,10 +2242,10 @@ If the idle timeout is enabled, a connection that remains idle for longer than
the advertised idle timeout (see {{transport-parameter-definitions}}) is closed.
A connection enters the draining state when the idle timeout expires.

Each endpoint advertises its own idle timeout to its peer. Endpoints restart
any timer they maintain when a packet from their peer is received and processed
successfully. The timer is also restarted when sending a packet containing
frames other than ACK or PADDING (an ACK-eliciting packet, see
Each endpoint advertises its own idle timeout to its peer. An enpdpoint
restarts any timer it maintains when a packet from their peer is received and
processed successfully. The timer is also restarted when sending a packet
containing frames other than ACK or PADDING (an ACK-eliciting packet, see
{{QUIC-RECOVERY}}), but only if no other ACK-eliciting packets have been sent
since last receiving a packet. Restarting when sending packets ensures that
connections do not prematurely time out when initiating new activity.
Expand Down