Re: [Make-wifi-fast] Fwd: [Battlemesh] BSS load element patch

[Dave Taht <dave.taht@gmail.com>]

the battlemesh threads are here:


http://ml.ninux.org/pipermail/battlemesh/2015-August/003645.html

http://ml.ninux.org/pipermail/battlemesh/2015-August/003745.html

On Fri, Aug 7, 2015 at 12:55 PM, Michael Welzl <michawe@ifi.uio.no> wrote:
> Hi,
>
> I find this intriguing:
>
>
>> On 07 Aug 2015, at 12:09, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> ---------- Forwarded message ----------
>> From: Paul Fuxjaeger <fuxjaeger@ftw.at>
>> Date: Fri, Aug 7, 2015 at 11:28 AM
>> Subject: Re: [Battlemesh] BSS load element patch
>> To: Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>
>>
>>
>> On 05.08.15 14:57, Bastian Bittorf wrote:
>>
>>> Does e.g. a client gets informed about a congested network
>>
>> Exactly.
>> It allows nearby clients/nodes to make MUCH better decisions. [1]
>
> Does anybody have information about how this is being used? Any examples?
>
> Cheers,
> Michael
>
>
>>
>>> or in other words: does it solve a problem?
>>
>> ###
>> Essentially, very small local channel utilization measurement reports
>> are broadcasted to all direct neighbors by piggybacking them onto
>> IEEE802.11 beacons. [2]
>> ###
>>
>> 1) Maintainers could better distinguish causes of link problems [3]
>> 2) Our current algorithms for rate control, routing and
>> network-selection could make better decisions if they have access this
>> "remote channel load" statistic.
>>
>> So, we think this feature could be really helpful. It increases the
>> networks capability to self-regulate, for a small price. [4]
>>
>>
>> -paul
>>
>> PS: Arthur did all the hard work, I'm just doing the cheap talking.
>>
>>
>>
>>
>>
>>
>> [1] that is probably the reason for recent AP models in the enterprise
>> segment already broadcasting it.
>>
>> [2] channel utilization measured at the receive antenna port of the
>> device that is sending that beacon.
>>
>> [3] if LTE-U/LAA/muLTEfire becomes widespread :( we need a way to detect
>> that such a nearby non-IEEE80211 source is blocking the channel.
>>
>> [4] Currently, OpenWRT sends around 200bytes PSDUs per beacon (depending
>> on mode etc). Assuming a 100ms beacon interval and 1Mbit/s, adding
>> these 7 bytes to them would increase the channel utilization each
>> beaconing node is generating by less than 0.06% of total airtime.
>>
>> _______________________________________________
>> Battlemesh mailing list
>> Battlemesh@ml.ninux.org
>> http://ml.ninux.org/mailman/listinfo/battlemesh
>>
>>
>> --
>> Dave Täht
>> worldwide bufferbloat report:
>> http://www.dslreports.com/speedtest/results/bufferbloat
>> And:
>> What will it take to vastly improve wifi for everyone?
>> https://plus.google.com/u/0/explore/makewififast
>> _______________________________________________
>> Make-wifi-fast mailing list
>> Make-wifi-fast@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>



-- 
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast