[quicwg/base-drafts] bytes_in_flight update issue (#2009)

Lars Eggert <notifications@github.com> Thu, 15 November 2018 14:05 UTC

Date: Thu, 15 Nov 2018 06:05:01 -0800
From: Lars Eggert <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc25dac037714b78dcbaea24a887474e980ab164592cf0000000118053f0d92a169ce16b845fa@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2009@github.com>
Subject: [quicwg/base-drafts] bytes_in_flight update issue (#2009)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bed7d0dd664c_bb73fe96eed45bc675945"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/v5v-3rMOxq5ggt69eEq_2vDJ_K8>

I think the following issue exists in the pseudo code:

For a new ACK block, `OnAckReceived()` first calls `OnPacketAcked()`, where `OnPacketAckedCC()` reduces `bytes_in_flight` by the sizes of whichwever packets were ACKed.

Then,`OnAckReceived()` calls `DetectLostPackets()`,  which reduces `bytes_in_flight` for every packet that it determines to be lost. That can cause `bytes_in_flight` to become zero.

Next, `SetLossDetectionTimer()` is called. The first thing that does is to cancel the `loss_detection_timer` when `bytes_in_flight` is zero.

So when and how are the packets that were declared lost retransmitted?


-- 
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/2009

[quicwg/base-drafts] bytes_in_flight update issue… Lars Eggert
Re: [quicwg/base-drafts] bytes_in_flight update i… Tatsuhiro Tsujikawa
Re: [quicwg/base-drafts] bytes_in_flight update i… ianswett
Re: [quicwg/base-drafts] bytes_in_flight update i… janaiyengar
Re: [quicwg/base-drafts] bytes_in_flight update i… Lars Eggert