RE: Submitted new I-D: Cache Digests for HTTP/2

I believe that Chrome and Firefox coalesce when DNS/SANs permit.  Edge/IE currently does not.

From: Alcides Viamontes E [mailto:alcidesv@zunzun.se]
Sent: Sunday, April 10, 2016 1:16 AM
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Kazuho Oku <kazuhooku@gmail.com>; HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: Submitted new I-D: Cache Digests for HTTP/2

Hello Martin,

We will take a closer look at this. But what is the state of coalescing regarding browser implementations?

On Fri, Apr 8, 2016 at 3:53 PM, Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.com>> wrote:
On 8 April 2016 at 10:44, Kazuho Oku <kazuhooku@gmail.com<mailto:kazuhooku@gmail.com>> wrote:
> So the question boils down to two.
>
> Q1. How many fresh resources exist per origin?

> Q2. What is the appropriate value for P?

I have some others:

What is the effect of connection coalescing on this? When coalescing,
Is a client better off sending a separate digest for each origin, or
is a single large blob better?