Date: Fri, 08 Feb 2019 08:44:40 -0800
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abb66b67b9c7bc1ad79a497a9882a23bb0ef50bfd292cf00000001187573f892a169ce1854ec6b@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/461866344@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_5c5db1f886997_22543ffa67ad45c0198981";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/RxdjfbsoXOPu2wAitYJO68hMJSI>


----==_mimepart_5c5db1f886997_22543ffa67ad45c0198981
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I might propose this comes down to a discovery problem for the proxy. What method(s) do you envisage the proxy used to decide to make an HTTP/3 connection to the authorative server? This seems related to the discussion in HTTP WG - https://github.com/httpwg/http-core/issues/194

If Alt-Svc is being used, the flow might be that the proxy attempts to make a cleartext HTTP/1.1 connection to the authoritative server and does an upgrade, as described in RFC 7838, to HTTP/3. In which case I don't think any action is required. 

If the proxy wants to opportunistically upgrade via some happy eyeballs approach described on https://github.com/httpwg/http-core/issues/194, we might want to provide guidance that either 1) it shouldn't be done for client requests with http:// or 2) that it should always be done.

-- 
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-461866344
----==_mimepart_5c5db1f886997_22543ffa67ad45c0198981
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>I might propose this comes down to a discovery problem for the proxy. =
What method(s) do you envisage the proxy used to decide to make an HTTP/3=
 connection to the authorative server? This seems related to the discussi=
on in HTTP WG - <a class=3D"issue-link js-issue-link" data-error-text=3D"=
Failed to load issue title" data-id=3D"405100391" data-permission-text=3D=
"Issue title is private" data-url=3D"https://github.com/httpwg/http-core/=
issues/194" data-hovercard-type=3D"issue" data-hovercard-url=3D"/httpwg/h=
ttp-core/issues/194/hovercard" href=3D"https://github.com/httpwg/http-cor=
e/issues/194">httpwg/http-core#194</a></p>
<p>If Alt-Svc is being used, the flow might be that the proxy attempts to=
 make a cleartext HTTP/1.1 connection to the authoritative server and doe=
s an upgrade, as described in RFC 7838, to HTTP/3. In which case I don't =
think any action is required.</p>
<p>If the proxy wants to opportunistically upgrade via some happy eyeball=
s approach described on <a class=3D"issue-link js-issue-link" data-error-=
text=3D"Failed to load issue title" data-id=3D"405100391" data-permission=
-text=3D"Issue title is private" data-url=3D"https://github.com/httpwg/ht=
tp-core/issues/194" data-hovercard-type=3D"issue" data-hovercard-url=3D"/=
httpwg/http-core/issues/194/hovercard" href=3D"https://github.com/httpwg/=
http-core/issues/194">httpwg/http-core#194</a>, we might want to provide =
guidance that either 1) it shouldn't be done for client requests with htt=
p:// or 2) that it should always be done.</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/2439#issuecomment-461866344">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq39a=
3-C-4G0750DG8wuOKfZJiTNzks5vLal4gaJpZM4awYUQ">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq7JqVa8a2vaD4qoSdxBwT0QN=
iTtoks5vLal4gaJpZM4awYUQ.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"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":"http=
s://github.githubassets.com/images/email/message_cards/header.png","avata=
r_image_url":"https://github.githubassets.com/images/email/message_cards/=
avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/q=
uicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@=
LPardue in #2439: I might propose this comes down to a discovery problem =
for the proxy. What method(s) do you envisage the proxy used to decide to=
 make an HTTP/3 connection to the authorative server? This seems related =
to the discussion in HTTP WG - https://github.com/httpwg/http-core/issues=
/194\r\n\r\nIf Alt-Svc is being used, the flow might be that the proxy at=
tempts to make a cleartext HTTP/1.1 connection to the authoritative serve=
r and does an upgrade, as described in RFC 7838, to HTTP/3. In which case=
 I don't think any action is required. \r\n\r\nIf the proxy wants to oppo=
rtunistically upgrade via some happy eyeballs approach described on https=
://github.com/httpwg/http-core/issues/194, we might want to provide guida=
nce that either 1) it shouldn't be done for client requests with http:// =
or 2) that it should always be done."}],"action":{"name":"View Issue","ur=
l":"https://github.com/quicwg/base-drafts/issues/2439#issuecomment-461866=
344"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2439#issuecomment=
-461866344",
"url": "https://github.com/quicwg/base-drafts/issues/2439#issuecomment-46=
1866344",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c5db1f886997_22543ffa67ad45c0198981--