So, what do you think the latency (including bloat in the satellites) will be?
My guess is > 2000 msec, based on the experience with Apple on ATT Wireless
back when it was rolled out (at 10 am, in each of 5 cities I tested, repeatedly
with smokeping, for 24 hour periods, the ATT Wireless access
> On 11 Jun, 2020, at 7:03 pm, David P. Reed wrote:
>
> So, what do you think the latency (including bloat in the satellites) will
> be? My guess is > 2000 msec, based on the experience with Apple on ATT
> Wireless back when it was rolled out (at 10 am, in each of 5 cities I tested,
> repeated
On Thursday, June 11, 2020 12:14pm, "Jonathan Morton"
said:
> > On 11 Jun, 2020, at 7:03 pm, David P. Reed
> wrote:
> >
> > So, what do you think the latency (including bloat in the satellites) will
> be? My guess is > 2000 msec, based on the experience with Apple on ATT
> Wireless
> back w
On Thu, 11 Jun 2020, David P. Reed wrote:
But I doubt that is where they are going. Instead, I suspect they haven't
thought about anything other than a packet at a time, with no thought to
reporting congestion by drops or ECN.
And it's super easy to build up seconds of lag on TCP if you don't
On Thursday, June 11, 2020 2:56pm, "David Lang" said:
> We will see, but since the answer to satellite-satellite communication being
> the
> bottleneck is to launch more satellites, this boils down to investment vs
> service quality. Since they are making a big deal about the latency, I exp
On Thu, 11 Jun 2020, David P. Reed wrote:
On Thursday, June 11, 2020 2:56pm, "David Lang" said:
We will see, but since the answer to satellite-satellite communication being the
bottleneck is to launch more satellites, this boils down to investment vs
service quality. Since they are making a
--- Begin Message ---
the graph/bitmap it creates is actually quite terse but also useful at
the same time
how often does it probe? (i'm curious about the number of data-points
per pixel)
--- End Message ---
___
Bloat mailing list
Bloat@lists.bufferbloa
