From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: Gert Doering <gert@space.net>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] [NNagain] FCC Upholds Denial of Starlink's RDOF Application
Date: Fri, 15 Dec 2023 13:43:25 +0100 [thread overview]
Message-ID: <02cc2879-ef99-4388-bc1e-335a4aaff6aa@gmail.com> (raw)
In-Reply-To: <ZXxIdbzif5ogB0IQ@Space.Net>
Le 15/12/2023 à 13:37, Gert Doering a écrit :
> Hi,
>
> On Fri, Dec 15, 2023 at 01:07:10PM +0100, Alexandre Petrescu via Starlink wrote:
>> subscriber ; they light only one, equalling 1gbit/s. It means that they could
>> scale it up later to 4 or 5 gbit/s, without additional installation. At the
> You do not need multiple fibers to transfer more than 1gbit/s - the benefit
> is "multiple services or multiple providers could use those extra fibers"
> (or "have a backup in case one is damanged")
>
> Fiber7.ch delivers 25 Gbit/s to the home in switzerland, on a single fiber :-)
It is worth noting indeed.
So, a requirement to a competitive satcom would be like 25 Gbit/s. I
think it is not impossible to make, if many intermediate layers (HAPS,
drones etc) are used, and larger band widths.
Alex
>
> Gert Doering
> -- NetMaster
next prev parent reply other threads:[~2023-12-15 12:43 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 21:25 [Starlink] FCC Upholds Denial of Starlink’s " Frantisek Borsik
[not found] ` <A8DC9114A92F47D5AAE1D332B5E5007D@SRA6>
2023-12-13 22:38 ` [Starlink] FCC Upholds Denial of Starlink's " Frantisek Borsik
2023-12-14 2:46 ` [Starlink] [NNagain] " Robert McMahon
2023-12-14 6:11 ` Frantisek Borsik
2023-12-14 17:48 ` David Bray, PhD
2023-12-14 18:47 ` Frantisek Borsik
2023-12-14 18:51 ` Nathan Simington
2023-12-14 19:44 ` Frantisek Borsik
2023-12-15 12:07 ` Alexandre Petrescu
2023-12-15 12:37 ` Gert Doering
2023-12-15 12:43 ` Alexandre Petrescu [this message]
2023-12-15 12:44 ` Gert Doering
2023-12-15 12:46 ` Frantisek Borsik
2023-12-15 13:24 ` Gert Doering
2023-12-15 13:40 ` Sebastian Moeller
2023-12-15 18:06 ` David Lang
2023-12-15 18:51 ` rjmcmahon
2023-12-15 19:13 ` David Lang
2023-12-15 21:29 ` rjmcmahon
2023-12-15 21:42 ` David Lang
2023-12-15 22:04 ` David Bray, PhD
2023-12-15 22:10 ` David Lang
2023-12-15 22:13 ` David Bray, PhD
2023-12-15 22:33 ` Kenline, Doug
2023-12-15 22:36 ` Dave Taht
2023-12-19 19:33 ` Alexandre Petrescu
2023-12-15 22:05 ` rjmcmahon
2023-12-15 22:13 ` David Lang
2023-12-15 22:26 ` Dave Taht
2023-12-16 4:16 ` David Lang
2023-12-16 17:30 ` rjmcmahon
2023-12-16 18:48 ` Robert McMahon
2023-12-16 21:44 ` Frantisek Borsik
2023-12-16 22:28 ` Robert McMahon
2023-12-17 0:25 ` Dave Taht
2023-12-23 21:17 ` J Pan
2023-12-18 8:25 ` David Lang
2023-12-15 15:46 ` Livingood, Jason
2023-12-17 17:32 ` Alexandre Petrescu
2023-12-17 18:06 ` Sebastian Moeller
2023-12-16 8:15 ` Alexandre Petrescu
2023-12-15 13:06 ` Sebastian Moeller
2023-12-16 8:09 ` Alexandre Petrescu
2023-12-16 11:14 ` Sebastian Moeller
2023-12-17 1:54 ` [Starlink] other fcc services at sea Dave Taht
2023-12-16 13:03 [Starlink] [NNagain] FCC Upholds Denial of Starlink's RDOF Application David Fernández
2023-12-18 8:09 ` David Lang
2023-12-16 14:33 David Fernández
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=02cc2879-ef99-4388-bc1e-335a4aaff6aa@gmail.com \
--to=alexandre.petrescu@gmail.com \
--cc=gert@space.net \
--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