linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 14:45:34 -0700	[thread overview]
Message-ID: <20070608214534.GB26702@devicescape.com> (raw)
In-Reply-To: <43e72e890706081310j47ed891cl1ebb132e65517db3@mail.gmail.com>

On Fri, Jun 08, 2007 at 04:10:10PM -0400, Luis R. Rodriguez wrote:
> On 6/8/07, Jouni Malinen <jkm@devicescape.com> wrote:

> >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).

> Wow, aren't those regulatory requirements breaking the spec? I wonder
> if loading a different rate algorithm depending on regdomain would do
> the job in a case like this.

What do you mean by breaking the spec? Local regulations come first and
whatever is to be used to transmit better comply with those no matter
what the IEEE 802.11 standard says. Just using a different rate
algorithm may not be enough to handle this kind of cases. There needs
to be a way to enforce some rules like the maximum continuous
transmission at a lower layer and somehow adjust the parameters if
needed.

This particular rule may not be too much of an issue for now since it
came up in a case where non-standard TX rate were used (i.e., something
below the minimum used in 802.11a). Anyway, we should try to be able to
handle whatever rules comes up now or in the future. Of course, one way
of handling limitations is not to allow transmissions at all, but that
may not always be the ideal solution.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2007-06-08 21:45 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
2007-06-08 20:10               ` Luis R. Rodriguez
2007-06-08 21:45                 ` Jouni Malinen [this message]
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=20070608214534.GB26702@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).