Date: Sat, 18 Nov 2017 03:03:58 +0000 (UTC)
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab4a35ce044d2e6491374892d711727dcaf43a43f392cf000000011627651e92a169ce105fcf55@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/941/345413832@github.com>
In-Reply-To: <quicwg/base-drafts/issues/941@github.com>
References: <quicwg/base-drafts/issues/941@github.com>
Subject: Re: [quicwg/base-drafts] Resume HTTP/2 TLS from QUIC ? (#941)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5a0fa31e11e4a_576b3f892ac08f301955de";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
tracking: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/rM7raCb7TqvjfMXNPpQIJXfew4w>

----==_mimepart_5a0fa31e11e4a_576b3f892ac08f301955de
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

+1 to making this possible.  We could add a MAY resume with the session ticket from the TCP/TLS 1.3 connection if available?

It would be nice to know if the resumption was likely to work or if the TCP and QUIC TLS 1.3 resumption tokens were completely disjoint.  So possibly we either need to encourage applications to make resumption back and forth between QUIC and TCP work OR include some explicit indicator?

-- 
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/941#issuecomment-345413832
----==_mimepart_5a0fa31e11e4a_576b3f892ac08f301955de
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>+1 to making this possible.  We could add a MAY resume with the session =
ticket from the TCP/TLS 1.3 connection if available?</p>
<p>It would be nice to know if the resumption was likely to work or if the =
TCP and QUIC TLS 1.3 resumption tokens were completely disjoint.  So possib=
ly we either need to encourage applications to make resumption back and for=
th between QUIC and TCP work OR include some explicit indicator?</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/issues/941#issuecomment-345413832">view it on GitHub</a>, or <a hr=
ef=3D"https://github.com/notifications/unsubscribe-auth/AWbkq4b4S6WEeCVzCQD=
WWMp1H-ERf9vvks5s3kkegaJpZM4QhXjN">mute the thread</a>.<img alt=3D"" height=
=3D"1" src=3D"https://github.com/notifications/beacon/AWbkq159_RaSuqcVN3o79=
Zz8N2MyTd_Rks5s3kkegaJpZM4QhXjN.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/issu=
es/941#issuecomment-345413832"></link>
  <meta itemprop=3D"name" content=3D"View Issue"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Issue 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":"@ianswett in #941: +1 to making =
this possible.  We could add a MAY resume with the session ticket from the =
TCP/TLS 1.3 connection if available?\r\n\r\nIt would be nice to know if the=
 resumption was likely to work or if the TCP and QUIC TLS 1.3 resumption to=
kens were completely disjoint.  So possibly we either need to encourage app=
lications to make resumption back and forth between QUIC and TCP work OR in=
clude some explicit indicator?"}],"action":{"name":"View Issue","url":"http=
s://github.com/quicwg/base-drafts/issues/941#issuecomment-345413832"}}}</sc=
ript>=

----==_mimepart_5a0fa31e11e4a_576b3f892ac08f301955de--