From: Jack Haverty <jack@3kitty.org>
To: nnagain@lists.bufferbloat.net
Subject: Re: [NNagain] The FCC 2024 Section 706 Report, GN Docket No. 22-270 is out!
Date: Mon, 26 Feb 2024 11:24:28 -0800 [thread overview]
Message-ID: <98a6dfd6-3731-4a33-8a84-76696813fd74@3kitty.org> (raw)
In-Reply-To: <CAA93jw5vN73pH9VOfxN1n8ciAjExo+9nfOzGJpS1uK9G9mWyWQ@mail.gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1795 bytes --]
On 2/26/24 07:06, Dave Taht via Nnagain wrote:
> I wish we could do a live demonstration on
> television
It's been years, but when I talked with non-techie people to help them
understand the difference between bandwidth and latency I used a
familiar human-human task to get the ideas across. E.g., take a group
of people at the end of a work session, who are trying to reach a
consensus about where to go for lunch. When everyone's sitting around a
table, a quick discussion can happen and a decision reached. Then make
them all go to separate offices scattered around the building and
achieve a similar consensus, communicating only by sending short notes
to each other carried by volunteer couriers (or perhaps 140-character
SMS texts). The difference in "latency" and its effect on the time it
takes to finish the task becomes clear quickly.
It seems like one could orchestrate a similar demonstration targetted
toward a non-technical audience -- e.g., members of some government
committee meeting in a room versus the same meeting with participants
scattered across the building and interactions performed by staffers
running around as "the network". Even if the staffers can convey huge
stacks of information (high bandwidth), the time it takes for them to
get from one member to others (latency) quickly becomes the primary
constraint.
This was also a good way to illustrate to non-techies how web pages
work, and why it sometimes takes a long time to get the entire page
loaded. Go to the library to get the text. Now go to the art
department to get the banners. Now go to the photo archives to get the
pictures. Now go to that customer to get the ads you promised to
show. .....
Jack Haverty
[-- Attachment #1.1.1.2: Type: text/html, Size: 2237 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2469 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
next prev parent reply other threads:[~2024-02-26 19:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 15:06 Dave Taht
2024-02-26 19:24 ` Jack Haverty [this message]
2024-02-26 20:02 ` [NNagain] [M-Lab-Discuss] " rjmcmahon
2024-02-26 20:59 ` Jack Haverty
2024-02-27 0:25 ` rjmcmahon
2024-02-27 2:06 ` Jack Haverty
2024-02-27 17:48 ` rjmcmahon
2024-02-27 20:11 ` Jack Haverty
[not found] ` <223D4AB0-DBA9-4DF2-AEEE-876C7B994E89@gmx.de>
2024-02-27 21:16 ` Jack Haverty
2024-02-27 21:29 ` rjmcmahon
2024-02-28 19:11 ` Fenwick Mckelvey
2024-02-27 21:06 [NNagain] " Livingood, Jason
2024-02-27 22:00 ` rjmcmahon
2024-02-27 23:17 ` Jack Haverty
2024-02-27 23:41 ` Jeremy Austin
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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=98a6dfd6-3731-4a33-8a84-76696813fd74@3kitty.org \
--to=jack@3kitty.org \
--cc=nnagain@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