Date: Wed, 06 Sep 2017 01:05:05 +0000 (UTC)
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4aba9e00749f659d943a3c9b2e68564f7bd870c583492cf0000000115c70bc092a169ce0f39df90@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/762@github.com>
Subject: [quicwg/base-drafts] Congestion feedback for rejected 0-RTT (#762)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_59af49c0bf940_5fbd3f94a7cffc304227c";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Ya8L7N4ExWlN4ifBnYj5qc5iVs4>

----==_mimepart_59af49c0bf940_5fbd3f94a7cffc304227c
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

When 0-RTT is rejected, any packets protected with those keys will be discarded by the server.  0-RTT rejection means that the server pretends that it can't read 0-RTT.  As a result, servers cannot (MUST NOT actually) acknowledge rejected 0-RTT.

This needs discussion in the recovery draft.  What do we tell the congestion controller about these packets?  The current design seems to only take bytes sent and packet loss as inputs to the algorithm.  That leads to the controller assuming that the packet was received successfully, when we have no way of knowing whether that is true or not.  We certainly don't want the client to ignore the fact that it sent packets, so what do we recommend?

See also #761.

-- 
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/762
----==_mimepart_59af49c0bf940_5fbd3f94a7cffc304227c
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>When 0-RTT is rejected, any packets protected with those keys will be discarded by the server.  0-RTT rejection means that the server pretends that it can't read 0-RTT.  As a result, servers cannot (MUST NOT actually) acknowledge rejected 0-RTT.</p>
<p>This needs discussion in the recovery draft.  What do we tell the congestion controller about these packets?  The current design seems to only take bytes sent and packet loss as inputs to the algorithm.  That leads to the controller assuming that the packet was received successfully, when we have no way of knowing whether that is true or not.  We certainly don't want the client to ignore the fact that it sent packets, so what do we recommend?</p>
<p>See also <a href="https://github.com/quicwg/base-drafts/issues/761" class="issue-link js-issue-link" data-url="https://github.com/quicwg/base-drafts/issues/761" data-id="255450371" data-error-text="Failed to load issue title" data-permission-text="Issue title is private">#761</a>.</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/762">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AWbkq9Uzr1TJLaNf-4uupzI2BxAN9Azjks5sfe_AgaJpZM4PNta6">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AWbkq-xCljbrG-SMVeSYXbj8DuMq8uX_ks5sfe_AgaJpZM4PNta6.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/quicwg/base-drafts/issues/762"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Congestion feedback for rejected 0-RTT (#762)"}],"action":{"name":"View Issue","url":"https://github.com/quicwg/base-drafts/issues/762"}}}</script>
----==_mimepart_59af49c0bf940_5fbd3f94a7cffc304227c--