IETF Logo Mail Archive

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

ianswett <notifications@github.com> Sat, 18 November 2017 03:04 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 5F95D124239 for <quic-issues@ietfa.amsl.com>; Fri, 17 Nov 2017 19:04:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.616
X-Spam-Level:
X-Spam-Status: No, score=-0.616 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 wn2WRyyEgMFQ for <quic-issues@ietfa.amsl.com>; Fri, 17 Nov 2017 19:03:59 -0800 (PST)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 3AC4F126D0C for <quic-issues@ietf.org>; Fri, 17 Nov 2017 19:03:59 -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=Cl1mvRGwHuN8y2GHHQZTSvlDyE8=; b=TvhgcT/a/wmwmoKR AJs8LwzeG4Be/CzsQEQxOwTWxvCExSceRNotr5n0rVf7DBoMmkbo28Hr3DjgLPKB XS7mXajqFopoYgl51am4pGo9chE0JubHgfSbX7o+n8u2yVlys+sBAI7Up1s1vES8 pSqivXXF0+omGlFmyrxJhbmVfog=
Received: by filter0500p1mdw1.sendgrid.net with SMTP id filter0500p1mdw1-29925-5A0FA31E-7 2017-11-18 03:03:58.209176906 +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 ismtpd0001p1iad2.sendgrid.net (SG) with ESMTP id vTnQqyCtTfeaHxvzxQGWdw for <quic-issues@ietf.org>; Sat, 18 Nov 2017 03:03:58.283 +0000 (UTC)
Date: Sat, 18 Nov 2017 03:03:58 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4a35ce044d2e6491374892d711727dcaf43a43f392cf000000011627651e92a169ce105fcf55@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/345413832@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_5a0fa31e11e4a_576b3f892ac08f301955de"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0CIuvcynALGurvNsAYZItE3Q2/jN8UmAWabn p2d83ttDIolYL2QUy4dig0oYu3L4bVrBEeT4Sx/ikOrBP75TkI3qQbk3YDocw9Cl+iPw+PAdoWrNPX 3h6zpdgFTAPYNemCb1FOI6OrQmxoR1aJ4Ehvr1LFQbaMesJZlr0b+9pdoA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/rM7raCb7TqvjfMXNPpQIJXfew4w>
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 03:04:00 -0000

+1 to making this possible.  We could add a MAY resume with the session ticket from the TCP/TLS 1.3 connection if available?

It would be nice to know if the resumption was likely to work or if the TCP and QUIC TLS 1.3 resumption tokens were completely disjoint.  So possibly we either need to encourage applications to make resumption back and forth between QUIC and TCP work OR include some explicit indicator?

-- 
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-345413832

v2.23.0 | Report a Bug | By Email