Re: [quicwg/base-drafts] Resume HTTP/2 TLS from QUIC ? (#941)

Subodh Iyengar <notifications@github.com> Sat, 18 November 2017 21:06 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 C4EFF12009C for <quic-issues@ietfa.amsl.com>; Sat, 18 Nov 2017 13:06:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 2WBkIbA4a_aV for <quic-issues@ietfa.amsl.com>; Sat, 18 Nov 2017 13:06:53 -0800 (PST)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 9B1D712008A for <quic-issues@ietf.org>; Sat, 18 Nov 2017 13:06:53 -0800 (PST)
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=5Ny0H3pzmyx8KZJE/8ER8QAwhnE=; b=r6Uwi+kaOUdv6cSf Cw5jnAOWhB8CNrBbXyGB/8JL9EVI3tYq8mXPDZ3ZsJlmsWI1jBxKcXxXeX5cZiMf g6bwVISXzPY3jxCG62j4PAngStnBu5nxiaRGa58YUavWvgFSc7DFF+JgjBKfh8wO c+o3piBqkuKYlzYjxFTvArHKKPc=
Received: by filter1143p1mdw1.sendgrid.net with SMTP id filter1143p1mdw1-20803-5A10A0EC-22 2017-11-18 21:06:52.834645054 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id 5OKq4mVeT9i5cuZ2nbV8yw for <quic-issues@ietf.org>; Sat, 18 Nov 2017 21:06:52.723 +0000 (UTC)
Date: Sat, 18 Nov 2017 21:06:53 +0000
From: Subodh Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb712da2ca7e7bb1030fdb06563d30d867d9a9dac92cf00000001162862ec92a169ce105fcf55@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/941/345471223@github.com>
In-Reply-To: <quicwg/base-drafts/issues/941@github.com>
References: <quicwg/base-drafts/issues/941@github.com>
Subject: Re: [quicwg/base-drafts] Resume HTTP/2 TLS from QUIC ? (#941)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a10a0eca0097_f303fcd92d48f3819638a5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: siyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
tracking:
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3vzVB0IjhwGUX8Y81kJGb4+Y/tAirvjl3oDB P7eIeEgsmcsfzPfrjvsda4Ph2WCPvok2+yQQ0OIKR8ScMTX+H7lvcNOZMjAjBuHhCbQewdtO8fOwyR 62X9GGkDXfam6yZAl7xVFo7sUYMHydOPtwYGWJPSuyd5epIOiV0cfIP1YQmRhLfYhiYI5T7PwYSamA o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/SFAxd3q6_KqmMhmCP7qTISaMLxo>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 18 Nov 2017 21:06:55 -0000

@davidben ya i mentioned that in a previous comment that tls tickets would have to have the quic params in them :) A QUIC compatible server would be aware that clients would use TLS 1.3 + TCP connections to them and send them the same ticket. 

We should probably also have a MUST restriction that this sharing should only be limited to TLS 1.3 + TCP clients (and maybe TLS 1.2 with Extended master secret) otherwise we end up running into issues with the session ticket for TLS 1.2  being reusable for 1.3 creating the potential for triple handshake like attacks.

-- 
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/941#issuecomment-345471223