[Battlemesh] FCC Contacts about Wifi Regulations

Paul Gardner-Stephen paul at servalproject.org
Fri Aug 5 09:49:00 CEST 2016


On Fri, Aug 5, 2016 at 5:05 PM, Jonathan Morton <chromatix99 at gmail.com>

> > On 5 Aug, 2016, at 10:24, Paul Gardner-Stephen <paul at servalproject.org>
> wrote:
> >
> >> I think the correct solution is as follows:
> >>
> >> 1: Allow software-level reconfiguration of the radios.  Make it as easy
> as possible to select the correct regulatory domain, using geolocation if
> practical.  Before selling/deploying hardware, set it up correctly for its
> intended region, or for a failsafe composite region which is compliant in
> all of the most common domains.
> > Unfortunately we know from the TP-LINK case just now, that the FCC
> doesn't like this, and experience from RC and others, is that the staff on
> the border during disasters also get cagey about any purely software option.
> >> 2: Make the end-user liable for the emissions of his hardware, if he
> has explicitly set an incorrect regulatory domain or made hardware
> modifications (eg. to increase its power output).  Place a prominent
> notice, as Juliusz suggested, informing the end-user of this responsibility.
> >>
> >> This solves both problems: freedom and flexibility is retained, and the
> FCC still has a way to enforce the regulations (with boots on the ground).
> > Except that they will instead enforce (as will many other national
> regulators) by declining approval to import/use.
> I still think it’s the *correct* solution.  The problem is convincing the
> authorities of that fact.

Yes, I agree that software only should be sufficient, but the
socio-political complications mean we need a pragmatic solution, which is
what I have tried to create.


>  - Jonathan Morton
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20160805/814dd4a2/attachment-0001.html>

More information about the Battlemesh mailing list