On 21 Mar, 2011, at 12:18 am, da...@lang.hm wrote:
0) Buffering more than 1 second of data is always unacceptable.
what about satellite links? my understanding is that the four round trips to
geosync orbit (request up, down, reply up down) result in approximatly 1 sec
round trip.
That
On 03/21/2011 09:50, Dave Täht wrote:
[..]
We're not testing interplanetary networks here, (rather, an artificially
induced one extending out well beyond the moon!) but it bears a little
thinking about.
Perhaps an idea for presenting bufferbloat visually? Draw a picture of the
space
On 21 Mar, 2011, at 12:50 am, Dave Täht wrote:
0) Buffering more than 1 second of data is always unacceptable.
Well, in the case of the DTN, it's required.
We're not testing interplanetary networks here, (rather, an artificially
induced one extending out well beyond the moon!) but it
On 3/20/2011 9:28 PM, da...@lang.hm wrote:
On Mon, 21 Mar 2011, Jonathan Morton wrote:
On 21 Mar, 2011, at 12:18 am, da...@lang.hm wrote:
0) Buffering more than 1 second of data is always unacceptable.
what about satellite links? my understanding is that the four round
trips to geosync
On Mar 17, 2011, at 5:05 AM, Fred Baker wrote:
I'm very much in favor of ECN, which in all of the tests I have done has
proven very effective at limiting queues to the knee. I'm also in favor of
delay-based TCPs like CalTech FAST and the Hamilton and CAIA models; FAST
tunes to having a
Heretical question: Why must the congestion notification implemented as a
(distributed) function of the network itself, and take the reaction of the
end hosts into consideration. If the signaling would only indicate the local
congestion state, but then move the reaction to that into the end
On Wed, 2011-03-16 at 23:22 +0100, Richard Scheffenegger wrote:
Heretical question: Why must the congestion notification implemented as a
(distributed) function of the network itself, and take the reaction of the
end hosts into consideration. If the signaling would only indicate the local
Furthermore, I learned that a couple of 10G switch vendors are planning to
have up to 4 GB of buffer RAM in their next generation of switches. So we
are not talking about thousands of packets in the buffer, but of millions
of
packets (think of up to 400ms buffering if only a single
