From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Daniel Drake <dsd@gentoo.org>, Felix Fietkau <nbd@openwrt.org>
Subject: Re: [RFC] mac80211: fix short preamble determination
Date: Mon, 13 Oct 2008 21:11:56 +0300 [thread overview]
Message-ID: <20081013181156.GC30095@jm.kir.nu> (raw)
In-Reply-To: <1223921012.10113.5.camel@johannes.berg>
On Mon, Oct 13, 2008 at 08:03:32PM +0200, Johannes Berg wrote:
> > Well, if you have many such devices, yes, but one might try to live
> > without such protection if there are some with very limited transmit
> > needs.
>
> Would you then announce short preamble as the AP? That'd mean all other
> stations would use short preamble and the poor non-short-preamble STA
> would be left completely in the dark wrt. its NAV.
Yes, indeed. In other words, this would be something that could work
mostly in cases where there is a STA with very limited needs (e.g., send
measurement results once an hour, etc.). I'm not aware of any such
deployment, though.
> Ohh. Just a few days ago I sent an email with a request for
> interpretation (there really just is a typo in 802.11-2007 but...) That
> got forwarded around a lot, but I guess at least TGmb will see it :)
Yeah.. I'm sure it will show up in TGmb in Dallas meeting (mid-Nov). It
might even get fixed eventually the 802.11-2010 (or 2011, or 2012, or
who knows when.. ;-).
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2008-10-13 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 8:26 [RFC] mac80211: fix short preamble determination Johannes Berg
2008-10-13 15:59 ` Jouni Malinen
2008-10-13 17:31 ` Johannes Berg
2008-10-13 17:54 ` Jouni Malinen
2008-10-13 18:03 ` Johannes Berg
2008-10-13 18:11 ` Jouni Malinen [this message]
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=20081013181156.GC30095@jm.kir.nu \
--to=j@w1.fi \
--cc=dsd@gentoo.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
/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