From: Dave Taht <dave.taht@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] The DoD "Transport Layer"
Date: Fri, 14 Oct 2022 12:31:35 -0700 [thread overview]
Message-ID: <CAA93jw4bZBDf3jJ-dboBbf9PS2TsYYJhW+myWHNUdOt7CJqWTw@mail.gmail.com> (raw)
In-Reply-To: <1665774889.392518761@apps.rackspace.com>
Dear David:
Would it cheer you up any to learn, that 15+ years after the debate
over UWB ended, that it's finally seeing FAR more
major uptake and reasonable standardization, and actual working chips?
It did me. I was pretty scarred by that mess also, and what was it?
the 272 notches the FCC demanded be cut out of it, which swamped
circuit design capabilities at the time... but not as bad as you.
I didn't know until recently that it had hit iphones in 2019. and was
part of the airtags, nor that the baseline latency on the things was
50us, with admittedly only a 1000 bit payload - Still crippled as to
distance, and total bandwidth to under 10mbits, but, power usage is
*amazing*.
https://en.wikipedia.org/wiki/Ultra-wideband
The SPARK chips in particular have a nice looking devkit.
Anyway... just as the swamp of ipx and non-interoperable email systems
finally died...
You can't in the end, keep a good idea down. Maybe on average it takes
25 years to settle on saner things.
... We have centuries to sort the solar system's internet out, and the more
we can do to convince the next generation as to the right principles
to apply to it, the better.
next prev parent reply other threads:[~2022-10-14 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1576.1665756002.1281.starlink@lists.bufferbloat.net>
2022-10-14 19:14 ` David P. Reed
2022-10-14 19:31 ` Dave Taht [this message]
[not found] <mailman.1586.1665775909.1281.starlink@lists.bufferbloat.net>
2022-10-14 20:14 ` David P. Reed
2022-10-15 17:33 ` Bruce Perens
2022-10-14 13:59 Dave Taht
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=CAA93jw4bZBDf3jJ-dboBbf9PS2TsYYJhW+myWHNUdOt7CJqWTw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=dpreed@deepplum.com \
--cc=starlink@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