From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@cozybit.com>
Cc: Jouni Malinen <j@w1.fi>,
linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH 5/5] mac80211: mesh beacon includes TIM IE
Date: Fri, 15 Jul 2011 12:00:23 +0200 [thread overview]
Message-ID: <1310724023.4164.22.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAG6hwVN3HED+LZdKN0zpNfjmK9FmBuBWnZ0qe9gYTPPYmCedTg@mail.gmail.com> (sfid-20110714_221703_735281_4D5F9F4B)
On Thu, 2011-07-14 at 13:16 -0700, Thomas Pedersen wrote:
> On Wed, Jul 13, 2011 at 11:25 PM, Jouni Malinen <j@w1.fi> 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?
johannes
next prev parent reply other threads:[~2011-07-15 10:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 23:45 [PATCH 0/5] mac80211: mesh beaconing Thomas Pedersen
2011-07-13 23:45 ` [PATCH 1/5] mac80211: give if_mesh a beacon Thomas Pedersen
2011-07-14 9:50 ` Johannes Berg
2011-07-15 9:45 ` Johannes Berg
2011-07-15 18:36 ` Thomas Pedersen
2011-07-15 18:41 ` Johannes Berg
2011-07-15 9:54 ` Johannes Berg
2011-07-15 19:30 ` Thomas Pedersen
2011-07-15 21:00 ` Johannes Berg
2011-07-17 17:36 ` Thomas Pedersen
2011-07-18 7:34 ` Johannes Berg
2011-07-13 23:45 ` [PATCH 2/5] mac80211: correct mesh beacon head Thomas Pedersen
2011-07-15 9:57 ` Johannes Berg
2011-07-15 18:44 ` Thomas Pedersen
2011-07-15 21:00 ` Johannes Berg
2011-07-13 23:45 ` [PATCH 3/5] mac80211: Ext. Supported Rates go in mesh beacon tail Thomas Pedersen
2011-07-15 9:58 ` Johannes Berg
2011-07-15 19:31 ` Thomas Pedersen
2011-07-13 23:45 ` [PATCH 4/5] mac80211: move RSN IE to tail of mesh beacon Thomas Pedersen
2011-07-14 9:51 ` Johannes Berg
2011-07-15 0:50 ` [PATCH v2 " Thomas Pedersen
2011-07-15 9:07 ` Johannes Berg
2011-07-15 18:49 ` Thomas Pedersen
2011-07-13 23:45 ` [PATCH 5/5] mac80211: mesh beacon includes TIM IE Thomas Pedersen
2011-07-14 6:25 ` Jouni Malinen
2011-07-14 20:16 ` Thomas Pedersen
2011-07-15 10:00 ` Johannes Berg [this message]
2011-07-18 14:11 ` Javier Cardona
2011-07-18 15:07 ` Johannes Berg
2011-07-14 9:52 ` Johannes Berg
2011-07-14 19:20 ` Thomas Pedersen
2011-07-15 10:50 ` [PATCH 0/5] mac80211: mesh beaconing Max Filippov
2011-07-15 18:17 ` Thomas Pedersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1310724023.4164.22.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=thomas@cozybit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).