Date: Mon, 11 Feb 2019 16:22:06 -0800
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab1a85fc07aae54283edea946296b977120824758892cf000000011879d3ae92a169ce1854ec6b@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/462552127@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_5c6211ae3f990_12f3fd95f0d45bc7487a1";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/MDlR8rPyxJj0BdVQv-LA3TaYaBA>


----==_mimepart_5c6211ae3f990_12f3fd95f0d45bc7487a1
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Perhaps "not very careful" was careful enough -- it says "such as HTTP/2," and mandates that the protocol needs a way to carry the scheme.  HTTP/3 does, so we're covered.  Do we think a reference to 8164 is warranted in the section about finding an HTTP/3 endpoint?

-- 
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-462552127
----==_mimepart_5c6211ae3f990_12f3fd95f0d45bc7487a1
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>Perhaps "not very careful" was careful enough -- it says "such as HTTP/2," and mandates that the protocol needs a way to carry the scheme.  HTTP/3 does, so we're covered.  Do we think a reference to 8164 is warranted in the section about finding an HTTP/3 endpoint?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/2439#issuecomment-462552127">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AWbkq-piUE05LKQd62nieWAxeNY9C2-zks5vMgkugaJpZM4awYUQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AWbkqxtFH2Yp-EWoPWVcOG7ZDeQ9L362ks5vMgkugaJpZM4awYUQ.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@MikeBishop in #2439: Perhaps \"not very careful\" was careful enough -- it says \"such as HTTP/2,\" and mandates that the protocol needs a way to carry the scheme.  HTTP/3 does, so we're covered.  Do we think a reference to 8164 is warranted in the section about finding an HTTP/3 endpoint?"}],"action":{"name":"View Issue","url":"https://github.com/quicwg/base-drafts/issues/2439#issuecomment-462552127"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2439#issuecomment-462552127",
"url": "https://github.com/quicwg/base-drafts/issues/2439#issuecomment-462552127",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5c6211ae3f990_12f3fd95f0d45bc7487a1--