Re: [quicwg/base-drafts] Change idle_timeout to max_idle_timeout (#3099)

[Marten Seemann <[e-mail]>]

marten-seemann commented on this pull request.



> @@ -2343,28 +2343,30 @@ source address.
 
 ## Idle Timeout {#idle-timeout}
 
-If the idle timeout is enabled, a connection is silently closed and the state is
-discarded when it remains idle for longer than both the advertised
-idle timeout (see {{transport-parameter-definitions}}) and three times the
+If the idle timeout is enabled by either peer, a connection is silently closed
+and its state is discarded when it remains idle for longer than the
+max_idle_timeout (see {{transport-parameter-definitions}}) and three times the

This sentence seems to contradict the next paragraph: The connection is closed when it remains idle for longer than the minimum of the max_idle_timeouts.

>  
-: The idle timeout is a value in milliseconds that is encoded as an integer; see
-  ({{idle-timeout}}).  If this parameter is absent or zero then the idle
-  timeout is disabled.
+: The max idle timeout is a value in milliseconds that is encoded as an integer;
+  see ({{idle-timeout}}).  Idle timeout is disabled when both endpoints omit this
+  transport parameteter or specify a value of 0.

In its current wording, this would mean that if one of the endpoints omits the parameter or sets it to 0, the resulting idle timeout would be 0 (since we're taking the minimum of both values).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3099#pullrequestreview-311011596