Re: [quicwg/base-drafts] QUIC advertisement description (#87)
Mike Bishop <notifications@github.com> Fri, 16 December 2016 21:41 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 617FB1293FF for <quic-issues@ietfa.amsl.com>; Fri, 16 Dec 2016 13:41:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.897
X-Spam-Level:
X-Spam-Status: No, score=-4.897 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-2.896, 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 I2NxRBR5dliF for <quic-issues@ietfa.amsl.com>; Fri, 16 Dec 2016 13:41:36 -0800 (PST)
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 83B81126CD8 for <quic-issues@ietf.org>; Fri, 16 Dec 2016 13:41:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=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=bjOtFFhb7/ALBQ/2KPnE4+kPWm4=; b=fRqQ3Om7PYLODLBG OZggy9mFWsJIMrEqEUMuR2TyGifHqk3QvwhQP6mors4FjAGjTKI5ioCyVBQdks+s lUshDuXiflHM/r28iCIdirS2avEKJIfPx3q5HbKm/SVNuxABjuDPbv0wpIID2zYI WVvgoat/nYako22Nj0NVlr06aOg=
Received: by filter0440p1mdw1.sendgrid.net with SMTP id filter0440p1mdw1-8327-58545F6D-39 2016-12-16 21:41:01.764481649 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id 7y4R-7lSTaqKSC4-Hi1Kqg for <quic-issues@ietf.org>; Fri, 16 Dec 2016 21:41:01.732 +0000 (UTC)
Date: Fri, 16 Dec 2016 13:41:01 -0800
From: Mike Bishop <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/87/267702530@github.com>
In-Reply-To: <quicwg/base-drafts/issues/87@github.com>
References: <quicwg/base-drafts/issues/87@github.com>
Subject: Re: [quicwg/base-drafts] QUIC advertisement description (#87)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58545f6d962c9_2c313fa5a0e79138283146"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak217W0TttBBtcP4VbamZiB4jxv5d+3tNhLI5I hLi1Iqf25KZcst3aaWB4KxDKcblzuKrRde0whKSbIP8zxPaihx8nhzsZhiog5vP25cYN2ADqV5V4tB pV4mSbjA00XokmkvFh4P0gDN0X9cfplOF92UAKo0LXCnDQgeHM0+XOD2Mjxm15L3XXA7qgEhBaVxLb k=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/eH3dq46idv9Wv0g4MysL5CulYT4>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quicwg/base-drafts <reply+0166e4ab5317bd162bedf30e0afbc53f21da89e780e1c53392cf00000001146c216d92a169ce0bafd3d6@reply.github.com>
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: Fri, 16 Dec 2016 21:41:38 -0000
Perhaps. Here's the thing: QUIC version and app-layer protocol aren't the same. So the question is whether there *needs* to be a hint from the application layer into QUIC's version negotiation about what versions the server supports.
Here are the paths I see that we need to support:
- **Client to server, first time**: This is inherently a 1-RTT handshake, so spending that same 1-RTT on version negotiation isn't a loss. However, if reuse of the TLS/TCP connection information is supported, this will likely never happen for an HTTP/2-to-QUIC transition.
- **Client to server, 0-RTT**: The cached information should contain information about the server's supported versions so the client can come back with the same version. The scenarios where one side has changed need consideration, though:
+ **Client upgraded:** This can be solved by caching the server's full set of supported versions and comparing against the client's supported set at connect time, not just caching the selected version.
+ **Server upgraded:** The current mechanism offers no way for a client to discover that the server *would have accepted* a version it didn't initially offer, whether because the server didn't previously support it or the client is being conservative. We should think about have a version-upgrade path as well.
Having a v= parameter in Alt-Svc *does* solve all of these. It gives a useful springboard if TLS allows 0-RTT using data obtained over TCP. The client will cache the list of supported versions with the Alt-Svc header and will learn about new ones when the Alt-Svc entry gets refreshed periodically.
Ideally, I'd like to see these solved for QUIC independent of HTTP, though -- if/when we manage that, the Alt-Svc parameter could become unnecessary.
--
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/87#issuecomment-267702530
- [quicwg/base-drafts] QUIC advertisement descripti… Lucas Pardue
- Re: [quicwg/base-drafts] QUIC advertisement descr… Mike Bishop
- Re: [quicwg/base-drafts] QUIC advertisement descr… Lucas Pardue
- Re: [quicwg/base-drafts] QUIC advertisement descr… Mike Bishop
- Re: [quicwg/base-drafts] QUIC advertisement descr… Mike Bishop
- Re: [quicwg/base-drafts] QUIC advertisement descr… Lucas Pardue
- Re: [quicwg/base-drafts] QUIC advertisement descr… Mike Bishop
- Re: [quicwg/base-drafts] QUIC advertisement descr… Mike Bishop
- Re: [quicwg/base-drafts] QUIC advertisement descr… Mike Bishop
- Re: [quicwg/base-drafts] QUIC advertisement descr… Lucas Pardue
- Re: [quicwg/base-drafts] QUIC advertisement descr… Mike Bishop
- Re: [quicwg/base-drafts] QUIC advertisement descr… Mike Bishop
- Re: [quicwg/base-drafts] QUIC advertisement descr… Mike Bishop