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

David Schinazi <> Wed, 08 January 2020 18:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 794D11208BB for <>; Wed, 8 Jan 2020 10:27:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.998
X-Spam-Status: No, score=-7.998 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, URIBL_BLOCKED=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 GawrgAkmpuB8 for <>; Wed, 8 Jan 2020 10:27:25 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4F824120133 for <>; Wed, 8 Jan 2020 10:27:23 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id A6CDB661E2B for <>; Wed, 8 Jan 2020 10:27:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1578508042; bh=fnkSqDMAI0aTsvZbwUSSbjdx+8fazNNtJ2A8k/nbC9c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=U5DXZ/9t/M7VDyT21doWRe39LxInlAltFM+1OL1rheb39P1LK+Jn5OgF4CjK1EGb/ gSjovP4iZdLU9fexoMyGak1Uptnl/nrBxLMveVaE6csCIjr/oMCNQr+PydGIbD0JsK d+I4ivc6VMGCJ3keBRiemyoIxqDDwJcuY+qR/8CE=
Date: Wed, 08 Jan 2020 10:27:22 -0800
From: David Schinazi <>
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_5e161f0a9864c_2c193f916bacd960344490"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
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 18:27:28 -0000

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

According to [RFC 6066](
> "HostName" contains the fully qualified DNS hostname of the server,
> as understood by the client.

Should we replace "DNS name" with "fully qualified DNS hostname"?

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