Re: [quicwg/base-drafts] HTTP/QUIC without Alt-Svc? (#253)

Erik Nygren <notifications@github.com> Fri, 31 March 2017 15:56 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 8563D12952C for <quic-issues@ietfa.amsl.com>; Fri, 31 Mar 2017 08:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.294
X-Spam-Level:
X-Spam-Status: No, score=-9.294 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_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, 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 y6ZMiRyo5lEk for <quic-issues@ietfa.amsl.com>; Fri, 31 Mar 2017 08:56:50 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext6.iad.github.net [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2B571294DF for <quic-issues@ietf.org>; Fri, 31 Mar 2017 08:56:49 -0700 (PDT)
Date: Fri, 31 Mar 2017 08:56:49 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490975809; bh=3K4kPHZoXHZyOB+t7gB0JUC1Yrhi8wjM++3lNqAHuvk=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=T/UOIG3mt3uc7NF1n/Xa6coPKrdTCzXVnkGWLpY15mKty+1TOEbavx/BBt3FNNdca ANUGK2608hMvhLgoV6FrjWKdF0Kdmn1De7CVo8UYQT+GqY0iQknNhpmlMZSc7lepMX W3RefT7Z3isegNY05BkYdY5Xry71iM60sI+ctZVI=
From: Erik Nygren <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab705cd4444803743bea0a6ec49c5c1b0ac9d68a6a92cf0000000114f63e4192a169ce0c2f403e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/253/290752706@github.com>
In-Reply-To: <quicwg/base-drafts/issues/253@github.com>
References: <quicwg/base-drafts/issues/253@github.com>
Subject: Re: [quicwg/base-drafts] HTTP/QUIC without Alt-Svc? (#253)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58de7c414748_30533fc1ba7d5c38138275"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: enygren
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/Y3oW7CvP5mA9VUq1RFptQhDZqKY>
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: Fri, 31 Mar 2017 15:56:51 -0000

What about extending the HTTP URI syntax in a way to give connection hints?
For example (very likely not the right syntax):

      https://www.example.com#svc=hq.443/

Where in the above example, the Origin (and thus host header and SNI) would come from the part before the "#".  On failure to connect, a TCP connect (ie without the hint) could also be used.  Cache entries would not include the part following the # as part of the cache key.

This is a variant of option 2, but with the difference that the Origin and object cache keys aren't impacted.  This is only appropriate for secured connections (eg, TLS / HTTPS).

-- 
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/253#issuecomment-290752706