Re: [quicwg/base-drafts] Make SNI more clearly mandatory (#3326)

ekr <notifications@github.com> Wed, 08 January 2020 22:56 UTC

Return-Path: <noreply@github.com>
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 <quic-issues@ietfa.amsl.com>; 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 <quic-issues@ietfa.amsl.com>; 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 <quic-issues@ietf.org>; 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 <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6JBRLTWXYKGQOTTCN4EOILDEVBNHHCBFKVVY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3326/c572298035@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3326@github.com>
References: <quicwg/base-drafts/pull/3326@github.com>
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: <https://mailarchive.ietf.org/arch/msg/quic-issues/NpVMo5xDgJx3TTKMpmF2SRW93AY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 22:56:54 -0000

On Wed, Jan 8, 2020 at 10:22 AM David Schinazi <notifications@github.com>
wrote:

> *@DavidSchinazi* commented on this pull request.
> ------------------------------
>
> In draft-ietf-quic-http.md
> <https://github.com/quicwg/base-drafts/pull/3326#discussion_r364375027>:
>
> > @@ -312,11 +317,14 @@ an explicit port.
>
>  ## Connection Establishment {#connection-establishment}
>
> -HTTP/3 relies on QUIC as the underlying transport.  The QUIC version being used
> -MUST use TLS version 1.3 or greater as its handshake protocol.  HTTP/3 clients
> -MUST indicate the target domain name during the TLS handshake. This may be done
> -using the Server Name Indication (SNI) {{!RFC6066}} extension to TLS or using
> -some other mechanism.
> +HTTP/3 relies on QUIC version 1 as the underlying transport.  The use of other
> +QUIC transport versions with HTTP/3 MAY be defined by future specifications.
> +
> +QUIC version 1 uses TLS version 1.3 or greater as its handshake protocol.
> +HTTP/3 clients MUST support a mechanism to indicate the target host to the
> +server during the TLS handshake.  Unless an alternative mechanism for indicating
> +the target host is used, clients MUST use the Server Name Indication (SNI)
> +{{!RFC6066}} extension to TLS if the target host is a DNS name.
>
> @ekr <https://github.com/ekr> Do you think WebRTC would use HTTP/3? I was
> somewhat expecting WebRTC to build something directly over QUICv1, not over
> HTTP/3?
>
Oh, yes. I missed which document this was in.

> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/pull/3326?email_source=notifications&email_token=AAIPLINHXJVVGSN4A4G5ZJ3Q4YKX7A5CNFSM4KEDE2WKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCRCNCNQ#discussion_r364375027>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAIPLIK34YQZLQWRQR7M5TDQ4YKX7ANCNFSM4KEDE2WA>
> .
>


-- 
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/3326#issuecomment-572298035