From: Seth Forshee <seth.forshee@canonical.com>
To: Zefir Kurtisi <zefir.kurtisi@neratec.com>
Cc: Wei Zhong <wzhong@google.com>,
wireless-regdb@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: wireless-regdb: update CA rules for 5600 - 5650 mHz
Date: Thu, 9 Jul 2015 09:04:17 -0500 [thread overview]
Message-ID: <20150709140417.GA142895@ubuntu-hedt> (raw)
In-Reply-To: <559CF926.8000508@neratec.com>
On Wed, Jul 08, 2015 at 12:19:18PM +0200, Zefir Kurtisi wrote:
> My claim is that in its current state the regdb does not exactly formalize the
> limitations given by regulatory for a simple reason: it uses channel semantics
> where it should only handle frequency ranges. Take the discussed rules for CA at
> hand: while the linked document considers frequencies from 5150 to 5350, the
> according rule for CA is defined as (5170 - 5250 @ 80). Why 5170 instead of 5150?
> Because we know there is no channel defined below 5170 - but why do we need to
> embed this information as a rule when it is already handled by SW?
>
> In the current regdb, both semantics are used, e.g. UA (5150-5350) vs. CA
> (5170-5250) or ES (5470-5725) vs. FI (5490-5710)).
I'm not surprised. I don't know that anyone has given it that much
thought before.
> This might sound like an irrelevant difference, but here is why it matters: the
> above mentioned rules for ES and FI would give the same channel lists - as long as
> we think in HT20 and HT40. But only ES gives access to 10 and 5MHz operation on
> channel 144.
Good example.
> My bottom line is: regulatory rules must not contain channel semantics - this is
> done by the SW. Rules must be a literal formalization of the country's regulatory,
> which always uses frequency ranges within defined band edges.
I'm generally in agreement. I'll try to pay closer attention to this in
the future.
> Sorry for this going off-topic. It has nothing to do with the changes proposed by
> Wei, but is more about something to keep in mind when considering upcoming support
> for narrow band channels at band edges.
Except that it seems to have inspired Wei to change the patch to do
exactly what you're arguing against ;-)
Seth
prev parent reply other threads:[~2015-07-09 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 5:44 wireless-regdb: update CA rules for 5600 - 5650 mHz Wei Zhong
2015-07-02 13:48 ` Seth Forshee
2015-07-02 14:21 ` Wei Zhong
2015-07-02 14:31 ` Seth Forshee
2015-07-03 11:08 ` Zefir Kurtisi
2015-07-03 14:20 ` Wei Zhong
2015-07-03 15:01 ` Zefir Kurtisi
2015-07-06 13:27 ` Seth Forshee
2015-07-06 14:40 ` Zefir Kurtisi
2015-07-06 17:13 ` Wei Zhong
2015-07-07 20:11 ` Seth Forshee
2015-07-08 10:19 ` Zefir Kurtisi
2015-07-09 14:04 ` Seth Forshee [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=20150709140417.GA142895@ubuntu-hedt \
--to=seth.forshee@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wireless-regdb@lists.infradead.org \
--cc=wzhong@google.com \
--cc=zefir.kurtisi@neratec.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