<div dir="ltr">Adding bufferbloat-fcc-discuss.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div>David<br></div></div></div></div>
<br><div class="gmail_quote">On Tue, Nov 10, 2015 at 10:45 AM, David Hilton <span dir="ltr"><<a href="mailto:quercus.aeternam@gmail.com" target="_blank">quercus.aeternam@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><p dir="ltr">I would like to propose a name for this: </p><p dir="ltr">Pronounced: SureFi (uncertain spelling, see below).</p><p dir="ltr">------------</p><p dir="ltr">It makes me think of some english words:<br>Sure, Certify, Jurify, Sure-fire</p><p dir="ltr">It is also similar to a chinese words:</p><p dir="ltr">Chinese: <a href="http://dictionary.hantrainerpro.com/chinese-english/translation-shi_city.htm" target="_blank">shì</a> (sure) - City, yes/correct, scholar, to release/set free, to look at, to show, strength/influence/momentum, persimmon...</p><p dir="ltr"><a href="http://dictionary.hantrainerpro.com/chinese-english/translation-shi_city.htm" target="_blank">http://dictionary.hantrainerpro.com/chinese-english/translation-shi_city.htm</a> (follow the arrow to more translations)</p><p dir="ltr">--------</p><p dir="ltr">There is a problem with the spelling. I think it's a little too long, plus "surefi" is taken by a small (1-person) tech company for retail businesses in NM, USA. ShurFi is available, but looks weird to me. SurFi is not available. SirFi is shorter, but I'd prefer the root "sure" be clear, vs. "sir". XrFi is short but not intuitive. SrFi might work, but might be read as SeniorFi?</p><p>What do you all think?</p></div><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><br clear="all"><div><div><div dir="ltr"><div>David<br></div></div></div></div></font></span><div><div class="h5">
<br><div class="gmail_quote">On Thu, Oct 15, 2015 at 7:59 PM, Dave Taht <span dir="ltr"><<a href="mailto:dave.taht@gmail.com" target="_blank">dave.taht@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Below is some older analysis by a marketing expert of the<br>
make-wifi-fast project plan (although it is linked to in fcc wifi<br>
letter, it is so long that I doubt few as read as far as the detailed<br>
- and ongoing!!! - problems in wifi)<br>
<br>
the planned - OPEN - engineering work on wifi is buried in the In<br>
closing section - here:<br>
<br>
<a href="https://docs.google.com/document/d/1Se36svYE1Uzpppe1HWnEyat_sAGghB3kE285LElJBW4/edit" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1Se36svYE1Uzpppe1HWnEyat_sAGghB3kE285LElJBW4/edit</a><br>
<br>
We are always looking for contributions of funds, resources, and<br>
engineering time towards actually making wifi better. I had hoped to<br>
kick off the per-station queuing portion of the effort last week,<br>
actually.<br>
<br>
Is there anyone here that is actually a member of the wifi alliance?<br>
Has anyone reached out to them?<br>
<br>
<a href="http://www.wi-fi.org/who-we-are/member-companies" rel="noreferrer" target="_blank">http://www.wi-fi.org/who-we-are/member-companies</a><br>
<br>
There are quite a large number of companies that have got their seven<br>
thousand dollar coffee cup from the alliance, after passing their<br>
lousy tests for certification.<br>
<br>
... snip snip - analysis by bill weinberg of the make-wifi-fast plan ....<br>
<br>
Here are my main impressions of the material you supplied and the<br>
efforts required:<br>
<br>
DIVERSE / DIFFUSE ACTION REQUIRED<br>
<br>
About 1/3 fto 1/2 of the concrete actions required/recommended can<br>
occur "organically", that is, through ad hoc and semi-organized<br>
efforts of individuals and small teams. The remaining work will<br>
require fairly dramatic engineering investments and also<br>
cross-industry changes in mindsets and practices - not something IMHO<br>
achievable without a paradigm shift (see below)<br>
<br>
BIGGEST CHALLENGES<br>
<br>
- binary blobs and open behavior: Even after 20 years of open source<br>
driving ecosystem expansion, key players remain incredibly guarded<br>
with regard to "their high-value IP" (herein intellectual property,<br>
not Internet Protocol), all the way down to low-level code in<br>
networking drivers. In this case I speak from very direct experience,<br>
in particular with semiconductor suppliers who service the WiFi<br>
marketplace. They are the real source of binary blobs, or more<br>
specifically, obfuscation and lack of access to chipset particulars<br>
and the code that should enable maximum wireless silicon ROI. These<br>
companies, for better or worse, are IP-driven and almost always<br>
IP-paranoid, even in / especially around otherwise open source<br>
settings. It will require a simultaneous carrot and stick approach to<br>
get them to abolish the blobs: a clear value proposition to fully<br>
open source drivers and exposed MAC and performance assist<br>
technologies, and an unpalatable onus for continuing business-as-usual<br>
<br>
- legacy / backward wireless standard interoperability: across the<br>
spectrum of IT we see how backward compatibility provides short-term<br>
business gain and long-term ecosystem pain. My favorite examples<br>
include the x86 architecture, the ARM architecture, HTML attributes,<br>
legacy encryption standards (now enabling back-off exploits), the US<br>
and IPv4 and support for 16 and 32 bit infrastructure in an<br>
increasingly 64 bit world. The WiFi document highlights how<br>
backward compatibility is killing WiFi performance. My suggestion is<br>
the establish a new "basement", wherein devices after a certain point<br>
will only support newer standards, with explicit provision on how to<br>
handle legacy with parallel tech, as was the case in the early days of<br>
WiFi (e.g., with USB-based and SD-interface devices vs. native ones)<br>
<br>
- Co-opting the WiFi Alliance: the WiFi brand is currently owned by<br>
the WiFi Alliance who, IMHO, think that they are doing a great job of<br>
managing the brand and of promoting WiFi evolution. Not.<br>
<br>
<br>
<br>
BIG SOLUTION<br>
<br>
I think the key is to "invent" a new WiFi. It might really use the<br>
most advanced versions of existing tech, but it would get a new name,<br>
and most importantly, new standards that encompass many/most of the<br>
micro-solutions outlined in Jim Getty's "Make WiFi Fast" document, as<br>
follows:<br>
<br>
- a clean transition to the most advanced, forward-looking spec cum standard<br>
<br>
- a consortium to (re)brand the new medium (call it Firefly or what<br>
you will) and establish ground rules for participation, enforced by<br>
branding rights:<br>
* no binary blobs ~ fully OSS drivers and other support code, up<br>
to a pre-defined level in the stack<br>
* driver coding standards for Linux, Windows and RTOSes to promote<br>
openness, anti-buffer bloat, etc.<br>
* specific provision for the use cases mentioned in Jim's document<br>
(e.g., multicast, mesh, IoT, etc. [pardon non orthogonal members])<br>
* specific rules on how to continue supporting legacy 802.11* with<br>
completely parallel infrastructure (albeit in same sorry band)<br>
* two (no less) strong founding members, comprised of one wireless<br>
chipset provider (of substance) and one OEM (ideal would be Intel and<br>
Cisco - dream on) and incentive for the rest of the gang to join on<br>
day 1 or 2<br>
* special extraordinary efforts to get Asia on board - China in<br>
particular - to participate (concessions probably required, esp.<br>
around security, as before)<br>
* start with a professional body management company (e.g., Global<br>
Inventures) but envision a small professional staff, especially to<br>
manage endowments and to instigate marketing<br>
* such a new group would need to 1) subsume the WiFi Alliance, 2)<br>
co-opt it and effectively take its place, or 3) find a way to<br>
complement the WiFi Alliance. The alternative is to stage a putsch<br>
and take over the WiFi Alliance from within, probably on the backs of<br>
key sponsoring members (see<br>
<a href="http://www.wi-fi.org/who-we-are/member-companies" rel="noreferrer" target="_blank">http://www.wi-fi.org/who-we-are/member-companies</a>) (am I overstating<br>
the actual importance of WFA?)<br>
<br>
...<br>
<br>
sincerely<br>
<span><font color="#888888"><br>
Dave Taht<br>
<a href="http://www.bufferbloat.net/projects/bloat/wiki/Daves_Media_Guidance" rel="noreferrer" target="_blank">http://www.bufferbloat.net/projects/bloat/wiki/Daves_Media_Guidance</a><br>
_______________________________________________<br>
bufferbloat-fcc-signers mailing list<br>
<a href="mailto:bufferbloat-fcc-signers@lists.redbarn.org" target="_blank">bufferbloat-fcc-signers@lists.redbarn.org</a><br>
<a href="http://lists.redbarn.org/mailman/listinfo/bufferbloat-fcc-signers" rel="noreferrer" target="_blank">http://lists.redbarn.org/mailman/listinfo/bufferbloat-fcc-signers</a><br>
</font></span></blockquote></div><br></div></div></div>
</blockquote></div><br></div>