From: Darrell Budic <budic@onholyground.com>
To: Nathan Owens <nathan@nathan.io>
Cc: Ulrich Speidel <ulrich@cs.auckland.ac.nz>,
starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink tidbits from NANOG
Date: Thu, 4 Nov 2021 20:18:45 -0500 [thread overview]
Message-ID: <E1D7521E-DE45-4BAD-849E-86FC6F40138F@onholyground.com> (raw)
In-Reply-To: <CALjsLJu8YiC0sKRX6VjOyoiHd4URDRLd_P6OW4nvtX5vBjuGmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]
> On Nov 4, 2021, at 8:05 PM, Nathan Owens <nathan@nathan.io> wrote:
>
> > They are using waves back to regional DCs now, but will be moving to
> > dark fiber over the next year or two
> If that means "radio" waves, then this goes a long way to explaining why
> there's already limited capacity even near the US-Canada border.
>
> Waves in this case generally refers to 10G/100G leased optical circuit capacity.
As has already been mentioned, I did mean optical waves. Comes from my perspective as a network guy who uses lots of optical transport and DWDM systems. Realized I should have been more specific about optical waves, especially in this forum. Even more specifically, “waves” are generally a product provided you by someone else who lights the fiber for you. In this case, probably Zayo, Lumen, Crown Castle, and maybe even Google operating the fiber. Generally 10G waves, or some multiple there of, although 100G waves are out there, and 400G are coming/testing/just entering production.
In this case, I suspect it means 10G waves given the currently estimated capacity of the ground stations. Moving to dark lets them do Nx10G links more cost effectively, or 100G link if the distance is short enough (around 100km at the moment before you have to go to the much more expensive coherent optics). And you can do you own support and monitoring, which I got the impression was part of their problem with Google’s NOC.
[-- Attachment #2: Type: text/html, Size: 2675 bytes --]
next prev parent reply other threads:[~2021-11-05 1:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 15:26 Darrell Budic
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 [this message]
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=E1D7521E-DE45-4BAD-849E-86FC6F40138F@onholyground.com \
--to=budic@onholyground.com \
--cc=nathan@nathan.io \
--cc=starlink@lists.bufferbloat.net \
--cc=ulrich@cs.auckland.ac.nz \
/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