Subject: Re: [quicwg/base-drafts] Idle Timer Can Fire Even with Outstanding Data to Send (#2744)
From: Nick Banks <[email-masked]>
To: quicwg/base-drafts <[email-masked]>
Cc: Subscribed <[email-masked]>
Date: Thu, 23 May 2019 03:10:51 -0700
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>

Thinking about this, another solution would be to continue to send a *blocked frame, while in the blocked state. Even if the peer acknowledged the first blocked frame, if you're still blocked, you send it again. Personally, for my implementation, this would be the easiest thing to implement.

I don't think the spec should make any requirements in this area, but I do think it should call this problem out and possibly make a recommendation.

-- 
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/2744#issuecomment-495156791