From: Christopher Robin <pheoni@gmail.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: Dave Taht <dave.taht@gmail.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] spacebee
Date: Tue, 13 Mar 2018 17:47:55 +0000 [thread overview]
Message-ID: <CAPjrEw87LruVGpnohFHP9RNUP_Pu8aiKyUzVJdX23r3+2ERtZg@mail.gmail.com> (raw)
In-Reply-To: <CAGhGL2CHdgFcKO9k5kOo9WukN8SLLCag715fCWgnGuzAZxPBFw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]
On Tue, Mar 13, 2018 at 1:03 PM Jim Gettys <jg@freedesktop.org> wrote:
> On Tue, Mar 13, 2018 at 12:52 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> 2) Although the FCC denied the application based on having inadaquate
>> radar reflectivity, according to their standards, the article states:
>>
>> "Websites dedicated to tracking operational satellites show the
>> SpaceBees in orbits virtually identical to those specified in Swarm’s
>> application." Ground stations can only get better.
>
>
Note that the objections are based on a non-operating SpaceBee. I’m not
seeing anything about one of the SpaceBees going dark for testing or not
responding due to malfunction. So the ground stations are prob getting both
GPS data from the sat and a fix on the radio signal to determine position.
If both of those methods of tracking disappear, there appears to be a
limited number of ground stations that could provide an accurate enough
location to allow for other orbitals to made an avoidance maneuver.
With all the noise around this launch, I haven’t been able to find info on
expected operational lifespan vs expected orbit decay. LEO’s can still last
for decades. The only thing I’m finding is an expected use for 6mo to 2yr,
but not sure how long after that the Spaceebee will stay in orbit and/or be
responsive with positional data.
While just 4 of these things in space isn’t a major concern, rogue
launching objects into space isn’t a scalable solution. This is especially
true as the cost of launching comes down into the “cheap” startup range.
These types of companies aren’t usually concerned 25yr impact plans, and
most wont last long enough to be around to assist if any problems occur
past that 2-3yr window.
We have rules for the road, the sea, and the sky. Space needs similar
protections. No, the FCC shouldn’t be that gatekeeper, but that’s where we
are at until an agency is stood up with authority to handle these kinds of
issues.
[-- Attachment #2: Type: text/html, Size: 3021 bytes --]
next prev parent reply other threads:[~2018-03-13 17:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 4:13 Dave Taht
2018-03-12 16:25 ` dpreed
2018-03-13 18:31 ` Dave Taht
2018-03-12 16:26 ` Jim Gettys
2018-03-12 17:18 ` dpreed
2018-03-12 17:34 ` Christopher Robin
2018-03-12 19:10 ` dpreed
2018-03-12 20:29 ` Christopher Robin
2018-03-13 16:12 ` Jim Gettys
2018-03-13 16:52 ` Dave Taht
2018-03-13 17:03 ` Jim Gettys
2018-03-13 17:31 ` Dave Taht
2018-03-14 1:49 ` Jonathan Morton
2018-03-13 17:47 ` Christopher Robin [this message]
2018-03-13 18:25 ` Dave Taht
2018-03-14 4:16 ` Matt Taggart
2018-03-13 17:49 ` valdis.kletnieks
2018-03-13 18:06 ` Dave Taht
2018-03-14 4:08 ` Matt Taggart
2018-03-15 20:22 ` Ray Ramadorai
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPjrEw87LruVGpnohFHP9RNUP_Pu8aiKyUzVJdX23r3+2ERtZg@mail.gmail.com \
--to=pheoni@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=jg@freedesktop.org \
/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