linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benoit Papillault <benoit.papillault@free.fr>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Bruno Randolf <br1@einfach.org>,
	linville@tuxdriver.com, juuso.oikarinen@nokia.com,
	ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: mark 1, 2, 5.5 and 11Mbps as mandatory rates for 802.11b
Date: Thu, 27 May 2010 14:09:19 +0200	[thread overview]
Message-ID: <4BFE60EF.7020800@free.fr> (raw)
In-Reply-To: <1274947716.3669.13.camel@jlt3.sipsolutions.net>

Le 27/05/2010 10:08, Johannes Berg a écrit :
> On Thu, 2010-05-27 at 09:45 +0900, Bruno Randolf wrote:
>> IEEE802.11-2007 clause 18.2.3.3 (p640) states that 1, 2, 5.5&  11 Mbits are
>> mandatory rates for what they call High Rate direct sequence spread spectrum
>> (HR/DSSS) PHY (with long PLCP).
>
> You're confused. Clause 18 is 11g, we knew that those were mandatory
> there, see the code you're modifying.
>
> Clause 15 is 11b, and it shouldn't change.
>
> So NACK.
>
> johannes

I just dig through the various standards and besides there are still 
some grey areas in my mind (like what is HR/DSSS/PBCC mentioned in 
Clause 18 or DSSS-OFDM as specified in Clause 19, hopefully both are 
optional), we have :

802.11a = Clause 17, called OFDM
802.11b = Clause 15 (called DSSS) & Clause 18 (called HR/DSSS).
802.11g = Clause 19, called ERP with lots of variants : ERP-DSSS/CCK, 
ERP-OFDM, ERP-PBCC
802.11n = Clause 20, called HT for High Throughput, which also includes 
DUP-OFDM

Clause 15 defines 1 Mbits and 2 Mbits rates, long PLCP only
Clause 18 defines 5.5 Mbits and 11 Mbits. Optionally, short PLCP is 
available for 2 Mbits, 5.5 Mbits and 11 Mbits. Since it's optional, such 
short PLCP rates are probably not part of the mandatory rates.

Basic rate set must includes mandatory rates set. This is apparently 
what every other AP do today and I indeed see no points in adding more 
rates to the basic rate set other than what is already defined in the 
mandatory rate set (except we cannot rely on this rule when joining an 
existing BSS/IBSS, of course).

Does the patch you posted is intended to create a 802.11b only or 
802.11bg AP/IBSS with a 802.11g hardware for instance?

Regards,
Benoit

  parent reply	other threads:[~2010-05-27 12:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 12:48 [PATCHv2] mac80211: Fix basic rates for created IBSS networks Juuso Oikarinen
2010-05-26 12:53 ` Johannes Berg
2010-05-26 13:13   ` Juuso Oikarinen
2010-05-26 13:27     ` Johannes Berg
2010-05-27  4:50       ` Juuso Oikarinen
2010-05-26 14:14     ` Johannes Berg
2010-05-27  0:41       ` Bruno Randolf
2010-05-27  8:12         ` Johannes Berg
2010-05-27  0:45       ` [PATCH] mac80211: mark 1, 2, 5.5 and 11Mbps as mandatory rates for 802.11b Bruno Randolf
2010-05-27  6:02         ` [ath5k-devel] " Benoit Papillault
2010-05-27  8:08         ` Johannes Berg
2010-05-27  8:11           ` Johannes Berg
2010-05-27 12:09           ` Benoit Papillault [this message]
2010-05-27 12:13             ` Johannes Berg
2010-05-27  5:06       ` [PATCHv2] mac80211: Fix basic rates for created IBSS networks Juuso Oikarinen
2010-05-27  8:11         ` Johannes Berg
2010-05-27  8:28           ` Juuso Oikarinen

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=4BFE60EF.7020800@free.fr \
    --to=benoit.papillault@free.fr \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=br1@einfach.org \
    --cc=johannes@sipsolutions.net \
    --cc=juuso.oikarinen@nokia.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).