From: Seth Forshee <seth.forshee@canonical.com>
To: Ryan Mounce <ryan@mounce.com.au>
Cc: wireless-regdb@lists.infradead.org,
linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH v2] wireless-regdb: Update rules for Australia (AU) and add 60GHz rules
Date: Thu, 23 Feb 2017 09:35:32 -0600 [thread overview]
Message-ID: <20170223153532.GA3479@ubuntu-hedt> (raw)
In-Reply-To: <20170223135253.1681-1-ryan@mounce.com.au>
On Fri, Feb 24, 2017 at 12:22:53AM +1030, Ryan Mounce wrote:
> Sourced from the current legislation at
> https://www.legislation.gov.au/Details/F2016C00432
>
> The current rules exceed legal limits between 5250-5330MHz, and permit
> illegal operation in 5600-5650MHz (disallowed regardless of DFS).
>
> Frequency ranges and EIRP limits for all ranges have been updated to
> match items 59-63, 65 in the linked document. As the rules for AU have
> never previously mirrored local regulations, changes include a
> significant increase in the allowable 2.4GHz EIRP and smaller increases
> in most other bands.
>
> In order to allow 80MHz operation between 5650-5730MHz (bordering two
> bands) the lower, more restrictive band has been rounded up by 5MHz.
>
> Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
> ---
> db.txt | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/db.txt b/db.txt
> index 05108e0..00e81b6 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -85,12 +85,17 @@ country AT: DFS-ETSI
> # 60 GHz band channels 1-4, ref: Etsi En 302 567
> (57000 - 66000 @ 2160), (40)
>
> +# Source:
> +# https://www.legislation.gov.au/Details/F2016C00432
> +# Both DFS-ETSI and DFS-FCC are acceptable per AS/NZS 4268 Appendix B
> country AU: DFS-ETSI
> - (2402 - 2482 @ 40), (20)
> - (5170 - 5250 @ 80), (17), AUTO-BW
> - (5250 - 5330 @ 80), (24), DFS, AUTO-BW
> - (5490 - 5710 @ 160), (24), DFS
> - (5735 - 5835 @ 80), (30)
> + (2400 - 2483.5 @ 40), (36)
The mention of ETSI EN 300 328 in item 55 (a) leads me to believe that
this is the limit we should be using, i.e. 500 mW. It is a bit confusing
though since it seems like such devices would also fall under "digital
modulation transmitters."
> + (5150 - 5250 @ 80), (23), NO-OUTDOOR, AUTO-BW
This looks correct.
> + (5250 - 5350 @ 80), (23), NO-OUTDOOR, AUTO-BW, DFS
Since this range requires TPC we need to set the power limit at 100 mW.
> + (5470 - 5600 @ 80), (30), DFS
> + (5650 - 5730 @ 80), (30), DFS
These ranges also require TPC so we need to set the limit at 500 mW.
> + (5730 - 5850 @ 80), (36)
In the document the ranges are 5650-5725 MHz and 5725-5850 MHz. I
suspect that the existing rules fudge that to line up with the wifi
channels, which technically is okay because the rules in the former
range are more restrictive. I wonder if we shouldn't be recording them
here as per the document and adding AUTO-BW. Johannes, any thoughts?
> + (57000 - 66000 @ 2160), (43), NO-OUTDOOR
This looks correct.
Thanks,
Seth
WARNING: multiple messages have this Message-ID (diff)
From: Seth Forshee <seth.forshee@canonical.com>
To: Ryan Mounce <ryan@mounce.com.au>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] [PATCH v2] wireless-regdb: Update rules for Australia (AU) and add 60GHz rules
Date: Thu, 23 Feb 2017 09:35:32 -0600 [thread overview]
Message-ID: <20170223153532.GA3479@ubuntu-hedt> (raw)
In-Reply-To: <20170223135253.1681-1-ryan@mounce.com.au>
On Fri, Feb 24, 2017 at 12:22:53AM +1030, Ryan Mounce wrote:
> Sourced from the current legislation at
> https://www.legislation.gov.au/Details/F2016C00432
>
> The current rules exceed legal limits between 5250-5330MHz, and permit
> illegal operation in 5600-5650MHz (disallowed regardless of DFS).
>
> Frequency ranges and EIRP limits for all ranges have been updated to
> match items 59-63, 65 in the linked document. As the rules for AU have
> never previously mirrored local regulations, changes include a
> significant increase in the allowable 2.4GHz EIRP and smaller increases
> in most other bands.
>
> In order to allow 80MHz operation between 5650-5730MHz (bordering two
> bands) the lower, more restrictive band has been rounded up by 5MHz.
>
> Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
> ---
> db.txt | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/db.txt b/db.txt
> index 05108e0..00e81b6 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -85,12 +85,17 @@ country AT: DFS-ETSI
> # 60 GHz band channels 1-4, ref: Etsi En 302 567
> (57000 - 66000 @ 2160), (40)
>
> +# Source:
> +# https://www.legislation.gov.au/Details/F2016C00432
> +# Both DFS-ETSI and DFS-FCC are acceptable per AS/NZS 4268 Appendix B
> country AU: DFS-ETSI
> - (2402 - 2482 @ 40), (20)
> - (5170 - 5250 @ 80), (17), AUTO-BW
> - (5250 - 5330 @ 80), (24), DFS, AUTO-BW
> - (5490 - 5710 @ 160), (24), DFS
> - (5735 - 5835 @ 80), (30)
> + (2400 - 2483.5 @ 40), (36)
The mention of ETSI EN 300 328 in item 55 (a) leads me to believe that
this is the limit we should be using, i.e. 500 mW. It is a bit confusing
though since it seems like such devices would also fall under "digital
modulation transmitters."
> + (5150 - 5250 @ 80), (23), NO-OUTDOOR, AUTO-BW
This looks correct.
> + (5250 - 5350 @ 80), (23), NO-OUTDOOR, AUTO-BW, DFS
Since this range requires TPC we need to set the power limit at 100 mW.
> + (5470 - 5600 @ 80), (30), DFS
> + (5650 - 5730 @ 80), (30), DFS
These ranges also require TPC so we need to set the limit at 500 mW.
> + (5730 - 5850 @ 80), (36)
In the document the ranges are 5650-5725 MHz and 5725-5850 MHz. I
suspect that the existing rules fudge that to line up with the wifi
channels, which technically is okay because the rules in the former
range are more restrictive. I wonder if we shouldn't be recording them
here as per the document and adding AUTO-BW. Johannes, any thoughts?
> + (57000 - 66000 @ 2160), (43), NO-OUTDOOR
This looks correct.
Thanks,
Seth
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2017-02-23 15:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 6:35 [PATCH] wireless-regdb: Update rules for Australia (AU) and add 60GHz rules Ryan Mounce
2017-02-18 6:35 ` [wireless-regdb] " Ryan Mounce
2017-02-18 20:45 ` Sebastian Gottschall
2017-02-18 20:45 ` [wireless-regdb] " Sebastian Gottschall
2017-02-19 0:01 ` Ryan Mounce
2017-02-19 0:01 ` [wireless-regdb] " Ryan Mounce
2017-02-19 12:16 ` Sebastian Gottschall
2017-02-19 12:16 ` [wireless-regdb] " Sebastian Gottschall
2017-02-19 12:36 ` Ryan Mounce
2017-02-19 12:36 ` [wireless-regdb] " Ryan Mounce
2017-02-22 21:30 ` Seth Forshee
2017-02-22 21:30 ` [wireless-regdb] " Seth Forshee
2017-02-22 23:05 ` Ryan Mounce
2017-02-22 23:05 ` [wireless-regdb] " Ryan Mounce
2017-02-23 5:58 ` Johannes Berg
2017-02-23 5:58 ` [wireless-regdb] " Johannes Berg
2017-02-23 13:01 ` Seth Forshee
2017-02-23 13:01 ` [wireless-regdb] " Seth Forshee
2017-02-23 13:52 ` [PATCH v2] " Ryan Mounce
2017-02-23 13:52 ` [wireless-regdb] " Ryan Mounce
2017-02-23 15:35 ` Seth Forshee [this message]
2017-02-23 15:35 ` Seth Forshee
2017-02-24 2:50 ` Ryan Mounce
2017-02-24 2:50 ` [wireless-regdb] " Ryan Mounce
2017-02-24 14:55 ` Seth Forshee
2017-02-24 14:55 ` [wireless-regdb] " Seth Forshee
2017-02-25 3:10 ` [PATCH v3] " Ryan Mounce
2017-02-25 3:10 ` [wireless-regdb] " Ryan Mounce
2017-03-01 14:59 ` Seth Forshee
2017-03-01 14:59 ` [wireless-regdb] " Seth Forshee
2017-03-07 13:11 ` Seth Forshee
2017-03-07 13:11 ` [wireless-regdb] " Seth Forshee
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=20170223153532.GA3479@ubuntu-hedt \
--to=seth.forshee@canonical.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ryan@mounce.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.