From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
linux-wireless@vger.kernel.org, victorg@ti.com,
linville@tuxdriver.com, kgiori@qca.qualcomm.com,
adrian@freebsd.org, j@w1.fi, coelho@ti.com, igalc@ti.com,
nbd@nbd.name, mathias.kretschmer@fokus.fraunhofer.de,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [PATCHv6 0/6] Add DFS master ability
Date: Mon, 21 Jan 2013 11:46:20 +0100 [thread overview]
Message-ID: <50FD1C7C.5050606@neratec.com> (raw)
In-Reply-To: <1358546933.7922.49.camel@jlt4.sipsolutions.net>
On 01/18/2013 11:08 PM, Johannes Berg wrote:
> Hi,
>
>> As stated before: "available until ..." time is not neccessary as far
>> as I know. Also the channel must stay available when AP stops operation,
>> I'll change that.
>
> Yeah, I checked the documents myself now ... strange, but hey. Radars
> are fixed installations and mostly active continually, so I guess they
> figured it was no big deal.
>
We were also unsure if this makes sense and contacted regulatory for
clarification. Indeed, with the current document a scenario where "I switched to a
DFS channel and skipped CAC because I passed one half a year ago" is fully
compliant. Practically, when you set up a new AP and do once a CAC for each DFS
channel during installation time, you don't need to do a CAC ever again (as long
as you do not see radars).
Why then bother with CAC at all, one might think. In fact, exploiting given
requirements to such extent is mandatory to make operation on DFS channels usable
(which btw. is not the scope of the patches discussed here).
> [...]
>
> johannes
>
next prev parent reply other threads:[~2013-01-21 10:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 13:04 [PATCHv6 0/6] Add DFS master ability Simon Wunderlich
2013-01-08 13:04 ` [PATCHv6 1/6] nl80211: check if channel can be used in join_ibss Simon Wunderlich
2013-01-16 22:35 ` Johannes Berg
2013-01-17 13:27 ` Simon Wunderlich
2013-01-08 13:04 ` [PATCHv6 2/6] cfg80211: check radar interface combinations Simon Wunderlich
2013-01-16 22:42 ` Johannes Berg
2013-01-16 22:44 ` Johannes Berg
2013-01-17 13:28 ` Simon Wunderlich
2013-01-30 16:34 ` Luciano Coelho
2013-01-30 16:56 ` Simon Wunderlich
2013-01-30 17:20 ` Luciano Coelho
2013-01-08 13:04 ` [PATCHv6 3/6] nl80211/cfg80211: add radar detection command/event Simon Wunderlich
2013-01-16 22:51 ` Johannes Berg
2013-01-17 13:40 ` Simon Wunderlich
2013-01-18 21:54 ` Johannes Berg
2013-01-21 10:44 ` Zefir Kurtisi
2013-01-23 12:49 ` Simon Wunderlich
2013-01-24 12:56 ` Zefir Kurtisi
2013-01-08 13:04 ` [PATCHv6 4/6] mac80211: " Simon Wunderlich
2013-01-16 22:59 ` Johannes Berg
2013-01-17 13:52 ` Simon Wunderlich
2013-01-18 22:00 ` Johannes Berg
2013-01-23 12:42 ` Simon Wunderlich
2013-01-08 13:04 ` [PATCHv6 5/6] mac80211: check radar interaction with scan and roc Simon Wunderlich
2013-01-16 23:00 ` Johannes Berg
2013-01-17 13:53 ` Simon Wunderlich
2013-01-08 13:04 ` [PATCHv6 6/6] nl80211: allow DFS in start_ap Simon Wunderlich
2013-01-16 23:22 ` [PATCHv6 0/6] Add DFS master ability Johannes Berg
2013-01-17 14:21 ` Simon Wunderlich
2013-01-18 22:08 ` Johannes Berg
2013-01-21 10:46 ` Zefir Kurtisi [this message]
2013-01-23 12:52 ` Simon Wunderlich
2013-01-24 12:19 ` Zefir Kurtisi
2013-01-23 12:57 ` Simon Wunderlich
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=50FD1C7C.5050606@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=adrian@freebsd.org \
--cc=coelho@ti.com \
--cc=igalc@ti.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=nbd@nbd.name \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=victorg@ti.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).