Date: Wed, 07 Jun 2017 01:23:10 -0700
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab47d08ac5455e4e31b3173724be4f73ce28210ae492cf00000001154f79ee92a169ce0df481a1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/600/c306725562@github.com>
In-Reply-To: <quicwg/base-drafts/pull/600@github.com>
References: <quicwg/base-drafts/pull/600@github.com>
Subject: Re: [quicwg/base-drafts] Split QUIC core from QUIC v1 (#600)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5937b7eed9628_66d3fa2c0e05c34797b6";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/igLJP9lqWa6BuvZOccMfjoJEWm8>

----==_mimepart_5937b7eed9628_66d3fa2c0e05c34797b6
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

> I'll note that it feels a little odd to have "core QUIC" not be multiplexed and have no concept of a crypto handshake.

Was wondering the same with the current draft text: there needs to be some requirements a custom crypto handshake must comply to. Such as as error handling, verifying the size of Client Initial Packet, how and when to accept clear text packets and how to transition to encryption. QUIC-TLS and TLS-1.3 covers this, but some information should probably be destilled in a general purpose handshake discussion.

-- 
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/600#issuecomment-306725562
----==_mimepart_5937b7eed9628_66d3fa2c0e05c34797b6
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<blockquote>
<p>I'll note that it feels a little odd to have "core QUIC" not be multiple=
xed and have no concept of a crypto handshake.</p>
</blockquote>
<p>Was wondering the same with the current draft text: there needs to be so=
me requirements a custom crypto handshake must comply to. Such as as error =
handling, verifying the size of Client Initial Packet, how and when to acce=
pt clear text packets and how to transition to encryption. QUIC-TLS and TLS=
-1.3 covers this, but some information should probably be destilled in a ge=
neral purpose handshake discussion.</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&mda=
sh;<br />You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, <a href=3D"https://github.com/quicwg/bas=
e-drafts/pull/600#issuecomment-306725562">view it on GitHub</a>, or <a href=
=3D"https://github.com/notifications/unsubscribe-auth/AWbkq6QOnImGf6Iqv4Glr=
r1kn8tMu2hsks5sBl3ugaJpZM4NyWse">mute the thread</a>.<img alt=3D"" height=
=3D"1" src=3D"https://github.com/notifications/beacon/AWbkq9tg6Et6aQUX8EiNN=
SKy6E8wMeXpks5sBl3ugaJpZM4NyWse.gif" width=3D"1" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewAction=
">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/pull=
/600#issuecomment-306725562"></link>
  <meta itemprop=3D"name" content=3D"View Pull Request"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Pull Request on GitHub"=
></meta>
</div>

<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_version"=
:"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"Gi=
tHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg=
/base-drafts","subtitle":"GitHub repository","main_image_url":"https://clou=
d.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290=
892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/asset=
s/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":"@mikkelfj in #600: \u003e I'll n=
ote that it feels a little odd to have \"core QUIC\" not be multiplexed and=
 have no concept of a crypto handshake.\r\n\r\nWas wondering the same with =
the current draft text: there needs to be some requirements a custom crypto=
 handshake must comply to. Such as as error handling, verifying the size of=
 Client Initial Packet, how and when to accept clear text packets and how t=
o transition to encryption. QUIC-TLS and TLS-1.3 covers this, but some info=
rmation should probably be destilled in a general purpose handshake discuss=
ion."}],"action":{"name":"View Pull Request","url":"https://github.com/quic=
wg/base-drafts/pull/600#issuecomment-306725562"}}}</script>=

----==_mimepart_5937b7eed9628_66d3fa2c0e05c34797b6--