[quicwg/base-drafts] PTO pseudocode should not arm the timer for PN spaces with no bytes in flight (#3674)

ianswett <notifications@github.com> Wed, 20 May 2020 02:10 UTC

Date: Tue, 19 May 2020 19:09:58 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK57CQBTA32TDKXW4GF42BZHNEVBNHHCKCPB6Y@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3674@github.com>
Subject: [quicwg/base-drafts] PTO pseudocode should not arm the timer for PN spaces with no bytes in flight (#3674)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ec491765306a_98f3f9abaecd968509799"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/xSesAJZgN1BXwvn9oXEM3Nw32rg>

The text is fairly clear that PTO is armed for PN spaces with in-flight packets, but the pseudocode for arming the PTO has no consideration for whether there are bytes in flight in that PN space, and instead only considers the last sent packet in a PN space.

I believe the easiest solution is to add a bytes_in_flight indexed by PN space and then checking it in GetEarliestTimeAndSpace(or whatever replaces it) when deciding whether to arm the PTO.
https://github.com/quicwg/base-drafts/blob/master/draft-ietf-quic-recovery.md#setting-the-loss-detection-timer

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

[quicwg/base-drafts] PTO pseudocode should not ar… ianswett
Re: [quicwg/base-drafts] PTO pseudocode should no… ianswett
Re: [quicwg/base-drafts] PTO pseudocode should no… ianswett