From: Sebastian Moeller <moeller0@gmx.de>
To: Michael Richardson <mcr@sandelman.ca>
Cc: =?UTF-8?Q?David_Fern=C3=A1ndez?= <davidfdzp@gmail.com>,
starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink "beam spread"
Date: Fri, 2 Sep 2022 14:27:03 +0200 [thread overview]
Message-ID: <F27851A7-8523-4E17-8DA2-E11964EA9C0B@gmx.de> (raw)
In-Reply-To: <16193.1662062192@localhost>
Hi Michael
> On Sep 1, 2022, at 21:56, Michael Richardson via Starlink <starlink@lists.bufferbloat.net> wrote:
>
>
> David Fernández via Starlink wrote:
>> If Starlink satellites are processing IP packets, shouldn't them be
>> shown in traceroutes? They are not shown now, AFAIK.
>
> sadly, they aren't doing IP processing.
> I don't think that they ever will decide to for NIH reasons.
> I suspect that their SDN hardware probably can, and I think that SR6 is
> probably ideal for their use, but...
Why would SR6 be better than any other "underlay" encapsulation here, like MPLS or SR-MPLS? Naively put this seems to trade 4 byte per label with a full 40 byte IPv6 header plus 8 bytes plus 16 bytes per "label". Asking out of genuine curiosity what are those additional bytes in overhead actually buying (except the freedom from MPLS).
Regards
Sebastian
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2022-09-02 12:27 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 15:19 David Fernández
2022-09-01 16:33 ` Darrell Budic
2022-09-02 9:32 ` David Fernández
2022-09-01 19:56 ` Michael Richardson
2022-09-02 12:27 ` Sebastian Moeller [this message]
2022-09-02 18:34 ` Michael Richardson
2022-09-02 20:11 ` Sebastian Moeller
[not found] <mailman.800.1661972667.1281.starlink@lists.bufferbloat.net>
2022-08-31 19:51 ` David P. Reed
2022-08-31 20:28 ` David Lang
2022-08-31 21:17 ` David P. Reed
2022-08-31 21:33 ` David Lang
2022-09-01 7:05 ` Mike Puchol
2022-09-01 11:43 ` Ulrich Speidel
2022-09-01 8:09 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
2022-08-31 14:51 David Fernández
2022-08-31 18:09 ` Michael Richardson
2022-08-31 21:46 ` Ulrich Speidel
2022-08-31 23:44 ` Lin Han
2022-09-01 19:26 ` Dave Taht
2022-08-31 8:15 David Fernández
[not found] <mailman.3.1661875202.32670.starlink@lists.bufferbloat.net>
2022-08-30 16:53 ` David P. Reed
2022-08-30 17:32 ` Doc Searls
2022-08-30 20:09 ` Mike Puchol
2022-08-30 20:35 ` Daniel AJ Sokolov
2022-08-30 20:40 ` Mike Puchol
2022-08-30 21:09 ` David Lang
2022-08-30 21:01 ` David Lang
2022-08-30 22:07 ` Brandon Butterworth
2022-08-30 22:21 ` David Lang
2022-08-30 22:37 ` Brandon Butterworth
2022-08-30 23:07 ` David Lang
2022-08-30 23:45 ` Brandon Butterworth
2022-08-30 23:28 ` David P. Reed
2022-08-31 0:12 ` David Lang
2022-08-31 0:31 ` Dave Taht
2022-08-31 0:32 ` David P. Reed
2022-08-31 10:29 ` Dave Collier-Brown
2022-08-31 18:51 ` David Lang
2022-08-31 19:04 ` Dave Taht
2022-08-30 22:50 ` Ulrich Speidel
2022-08-30 23:13 ` David Lang
2022-08-31 0:46 ` tom
2022-08-31 0:58 ` Dave Taht
2022-08-31 7:36 ` Mike Puchol
2022-08-31 6:26 ` Sebastian Moeller
2022-08-31 7:25 ` Ulrich Speidel
2022-08-31 7:31 ` Hayden Simon
2022-08-31 7:33 ` David Lang
2022-08-31 9:59 ` Mike Puchol
2022-08-31 10:06 ` David Lang
2022-08-31 10:12 ` Mike Puchol
2022-08-31 17:52 ` Dick Roy
2022-08-31 13:41 ` Ulrich Speidel
2022-08-31 14:30 ` Mike Puchol
2022-08-31 21:44 ` Ulrich Speidel
2022-09-01 7:58 ` Sebastian Moeller
2022-09-01 11:38 ` Ulrich Speidel
2022-09-01 19:54 ` Michael Richardson
2022-09-01 21:08 ` tom
2022-09-02 7:52 ` Sebastian Moeller
2022-09-02 12:29 ` tom
2022-08-31 7:49 ` Sebastian Moeller
2022-08-31 9:25 ` Brandon Butterworth
2022-08-31 9:34 ` David Lang
2022-09-01 9:12 ` Brandon Butterworth
2022-08-31 14:52 ` 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=F27851A7-8523-4E17-8DA2-E11964EA9C0B@gmx.de \
--to=moeller0@gmx.de \
--cc=davidfdzp@gmail.com \
--cc=mcr@sandelman.ca \
--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