* [Cake] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final @ 2015-10-06 0:13 Dave Taht 2015-10-06 12:03 ` [Cake] [Bloat] " Rich Brown 2015-10-06 13:49 ` [Cake] [OpenWrt-Devel] " Linus Lüssing 0 siblings, 2 replies; 5+ messages in thread From: Dave Taht @ 2015-10-06 0:13 UTC (permalink / raw) To: fcc, cerowrt-devel, make-wifi-fast, cake, Battle of the Mesh Mailing List, bloat, OpenWrt Development List see: https://docs.google.com/document/d/1E1D1vWP9uA97Yj5UuBPZXuQEPHARp-AhRqUOeQB2WPk/edit?usp=sharing for more details. We still have a boatload of footnotes (help?) to add back in properly, and there are no doubt other problems we will catch in the morning. Comment away! As we are hard up against deadlines, and I no longer expect substantial changes, all new offers of signature will be considered final. signatures are now being collected via: http://goo.gl/forms/WCF7kPcFl9 - the 70+ that have already committed need to be contacted again to approve this draft. -- Dave Täht Do you want faster, better, wifi? https://www.patreon.com/dtaht ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Cake] [Bloat] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final 2015-10-06 0:13 [Cake] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final Dave Taht @ 2015-10-06 12:03 ` Rich Brown 2015-10-06 13:49 ` [Cake] [OpenWrt-Devel] " Linus Lüssing 1 sibling, 0 replies; 5+ messages in thread From: Rich Brown @ 2015-10-06 12:03 UTC (permalink / raw) To: Dave Taht Cc: fcc, make-wifi-fast, cake, cerowrt-devel, bloat, OpenWrt Development List, Battle of the Mesh Mailing List > We still have a boatload of footnotes (help?) to add back in properly, I am fixing them now. (The Footnotes were converted to Endnotes when I imported my local copy back to Google Docs) Rich ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Cake] [OpenWrt-Devel] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final 2015-10-06 0:13 [Cake] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final Dave Taht 2015-10-06 12:03 ` [Cake] [Bloat] " Rich Brown @ 2015-10-06 13:49 ` Linus Lüssing 2015-10-06 14:21 ` [Cake] [Battlemesh] " Benjamin Henrion 1 sibling, 1 reply; 5+ messages in thread From: Linus Lüssing @ 2015-10-06 13:49 UTC (permalink / raw) To: Dave Taht Cc: fcc, make-wifi-fast, cake, cerowrt-devel, bloat, OpenWrt Development List, Battle of the Mesh Mailing List On Tue, Oct 06, 2015 at 02:13:36AM +0200, Dave Taht wrote: > Comment away! There are many good points made in this text. I like the Volkswagen example and the suggestion to require opening up the firmware. For the latter, had been thinking about that before briefly, but kind of dismissed it early, basically because the reasoning in my head was that FCC shouldn't make any requirements regarding the form of the software at all. They should only regulate the result. Actually this text and the VW example convinced me :). And yes, now I think with that we can push even further, suggesting to require open and modifiable source code (for the wifi part at least). The VW example gives us the opportunity and strategic advantage to be able to demandn more without sounding unreasonable. ~~~~~ Some quotations and remarks: "'It is our view that the rules appear to regulate the "means" not the "ends"'" -> So does the alternate approach in the end, but in the opposite "extreme" "This software contains built-in configurations to ensure that radios are used in compliance with the local laws and regulations." -> "ensure" seems to be a too strong word to me "is a natural target for both criminal exploitation and cyberwarfare" -> Just my personal taste, but I don't like using the word "war" for mere economical power play between nations as it seems to soften the original meaning of "war", meaning to kill people (don't like the term "cryptowars" either - maybe that taste might have cultural roots; the word "war" is never used in German language in contexts like these while it seems more common in the US and probably other countries too?) "It is currently limiting our attempts to fix the ath9k and mt76 devices" -> What is meant by that exactly? ath9k is open source, binary firmwares can't be the issue you mean here... - with "it is limiting", do you mean "new, emerging devices with locked firmwares are limiting..."? Maybe clarify the "it"? "If the Commission does not intend to prohibit the upgrade or replacement of firmware in Wi-Fi devices, rules would be welcomed that actually encouraged non-destructive interpretations by equipment vendors." -> That one might need explanations too. Actually, I think it is explained later, with citatitons of vendors. But ending the paragraph there leaves a questions mark for quite a while. ~~~~~ Not sure how much time is left to work on the text - content wise everything seems to be in there. Structually maybe a guiding thread could be worked out a little more. The beginning is good and mentions and summarizes the main points well. Some points and explanations seem to be repeated several times after that though. Maybe things could be "unbloated" a little here and there ;). Also the recommendations are not quite clear at some points to me. The "Alternate Approach" and "Recommendations" sections are clear by mandating open and modifiable firmwares for the wifi parts at least. But some other parts seem to allude to different suggestions. For instance as of writing this email, the draft also contains: "The portion of the source code that controls the radio is very small compared to the entirety of the underlying operating system, Graphical User Interface, routing and switching code, and all the other functions that make up a modern Wi-Fi router. As such, restricting the entire firmware to carries with it a lot of collateral damage by also preventing improvements to these other parts." Which seems to reverse the recommendation. Thanks for this great draft and the work you guys have put into it so far! Cheers, Linus ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Cake] [Battlemesh] [OpenWrt-Devel] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final 2015-10-06 13:49 ` [Cake] [OpenWrt-Devel] " Linus Lüssing @ 2015-10-06 14:21 ` Benjamin Henrion 2015-10-06 15:17 ` Linus Lüssing 0 siblings, 1 reply; 5+ messages in thread From: Benjamin Henrion @ 2015-10-06 14:21 UTC (permalink / raw) To: Battle of the Mesh Mailing List Cc: fcc, make-wifi-fast, cake, cerowrt-devel, bloat, OpenWrt Development List On Tue, Oct 6, 2015 at 3:49 PM, Linus Lüssing <linus.luessing@c0d3.blue> wrote: > On Tue, Oct 06, 2015 at 02:13:36AM +0200, Dave Taht wrote: >> Comment away! > > There are many good points made in this text. > > I like the Volkswagen example and the suggestion to require > opening up the firmware. > > For the latter, had been thinking about that before briefly, > but kind of dismissed it early, basically because the reasoning in > my head was that FCC shouldn't make any requirements regarding > the form of the software at all. They should only regulate the > result. Blobs cannot be trusted to do the right thing. -- Benjamin Henrion <bhenrion at ffii.org> FFII Brussels - +32-484-566109 - +32-2-4148403 "In July 2005, after several failed attempts to legalise software patents in Europe, the patent establishment changed its strategy. Instead of explicitly seeking to sanction the patentability of software, they are now seeking to create a central European patent court, which would establish and enforce patentability rules in their favor, without any possibility of correction by competing courts or democratically elected legislators." ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Cake] [Battlemesh] [OpenWrt-Devel] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final 2015-10-06 14:21 ` [Cake] [Battlemesh] " Benjamin Henrion @ 2015-10-06 15:17 ` Linus Lüssing 0 siblings, 0 replies; 5+ messages in thread From: Linus Lüssing @ 2015-10-06 15:17 UTC (permalink / raw) To: Battle of the Mesh Mailing List Cc: fcc, make-wifi-fast, cake, cerowrt-devel, bloat, OpenWrt Development List On Tue, Oct 06, 2015 at 04:21:38PM +0200, Benjamin Henrion wrote: > On Tue, Oct 6, 2015 at 3:49 PM, Linus Lüssing <linus.luessing@c0d3.blue> wrote: > > On Tue, Oct 06, 2015 at 02:13:36AM +0200, Dave Taht wrote: > >> Comment away! > > > > There are many good points made in this text. > > > > I like the Volkswagen example and the suggestion to require > > opening up the firmware. > > > > For the latter, had been thinking about that before briefly, > > but kind of dismissed it early, basically because the reasoning in > > my head was that FCC shouldn't make any requirements regarding > > the form of the software at all. They should only regulate the > > result. > > Blobs cannot be trusted to do the right thing. I know (and I guess we all do here?). I don't get the purpose of this comment, sorry :(. ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-10-06 15:17 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-10-06 0:13 [Cake] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final Dave Taht 2015-10-06 12:03 ` [Cake] [Bloat] " Rich Brown 2015-10-06 13:49 ` [Cake] [OpenWrt-Devel] " Linus Lüssing 2015-10-06 14:21 ` [Cake] [Battlemesh] " Benjamin Henrion 2015-10-06 15:17 ` Linus Lüssing
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox