Date: Wed, 07 Dec 2016 16:37:46 -0800
From: Mike Bishop <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/30/review/11928784@github.com>
In-Reply-To: <quicwg/base-drafts/pull/30@github.com>
References: <quicwg/base-drafts/pull/30@github.com>
Subject: Re: [quicwg/base-drafts] TLS interface overview (#30)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5848ab5ae1097_702d3f95adccd1343641f1";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/gUoTnUmR_Jz6i9w_ryclEteM384>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab1d89f7b612255ae250ee1514e2060c82a3292fbf92cf0000000114606d5a92a169ce0b706324@reply.github.com>

----==_mimepart_5848ab5ae1097_702d3f95adccd1343641f1
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

MikeBishop commented on this pull request.



> +Additional functions might be needed to configure TLS.
+
+
+### Handshake Interface
+
+In order to drive the handshake, TLS depends on being able to send and receive
+handshake messages on stream 1.  There are two basic functions on this
+interface: one where QUIC requests handshake messages and one where QUIC
+provides handshake packets.
+
+A QUIC client starts TLS by requesting TLS handshake octets from
+TLS.  The client acquires handshake octets before sending its first packet.
+
+A QUIC server starts the process by providing TLS with any stream 1 octets that
+might have arrived.  Only in-sequence packets are delivered; packets that arrive
+out of order are buffered by QUIC until all preceding packets are available.

Should this be "frames"?  Packets might be lost and retransmitted, so you wouldn't necessarily have preceding packets becoming available.  (Not including in the purely-editorial commit I'm preparing, because I'm not certain if that's the correct wording.)

-- 
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/pull/30#pullrequestreview-11928784
----==_mimepart_5848ab5ae1097_702d3f95adccd1343641f1
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p><b>@MikeBishop</b> commented on this pull request.</p>

<hr>

<p>In <a href="https://github.com/quicwg/base-drafts/pull/30#pullrequestreview-11928784">draft-ietf-quic-tls.md</a>:</p>
<pre style='color:#555'>&gt; +Additional functions might be needed to configure TLS.
+
+
+### Handshake Interface
+
+In order to drive the handshake, TLS depends on being able to send and receive
+handshake messages on stream 1.  There are two basic functions on this
+interface: one where QUIC requests handshake messages and one where QUIC
+provides handshake packets.
+
+A QUIC client starts TLS by requesting TLS handshake octets from
+TLS.  The client acquires handshake octets before sending its first packet.
+
+A QUIC server starts the process by providing TLS with any stream 1 octets that
+might have arrived.  Only in-sequence packets are delivered; packets that arrive
+out of order are buffered by QUIC until all preceding packets are available.
</pre>
<p>Should this be "frames"?  Packets might be lost and retransmitted, so you wouldn't necessarily have preceding packets becoming available.  (Not including in the purely-editorial commit I'm preparing, because I'm not certain if that's the correct wording.)</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/pull/30#pullrequestreview-11928784">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AWbkqwcpVny8s_7PzLfCZcQw8kghteKbks5rF1FagaJpZM4K9Ynx">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AWbkq_LVOFvBIfOPQOQWyOgLEx7TdRHwks5rF1FagaJpZM4K9Ynx.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/pull/30#pullrequestreview-11928784"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request 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":"PERSON","message":"@MikeBishop commented on #30"}],"action":{"name":"View Pull Request","url":"https://github.com/quicwg/base-drafts/pull/30#pullrequestreview-11928784"}}}</script>
----==_mimepart_5848ab5ae1097_702d3f95adccd1343641f1--