Re: [quicwg/base-drafts] SNI encryption (#795)
Martin Thomson <notifications@github.com> Thu, 12 July 2018 06:03 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 238BA130DC6 for <quic-issues@ietfa.amsl.com>; Wed, 11 Jul 2018 23:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.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_HI=-5, 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 5Gbo4P_t_Ay0 for <quic-issues@ietfa.amsl.com>; Wed, 11 Jul 2018 23:03:16 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E079130DCB for <quic-issues@ietf.org>; Wed, 11 Jul 2018 23:03:16 -0700 (PDT)
Date: Wed, 11 Jul 2018 23:03:15 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1531375395; bh=hvUBAxXJdt92b2DWUCErI5o2TYRXui3V9oZI4j0P7eI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fMhymyveR2Bi5gOqiLSnqA81JD34OZfA6K9ch4OTANLUK5/xjBHvLZd+IOU3kepKp p8aJF3uvVnGVkGJqKcq/uGeBH4GFobVRq3S4UxwNIbv7Bcs9gJBq+oVPwr2bqAFCkU dpeNFdOkp9bnH9KBsPKOmV3YOiDknfLr413ce9Cs=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba9a6db4448312035b644927817a3623e87fab0e792cf00000001175eb12392a169ce0f861fa8@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/795/404399245@github.com>
In-Reply-To: <quicwg/base-drafts/issues/795@github.com>
References: <quicwg/base-drafts/issues/795@github.com>
Subject: Re: [quicwg/base-drafts] SNI encryption (#795)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b46ef234610f_5be03fe18cc96f78580ca"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/JgiwCEpN_GVSugzYG__6rPWKe28>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 12 Jul 2018 06:03:20 -0000
My assessment here is that this will either happen in TLS or not and we don't need to track it specially in QUIC. No solution that I'm aware of will require changes to QUIC to be used because it all happens entirely outside the protocol (e.g., in DNS) or entirely within TLS. There's a small risk that the overzealous use of padding in some cases might make it hard for QUIC to benefit from this, or that the arrangement of the design is too narrow in applicability for it to apply to QUIC, but that seems unlikely given the actors. Those involved are motivated to have it work for QUIC. So I'm going to close this. If we need some changes to QUIC to support a particular design, we can discuss the specific requirements as they come up. Most likely, any such discussion would need to be left to v2. -- 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/795#issuecomment-404399245
- Re: [quicwg/base-drafts] SNI encryption (#795) ekr
- Re: [quicwg/base-drafts] SNI encryption (#795) Lars Eggert
- Re: [quicwg/base-drafts] SNI encryption (#795) Juha-Matti Tilli
- Re: [quicwg/base-drafts] SNI encryption (#795) ianswett
- Re: [quicwg/base-drafts] SNI encryption (#795) Juha-Matti Tilli
- [quicwg/base-drafts] SNI encryption (#795) Martin Thomson
- Re: [quicwg/base-drafts] SNI encryption (#795) hardie
- Re: [quicwg/base-drafts] SNI encryption (#795) Mike Bishop
- Re: [quicwg/base-drafts] SNI encryption (#795) Martin Thomson
- Re: [quicwg/base-drafts] SNI encryption (#795) Martin Thomson
- Re: [quicwg/base-drafts] SNI encryption (#795) Martin Thomson
- Re: [quicwg/base-drafts] SNI encryption (#795) Martin Thomson
- Re: [quicwg/base-drafts] SNI encryption (#795) MikkelFJ
- Re: [quicwg/base-drafts] SNI encryption (#795) Martin Thomson