On 12-5-2017 21:21, Steve deRosier wrote: > Hi Ben, > > On Fri, May 12, 2017 at 7:12 AM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: >> >> >> On 05/11/2017 04:38 AM, Kalle Valo wrote: >>> [snip] >>> o I don't know about other countries, but in Finland applying for any >>> type of license (even if just to a license to drive a moped) needs >>> both time and money. So there is significant effort anyway needed to >>> legally use this band. And how many users there really are is unclear. >> >> >> This is almost certainly not going to be used by regular end-users. It is >> going to be >> used by public safety organizations who are buying equipment from companies >> using open-wrt, LEDE, or similar, or possibly small teams at public safety >> organizations doing the work themselves. Rather than having each of these >> vendors > > I agree 100% that this won't be used by "regular end-users", if you > define those users as the 99% of the population who will go to Best > Buy and buy a router, plug it into their network and use it to get > their iOS updates and download movies from Netflix. These aren't the > users that the FCC is worried about. They're concerned about the user > who buys an OpenWRT compatible router, installs OpenWRT on it, builds > a custom kernel. And that person happens to live in an area with > congested WiFi bands, the person notices an option to use these other > non-congested bands, decides that ignoring the warning would be > harmless and the FCC won't ever know anyway. > > And then there's a fire or other event in the area, and the emergency > workers can't communicate. At best case, the FCC investigates and > slaps a $25,000 fine on the operator. At worst case, someone dies. > > I don't feel it's responsible as an engineer to hide behind "well, we > warned them that they shouldn't do that" while ignoring my culpability > in the matter. Setting the stage for others to fail due to their > ignorance is not ethical. Totally agree this is about being responsible. > Anyone building a custom kernel is able to enable a config option. You > can say that, "sure they can pull the patch from here and enable it > anyway" or "they can figure it out and do it themselves, it's easy", > but I do think there's a significant difference between being able to > build a custom kernel with a configuration enabled vs being able to > find and apply a random patch to a kernel and get it building and > working. That's a different level of expertise. And going through that > effort gives a person some time to reflect and think about if it > should be done in the first place. > > Adding this code to mainline makes it a feature of Linux and this > driver. There's no way around that argument. Saying that "this is > almost certainly not going to be used by regular end-users" is both > fairly true as well as disingenuous. You're still making it an > accepted feature. Indeed. I had my concerns back when the CFG80211_CERTIFICATION_ONUS was added to the kernel, but that is water under the bridge. It is not only these kind of changes the FCC is looking at. They also have issues with 802.11d support. That does not even need a custom kernel. The end-user just sets the country to some nice EU channel while being in the US and screw up some weather radar. It has happened. Not life-threatening, unless some tornado was missed maybe, but the concern is justified. How the FCC is handling it may indeed be pointless and technically misinformed, but that is because there is no good solution right now. At least not a solution that assures it will not happen. I can only agree that we as a community should not accommodate such (ab)use. Finding a solution that is working for everyone is indeed the real challenge. Regards, Arend
