From: "Jouni Malinen" <jkm@devicescape.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Jiri Benc <jbenc@suse.cz>, Michael Wu <flamingice@sourmilk.net>,
Larry Finger <larry.finger@lwfinger.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH V3] mac80211: Set low initial rate in rc80211_simple
Date: Fri, 8 Jun 2007 11:34:46 -0700 [thread overview]
Message-ID: <20070608183446.GJ14078@devicescape.com> (raw)
In-Reply-To: <43e72e890706081112k76e17827t4c66dbccdcee0e03@mail.gmail.com>
On Fri, Jun 08, 2007 at 02:12:57PM -0400, Luis R. Rodriguez wrote:
> On 6/8/07, Jouni Malinen <jkm@devicescape.com> wrote:
> >There are some odd cases, where disabling the lowest supported rate may
> >even be required due to regulatory rules..
> Just curious -- are you aware of a regulatory domain where this is the
> case? Who defines those rules? For example, AFAICT FCC only talk about
> power, and spectrum ranges. Where would I even look for these type of
> restrictions?
I don't remember all the details, but one case I've heard of was about
a rule that specified high bandwidth wireless operations and what
exactly would be high enough to be acceptable. And no, this was not
from FCC. Unfortunately, I do not have any good pointers for where to
look for this type of restrictions in an easy to use form (as in
something that I could easily understand ;-).
One related issue is the requirement for not transmitting continuously
for longer than a quite short time period before sensing the medium
again (this is from Japan). This may require at least fragmentation
based on TX rate (i.e., if low rate is used, fragmentation threshold
needs to be set lower) and in some cases, it may just be easier to drop
the lowest TX rates completely to avoid frames that may take long time
to transmit.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2007-06-08 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 3:03 [PATCH V3] mac80211: Set low initial rate in rc80211_simple Larry Finger
2007-06-08 3:38 ` Michael Wu
2007-06-08 3:49 ` Larry Finger
2007-06-08 5:05 ` Michael Wu
2007-06-08 9:21 ` Jiri Benc
2007-06-08 14:58 ` Jouni Malinen
2007-06-08 18:12 ` Luis R. Rodriguez
2007-06-08 18:34 ` Jouni Malinen [this message]
2007-06-08 20:10 ` Luis R. Rodriguez
2007-06-08 21:45 ` Jouni Malinen
2007-06-08 16:35 ` Michael Wu
2007-06-11 17:31 ` John W. Linville
2007-06-11 18:11 ` Michael Wu
2007-06-11 18:43 ` John W. Linville
2007-06-11 19:09 ` Michael Wu
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=20070608183446.GJ14078@devicescape.com \
--to=jkm@devicescape.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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).