From: Daniel AJ Sokolov <daniel@falco.ca>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] data sovereignty
Date: Fri, 5 Nov 2021 11:01:48 -0700 [thread overview]
Message-ID: <b53b4ce0-9b75-f696-1b98-d5077d9bd8fc@falco.ca> (raw)
In-Reply-To: <31604.1636124427@localhost>
On 2021-11-05 at 8:00 a.m., Michael Richardson wrote:
> A question that was asked was: what is the altitude at which the data has
> left the country...
That's a good question.
The answer may not be in airspace vs. space. (That border is undefined,
but if there is not enough air to get downlift, I would say it's not
airspace anymore, but space.)
One answer may be that the vessel that is routing the data flies under a
certain carrier flag. So one could argue that all SpaceX satellites are
US flagged, as they obtained their license from the FCC. (Same for OneWeb.)
Could there be VPNs creating virtual Canadian territory in cyberspace?
Why not, eh!
Daniel AJ
next prev parent reply other threads:[~2021-11-05 18:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 15:26 [Starlink] Starlink tidbits from NANOG 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
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 [this message]
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=b53b4ce0-9b75-f696-1b98-d5077d9bd8fc@falco.ca \
--to=daniel@falco.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