Re: HTTP/2 and TCP CWND

["Simpson, Robby (GE Energy Management)" <[e-mail]>]

It appears to me that the chief concern is in regards to HTTP/2's use of a
single flow vs. HTTP/1's use of multiple flows.  I fail to see how
changing CWND is going to make a difference (except for a beginning,
potentially nasty, burst) since, if the flows are sharing the same
end-to-end paths, they will still be competing and will steady-state to
"equal" CWND's.


Further, this is not specific to HTTP/2.  There are plenty of other
applications out there using TCP that have suffered from HTTP/1's use of
multiple simultaneous flows.  I fail to see how HTTP/2 is in a better
situation to correct that issue than any other application or, more
importantly, than the appropriate layer (4) or the offender (HTTP/1).

Am I missing something, or is the concern really that some folks are
looking for a way to throttle or compete with HTTP/1 flows?

- Robby