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

Mike Bishop <notifications@github.com> Wed, 01 February 2017 18:19 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 4619D129547 for <quic-issues@ietfa.amsl.com>; Wed, 1 Feb 2017 10:19:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.514
X-Spam-Level:
X-Spam-Status: No, score=-4.514 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, 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 WNwJFtvD4li9 for <quic-issues@ietfa.amsl.com>; Wed, 1 Feb 2017 10:19:18 -0800 (PST)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 339D9129543 for <quic-issues@ietf.org>; Wed, 1 Feb 2017 10:19:17 -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=En2nLTQYQ4LVJGIVgJ0w0IKYtRc=; b=pvuHmuyoSsjeboAo KToiDmqCbDcb/eykKUd0M45g/H+zAPAzKgiuiOdwEiJs2PQsDic48+QGS19GAK8Y 8+oSO4H2gwAjoZR2ihFdjC8Bi1/Fpu//fs/1x2xgVXdWGa9mmXuqvUwzjvLXzs65 dprXI1Bbr+tKr+EoBOT6Fgs1Kxs=
Received: by filter1080p1mdw1.sendgrid.net with SMTP id filter1080p1mdw1-29419-589226A4-35 2017-02-01 18:19:16.772111216 +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 ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id hiuMQswITEOP1O9iG1VJNA for <quic-issues@ietf.org>; Wed, 01 Feb 2017 18:19:16.727 +0000 (UTC)
Date: Wed, 01 Feb 2017 10:19:16 -0800
From: Mike Bishop <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/253/276736742@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_589226a49ae83_719b3fc37252f13c151931"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2niOZAaeQ7JB26QhnEMWJiMhKEgx+Z1ns/ML GlsCCvMMYIapN8eHEwfAk03ZkwtvvOKHN/Ywmkn4w5G4/zGJq0PNyX89lPuS8B7GCGJi1hBjRAJCD3 SNJEJcJ9Bf2Y9aaMaLnt08C32TlR+T45xXoYWCVFb2Fx0/E0lvnsJnQvb6dYh3PJYutDlMr/Gf2fLP 0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/gEXJm_FdsQ0UKHfTW6pzqpSU5hg>
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, 01 Feb 2017 18:19:21 -0000

Oh, and also in RFC 7230:

> Although HTTP is independent of the transport protocol, the "http"   scheme is specific to TCP-based services because the name delegation   process depends on TCP for establishing authority.  **An HTTP service   based on some other underlying connection protocol would presumably   be identified using a different URI scheme....**

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