Return-Path: X-Original-To: quic-issues@ietfa.amsl.com Delivered-To: quic-issues@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF0CD12020A for ; Wed, 8 Jan 2020 14:56:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.999 X-Spam-Level: X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4yBYy-Er4guB for ; Wed, 8 Jan 2020 14:56:51 -0800 (PST) Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3F0312012A for ; Wed, 8 Jan 2020 14:56:51 -0800 (PST) Date: Wed, 08 Jan 2020 14:56:49 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1578524209; bh=vmMdKPKzNVs08lo5Jzq/3UvHyuRPZKLmmcy9GqknWAo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gJ4I4rfklu/zMmCIzWKW+APMXVBInNDxyXIQGf/ZFr2ZLSkbuOGSIDI8ZGSIVJaaF KNQhl3kAyPWzsDqnsXWmORcbUptla9fWN8lWmPLFIyVICO/zvWsA573qyVCHG34JFw IGsW2sykMo332CAM7bL5FRrwzFoymumD5EMEYlxQ= From: ekr Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Make SNI more clearly mandatory (#3326) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5e165e31e0be0_7be13fe500ecd96415581f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: ekr X-GitHub-Recipient: quic-issues X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.29 List-Id: Notification list for GitHub issues related to the QUIC WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jan 2020 22:56:54 -0000 ----==_mimepart_5e165e31e0be0_7be13fe500ecd96415581f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Jan 8, 2020 at 10:22 AM David Schinazi = =0D wrote:=0D =0D > *@DavidSchinazi* commented on this pull request.=0D > ------------------------------=0D >=0D > In draft-ietf-quic-http.md=0D > = :=0D >=0D > > @@ -312,11 +317,14 @@ an explicit port.=0D >=0D > ## Connection Establishment {#connection-establishment}=0D >=0D > -HTTP/3 relies on QUIC as the underlying transport. The QUIC version b= eing used=0D > -MUST use TLS version 1.3 or greater as its handshake protocol. HTTP/3= clients=0D > -MUST indicate the target domain name during the TLS handshake. This ma= y be done=0D > -using the Server Name Indication (SNI) {{!RFC6066}} extension to TLS o= r using=0D > -some other mechanism.=0D > +HTTP/3 relies on QUIC version 1 as the underlying transport. The use = of other=0D > +QUIC transport versions with HTTP/3 MAY be defined by future specifica= tions.=0D > +=0D > +QUIC version 1 uses TLS version 1.3 or greater as its handshake protoc= ol.=0D > +HTTP/3 clients MUST support a mechanism to indicate the target host to= the=0D > +server during the TLS handshake. Unless an alternative mechanism for = indicating=0D > +the target host is used, clients MUST use the Server Name Indication (= SNI)=0D > +{{!RFC6066}} extension to TLS if the target host is a DNS name.=0D >=0D > @ekr Do you think WebRTC would use HTTP/3? I w= as=0D > somewhat expecting WebRTC to build something directly over QUICv1, not = over=0D > HTTP/3?=0D >=0D Oh, yes. I missed which document this was in.=0D =0D > =E2=80=94=0D > You are receiving this because you were mentioned.=0D > Reply to this email directly, view it on GitHub=0D > ,=0D > or unsubscribe=0D > =0D > .=0D >=0D =0D =0D -- =0D You are receiving this because you are subscribed to this thread.=0D Reply to this email directly or view it on GitHub:=0D https://github.com/quicwg/base-drafts/pull/3326#issuecomment-572298035= ----==_mimepart_5e165e31e0be0_7be13fe500ecd96415581f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Jan 8, 2020 at 10:22 AM David Schinazi <notifications@github.c= om>
=0D wrote:
=0D
=0D > *@DavidSchinazi* commented on this pull request.
=0D > ------------------------------
=0D >
=0D > In draft-ietf-quic-http.md
=0D > <https://github.com/quicwg/base-drafts/pull/3326#discussion_r3643= 75027>:
=0D >
=0D > > @@ -312,11 +317,14 @@ an explicit port.
=0D >
=0D > ## Connection Establishment {#connection-establishment}
=0D >
=0D > -HTTP/3 relies on QUIC as the underlying transport. The QUIC versio= n being used
=0D > -MUST use TLS version 1.3 or greater as its handshake protocol. HTT= P/3 clients
=0D > -MUST indicate the target domain name during the TLS handshake. This= may be done
=0D > -using the Server Name Indication (SNI) {{!RFC6066}} extension to TL= S or using
=0D > -some other mechanism.
=0D > +HTTP/3 relies on QUIC version 1 as the underlying transport. The u= se of other
=0D > +QUIC transport versions with HTTP/3 MAY be defined by future specif= ications.
=0D > +
=0D > +QUIC version 1 uses TLS version 1.3 or greater as its handshake pro= tocol.
=0D > +HTTP/3 clients MUST support a mechanism to indicate the target host= to the
=0D > +server during the TLS handshake. Unless an alternative mechanism f= or indicating
=0D > +the target host is used, clients MUST use the Server Name Indicatio= n (SNI)
=0D > +{{!RFC6066}} extension to TLS if the target host is a DNS name.
= =0D >
=0D > @ekr <https://github.com/ekr> Do you think WebRTC would use HT= TP/3? I was
=0D > somewhat expecting WebRTC to build something directly over QUICv1, n= ot over
=0D > HTTP/3?
=0D >
=0D Oh, yes. I missed which document this was in.
=0D
=0D > =E2=80=94
=0D > You are receiving this because you were mentioned.
=0D > Reply to this email directly, view it on GitHub
=0D > <https://github.com/quicwg/base-drafts/pull/3326?email_source=3Dn= otifications&email_token=3DAAIPLINHXJVVGSN4A4G5ZJ3Q4YKX7A5CNFSM4KEDE2= WKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCRC= NCNQ#discussion_r364375027>,
=0D > or unsubscribe
=0D > <https://github.com/notifications/unsubscribe-auth/AAIPLIK34YQZLQ= WRQR7M5TDQ4YKX7ANCNFSM4KEDE2WA>
=0D > .
=0D >
=0D =0D =0D

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on = GitHub, or unsubscribe.3D""

=0D = ----==_mimepart_5e165e31e0be0_7be13fe500ecd96415581f--