From: Michael Richardson <mcr@sandelman.ca>
To: =?UTF-8?Q?David_Fern=C3=A1ndez?= <davidfdzp@gmail.com>,
"Vint Cerf" <vint@google.com>
Cc: starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] The "reasons" that bufferbloat isn't a problem
Date: Thu, 06 Jun 2024 13:12:43 -0400 [thread overview]
Message-ID: <31302.1717693963@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAHxHggch0QjVzQhgdastjBTw3_78DdEqC-ug7iqE81sJiQphaw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Vint Cerf via Starlink <starlink@lists.bufferbloat.net> wrote:
> I hope you all realize that quantum entanglement does NOT facilitate
> FTL communication.
I got a book last month for my birthday:
https://app.thestorygraph.com/books/99c04ecc-8cda-44ea-addf-1b19cd934ab8
Black Holes, by Brian Cox, Jeff Forshaw. It's very good.
The style reminds me greatly of a book a read as a pre-teen:
Dancing Wu Li Masters: An Overview of the New Physics, Gary Zukav
which eventually led me to a degree in physics.
I didn't know about Penrose Diagram's
https://en.wikipedia.org/wiki/Penrose_diagram
until this book. The book explains quite clearly why entanglement can't be
used for communication.
At one point, when we were trying to mix DNSSEC and IPsec in FreeS/SWAN's
opportunistic encryption, we realized that DNS record (changes) propogate with a kind
of maximum speed, akin to a speed of TTL. But, IPsec IKE connections are a
bit like workholes, and if they beat the DNS change across the Internet, then
things can fail. Alas, my wormhole explanation fell flat.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2024-06-06 17:12 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 14:46 David Fernández
2024-06-05 14:57 ` Vint Cerf
2024-06-06 17:12 ` Michael Richardson [this message]
2024-06-06 10:18 ` Alexandre Petrescu
2024-06-06 10:37 ` Aidan Van Dyk
2024-06-06 10:33 ` Alexandre Petrescu
-- strict thread matches above, loose matches on Subject: below --
2024-06-07 7:36 David Fernández
2024-06-05 15:16 David Fernández
2024-06-05 15:21 ` Bless, Roland (TM)
2024-06-05 15:32 ` David Fernández
2024-06-05 16:24 ` Sebastian Moeller
2024-06-06 23:10 ` Michael Richardson
2024-06-07 1:39 ` David Lang
2024-06-07 6:20 ` Sebastian Moeller
2024-06-07 17:41 ` Eugene Y Chang
2024-06-07 17:51 ` David Lang
2024-06-07 20:09 ` Eugene Y Chang
2024-06-08 1:53 ` David Lang
2024-06-05 16:23 ` Sebastian Moeller
2024-06-06 7:07 ` David Fernández
2024-06-06 7:41 ` Sebastian Moeller
2024-05-08 9:31 David Fernández
2024-05-07 12:13 David Fernández
2024-05-07 12:46 ` Dave Collier-Brown
2024-05-07 19:09 ` Eugene Y Chang
2024-05-07 19:11 ` Dave Taht
2024-05-07 19:14 ` Jeremy Austin
2024-05-07 19:46 ` Dave Taht
2024-05-07 20:03 ` Eugene Y Chang
2024-05-07 20:05 ` Frantisek Borsik
2024-05-07 20:25 ` Eugene Y Chang
[not found] <mailman.2773.1714488060.1074.starlink@lists.bufferbloat.net>
2024-04-30 18:05 ` [Starlink] It’s the Latency, FCC Colin_Higbie
2024-04-30 19:04 ` Eugene Y Chang
2024-05-01 0:36 ` David Lang
2024-05-01 1:30 ` [Starlink] Itʼs " Eugene Y Chang
2024-05-01 1:52 ` Jim Forster
2024-05-01 3:59 ` Eugene Y Chang
2024-05-01 4:12 ` David Lang
2024-05-01 18:51 ` Eugene Y Chang
2024-05-01 19:18 ` David Lang
2024-05-01 21:12 ` Eugene Y Chang
2024-05-01 21:27 ` Sebastian Moeller
2024-05-01 22:19 ` Eugene Y Chang
2024-05-06 11:25 ` [Starlink] The "reasons" that bufferbloat isn't a problem Rich Brown
2024-05-06 12:11 ` Dave Collier-Brown
2024-05-07 0:43 ` Eugene Y Chang
2024-05-07 12:05 ` Dave Collier-Brown
[not found] ` <CAJUtOOhH3oPDCyo=mk=kwzm5DiFp7OZPiFu+0MzajTQqps==_g@mail.gmail.com>
2024-05-06 19:47 ` Rich Brown
2024-05-07 0:38 ` Eugene Y Chang
2024-05-07 10:50 ` Rich Brown
2024-05-08 1:48 ` Dave Taht
2024-05-08 7:58 ` Frantisek Borsik
2024-05-08 8:01 ` Frantisek Borsik
2024-05-08 18:29 ` Eugene Y Chang
2024-06-04 18:19 ` Stuart Cheshire
2024-06-04 20:06 ` Sauli Kiviranta
2024-06-04 20:58 ` Eugene Y Chang
2024-06-05 11:36 ` Alexandre Petrescu
2024-06-05 13:08 ` Aidan Van Dyk
2024-06-05 13:28 ` Alexandre Petrescu
2024-06-05 13:40 ` Gert Doering
2024-06-05 13:43 ` Alexandre Petrescu
2024-06-05 14:16 ` David Lang
2024-06-05 15:10 ` Sebastian Moeller
2024-06-05 16:21 ` Alexandre Petrescu
2024-06-05 19:17 ` Eugene Y Chang
2024-06-04 23:03 ` Rich Brown
2024-06-06 17:51 ` Stuart Cheshire
2024-06-07 2:28 ` Dave Taht
2024-06-07 5:36 ` Sebastian Moeller
2024-06-07 7:51 ` Gert Doering
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31302.1717693963@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=davidfdzp@gmail.com \
--cc=starlink@lists.bufferbloat.net \
--cc=vint@google.com \
/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