Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "dpreed@deepplum.com" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] spacebee
Date: Mon, 12 Mar 2018 12:25:59 -0400 (EDT)	[thread overview]
Message-ID: <1520871959.09216206@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw63zYCHFj6mJTSSkc6i_7h2hkOpZbJQvgAhPqMEnTFqgA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2806 bytes --]


 
This is fascinating. Could it be that the idea of "open networks of satellites" are going to start to play the role of WiFi or UWB? Scalable sharing of orbital space, using a simple cooperative protocol? In other words, the first step toward what Vint Cerf championed as the "Interplanetary Internet?
 
 
 
If so, that explains why the FCC id doing the bidding of its masters. Sure, we need a few rules of the road to manage space orbits, etc. That's in *everyone's* public interest.
 
 
 
But do we need the rules to be set by a fully captured regulatory mechanism in the pockets of monopoly capital?
 
 
 
I wrote this comment to another mailing list. Thought you might find it interesing here as well. (This reflects very deep personal experience with building scalable decentralized systems for most of my life, plus encounters with the FCC around getting UWB authorized - it was defenestrated in the form that they authorized it - and my experiences with the "be very afraid" camp that informs the FCC's idea that SDR is not to be allowed, ever, in products certified for sale in the US to consumers). It's remarkable how the idea that "we need rules of the road" gets perverted into "the US and its corporate owners must have power over", esp. in the FCC.
 
-----------------------
 
One should ask, why hasn't NASA stepped in to facilitate discussion of orbital rules of the road? Preferably the minimum necessary rules, allowing the most flexibility to innovate and create value.
 
 
 
And one should also ask, one whose behalf is FCC making these choices?
 
 
 
Space, in theory, belongs to all of us. Not governments defined by national boundaries, not the UN, ... it *belongs* to us, just as the Sea does.
 
 
 
It's helpful to have rules (for example, the WiFi rules which extend Part 15's "accept all interference and don't deliberately interfere" to a concrete - listen for energy before you transmit, and transmit using a power and modulation that has the least impact on others. Bran Ferren called this the "Golden Rule". The law of the sea is similar.
 
 
 
One can ask whether the FCC has any legitimate constitutional mandate over space at all. Maybe that should be taken to the (sadly plutocratic) Supreme Court, or even better, a true judicial court that incorporates the interests and fairness to all of the planet?
 
 
 
We should remember that if Swarm launched and operated its network of satellites from the middle of the ocean (remember Pirate Radio Stations in the UK beyond the coastal zone), the US FCC could not touch them. Arguably, there's no one who could legally touch them.
 
 
 
That said, we need rules of the road, like we do for drones. But they should not be written by those who stand to lose their privileges.
 
 
 

[-- Attachment #2: Type: text/html, Size: 7966 bytes --]

  reply	other threads:[~2018-03-12 16:25 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 [this message]
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
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=1520871959.09216206@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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