IETF Logo Mail Archive

Re: [quicwg/base-drafts] Clarify use of HTTP request with http scheme over HTTP/3 (#2439)

Mike Bishop <notifications@github.com> Fri, 08 February 2019 17:24 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 6642E128766 for <quic-issues@ietfa.amsl.com>; Fri, 8 Feb 2019 09:24:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level:
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 zIrf3SBk9O-h for <quic-issues@ietfa.amsl.com>; Fri, 8 Feb 2019 09:24:33 -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 468EF1200ED for <quic-issues@ietf.org>; Fri, 8 Feb 2019 09:24:33 -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=K2pi/MjsHPefr1/aBL8KmbQQIEE=; b=UXDJ8wQPE7pratYw ZCZrv9hoDmtNPkucX9ImtcNGci5y+pqdQMsO8PQRar9+VJ56ddHnmctlVWtul4cI RCQTXge/l7ZOBCuNUyaq8QJLCnP1wvCXX31AMBPP6G/LrW2yEnvmeWbYzNpmYFVx ogS1DY0zDEJn2xnO4yefF3mEcU0=
Received: by filter1189p1las1.sendgrid.net with SMTP id filter1189p1las1-17379-5C5DBB4E-24 2019-02-08 17:24:30.992392022 +0000 UTC m=+1875.462459637
Received: from github-lowworker-05ceafd.cp1-iad.github.net (unknown [192.30.252.40]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id Xlg_rmPGSlWgKH2CyS0pjQ for <quic-issues@ietf.org>; Fri, 08 Feb 2019 17:24:30.880 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-05ceafd.cp1-iad.github.net (Postfix) with ESMTP id D464D4603EC for <quic-issues@ietf.org>; Fri, 8 Feb 2019 09:24:30 -0800 (PST)
Date: Fri, 08 Feb 2019 17:24:31 +0000
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb7b601f6594a8494efe5073143ed23d653ad370a92cf0000000118757d4e92a169ce1854ec6b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2439/461879685@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2439@github.com>
References: <quicwg/base-drafts/issues/2439@github.com>
Subject: Re: [quicwg/base-drafts] Clarify use of HTTP request with http scheme over HTTP/3 (#2439)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5dbb4ed3001_52333fcc336d45b826526d"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0RIgxhGlrc9Hx5fsPNVkt5jjCHTNjnNA3/83 POfmrg/GqPECcqyqVb5LoHdw/dHtmsn2xx7ueErOdpErH3iwrrhdwHj+mDZdMypy6rCiLmWYpURDLg H8ag5JGve1rBhx/eVHfkqLHWIURB3mek9Hei9AakafsLC/4oS4H7Pp19M5BgqmEOjkXJuuMv5+9Y7g k=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/M55nnLpyjHs2OQDvn4y7l5cf4vU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Feb 2019 17:24:35 -0000

This is another variant of #253 -- HTTP/2 and HTTP/3 explicitly include the scheme and the authority with all requests, so the server knows what it's being asked for.  The question is how the client decides that a QUIC endpoint is authoritative for this particular URL.

RFC 7838 describes how an https://-schemed request might come to be sent to an HTTP/3 endpoint and the resolution of the issue was to ask the HTTP WG to define other ways.  Adding RFC 8164 as well, an http://-schemed resource might also be requested over HTTP/3; it's up to the HTTPbis group whether they want to enable a direct upgrade there as well.

I don't currently see any text required for this, but if you have suggestions, I'm happy to review or expand the discussion to the list.

-- 
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/2439#issuecomment-461879685

v2.23.0 | Report a Bug | By Email