[Starlink] Re: Starlink Digest, Vol 53, Issue 14

[Michael Richardson <mcr@sandelman.ca>]

David Fernández via Starlink wrote:
    > I understand that SCONE info about maximum possible bandwidth (bottleneck
    > maximum possible bandwidth, not zero, of course) available on the path
    > between a QUIC client and server is not to define a steady state (although
    > it could be), but may be better used to set the size of the initial burst
    > of packets after a connection is established, during the slow start phase,
    > to a value that can be more optimal than just a fixed value like 10 (RFC
    > 6928), which was updated as networks became faster (with more
    > capacity).

No, that's not the goal as I understand it.
It's to tell the client that asking for 4K video is not going to work.
Yes, it might be able to get an initial few seconds of 4K, but then the burst
tolerances (token buckets, etc.) of the network will be exhausted, and the 4K
will begin to fail.
The video will then pause/skip/.. and the client will go back to 2K.
Lather. Rinse. Repeat.

    > The advantage of QUIC vs. TCP for web browsing should be an increased
    > interactivity, less RTTs to do connections, more responsiveness of sites,
    > less lag and latency, although it seems people is not really noticing the
    > difference after sites start using HTTP/3 vs. HTTP/2.

Probably the most important thing is that it gets rid of head of queue blocking.

    > For example, today, the following site was reported as recently starting
    > using HTTP/3:
    > Pokemon.com (https://w3techs.com/sites/info/pokemon.com)

    > If anybody made a survey to usual Pokemon site visitors, I wonder if they
    > noticed that change.

When I think about QUIC, I think about PsyDuck for some reason.
When I think about TCP, I think about JigglyPuff.
Or maybe Kirby (not a pokemon).
And, when I think about UUCP, I think about Thomas the Tank Engine.
Yes, I was a parent over the last 20 years.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [