From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Fwd: Starlink routing
Date: Mon, 23 Jan 2023 02:29:19 -0800 [thread overview]
Message-ID: <CAA93jw5f2b7DpzhbokGqq=zudg9z3sPAGmD_=-E21LnhyGO_vQ@mail.gmail.com> (raw)
In-Reply-To: <8812ae58-d5bf-1b6a-e176-4ef81ddf595d@efes.iucc.ac.il>
Low-Power SDR Design on an FPGA for Inter-Satellite Communications:
https://ieeexplore.ieee.org/ielaam/92/8502886/8412572-aam.pdf
Also good thread on nanog:
---------- Forwarded message ---------
From: Hank Nussbacher <hank@efes.iucc.ac.il>
Date: Sun, Jan 22, 2023 at 10:12 PM
Subject: Re: Starlink routing
To: <nanog@nanog.org>
On 23/01/2023 0:42, Michael Thomas wrote:
> I read in the Economist that the gen of starlink satellites will have
> the ability to route messages between each satellite. Would
> conventional routing protocols be up to such a challenge? Or would it
> have to be custom made for that problem? And since a lot of companies
> and countries are getting on that action, it seems like fertile ground
> for (bad) wheel reinvention?
>
> Mike
>
For further reading try:
https://www.internetsociety.org/wp-content/uploads/2022/11/Perspectives-on-LEO-Satellites.pdf
-Hank
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2023-01-23 10:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8812ae58-d5bf-1b6a-e176-4ef81ddf595d@efes.iucc.ac.il>]
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='CAA93jw5f2b7DpzhbokGqq=zudg9z3sPAGmD_=-E21LnhyGO_vQ@mail.gmail.com' \
--to=dave.taht@gmail.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