From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Starlink list <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink no longer available to the Ukrainian army?
Date: Sun, 16 Oct 2022 16:37:14 -0400 [thread overview]
Message-ID: <20327.1665952634@localhost> (raw)
In-Reply-To: <79o05892-1pp0-q94r-1172-rr80r56o168n@ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
David Lang via Starlink <starlink@lists.bufferbloat.net> wrote:
> With Russia targeting infrastructure, how well is that going to be working?
> between power outages and even a relatively small handful of exchanges hit, I
> wouldn't expect any wired infrastructure to be that reliable.
https://ripe84.ripe.net/archives/video/738/
https://ripe84.ripe.net/archives/video/739/
https://nogalliance.org/our-task-forces/keep-ukraine-connected/
The most needed items have been fiber splicing units, and because there are
few secure places to keep them in Ukraine, they have been trying to keep them
in Poland. Last I heard that was a logistical challenge for the NOG Alliance.
There have also been significant VAT problems with donations from outside the
EU, even though they ultimate destination is outside the EU.
--
Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]
next prev parent reply other threads:[~2022-10-16 20:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 12:06 Juliusz Chroboczek
2022-10-14 12:45 ` David Lang
2022-10-14 13:05 ` Juliusz Chroboczek
2022-10-14 13:11 ` David Lang
2022-10-14 14:17 ` Mike Puchol
2022-10-14 18:26 ` Juliusz Chroboczek
2022-10-14 20:44 ` Mike Puchol
2022-10-16 17:31 ` Steve Stroh
2022-10-16 17:56 ` Dave Taht
2022-10-16 18:28 ` Vint Cerf
2022-10-14 12:51 ` Mike Puchol
2022-10-14 13:13 ` Juliusz Chroboczek
2022-10-14 14:15 ` Mike Puchol
2022-10-14 16:05 ` Juliusz Chroboczek
2022-10-14 17:13 ` Kurtis Heimerl
2022-10-14 17:28 ` David Lang
2022-10-14 18:16 ` Juliusz Chroboczek
2022-10-14 18:32 ` Larry Press
2022-10-14 19:32 ` Benjamin Henrion
2022-10-14 19:35 ` David Lang
2022-10-14 20:07 ` David Lang
2022-10-14 22:29 ` Dave Taht
2022-10-15 16:51 ` Larry Press
2022-10-16 6:42 ` Sebastian Moeller
2022-10-16 8:45 ` Bruce Perens
2022-10-16 16:31 ` Dave Taht
2022-10-16 17:00 ` Sebastian Moeller
2022-10-16 19:55 ` Brandon Butterworth
2022-10-16 20:25 ` Bruce Perens
2022-11-02 3:50 ` [Starlink] 25 years of open source - where we went wrong, and how to fix it Dave Taht
2022-10-14 19:13 ` [Starlink] Starlink no longer available to the Ukrainian army? tom
2022-10-14 19:41 ` David Lang
2022-10-14 20:09 ` Dave Taht
2022-10-16 17:50 ` Steve Stroh
2022-10-16 17:57 ` Nathan Owens
2022-10-16 18:01 ` Dave Taht
2022-10-16 18:29 ` Vint Cerf
2022-10-16 18:33 ` David Lang
2022-10-16 18:44 ` Sebastian Moeller
2022-10-16 19:03 ` Brandon Butterworth
2022-10-16 19:37 ` Ulrich Speidel
2022-10-16 19:51 ` David Lang
2022-10-16 20:37 ` Michael Richardson [this message]
2022-10-16 20:52 ` Bruce Perens
2022-10-16 22:17 ` Brandon Butterworth
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=20327.1665952634@localhost \
--to=mcr+ietf@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