IETF Logo Mail Archive

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

Lucas Pardue <notifications@github.com> Wed, 08 February 2017 01: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 108891296F4 for <quic-issues@ietfa.amsl.com>; Tue, 7 Feb 2017 17:04:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.187
X-Spam-Level:
X-Spam-Status: No, score=-6.187 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-1.887, RP_MATCHES_RCVD=-0.001, 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 zzxepsHf4VOJ for <quic-issues@ietfa.amsl.com>; Tue, 7 Feb 2017 17:04:26 -0800 (PST)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 4B780129431 for <quic-issues@ietf.org>; Tue, 7 Feb 2017 17:04:26 -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=vKt8J1N+jam39ehLmH+j46+HU/I=; b=YIpjyWtM1cj64sq6 M+OlfcNDNo/4e881K9hdNhs74EwBAftmIoS8vsrZt0xlh5JazC+gu6oqEQ6byOBl L0ri/cknLXrAs0ekRP+vmjEpV6zp9sDIIH8kV/MaUjl/jDBysHbiyjwHKzPMA4U6 Ti0+FJszLOmw+/KJzhd9PvFwcus=
Received: by filter0962p1mdw1.sendgrid.net with SMTP id filter0962p1mdw1-2888-589A6E99-4 2017-02-08 01:04:25.032820276 +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 mUFcqHiLRcOVWKcXyaxh5g for <quic-issues@ietf.org>; Wed, 08 Feb 2017 01:04:25.045 +0000 (UTC)
Date: Tue, 07 Feb 2017 17:04:24 -0800
From: Lucas Pardue <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/253/278196644@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_589a6e98e79b1_61923fac921a314013169c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1PZ6rCD5SmUNU02dmFcqHkQGdYgb21aEIeyj Jz+db3meeovooVWbE+eVdsewSpU/taDixUAfJ162fIu9cf6qZu88jxPhawgctXSDi7WlTabPjX6ecF Yte8br/XO0IAYV6exwrrenIZGSrcjGbXZ/PMrKyqHf19P3Idw1qgZ0UHt8G1k6JPjVX7kH1e9S+Htf 8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/bCnL47fNTwsAMTCNMenew0dyYpU>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
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: Wed, 08 Feb 2017 01:04:29 -0000

Ah so I understand better that there's a slight dichotomy here. If a client
is configured to use an HTTPS proxy, and an origin advertises "hq" what
proxy should the client use? I don't think it's fair to assume that a
single proxy application has to support HTTPS and HTTP/QUIC.

If an HTTPS proxy were to offer an alt-svc itself that points to a
standalone HTTP/QUIC-only proxy, then does that upset things when the
client comes to try an access a new origin with a https scheme?

I think this is channeling some of McManus' earlier comments. If this is
repeating discussion of that old proxy thread then apologies, I'll do some
more background reading.


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

v2.23.0 | Report a Bug | By Email