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

Ryan Hamilton <> Wed, 08 January 2020 19:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 77AB312020A for <>; Wed, 8 Jan 2020 11:21:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hI-gl4za0AJ1 for <>; Wed, 8 Jan 2020 11:21:18 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D59D61201EA for <>; Wed, 8 Jan 2020 11:21:17 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 3C748A0553 for <>; Wed, 8 Jan 2020 11:21:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1578511277; bh=xbWchZUOzlDupn9UL2ctgjSOcybwU9Jh9tnpxa8tVkw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mf7Ab7+z47vd3w2q2hAYK4dPsYOkz/swAGD8KS1EeDMhupQKXbRKgkcHxQfUQgGpV RUIJB8Tz7fRRUbYZ7MRpbhjYoXRfdIUqxQKDsx7XQ+rzboFJtdWPeIUFC982Ik24VO ZNPUUTxacxNjvydk59YNKq4fWp4ii8EYjX97EG6g=
Date: Wed, 08 Jan 2020 11:21:17 -0800
From: Ryan Hamilton <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3326/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Make SNI more clearly mandatory (#3326)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e162bad2d85e_18983fc754acd9641601c1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: RyanAtGoogle
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
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 19:21:21 -0000

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

In general, I don't think clients know if the hostname of the server in the URL is fully qualified or not, so the "as understood by the client" part seems important.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: