- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Wed, 11 Jul 2018 14:40:29 +1000
- To: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
- Cc: Benjamin Schwartz <bemasc@google.com>, Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>, HTTP Working Group <ietf-http-wg@w3.org>
Not Lucas' main point, but... On Wed, Jul 11, 2018 at 2:15 PM Lucas Pardue <Lucas.Pardue@bbc.co.uk> wrote: > There seems no option for H2 connection coalescing in the above case, since the client is not responsible for performing DNS resolution but is responsible for creating the HTTP/2 over TLS session. The same applies for HTTP/QUIC session. If you take the rules from h2 directly, then yes, there is no option to coalesce, because the client remains ignorant of the DNS records that might point to the same IP address. However, the ORIGIN frame relieves the client of that constraint and would allow for coalescing in that case.
Received on Wednesday, 11 July 2018 04:41:04 UTC