On Fri, Jul 15, 2011 at 3:00 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Thu, 2011-07-14 at 13:16 -0700, Thomas Pedersen wrote: >> On Wed, Jul 13, 2011 at 11:25 PM, Jouni Malinen <j@xxxxx> wrote: >> > On Wed, Jul 13, 2011 at 04:45:47PM -0700, Thomas Pedersen wrote: >> >> Even though we don't currently implement PS for mesh points, the >> >> standard asks us to include a TIM element in beacons. Include an empty >> >> element for now. >> > >> > Is it allowed to not support PS in this type of case? AP does not have >> > such option.. >> > >> >> You're right, it doesn't look like PS support is optional. The >> standard requires us to respect the PS states of peers. Support for >> this will require some work, but in the meantime, we can include a TIM >> element indicating no frames buffered here, as well as a Mesh Awake >> Window which never expires. >> >> Otherwise, until we implement proper PS, might it be better not to >> include the TIM IE at all? > > Or just not pretend to support the latest mesh draft ... > > I don't think PS support can be hard. We have all of it in AP mode > anyway, so you just need to generalise that a bit, maybe refactor like I > said in my other email, and you should be able to get it up & running > pretty quickly? Mesh frame buffering can probably reuse most of the AP mode, yes. The difficult part is on the receiving STA as it must track the beacon transmit times of each mesh peer. I don't know how/if we can implement this in a vendor-neutral mac80211ish sort of way. That said, only buffering seems to be mandatory: "A mesh STA SHALL have the capability to buffer frames and to perform mesh power mode tracking" but "A mesh STA MAY use mesh power modes to reduce its power consumption". Cheers, Javier -- Javier Cardona cozybit Inc. http://www.cozybit.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
