Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Spencer Sevilla <spencer.builds.networks@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] data sovereignty
Date: Fri, 5 Nov 2021 08:07:34 -0700	[thread overview]
Message-ID: <D31131E9-6F8B-4D8C-B7C6-3EE426E578C4@gmail.com> (raw)
In-Reply-To: <31604.1636124427@localhost>

For what it’s worth, space is usually defined as either 50 miles (80km) or 62 miles (100 km) depending on the agency in question. I couldn’t find specific resources on how high a country’s “airspace” goes, but I do believe that “space" is considered international territory.

https://en.wikipedia.org/wiki/K%C3%A1rm%C3%A1n_line
https://en.wikipedia.org/wiki/Space_law

Spencer

> On Nov 5, 2021, at 08:00, Michael Richardson <mcr@sandelman.ca> wrote:
> 
> 
> A number of Canadian IXs have pondered whether we could get Starlink to peer
> via air.    I don't think this will be possible until they move to IPv6
> so that they can do some geographic allocation of end-station addresses.
> 
> A question that was asked was: what is the altitude at which the data has
> left the country...   Heinlein's _Man Who Sold the Moon_ is not true.
> Countries have a limited altitude in which to claim soveignty.  But, what is
> it?  (Would Alphabet Loon be within it? I suspect so)
> 
> Will this argument about data sovereignty be used by national governments (or
> rather, the associated incumbent telco-ISPs) to forbid spending public money
> on Starlink?
> 
> 
> 
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink


  reply	other threads:[~2021-11-05 15:07 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 [this message]
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=D31131E9-6F8B-4D8C-B7C6-3EE426E578C4@gmail.com \
    --to=spencer.builds.networks@gmail.com \
    --cc=mcr@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