From: Leonard Kleinrock <lk@cs.ucla.edu>
To: James Hurley <jamesghurley@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>, Vasu Kaker <vasuk@mit.edu>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
starlink@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>,
Josh Mermel <joshmermel@gmail.com>,
Jamie Tucker-Foltz <jtuckerfoltz@gmail.com>,
"Yao, Lisa (US)" <LYao@ttivanguard.com>
Subject: Re: [Bloat] [Starlink] [Make-wifi-fast] Talk now up: How the internet really works
Date: Thu, 10 Mar 2022 10:57:24 -0800 (PST) [thread overview]
Message-ID: <ADEB3ACC-8812-489A-A24C-AAD4B452ECCE@cs.ucla.edu> (raw)
In-Reply-To: <3404DB00-7F01-409A-A9CE-DC889E05EAB9@gmail.com>
Let me add that Dave’s presentation was amazing and so beautifully done. As with all his other works, he put in a great deal of effort and thinking. Well done Dave.
Len
Sent from my iPhone
> On Mar 10, 2022, at 6:25 AM, James Hurley <jamesghurley@gmail.com> wrote:
>
> Great talk Dave & MIT jugglers
>
> Dave is there any chance you can share the slides you were presenting in the video?
>
>> On 8 Mar 2022, at 16:07, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> My talk last week at TTI Vanguard is now up on youtube. I used no
>> slides, and a bunch of new simple analogies (including the world's
>> most elaborate "rickroll"!) to explain the problems videoconferencing
>> and voice have with competing with web traffic, with bits about
>> cryptography, packet loss, bufferbloat, fair queueing and active queue
>> management across all our access technologies today, as well as some
>> notes as to the NTIA broadband programs and ongoing FCC measurements.
>>
>> https://www.youtube.com/watch?v=TWViGcBlnm0
>>
>> My special thanks to Len and Nancy Kleinrock, and to Lisa Yao, CEO of
>> TTI Vanguard, for sponsoring my talk and travel. Plug: There were a
>> bunch of very interesting other talks at that conference (including
>> one amazing one on quantum computing that went over my head
>> completely) that I enjoyed greatly. A huge thx also to my volunteers,
>> Jamie, Vasu, and Joshua, who went the extra mile to help out.
>>
>> I am of course trying to reach new audiences outside our circle with
>> my talk, please reshare widely?
>>
>> --
>> I tried to build a better future, a few times:
>> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>>
>> Dave Täht CEO, TekLibre, LLC
>> _______________________________________________
>> Make-wifi-fast mailing list
>> Make-wifi-fast@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2022-03-10 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 15:07 [Bloat] " Dave Taht
2022-03-08 16:24 ` [Bloat] [EXT] " Yao, Lisa (US)
2022-03-10 3:50 ` Joshua Mermelstein
2022-03-10 14:08 ` [Bloat] [Make-wifi-fast] " James Hurley
2022-03-10 18:57 ` Leonard Kleinrock [this message]
2022-03-11 1:19 ` [Bloat] [Starlink] " Vint Cerf
2022-03-11 15:51 ` Dave Taht
2022-03-11 16:38 ` Rich Brown
2022-03-11 17:37 ` [Bloat] [EXT] " Yao, Lisa (US)
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=ADEB3ACC-8812-489A-A24C-AAD4B452ECCE@cs.ucla.edu \
--to=lk@cs.ucla.edu \
--cc=LYao@ttivanguard.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=jamesghurley@gmail.com \
--cc=joshmermel@gmail.com \
--cc=jtuckerfoltz@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=starlink@lists.bufferbloat.net \
--cc=vasuk@mit.edu \
/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