From: Michael Richardson <mcr@sandelman.ca>
To: =?UTF-8?Q?Bj=C3=B8rn_Ivar_Teigen?= <bjorn@domos.no>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] PhD thesis with results related to buffering needs on variable-capacity links
Date: Tue, 03 Jan 2023 10:08:03 -0500 [thread overview]
Message-ID: <27202.1672758483@localhost> (raw)
In-Reply-To: <CAKf5G6+fw+ksxPJJkS1kegjeUZqHWYmBTZHt3Yw-nOSzPc0Eww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Thank you for sharing your thesis!
Bjørn Ivar Teigen via Bloat wrote:
> The thesis begins by investigating which performance issues are most
> prevalent in today's WiFi networks. We show that both queuing latency
> and the WiFi protocol specification itself are significant
> contributors. By building a model of the WiFi protocol behavior we
> quantify the performance of the protocol in terms of quality
> attenuation. We find that significant performance variability is an
> inherent consequence of the protocol design.
I guess that your thesis is mostly technical.
(I haven't clicked on the link yet)
I wonder if there is work that might occur from the business department end
of things. Why do we have 15 years of WiFi optimization, which seem to be
taking us further away from low latency. Are the new protocols actually
improving the situation for the end consumer? My impression is no.
Nobody notices because the quality is so unpredictable.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2023-01-03 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 9:57 Bjørn Ivar Teigen
2023-01-03 15:08 ` Michael Richardson [this message]
2023-01-03 16:41 ` Bjørn Ivar Teigen
2023-01-04 7:08 ` Taraldsen Erik
2023-01-03 23:52 ` Toke Høiland-Jørgensen
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=27202.1672758483@localhost \
--to=mcr@sandelman.ca \
--cc=bjorn@domos.no \
--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