[quicwg/base-drafts] Coalescing in HTTP/QUIC (#940)
Mike Bishop <notifications@github.com> Thu, 16 November 2017 23:48 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 33EDB12708C for <quic-issues@ietfa.amsl.com>; Thu, 16 Nov 2017 15:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 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_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 CAf6ZzuFVUn9 for <quic-issues@ietfa.amsl.com>; Thu, 16 Nov 2017 15:48:51 -0800 (PST)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 44C70124B09 for <quic-issues@ietf.org>; Thu, 16 Nov 2017 15:48:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=j240N7P0XrO1XgBZ45xy0lanEJw=; b=WToHWStg4N8Ws1BX z+EYIQuOxy/W9XJjPrzvcCRuZbjwLsAwefYyhUMYK3UDpBFDaPW/COUkUVJjDycA 7wxB4ttbCVhaPFknrPPwRr5ZXGsOMsF0cvN99bdg7KeZVmI8MDBLPyLCYBHdNzQ7 Bcl7mA2sCwev/IIwh6R9IeafSKI=
Received: by filter0359p1iad2.sendgrid.net with SMTP id filter0359p1iad2-9409-5A0E23E2-2 2017-11-16 23:48:50.122028662 +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 ismtpd0009p1iad1.sendgrid.net (SG) with ESMTP id 0oDgbXFnTGe5Jrf3zmAGig for <quic-issues@ietf.org>; Thu, 16 Nov 2017 23:48:49.925 +0000 (UTC)
Date: Thu, 16 Nov 2017 23:48:50 +0000
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbf059e4efae8f7c8dcfaf81c3d303f9129f60a9492cf000000011625e5e192a169ce105fa92a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/940@github.com>
Subject: [quicwg/base-drafts] Coalescing in HTTP/QUIC (#940)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a0e23e1cd41e_7d7a3f9bc058ef3064524"; 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
tracking:
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2+EBvq8L1M7yOBLQJAaqyadDlh0DyF4HjhCY lXCjq7pmYYkJxMpj8XeDxVxiFbgm8jgv72f6u4N15RG9rEJP4hljWHmED0oaKQOtIERubpCM1ba3gc 28dVJmsluWNL/kH+70Dhx91zkU+0XXs7xQI+shcFnJL/QKIBnw1Pgdlkreiujd3FOCTl58LahxATBt Q=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/gtUQidc3t2Syj9JDG49DyCGR8qE>
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: Thu, 16 Nov 2017 23:48:53 -0000
As @LPardue notes, the draft currently omits any language about connection reuse. We'll need text for that. As a first pass, note that there is no way to directly address an HTTP/QUIC endpoint by URI/URL. So an HTTP/QUIC endpoint is somewhat analogous to an HTTP/2 endpoint for an origin which doesn’t appear in the DNS record. With that as our starting point, here are some thoughts: - The only reason you’re speaking HTTP/QUIC for example.com in the first place is because you have an Alt-Svc record for example.com. If you have Alt-Svc records for other origins that happen to share the same certificate pointing to the same host:port, this should be coalesced. - It seems a pity that you would need to speak individually to each origin for this. Coincidentally, Ben Schwartz and I were having a conversation about reviving Alt-Svc records in DNS…. - In the absence of Alt-Svc records, draft-ietf-httpbis-origin-frame permits coalescing in HTTP/2 based on the combination of the server’s possession of the correct certificate and assertion that it wants the traffic. Like #371, there would need to be a very short draft that defines the ORIGIN frame for HTTP/QUIC as Exceptionally Similar™ to the one in draft-ietf-httpbis-origin-frame. -- 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/940
- [quicwg/base-drafts] Coalescing in HTTP/QUIC (#94… Mike Bishop
- Re: [quicwg/base-drafts] Coalescing in HTTP/QUIC … Lucas Pardue
- Re: [quicwg/base-drafts] Coalescing in HTTP/QUIC … Mike Bishop