All of lore.kernel.org
 help / color / mirror / Atom feed
* [wireless-regdb] [RFC] wireless-regdb: Update rules for 2.4GHz limit Republic of Korea (KR)
@ 2017-09-14 14:49 Andreas Mohr
  2017-09-26 15:12 ` Andreas Mohr
  2017-09-26 20:16 ` Seth Forshee
  0 siblings, 2 replies; 7+ messages in thread
From: Andreas Mohr @ 2017-09-14 14:49 UTC (permalink / raw)
  To: Seth Forshee; +Cc: wireless-regdb

Dear Sir / Madam,

we have initiated a WiFi SAR/RF testing/certification effort of our current device
(handheld, TI WL1271 WLAN/Bluetooth BLE module, current Linux distribution: Ubuntu 12.04 LTS, to be modernized).

During our activities with Korean KC certification body, the following request has been made (TÜV Korea):

Mail 2016-06-14:
"
Please keep the power limit of less than 20mW as sent in our previous e-mail (if not fulfilled, the test will be failed).
<red>Please do not send out samples before it complies to the requirement.</red>
"

20mW equals 13dBm.

We already successfully applied a modified signed regulatory.bin to have (and thus use) the reduced limit,
however obviously we'd strongly prefer to have an official upstream release binary which:
- where not up-to-date (e.g. older distribution base) can be custom-applied
- where already up-to-date vs. upstream implicitly does have/receive all necessary future updates
- is signed with official wireless-regdb / distro keys

We then asked for a paper trail (specs document, black-and-white dead-tree notice etc.)
in order to file a thoroughly/legitimately claimed request for conformance update of wireless-regdb
(simply due to properly knowing the root cause / explanation for this request!
Details on why this limit has been imposed, when it got required, which modulation types it applies to, ...),
however that turned out to be difficult.
We ultimately succeeded in receiving the proper reference (Korean document, available upon request)
which lists the 20mW requirement.

Also, a prior Internet search for
"dBm site:rra.go.kr" had resulted in
https://www.rra.go.kr/FileDownSvl?file_type=research2&file_parentseq=1044&file_seq=1
(4.ÀüÀÚÆÄÀÎüº¸È£´ëÃ¥¿¬±¸.pdf , a nice UTF-8 mis-transcoding of originally Korean cp949 4.체호책.pdf 4.[uCCB4 uD638 uCC45].pdf)
which appears to list device measurements, and where notably
many 802.11g values of various company device models appear to be restricted to the 13dBm (i.e., 20mW) area.


Due to other delays, this issue has not been pursued here (sorry!).
Unfortunately it looks like
wireless-regdb HEAD (9b3317bd4) does not yet have any change which would fulfill this certification requirement.

Thus, I am now proposing (RFC) the following minimum (potentially extended/documented) update.
I decided to restrict the limitation to 2.4GHz area only since
the current certification effort (and thus the limit request) is about 2.4GHz.

Thank you!

Yours sincerely

Andreas Mohr


From 0added12024197148e87633c28959334795cbd02 Mon Sep 17 00:00:00 2001
From: Andreas Mohr <andim2@users.sf.net>
Date: Wed, 13 Sep 2017 11:51:54 +0200
Subject: [PATCH] wireless-regdb: reduce power level limit of KR (Korea)
 802.11b/g/n to the certification-requested "20mW" (13dBm).

Signed-off-by: Andreas Mohr <andim2@users.sf.net>
---
 db.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db.txt b/db.txt
index e48f9a6..97b22b0 100644
--- a/db.txt
+++ b/db.txt
@@ -668,7 +668,7 @@ country KP: DFS-JP
 	(5735 - 5815 @ 20), (30)
 
 country KR: DFS-JP
-	(2402 - 2482 @ 40), (20)
+	(2402 - 2482 @ 40), (13)
 	(5170 - 5250 @ 80), (20), AUTO-BW
 	(5250 - 5330 @ 80), (20), DFS, AUTO-BW
 	(5490 - 5710 @ 160), (30), DFS
-- 
2.9.5


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

^ permalink raw reply related	[flat|nested] 7+ messages in thread

* Re: [wireless-regdb] [RFC] wireless-regdb: Update rules for 2.4GHz limit Republic of Korea (KR)
  2017-09-14 14:49 [wireless-regdb] [RFC] wireless-regdb: Update rules for 2.4GHz limit Republic of Korea (KR) Andreas Mohr
@ 2017-09-26 15:12 ` Andreas Mohr
  2017-09-26 18:49   ` Seth Forshee
  2017-09-26 20:16 ` Seth Forshee
  1 sibling, 1 reply; 7+ messages in thread
From: Andreas Mohr @ 2017-09-26 15:12 UTC (permalink / raw)
  To: Andreas Mohr; +Cc: Seth Forshee, wireless-regdb

Dear Sir / Madam,

On Thu, Sep 14, 2017 at 04:49:42PM +0200, Andreas Mohr wrote:
> Dear Sir / Madam,
> 
> we have initiated a WiFi SAR/RF testing/certification effort of our current device
> (handheld, TI WL1271 WLAN/Bluetooth BLE module, current Linux distribution: Ubuntu 12.04 LTS, to be modernized).
> 
> During our activities with Korean KC certification body, the following request has been made (TÜV Korea):
> 
> Mail 2016-06-14:
> "
> Please keep the power limit of less than 20mW as sent in our previous e-mail (if not fulfilled, the test will be failed).
> <red>Please do not send out samples before it complies to the requirement.</red>
> "
> 
> 20mW equals 13dBm.

Any thoughts on my change request? Further input needed?

Thank you!

Yours sincerely

Andreas Mohr

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [wireless-regdb] [RFC] wireless-regdb: Update rules for 2.4GHz limit Republic of Korea (KR)
  2017-09-26 15:12 ` Andreas Mohr
@ 2017-09-26 18:49   ` Seth Forshee
  0 siblings, 0 replies; 7+ messages in thread
From: Seth Forshee @ 2017-09-26 18:49 UTC (permalink / raw)
  To: Andreas Mohr; +Cc: Andreas Mohr, wireless-regdb

On Tue, Sep 26, 2017 at 05:12:28PM +0200, Andreas Mohr wrote:
> Dear Sir / Madam,
> 
> On Thu, Sep 14, 2017 at 04:49:42PM +0200, Andreas Mohr wrote:
> > Dear Sir / Madam,
> > 
> > we have initiated a WiFi SAR/RF testing/certification effort of our current device
> > (handheld, TI WL1271 WLAN/Bluetooth BLE module, current Linux distribution: Ubuntu 12.04 LTS, to be modernized).
> > 
> > During our activities with Korean KC certification body, the following request has been made (TÜV Korea):
> > 
> > Mail 2016-06-14:
> > "
> > Please keep the power limit of less than 20mW as sent in our previous e-mail (if not fulfilled, the test will be failed).
> > <red>Please do not send out samples before it complies to the requirement.</red>
> > "
> > 
> > 20mW equals 13dBm.
> 
> Any thoughts on my change request? Further input needed?

No more input at this point, I just need to make some time to look at
this. Apologies for the delay.

Seth

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [wireless-regdb] [RFC] wireless-regdb: Update rules for 2.4GHz limit Republic of Korea (KR)
  2017-09-14 14:49 [wireless-regdb] [RFC] wireless-regdb: Update rules for 2.4GHz limit Republic of Korea (KR) Andreas Mohr
  2017-09-26 15:12 ` Andreas Mohr
@ 2017-09-26 20:16 ` Seth Forshee
  2017-09-27 13:53   ` Andreas Mohr
  1 sibling, 1 reply; 7+ messages in thread
From: Seth Forshee @ 2017-09-26 20:16 UTC (permalink / raw)
  To: Andreas Mohr; +Cc: wireless-regdb

On Thu, Sep 14, 2017 at 04:49:42PM +0200, Andreas Mohr wrote:
> Dear Sir / Madam,
> 
> we have initiated a WiFi SAR/RF testing/certification effort of our current device
> (handheld, TI WL1271 WLAN/Bluetooth BLE module, current Linux distribution: Ubuntu 12.04 LTS, to be modernized).
> 
> During our activities with Korean KC certification body, the following request has been made (TÜV Korea):
> 
> Mail 2016-06-14:
> "
> Please keep the power limit of less than 20mW as sent in our previous e-mail (if not fulfilled, the test will be failed).
> <red>Please do not send out samples before it complies to the requirement.</red>
> "
> 
> 20mW equals 13dBm.
> 
> We already successfully applied a modified signed regulatory.bin to have (and thus use) the reduced limit,
> however obviously we'd strongly prefer to have an official upstream release binary which:
> - where not up-to-date (e.g. older distribution base) can be custom-applied
> - where already up-to-date vs. upstream implicitly does have/receive all necessary future updates
> - is signed with official wireless-regdb / distro keys
> 
> We then asked for a paper trail (specs document, black-and-white dead-tree notice etc.)
> in order to file a thoroughly/legitimately claimed request for conformance update of wireless-regdb
> (simply due to properly knowing the root cause / explanation for this request!
> Details on why this limit has been imposed, when it got required, which modulation types it applies to, ...),
> however that turned out to be difficult.
> We ultimately succeeded in receiving the proper reference (Korean document, available upon request)
> which lists the 20mW requirement.
> 
> Also, a prior Internet search for
> "dBm site:rra.go.kr" had resulted in
> https://www.rra.go.kr/FileDownSvl?file_type=research2&file_parentseq=1044&file_seq=1
> (4.ÀüÀÚÆÄÀÎüº¸È£´ëÃ¥¿¬±¸.pdf , a nice UTF-8 mis-transcoding of originally Korean cp949 4.체호책.pdf 4.[uCCB4 uD638 uCC45].pdf)
> which appears to list device measurements, and where notably
> many 802.11g values of various company device models appear to be restricted to the 13dBm (i.e., 20mW) area.
> 
> 
> Due to other delays, this issue has not been pursued here (sorry!).
> Unfortunately it looks like
> wireless-regdb HEAD (9b3317bd4) does not yet have any change which would fulfill this certification requirement.
> 
> Thus, I am now proposing (RFC) the following minimum (potentially extended/documented) update.
> I decided to restrict the limitation to 2.4GHz area only since
> the current certification effort (and thus the limit request) is about 2.4GHz.

I can't read the document you reference above, and my own searches don't
seem to turn up anything authoritative. I consider the source of the
original 20 dBm limit reliable, but it was added in 2013 so it's
possible things have changed since then.

I'll give a few days for any other comments, and if there are none I
will apply the change.

Thanks,
Seth

> Thank you!
> 
> Yours sincerely
> 
> Andreas Mohr
> 
> 
> From 0added12024197148e87633c28959334795cbd02 Mon Sep 17 00:00:00 2001
> From: Andreas Mohr <andim2@users.sf.net>
> Date: Wed, 13 Sep 2017 11:51:54 +0200
> Subject: [PATCH] wireless-regdb: reduce power level limit of KR (Korea)
>  802.11b/g/n to the certification-requested "20mW" (13dBm).
> 
> Signed-off-by: Andreas Mohr <andim2@users.sf.net>
> ---
>  db.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/db.txt b/db.txt
> index e48f9a6..97b22b0 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -668,7 +668,7 @@ country KP: DFS-JP
>  	(5735 - 5815 @ 20), (30)
>  
>  country KR: DFS-JP
> -	(2402 - 2482 @ 40), (20)
> +	(2402 - 2482 @ 40), (13)
>  	(5170 - 5250 @ 80), (20), AUTO-BW
>  	(5250 - 5330 @ 80), (20), DFS, AUTO-BW
>  	(5490 - 5710 @ 160), (30), DFS
> -- 
> 2.9.5
> 

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [wireless-regdb] [RFC] wireless-regdb: Update rules for 2.4GHz limit Republic of Korea (KR)
  2017-09-26 20:16 ` Seth Forshee
@ 2017-09-27 13:53   ` Andreas Mohr
  2017-10-19 22:18     ` Seth Forshee
  0 siblings, 1 reply; 7+ messages in thread
From: Andreas Mohr @ 2017-09-27 13:53 UTC (permalink / raw)
  To: Seth Forshee; +Cc: Andreas Mohr, wireless-regdb

Hello Mr. Forshee,

On Tue, Sep 26, 2017 at 04:16:57PM -0400, Seth Forshee wrote:
> On Thu, Sep 14, 2017 at 04:49:42PM +0200, Andreas Mohr wrote:
> I can't read the document you reference above, and my own searches don't
> seem to turn up anything authoritative. I consider the source of the
> original 20 dBm limit reliable, but it was added in 2013 so it's
> possible things have changed since then.

Yes, my own Internet research didn't turn up much either.


> I'll give a few days for any other comments, and if there are none I
> will apply the change.

From my POV this is a very appreciable policy.

So:
- we've got a hard cert requirement
- provided specs are not nearly as hard (ahem)
- so, have it applied after some suitable complaint period
- then, this limit will be globally in effect in certain "less decipherable" countries ;-),
  and if there happens to be a problem, the properly country-prolific users there
  will then be able to
  provide much more precise/direct input as to
  whether or not currently chosen regulation settings are appropriate, *and why*

Thank you!

Andreas Mohr

-- 
¿umop apisdn upside down?
(by daniweb.com user Bench)

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [wireless-regdb] [RFC] wireless-regdb: Update rules for 2.4GHz limit Republic of Korea (KR)
  2017-09-27 13:53   ` Andreas Mohr
@ 2017-10-19 22:18     ` Seth Forshee
  2017-10-26  7:54       ` Andreas Mohr
  0 siblings, 1 reply; 7+ messages in thread
From: Seth Forshee @ 2017-10-19 22:18 UTC (permalink / raw)
  To: Andreas Mohr; +Cc: Andreas Mohr, wireless-regdb

On Wed, Sep 27, 2017 at 03:53:32PM +0200, Andreas Mohr wrote:
> Hello Mr. Forshee,
> 
> On Tue, Sep 26, 2017 at 04:16:57PM -0400, Seth Forshee wrote:
> > On Thu, Sep 14, 2017 at 04:49:42PM +0200, Andreas Mohr wrote:
> > I can't read the document you reference above, and my own searches don't
> > seem to turn up anything authoritative. I consider the source of the
> > original 20 dBm limit reliable, but it was added in 2013 so it's
> > possible things have changed since then.
> 
> Yes, my own Internet research didn't turn up much either.
> 
> 
> > I'll give a few days for any other comments, and if there are none I
> > will apply the change.
> 
> From my POV this is a very appreciable policy.
> 
> So:
> - we've got a hard cert requirement
> - provided specs are not nearly as hard (ahem)
> - so, have it applied after some suitable complaint period
> - then, this limit will be globally in effect in certain "less decipherable" countries ;-),
>   and if there happens to be a problem, the properly country-prolific users there
>   will then be able to
>   provide much more precise/direct input as to
>   whether or not currently chosen regulation settings are appropriate, *and why*

Applied, thanks!

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [wireless-regdb] [RFC] wireless-regdb: Update rules for 2.4GHz limit Republic of Korea (KR)
  2017-10-19 22:18     ` Seth Forshee
@ 2017-10-26  7:54       ` Andreas Mohr
  0 siblings, 0 replies; 7+ messages in thread
From: Andreas Mohr @ 2017-10-26  7:54 UTC (permalink / raw)
  To: Seth Forshee; +Cc: Andreas Mohr, wireless-regdb, Andreas Mohr

Hello,

On Thu, Oct 19, 2017 at 05:18:41PM -0500, Seth Forshee wrote:
> Applied, thanks!

Verified to indeed have hit upstream project repo, and communicated this great news.

Wonderful support, thank you!

Andreas Mohr

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2017-10-26  7:55 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-09-14 14:49 [wireless-regdb] [RFC] wireless-regdb: Update rules for 2.4GHz limit Republic of Korea (KR) Andreas Mohr
2017-09-26 15:12 ` Andreas Mohr
2017-09-26 18:49   ` Seth Forshee
2017-09-26 20:16 ` Seth Forshee
2017-09-27 13:53   ` Andreas Mohr
2017-10-19 22:18     ` Seth Forshee
2017-10-26  7:54       ` Andreas Mohr

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.