IETF Logo Mail Archive

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

Ryan Hamilton <notifications@github.com> Tue, 07 February 2017 01:47 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 A1684129569 for <quic-issues@ietfa.amsl.com>; Mon, 6 Feb 2017 17:47:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.569
X-Spam-Level:
X-Spam-Status: No, score=-4.569 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_24=1.618, 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, 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 OPEJQDY28DAs for <quic-issues@ietfa.amsl.com>; Mon, 6 Feb 2017 17:47:05 -0800 (PST)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 69D1F1294E2 for <quic-issues@ietf.org>; Mon, 6 Feb 2017 17:47:05 -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=zADiAxU6nzewlyfKdadl687uiT0=; b=DUSowFjwn68/w1AD RufrGoQgGWiSG0n6nIpQIr9jsHa/OEK+XMVmJN3zv6utnjJ+BgYdAUMnUTwken/k a6dNZ3fEugnDPaIZ3QTxRN+A6ZAHo3ebWr21Xh4rIlu8rvQsy3sQjI8c0a6Fc0rt JQddXd51/hswGqpf9SFiMyh54y0=
Received: by filter0531p1mdw1.sendgrid.net with SMTP id filter0531p1mdw1-23623-5899270D-4F 2017-02-07 01:46:53.318756628 +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 ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id DzWKR5ZuR-Snu9LVlB20cg for <quic-issues@ietf.org>; Tue, 07 Feb 2017 01:46:53.250 +0000 (UTC)
Date: Mon, 06 Feb 2017 17:46:53 -0800
From: Ryan Hamilton <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/253/277875585@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_5899270d1f789_3d123f8e0a683134159326"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: RyanAtGoogle
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0q5kmGYvd3hBI0wWmIpqmgKVBok6NYdF6zf2 CidG6FxrPEKVqIQvuwtsymQfQDT6YdH94IOwOkJNH3vhV+BEuS5yV0nEHuVtZSKsjYb9LJOEHZFy3M 8g+ZMbIlOQlUZzc8M8K7afzFLQKdZJVGPHOn6ufMbDWC6kgHVh77k7YhJQc7HNvX/QsFUaOY/C/uys 4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/-SW3BIB4-vjoz0TEXpxZOhZZ-sg>
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: Tue, 07 Feb 2017 01:47:07 -0000

One example of such an "authoritative endpoint is over QUIC" is a QUIC proxy. That is to say, a semantically "HTTP proxy' which one speaks to via QUIC. Chrome today, for example, can be configured to speak QUIC to a proxy by using the "scheme" "quic" in the proxy.pac function.

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

v2.23.0 | Report a Bug | By Email