From: Darrell Budic <budic@onholyground.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Starlink tidbits from NANOG
Date: Thu, 4 Nov 2021 10:26:50 -0500 [thread overview]
Message-ID: <7907F9D1-9511-4254-BD8F-701888EB6778@onholyground.com> (raw)
I was at NANOG in Minneapolis, and got a chance to ask a couple question of a Starlink Network Engineer who’s attending. I was already talking to him about Starlink’s network efforts (see below) but it was nice to meet in person. Don’t quote me on any of this, but here’s a few tidbits this list may appreciate:
- Starlink is expanding their own network operations, and is connecting to more IXPs. They were already on SIX in Seattle, have connected to DECIX NY, and are in the process of connecting to ChIX in Chicago. As I run ChIX, I had a good excuse to talk to them about other things. :) IXPs and their own networks are in the works for Europe and other areas as well.
- They have been obtaining more v4 addresses, but I don’t know if they have enough to not do CGNAT. I don't think they do yet, but it seems like it may be a long term target.
- v6 is deliberately not fully functional, but they know some of use are using it and it will eventually be fully activated. May be waiting on the regional connectivity, so will be intersting to see if changes for some areas and not others as they roll it out.
- They hate Google's outsourced NOC as much as the rest of us
- New ground stations with more capacity are coming (and will be upgrades). They are using waves back to regional DCs now, but will be moving to dark fiber over the next year or two
- the new satellites have more than 2 lasers, and there is enough capacity on them to do routing. no details on how or what protocols, alas
- new birds also have 2-3x more ku bandwidth than first gen
- new dishes are in the works, v4 coming with lower power use, more capacity, not round any more
- larger dishes coming for commercial apps
- as we know, they aren’t doing any AQM yet, but it sounds like it may be in the works and we may see it in new code in 4-6 months. Not my guys department, so no more details.
- it’s encrypted up and down. I didn’t know that yet, but I may have just missed it.
-Darrell
next reply other threads:[~2021-11-04 15:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 15:26 Darrell Budic [this message]
2021-11-04 16:21 ` Dave Taht
2021-11-04 16:46 ` Dave Taht
2021-11-04 17:11 ` Dave Taht
2021-11-05 1:30 ` Darrell Budic
2021-11-05 1:41 ` Darrell Budic
2021-11-05 1:46 ` Darrell Budic
2021-11-04 18:16 ` Michael Richardson
2021-11-04 18:25 ` Inemesit Affia
2021-11-04 18:29 ` Dave Taht
2021-11-04 19:10 ` Michael Richardson
2021-11-05 0:34 ` Ulrich Speidel
2021-11-05 1:05 ` Nathan Owens
2021-11-05 1:18 ` Darrell Budic
2021-11-05 22:24 ` Ulrich Speidel
2021-11-05 15:00 ` [Starlink] data sovereignty Michael Richardson
2021-11-05 15:07 ` Spencer Sevilla
2021-11-05 17:36 ` Daniel AJ Sokolov
2021-11-05 18:01 ` Daniel AJ Sokolov
2021-11-05 22:12 ` [Starlink] Starlink tidbits from NANOG Ulrich Speidel
2021-11-05 1:27 ` Darrell Budic
2021-11-05 15:03 ` Michael Richardson
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=7907F9D1-9511-4254-BD8F-701888EB6778@onholyground.com \
--to=budic@onholyground.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