Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456)

janaiyengar <notifications@github.com> Tue, 19 June 2018 18:46 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 1DD87130E18 for <quic-issues@ietfa.amsl.com>; Tue, 19 Jun 2018 11:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Is1P9TAH0nuz for <quic-issues@ietfa.amsl.com>; Tue, 19 Jun 2018 11:46:09 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F082130DC2 for <quic-issues@ietf.org>; Tue, 19 Jun 2018 11:46:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=EoSsr41Kunx0wYmegmcLL07eQHM=; b=BmBoCb0Cpcg3RLH2 YZBQ5y7VYyAUa9XuJv9qfLv8yjotoDDgdCjL7olBGj1DFiXm/FM7bes6lFJElUxt mXa1oR/CuNyiLX6kAdk26RsMUKZB7wJrUSkkbqDZQUkoxg/D6Z1y0VyvWiNrKKF6 GY7txvl55rQ/jWL+tUZVyDuivw8=
Received: by filter0347p1iad2.sendgrid.net with SMTP id filter0347p1iad2-16914-5B294F6F-E 2018-06-19 18:46:07.228973542 +0000 UTC
Received: from github-lowworker-b40b5a4.cp1-iad.github.net (unknown [192.30.252.36]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id kp8DmpfsSLiNOnWTz51dBQ for <quic-issues@ietf.org>; Tue, 19 Jun 2018 18:46:07.175 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-b40b5a4.cp1-iad.github.net (Postfix) with ESMTP id 275B43E0C10 for <quic-issues@ietf.org>; Tue, 19 Jun 2018 11:46:07 -0700 (PDT)
Date: Tue, 19 Jun 2018 18:46:07 +0000
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5de519e9bec40106b11a2d6b423f03333d9beba992cf000000011741116f92a169ce13dcc0d7@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1456/398504617@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1456@github.com>
References: <quicwg/base-drafts/issues/1456@github.com>
Subject: Re: [quicwg/base-drafts] Support for multiplexing middleboxes by requiring SNI (#1456)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b294f6f2513c_c542b0b1af8ef58123740"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3ax9aqCbW5ydhyVIpjtQaTXiqLDzES2A363m MmO3I8tDvOxtOZRmZQBeLXyI2D7YMM+P0H8HGuKBYpy4EICBgWtjb0aeJOIRD28O1Ja9R5K27XrcZU 84le20TAfRkpI8kawaIxSVCPrinZ6cmIL5JJh7Q8UU1bOU8V9kwYMwHyjO0Kqev9U1CJCPFI6ph+fz 4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/W5Njp-aYqQBWqp2y0oguRcjydHc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 19 Jun 2018 18:46:11 -0000

As noted already, QUIC inherits TLS's requirements of SNI (the SNI field is still part of TLS), and QUIC-HTTP inherits HTTP/2's requirements of SNI. @jmtilli : If you're concerned about encrypted SNI, that conversation ought to apply to HTTP over TCP as well, so I would take that to the httpbis working group. If you are concerned about other applications using QUIC without SNI, that'll probably be relevant when considering other applications mapped on QUIC, which we haven't done yet as a wg.

-- 
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/issues/1456#issuecomment-398504617