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

ekr <notifications@github.com> Wed, 08 January 2020 13:54 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 B006512004C for <quic-issues@ietfa.amsl.com>; Wed, 8 Jan 2020 05:54:32 -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_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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 rcVbxLQqZGAE for <quic-issues@ietfa.amsl.com>; Wed, 8 Jan 2020 05:54:30 -0800 (PST)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C668F120044 for <quic-issues@ietf.org>; Wed, 8 Jan 2020 05:54:30 -0800 (PST)
Received: from github-lowworker-f144ac1.va3-iad.github.net (github-lowworker-f144ac1.va3-iad.github.net [10.48.16.59]) by smtp.github.com (Postfix) with ESMTP id F1E6852006A for <quic-issues@ietf.org>; Wed, 8 Jan 2020 05:54:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1578491669; bh=d3f+/TYHP7U20RBisN41Kzr4dK7D7UcWEyerZcey6V4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wghLcxurmBsQdcMXqcwaFYrp2xGnNSEPzySbsGTlX/ABTDeHci7wzNAwwESWHFq28 QQ0+pvHg/j/44dgUkM8lTzcmlVx8ODES5DoEoLZKn7NNCDwmNFl4BYr3sbSh9/3uf+ vWBqGAXCvcILnt2uZ62TLEnduLpb1E7LbdnaBvwc=
Date: Wed, 08 Jan 2020 05:54:29 -0800
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6G6J4KH2WI2WPCNYN4EMIZLEVBNHHCBFKVVY@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/review/339876987@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_5e15df15e1f55_1e433ff5204cd95c11104c"; 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/Vg0vLcfKMPe98vR5Npes9Z15RZA>
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 13:54:33 -0000

ekr commented on this pull request.



> @@ -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.

Maybe
"If the server is identified by a DNS name, clients MUST send the Server Name Indication (SNI) ... extension to TLS unless an alternative mechanism for indicating the server is available"

Note that we'll want to carefully word this to avoid requiring SNI when doing QUIC with mDNS candidates for WebRTC.

-- 
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#pullrequestreview-339876987