From: Michael Richardson <mcr@sandelman.ca>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Global CDN Services Market About $5B in 2023, Expected To Grow 3%
Date: Fri, 12 Jul 2024 19:41:28 -0400 [thread overview]
Message-ID: <17937.1720827688@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAJUtOOi6riQecLShaaDpss93k+oAwpu+izA=ySOyGQ3pzRCD-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
Lower latency for video demand means that I can stop/rewind/scroll with less
annoyance. We saw this in the demos that showed up at IETF hackathons a few
years ago.
Customers are *not* demanding that, because:
a) they don't know it's about latency.
b) the end users experience the pain, not the netflix/disney+/etc. people
c) it's hard for CDN people to actually do anything about last-mile bloat.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
prev parent reply other threads:[~2024-07-12 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 10:31 Frantisek Borsik
2024-07-12 10:48 ` Sebastian Moeller
2024-07-12 13:21 ` Livingood, Jason
2024-07-12 23:41 ` Michael Richardson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17937.1720827688@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox