W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2013

Re: [tsvwg] The List (of application-layer desired features)

From: Michael Welzl <michawe@ifi.uio.no>
Date: Thu, 5 Sep 2013 10:22:29 +0200
Cc: Roberto Peon <grmocg@gmail.com>, tsvwg@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>, Joe Touch <touch@isi.edu>
Message-Id: <BA5B0AA8-D99F-4150-924F-6985D90B042F@ifi.uio.no>
To: Yuchung Cheng <ycheng@google.com>

> There is an old work called congestion manager but it's not useful b/c
> it's sender based.

Why does that make it useless? What's missing - isn't it just client=>server signaling of: "I assume the bottleneck is my access link, so I'll tell you which flows belong together, and I'll tell you my priorities"?
But - if you knew which flows share a bottleneck, part #1 would be unnecessary, and then I'm not so sure if you need the client to tell the server about priorities, wouldn't the server know better?


PS: this makes me wonder about the GreatSnipe congestion manager you once presented in ICCRG - any news about that? Is it going to be a part of QUIC? I think it's very interesting work.
Received on Thursday, 5 September 2013 08:22:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:15 UTC