From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink at sea
Date: Wed, 3 Jul 2024 15:40:12 +1200 [thread overview]
Message-ID: <1de04eda-c341-4db9-a736-196765c77437@auckland.ac.nz> (raw)
In-Reply-To: <CAA93jw7beHsoUkDKYhRB0S3VhU5UHbhvGNnTvfN1b37LqyXKhg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2519 bytes --]
Given where the author of the blog was, most of the latency would have
been from the space segment - the 20 ms are only realistic if the
satellite that Dishy talks to can downlink to a ground station within a
few 100 km. If the laser ISLs are involved, the path is usually much
longer (and the transfer points into and out of the Internet proper
aren't always the closest or most obvious ground stations either. We see
traceroutes from Tarawa pass through Auckland, regardless of target,
despite there being closer ground stations in Australia, for example.
It'd be also interesting to see where cruise ships have which
experience. Antarctica does well because the ship and therefore user
density is low, and there is little competition for the ISLs. Similarly,
ships in moderate latitudes below the mid-50's now typically see a lot
of satellites that they can use, and as long as they don't all crowd in
large numbers into a single harbour, they should generally be fine. The
crunch point will be when you get high concentrations of large ships in
northern locations - Norway, Svalbard and Alaska / Inside Passage at
this time of year come to mind. That's where low visible capacity meets
high user density.
I also wonder how much of a role demographics play. My only trip on a
cruise ship to date is a story in its own right, but at the time I
couldn't help but notice that I was 30-40 years younger than the age
average on board. So quite how many gamers / streamers there'd be among
the digital migrants aboard would have been questionable. But then
again, that was some time ago, and I'm sure there'd be a few digital
natives now. Certainly, there will be in future. So how will that impact
on demand and the ability to accommodate the growth in demand?
On 3/07/2024 8:40 am, Dave Taht via Starlink wrote:
>
> https://circleid.com/posts/20240501-starlink-service-is-great-on-some-cruise-ships
>
> --
> https://www.linkedin.com/feed/update/urn:li:activity:7203400057172180992/
> Donations Drive.
> Dave Täht CSO, LibreQos
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
[-- Attachment #2: Type: text/html, Size: 4207 bytes --]
next prev parent reply other threads:[~2024-07-03 3:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 20:40 Dave Taht
2024-07-03 3:40 ` Ulrich Speidel [this message]
2024-07-03 17:21 ` Larry Press
2024-07-03 4:21 ` Marc Blanchet
2024-07-03 4:26 ` J Pan
2024-07-03 17:06 ` Larry Press
2024-07-03 22:06 ` Michael Richardson
2024-07-14 19:32 ` J Pan
-- strict thread matches above, loose matches on Subject: below --
2022-07-14 0:20 Dave Taht
2022-07-14 0:31 ` David Lang
2022-07-14 0:36 ` Gary E. Miller
2022-07-14 0:40 ` David Lang
2022-07-14 0:59 ` Gary E. Miller
2022-07-14 1:36 ` David Lang
2022-07-14 5:46 ` Larry Press
2022-07-14 7:00 ` David Lang
2022-07-14 11:15 ` Mike Puchol
2022-07-14 11:32 ` Sebastian Moeller
2022-07-14 12:02 ` Mike Puchol
2022-07-14 12:34 ` Sebastian Moeller
2022-07-14 12:49 ` Nitinder Mohan
2022-07-14 12:57 ` Jared Mauch
2022-07-14 13:05 ` Nitinder Mohan
2022-07-14 13:33 ` Nitinder Mohan
2022-07-14 14:56 ` Mike Puchol
2022-07-14 15:28 ` Sebastian Moeller
2022-07-14 15:32 ` Nathan Owens
2022-07-27 21:17 ` 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=1de04eda-c341-4db9-a736-196765c77437@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--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