netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jouni Malinen <jkm@devicescape.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] Geographical/regulatory information for ieee80211
Date: Fri, 14 Apr 2006 15:01:20 -0500	[thread overview]
Message-ID: <443FFF90.7030204@lwfinger.net> (raw)
In-Reply-To: <20060414152715.GC29461@instant802.com>

Jouni Malinen wrote:
> The maximum power would be quite useful--I would say required--part of
> regulatory domain information.. In other words, I would like to see the
> groups created in a way that would take differences in power limits into
> account. Without this, the groups will need to be re-created at some
> point in the future when IEEE 802.11d and IEEE 802.11h would like to use
> the same table.. In addition, flag of specifying indoor/outdoor/both
> would be a nice addition.
> 
> It would be useful to have a text file with all the information in an
> easily parseable format. I would like to be able to add a user space
> tool that uses this file to take care of channel/TX power policies. The
> needed parameters would then be configured for the kernel side 802.11
> whenever needed.

Good idea to include power and indoor etc. flags. I will also include flags to indicate that 
scanning should be passive on a given channel.

Have you any thoughts on the structure of the text file for parsing?

Larry



  reply	other threads:[~2006-04-14 20:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14  0:59 [RFC] Geographical/regulatory information for ieee80211 Larry Finger
2006-04-14 11:41 ` Ulrich Kunitz
2006-04-14 11:58   ` Faidon Liambotis
2006-04-14 15:27 ` Jouni Malinen
2006-04-14 20:01   ` Larry Finger [this message]
2006-04-15 17:07   ` Faidon Liambotis
2006-04-15 17:47 ` Christoph Hellwig
2006-04-17 17:55   ` Rick Jones
2006-04-27  0:54     ` Larry Finger
2006-04-28 11:17       ` Harald Welte
2006-04-29  0:31       ` Jouni Malinen

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=443FFF90.7030204@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=jkm@devicescape.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).