Date: Tue, 28 Jul 2020 18:59:38 -0700
From: Kazu Yamamoto <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK2A7JS477FWIQWQR7V5FS4QVEVBNHHCPSIYIY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3969@github.com>
Subject: [quicwg/base-drafts] loss_detection_timer.update in recovery (#3969)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5f20d80ab2fe0_796416f8238311";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/20DtoJquR11nvtUxQmfkYseok7M>


----==_mimepart_5f20d80ab2fe0_796416f8238311
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

When a client is downloading a large contents from a server, the server sends `STREAM` repeatedly and the client sends `ACK` repeatedly. In this situation, `time_of_last_ack_eliciting_packet` is not updated in the client side. So, `timeout - now()`in `loss_detection_timer.update` can be a non-positive timeout value.

It seems to me that it is unclear how `loss_detection_timer.update` should behave when timeout value is non-positive.


-- 
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/issues/3969
----==_mimepart_5f20d80ab2fe0_796416f8238311
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p></p>
<p>When a client is downloading a large contents from a server, the server sends <code>STREAM</code> repeatedly and the client sends <code>ACK</code> repeatedly. In this situation, <code>time_of_last_ack_eliciting_packet</code> is not updated in the client side. So, <code>timeout - now()</code>in <code>loss_detection_timer.update</code> can be a non-positive timeout value.</p>
<p>It seems to me that it is unclear how <code>loss_detection_timer.update</code> should behave when timeout value is non-positive.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3969">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJKYXL56IXUX2R6RWTM3R557AVANCNFSM4PLDJLCA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJKZM65I6X24YGDYS6KLR557AVA5CNFSM4PLDJLCKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4J6JDBDA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3969",
"url": "https://github.com/quicwg/base-drafts/issues/3969",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5f20d80ab2fe0_796416f8238311--