Wireless-regdb Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: "Bjørn Mork" <bjorn@mork.no>,
	"Dmitry Ivanov" <dmitrijs.ivanovs@ubnt.com>
Cc: wireless-regdb@lists.infradead.org,
	Peter Gent <Peter.Gent@mbie.govt.nz>,
	Jouni Malinen <jouni@qca.qualcomm.com>
Subject: Re: [wireless-regdb] [PATCH] Specify Australian DFS region as DFS-ETSI
Date: Tue, 5 May 2015 16:09:24 -0500	[thread overview]
Message-ID: <20150505210924.GB109672@ubuntu-hedt> (raw)
In-Reply-To: <87d22f8f4d.fsf@nemi.mork.no>

On Tue, May 05, 2015 at 12:58:58PM +0200, Bjørn Mork wrote:
> Jouni Malinen <jouni@qca.qualcomm.com> writes:
> > On Tue, May 05, 2015 at 11:32:16AM +0300, Dmitry Ivanov wrote:
> >> Currently, DFS region for Australia is not specified. This prevents starting AP with AU country code on DFS-affected channel in 5 GHz band with latest cfg80211 and hostapd because there is an explicit check for such condition.
> >> 
> >> This patch specifies DFS region for Australia as DFS-ETSI. Alternatively, DFS-FCC can be used.
> >
> > I would have used DFS-FCC here unless you have a clear indication of
> > DFS-ETSI being closer to requirements. In addition, there should be a
> > Signed-off-by: tag in the commit log as described in the CONTRIBUTING
> > file.
> 
> From what I can gather from
> http://www.comlaw.gov.au/Details/F2014L01253
> the details are hidden in the standard "AS/NZS 4268:2012". The scope
> here:
>   http://shop.standards.co.nz/catalog/4268:2012%28AS|NZS%29/scope?
> shows the existence of an appendix "B" titled
> 
>  "DYNAMIC FREQUENCY SELECTION (DFS) AND TRANSMIT POWER CONTROL (TPC)
>   REQUIREMENTS FOR RADIO LOCAL AREA NETWORK (RLAN) TRANSMITTERS
>   OPERATING IN 5250 TO 5350 MHz OR 5470 TO 5725 MHz"
> 
> But I'm afraid you'll have to buy the standard to get the full details...
> 
> Given hysterical raisins, and the general tendency to reference ETSI
> standards and ERC decisions, I'd say that DFS-ETSI is more likely.  Why
> would they use FCC rules?
> 
> But it should probably be kept aligned with the NZ entry, which
> currently is DFS-FCC.  Don't know the source of that, though.  Could
> very well be wrong...  Ref the "EN 301 893 V1.7.1" alternative given
> here:  https://gazette.govt.nz/notice/id/2015-go694

That's the most official-looking (free) source of information I could
trun up as well.

Dmitry, you site AS/NZS 4268 as your source - do you have access to
this, and can you confirm that the requirements are closest to DFS-ETSI?
It would be great if someone else with access to the document could ack
this as well, since at first blush this appears to be in contradiction
to Peter's email.

I agree that it doesn't seem to make any sense for Australia and New
Zealand to be different here. So if Australia is specified to use
DFS-ETSI I think New Zealand should be changed to use it as well.

Thanks,
Seth

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb

  reply	other threads:[~2015-05-05 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05  8:32 [wireless-regdb] [PATCH] Specify Australian DFS region as DFS-ETSI Dmitry Ivanov
2015-05-05  8:48 ` Jouni Malinen
2015-05-05 10:58   ` Bjørn Mork
2015-05-05 21:09     ` Seth Forshee [this message]
2015-05-06  8:16       ` Dmitrijs Ivanovs
2015-05-06 15:57         ` Seth Forshee
2015-05-07  8:16           ` [wireless-regdb] [PATCH] Change DFS domain to DFS-ETSI for Australia and New Zealand Dmitry Ivanov
2015-05-07 13:37             ` Seth Forshee
2015-05-15 12:48             ` Seth Forshee
  -- strict thread matches above, loose matches on Subject: below --
2015-05-05  9:07 [wireless-regdb] [PATCH] Specify Australian DFS region as DFS-ETSI Dmitry Ivanov

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=20150505210924.GB109672@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=Peter.Gent@mbie.govt.nz \
    --cc=bjorn@mork.no \
    --cc=dmitrijs.ivanovs@ubnt.com \
    --cc=jouni@qca.qualcomm.com \
    --cc=wireless-regdb@lists.infradead.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