Date: Mon, 25 Sep 2017 04:50:58 +0000 (UTC)
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abc540bba6f5565823c6465d499ce4234531add00892cf0000000115e04d3192a169ce0d78bf28@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/495/331776572@github.com>
In-Reply-To: <quicwg/base-drafts/issues/495@github.com>
References: <quicwg/base-drafts/issues/495@github.com>
Subject: Re: [quicwg/base-drafts] Guidance for port number use (#495)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_59c88b31c5d47_26c93f96ee4aef88311f1";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ytgxXiEvIc9kR7bVzcYREJVJQek>

----==_mimepart_59c88b31c5d47_26c93f96ee4aef88311f1
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

TLS 1.3 does not require that SNI be used.  HTTP/2 does.  We won't be picking up the TLS usage requirements from h2, mainly because TLS 1.3 invalidates virtually all of them.  Mandatory SNI is one that we won't get.

@igorlord, can you open an issue to track this.  I don't think that there was ever any intent to differ from HTTP/2 on this point, but we need to make sure that we don't lose it.

-- 
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/495#issuecomment-331776572
----==_mimepart_59c88b31c5d47_26c93f96ee4aef88311f1
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>TLS 1.3 does not require that SNI be used.  HTTP/2 does.  We won't be pi=
cking up the TLS usage requirements from h2, mainly because TLS 1.3 invalid=
ates virtually all of them.  Mandatory SNI is one that we won't get.</p>
<p><a href=3D"https://github.com/igorlord" class=3D"user-mention">@igorlord=
</a>, can you open an issue to track this.  I don't think that there was ev=
er any intent to differ from HTTP/2 on this point, but we need to make sure=
 that we don't lose it.</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/495#issuecomment-331776572">view it on GitHub</a>, or <a hr=
ef=3D"https://github.com/notifications/unsubscribe-auth/AWbkq_VhJ0ox8fkga98=
m81eUU4njH3rPks5slzExgaJpZM4NPiFl">mute the thread</a>.<img alt=3D"" height=
=3D"1" src=3D"https://github.com/notifications/beacon/AWbkq9tNphHLBRjw5OkLE=
E6IFu89JJSwks5slzExgaJpZM4NPiFl.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/495#issuecomment-331776572"></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":"@martinthomson in #495: TLS 1.3 =
does not require that SNI be used.  HTTP/2 does.  We won't be picking up th=
e TLS usage requirements from h2, mainly because TLS 1.3 invalidates virtua=
lly all of them.  Mandatory SNI is one that we won't get.\r\n\r\n@igorlord,=
 can you open an issue to track this.  I don't think that there was ever an=
y intent to differ from HTTP/2 on this point, but we need to make sure that=
 we don't lose it."}],"action":{"name":"View Issue","url":"https://github.c=
om/quicwg/base-drafts/issues/495#issuecomment-331776572"}}}</script>=

----==_mimepart_59c88b31c5d47_26c93f96ee4aef88311f1--