Date: Thu, 23 May 2019 03:10:51 -0700
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK4A3LEUTW6NGOA5IGN26OSCXEVBNHHBVJMHUM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2744/495156791@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2744@github.com>
References: <quicwg/base-drafts/issues/2744@github.com>
Subject: Re: [quicwg/base-drafts] Idle Timer Can Fire Even with Outstanding
 Data to Send (#2744)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5ce671abca642_6e2e3fe39d2cd95c13743c";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/1masLVO15UbvxcCdUCYkZ_VhjWo>


----==_mimepart_5ce671abca642_6e2e3fe39d2cd95c13743c
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

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
----==_mimepart_5ce671abca642_6e2e3fe39d2cd95c13743c
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>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.</p>
<p>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.</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/2744?email_source=notifications&amp;email_token=AFTOJK5QWANDIDU7PEWYRETPWZUSXA5CNFSM4HOS3R3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWBX4NY#issuecomment-495156791">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK3AEW44C75EBPDOZI3PWZUSXANCNFSM4HOS3R3A">mute the thread</a>.<img src="https://github.com/notifications/beacon/AFTOJK52TBLJTWCWUAHZUUDPWZUSXA5CNFSM4HOS3R3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWBX4NY.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/2744?email_source=notifications\u0026email_token=AFTOJK5QWANDIDU7PEWYRETPWZUSXA5CNFSM4HOS3R3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWBX4NY#issuecomment-495156791",
"url": "https://github.com/quicwg/base-drafts/issues/2744?email_source=notifications\u0026email_token=AFTOJK5QWANDIDU7PEWYRETPWZUSXA5CNFSM4HOS3R3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWBX4NY#issuecomment-495156791",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5ce671abca642_6e2e3fe39d2cd95c13743c--