Date: Thu, 05 Jan 2017 19:07:51 -0800
From: Martin Thomson <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/126@github.com>
Subject: [quicwg/base-drafts] Provide separate transport parameters for 0-RTT
 (#126)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_586f0a076eaeb_38013fe2aed9b1301339e1";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Q3iPdgFGoKW9uy_XTZDsbJnPDbc>
Cc: Subscribed <subscribed@noreply.github.com>
Reply-To: quic@ietf.org


----==_mimepart_586f0a076eaeb_38013fe2aed9b1301339e1
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

TLS provides an extension that limits the amount of data that can be sent during 0-RTT.  This is an explicit configuration item, even though TCP flow control would naturally limit the amount of data a client can send to a server with 0-RTT.  The reason for this is that servers might have to hold some or all of the 0-RTT data.  That buffering might be part of replay mitigation, for example.  A server that supports 0-RTT can use that limit to ensure that it doesn't have to buffer more than it is willing to buffer.

In #122, I have chosen to carry over the values for initial flow control window and concurrent stream limit.  We might want to provide separate transport parameters for 0-RTT so that servers can apply lower limits.

-- 
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/126
----==_mimepart_586f0a076eaeb_38013fe2aed9b1301339e1
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>TLS provides an extension that limits the amount of data that can be sent during 0-RTT.  This is an explicit configuration item, even though TCP flow control would naturally limit the amount of data a client can send to a server with 0-RTT.  The reason for this is that servers might have to hold some or all of the 0-RTT data.  That buffering might be part of replay mitigation, for example.  A server that supports 0-RTT can use that limit to ensure that it doesn't have to buffer more than it is willing to buffer.</p>
<p>In <a href="https://github.com/quicwg/base-drafts/pull/122" class="issue-link js-issue-link" data-url="https://github.com/quicwg/base-drafts/issues/122" data-id="198678499" data-error-text="Failed to load issue title" data-permission-text="Issue title is private">#122</a>, I have chosen to carry over the values for initial flow control window and concurrent stream limit.  We might want to provide separate transport parameters for 0-RTT so that servers can apply lower limits.</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/126">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AWbkq3mkXijdPQC7WpgnXJft1XTa8sOQks5rPbAHgaJpZM4LcXKi">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AWbkq04_xWXcNuVEIHpwhTDI31-i1CNEks5rPbAHgaJpZM4LcXKi.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/126"></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":"Provide separate transport parameters for 0-RTT (#126)"}],"action":{"name":"View Issue","url":"https://github.com/quicwg/base-drafts/issues/126"}}}</script>
----==_mimepart_586f0a076eaeb_38013fe2aed9b1301339e1--