Skip to contentSkip to conversation

crda: Updated regulatory information for France (FR)

PATCH In review Benoit PAPILLAULT 4 participants 9 messages Oct 21, 2008 – Oct 24, 2008 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

PATCH 4/5 crda: Updated regulatory information for France (FR)

This patch is for review. It might be tricky to use the INDOOR/OUTDOOR with those definitions, but it will be another issue.

---
 db.txt |   15 ++++++++++-----
 1 files changed, 10 insertions(+), 5 deletions(-)
db.txt +10 -5
index 6a282b6..bfc91ef 100644
@@ -199,12 +199,17 @@ country FI:
 	(5170 - 5250 @ 40), (N/A, 20)
 	(5250 - 5330 @ 40), (N/A, 20), DFS
 	(5490 - 5710 @ 40), (N/A, 27), DFS
-
+# Data from http://www.arcep.fr/index.php?id=9272#12931
+# Updated 2008-10-04
+# 1W => 30dBm, 200mW => 23dBm, 100mW => 20dBm, 10mW => 10dBm
+# TPC is needed for 5250-5350 and 5470-5725, which flag to use?
 country FR:
-	(2402 - 2482 @ 40), (N/A, 20)
-	(5170 - 5250 @ 40), (N/A, 20)
-	(5250 - 5330 @ 40), (N/A, 20), DFS
-	(5490 - 5710 @ 40), (N/A, 27), DFS
+	(2400 - 2454 @ 40), (N/A, 20)
+	(2454 - 2483.5 @ 40), (N/A, 20), NO-OUTDOOR
+	(2454 - 2483.5 @ 40), (N/A, 10), NO-INDOOR
+	(5150 - 5250 @ 40), (N/A, 23), NO-OUTDOOR
+	(5250 - 5350 @ 40), (N/A, 23), NO-OUTDOOR, DFS, PASSIVE-SCAN
+	(5470 - 5725 @ 40), (N/A, 30), DFS, PASSIVE-SCAN
 
 country GE:
 	(2402 - 2482 @ 40), (N/A, 20)
Signature · 1 line
1.5.6.5
#2 lore raw

db.txt country FI: · line 204

Quoted 3 lines · Benoit PAPILLAULT
db.txt +3 -0
+# Data from http://www.arcep.fr/index.php?id=9272#12931
+# Updated 2008-10-04
+# 1W => 30dBm, 200mW => 23dBm, 100mW => 20dBm, 10mW => 10dBm

You can say "200mW" in the definitions and the tool will automatically convert it.

db.txt country FI: · line 207

Quoted 7 lines
db.txt +2 -4
+# TPC is needed for 5250-5350 and 5470-5725, which flag to use?
 country FR:
-	(2402 - 2482 @ 40), (N/A, 20)
-	(5170 - 5250 @ 40), (N/A, 20)
-	(5250 - 5330 @ 40), (N/A, 20), DFS
-	(5490 - 5710 @ 40), (N/A, 27), DFS
+	(2400 - 2454 @ 40), (N/A, 20)

i.e.

(2400 - 2454 @ 40), (N/A, 100mW)

I think I did this for the DE one.

johannes

#3 lore raw
In reply to Benoit PAPILLAULT

CC'ing Jean as he's another French wireless developer.

Quoted 2 lines · Benoit PAPILLAULT

This patch is for review. It might be tricky to use the INDOOR/OUTDOOR with those definitions, but it will be another issue.

INDOOR/OUTDOOR flag is welcomed when it can be determined. In order to make use of it we will need to add wireless state in cfg80211, and let the user be able to update this, say through iw or wpa_supplicant. But that's for later just as with DFS.

But using it in the db is great, thanks.

Quoted 15 lines
---
 db.txt |   15 ++++++++++-----
 1 files changed, 10 insertions(+), 5 deletions(-)
db.txt +1 -1
index 6a282b6..bfc91ef 100644
@@ -199,12 +199,17 @@ country FI:
        (5170 - 5250 @ 40), (N/A, 20)
        (5250 - 5330 @ 40), (N/A, 20), DFS
        (5490 - 5710 @ 40), (N/A, 27), DFS
-
+# Data from http://www.arcep.fr/index.php?id=9272#12931

db.txt country FI: · line 208

Quoted 10 lines
db.txt +5 -4
+# Updated 2008-10-04
+# 1W => 30dBm, 200mW => 23dBm, 100mW => 20dBm, 10mW => 10dBm
+# TPC is needed for 5250-5350 and 5470-5725, which flag to use?
 country FR:
-       (2402 - 2482 @ 40), (N/A, 20)
-       (5170 - 5250 @ 40), (N/A, 20)
-       (5250 - 5330 @ 40), (N/A, 20), DFS
-       (5490 - 5710 @ 40), (N/A, 27), DFS
+       (2400 - 2454 @ 40), (N/A, 20)
+       (2454 - 2483.5 @ 40), (N/A, 20), NO-OUTDOOR

2483.5 - 2454 = 29.5 so 29.5 should be the max bandwidth.

db.txt country FI: · line 209

Quoted 1 line
db.txt +1 -0
+       (2454 - 2483.5 @ 40), (N/A, 10), NO-INDOOR

Same here.

db.txt country FI: · line 212

Quoted 3 lines
db.txt +3 -0
+       (5150 - 5250 @ 40), (N/A, 23), NO-OUTDOOR
+       (5250 - 5350 @ 40), (N/A, 23), NO-OUTDOOR, DFS, PASSIVE-SCAN
+       (5470 - 5725 @ 40), (N/A, 30), DFS, PASSIVE-SCAN

Hm, actually so I had removed PASSIVE-SCAN from all entries as I had determined that this was only used for DFS purposes. As you can see in your case both have DFS so I'd leave only DFS. So essentially we can get rid of these:

RRF_PASSIVE_SCAN = 1<<7, /* passive scan is required */
RRF_NO_IBSS = 1<<8, /* IBSS is not allowed */

What I noted was that PASSIVE-SCAN for example was only used for when we don't have DFS in STA and NO_IBSS when we don't have DFS in IBSS.

So we can just stick to DFS flag, unless you are aware of other considerations for them. Thoughts?

Luis

#4 lore raw
Quoted 2 lines · Luis R. Rodriguez

CC'ing Jean as he's another French wireless developer.

I have not been living in France for a while, like more than
10 years ;-)
I think Benoit is on top of things, and as I'm not familiar
with it, I'll defer to him.

Jean

#5 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jean Tourrilhes a =E9crit :

Quoted 10 lines · Luis R. Rodriguez
Quoted 2 lines

CC'ing Jean as he's another French wireless developer.

=20
I have not been living in France for a while, like more than
10 years ;-)
I think Benoit is on top of things, and as I'm not familiar
with it, I'll defer to him.
=20
Jean

Indeed, I read lots of paper, website, source code and I know a lot for sure. But at the end, that's my own interpretation and I might still be wrong, so having peer review is still needed.

Regards,
Benoit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJAAisOR6EySwP7oIRAhW9AJ9vUcgHiPLQGcUwgyHRBsKdMLZgcwCfQEyn bwGnbRXBEARYX6TCy3eqVns=3D
=3DRr7k
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#6 lore raw
In reply to Luis R. Rodriguez

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Luis R. Rodriguez a =E9crit :

Quoted 4 lines

CC'ing Jean as he's another French wireless developer. =20

Quoted 1 line · Benoit PAPILLAULT

This patch is for review. It might be tricky to use the INDOOR/OUTDO=

OR

Quoted 5 lines
Quoted 1 line

with those definitions, but it will be another issue.

=20
INDOOR/OUTDOOR flag is welcomed when it can be determined. In order to make use of it we will need to add wireless state in cfg80211, and let the user be able to update this, say through iw or wpa_supplicant=

=2E

Quoted 1 line

But that's for later just as with DFS.

=46ine with me here.

Quoted 8 lines

=20
But using it in the db is great, thanks.
=20

Quoted 5 lines
---
 db.txt |   15 ++++++++++-----
 1 files changed, 10 insertions(+), 5 deletions(-)
Quoted 12 lines

db.txt country FI: · line 204

Quoted 12 lines
db.txt +3 -1
index 6a282b6..bfc91ef 100644
@@ -199,12 +199,17 @@ country FI:
        (5170 - 5250 @ 40), (N/A, 20)
        (5250 - 5330 @ 40), (N/A, 20), DFS
        (5490 - 5710 @ 40), (N/A, 27), DFS
-
+# Data from http://www.arcep.fr/index.php?id=3D9272#12931
+# Updated 2008-10-04
+# 1W =3D> 30dBm, 200mW =3D> 23dBm, 100mW =3D> 20dBm, 10mW =3D> 10dB=

m

Quoted 10 lines

db.txt country FI: · line 208

Quoted 8 lines
db.txt +3 -4
+# TPC is needed for 5250-5350 and 5470-5725, which flag to use?
 country FR:
-       (2402 - 2482 @ 40), (N/A, 20)
-       (5170 - 5250 @ 40), (N/A, 20)
-       (5250 - 5330 @ 40), (N/A, 20), DFS
-       (5490 - 5710 @ 40), (N/A, 27), DFS
+       (2400 - 2454 @ 40), (N/A, 20)
+       (2454 - 2483.5 @ 40), (N/A, 20), NO-OUTDOOR

=20
2483.5 - 2454 =3D 29.5 so 29.5 should be the max bandwidth.

Not exactly. The maximum power in this band depends on whether we are indoor or outdoor. If we are indoor, we are allowed to have 20dBm in th= e
whole 2400 - 2454 MHz band and can still use 40MHz bandwidth. Maybe I should describe that different?

	(2412 - 2483.5 @ 40), (N/A, 20), NO-OUTDOOR
        (2412 - 2454 @ 40), (N/A, 20), NO-INDOOR
        (2454 - 2483.5 @ 40) (N/A, 10), NO-INDOOR

In fact, this depends on the indoor/outdoor flags issue which can be resolved later.

Quoted 8 lines

=20

db.txt country FI: · line 209

Quoted 1 line
db.txt +1 -0
+       (2454 - 2483.5 @ 40), (N/A, 10), NO-INDOOR

=20
Same here.
=20

db.txt country FI: · line 212

Quoted 3 lines
db.txt +3 -0
+       (5150 - 5250 @ 40), (N/A, 23), NO-OUTDOOR
+       (5250 - 5350 @ 40), (N/A, 23), NO-OUTDOOR, DFS, PASSIVE-SCAN
+       (5470 - 5725 @ 40), (N/A, 30), DFS, PASSIVE-SCAN
Quoted 7 lines

=20
Hm, actually so I had removed PASSIVE-SCAN from all entries as I had determined that this was only used for DFS purposes. As you can see in your case both have DFS so I'd leave only DFS. So essentially we can get rid of these:
=20
RRF_PASSIVE_SCAN =3D 1<<7, /* passive scan is required=

*/

Quoted 7 lines

RRF_NO_IBSS =3D 1<<8, /* IBSS is not allowed */
=20
What I noted was that PASSIVE-SCAN for example was only used for when we don't have DFS in STA and NO_IBSS when we don't have DFS in IBSS. =20
So we can just stick to DFS flag, unless you are aware of other considerations for them. Thoughts?

If it's documented that the DFS flag implies PASSIVE_SCAN, that's fine with me.

Quoted 2 lines

=20
Luis

Regards,
Benoit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJAAwhOR6EySwP7oIRApcqAKC/+B/fPUu6+8caHOqnA/GwsnGCdwCfcuSR YX46su0CSrQCynR/RQ1CLnM=3D
=3D9NM9
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#7 lore raw
Quoted 19 lines · Benoit PAPILLAULT
Quoted 5 lines
Quoted 5 lines
db.txt +4 -0
+# Data from http://www.arcep.fr/index.php?id=9272#12931
+# Updated 2008-10-04
+# 1W => 30dBm, 200mW => 23dBm, 100mW => 20dBm, 10mW => 10dBm
+# TPC is needed for 5250-5350 and 5470-5725, which flag to use?
 country FR:
Quoted 8 lines

db.txt country FI: · line 208

Quoted 6 lines
db.txt +2 -4
-       (2402 - 2482 @ 40), (N/A, 20)
-       (5170 - 5250 @ 40), (N/A, 20)
-       (5250 - 5330 @ 40), (N/A, 20), DFS
-       (5490 - 5710 @ 40), (N/A, 27), DFS
+       (2400 - 2454 @ 40), (N/A, 20)
+       (2454 - 2483.5 @ 40), (N/A, 20), NO-OUTDOOR

2483.5 - 2454 = 29.5 so 29.5 should be the max bandwidth.

Not exactly. The maximum power in this band depends on whether we are indoor or outdoor. If we are indoor, we are allowed to have 20dBm in the whole 2400 - 2454 MHz band and can still use 40MHz bandwidth. Maybe I should describe that different?

Quoted 6 lines
        (2412 - 2483.5 @ 40), (N/A, 20), NO-OUTDOOR
        (2412 - 2454 @ 40), (N/A, 20), NO-INDOOR
        (2454 - 2483.5 @ 40) (N/A, 10), NO-INDOOR

In fact, this depends on the indoor/outdoor flags issue which can be resolved later.

But I wasn't speaking about power, I was speaking about channel bandwidth. You cannot fit a 40 MHz channel into the freq range 2483.5 - 2454.

Quoted 16 lines
Quoted 16 lines
Quoted 1 line

+ (2454 - 2483.5 @ 40), (N/A, 10), NO-INDOOR

Same here.

db.txt country FI: · line 212

Quoted 3 lines
db.txt +3 -0
+       (5150 - 5250 @ 40), (N/A, 23), NO-OUTDOOR
+       (5250 - 5350 @ 40), (N/A, 23), NO-OUTDOOR, DFS, PASSIVE-SCAN
+       (5470 - 5725 @ 40), (N/A, 30), DFS, PASSIVE-SCAN

Hm, actually so I had removed PASSIVE-SCAN from all entries as I had determined that this was only used for DFS purposes. As you can see in your case both have DFS so I'd leave only DFS. So essentially we can get rid of these:

RRF_PASSIVE_SCAN = 1<<7, /* passive scan is required */
RRF_NO_IBSS = 1<<8, /* IBSS is not allowed */

Quoted 8 lines
Quoted 5 lines

What I noted was that PASSIVE-SCAN for example was only used for when we don't have DFS in STA and NO_IBSS when we don't have DFS in IBSS.

So we can just stick to DFS flag, unless you are aware of other considerations for them. Thoughts?

If it's documented that the DFS flag implies PASSIVE_SCAN, that's fine with me.

We'll have to add the docs, this is just what what I determined from my own review on regulatory, with regulatory folks. I asked a "why" for each flag.

Luis

#8 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Luis R. Rodriguez a =E9crit :

Quoted 3 lines · Benoit PAPILLAULT
Quoted 2 lines
Quoted 1 line

2483.5 - 2454 =3D 29.5 so 29.5 should be the max bandwidth.

Not exactly. The maximum power in this band depends on whether we ar=

e

Quoted 1 line
Quoted 1 line

indoor or outdoor. If we are indoor, we are allowed to have 20dBm in=

the

Quoted 1 line
Quoted 1 line

whole 2400 - 2454 MHz band and can still use 40MHz bandwidth. Maybe =

I

Quoted 6 lines
Quoted 6 lines

should describe that different?

        (2412 - 2483.5 @ 40), (N/A, 20), NO-OUTDOOR
        (2412 - 2454 @ 40), (N/A, 20), NO-INDOOR
        (2454 - 2483.5 @ 40) (N/A, 10), NO-INDOOR
Quoted 6 lines
Quoted 2 lines

In fact, this depends on the indoor/outdoor flags issue which can be resolved later.

=20
But I wasn't speaking about power, I was speaking about channel bandwidth. You cannot fit a 40 MHz channel into the freq range 2483.5 - 2454.

The whole band is still 2412-2483.5MHz in both cases (indoor/outdoor), this is just that different TX power rules apply for frequencies below 2454 MHz and above when used outdoor.

To me, it's valid to have a 40MHz channel centered at 2462 MHz covering the range [2442, 2482] MHz. When used outdoor, it will be limited to 10 dBm on the whole range.

Regards,
Benoit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJAYuHOR6EySwP7oIRAseyAKCjiDkOs39MIBnhjA3OQDsgfCJzYQCgr1aA R9UNky9HVhPQwtl9pwInL88=3D
=3D7Rzj
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#9 lore raw
Quoted 7 lines · Benoit PAPILLAULT

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=20
Luis R. Rodriguez a =E9crit :

Quoted 3 lines · Benoit PAPILLAULT
Quoted 2 lines
Quoted 1 line

2483.5 - 2454 =3D 29.5 so 29.5 should be the max bandwidth.

Not exactly. The maximum power in this band depends on whether we =

are

Quoted 1 line
Quoted 1 line
Quoted 1 line

indoor or outdoor. If we are indoor, we are allowed to have 20dBm =

in the

Quoted 1 line
Quoted 1 line
Quoted 1 line

whole 2400 - 2454 MHz band and can still use 40MHz bandwidth. Mayb=

e I

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

should describe that different?

        (2412 - 2483.5 @ 40), (N/A, 20), NO-OUTDOOR
        (2412 - 2454 @ 40), (N/A, 20), NO-INDOOR
        (2454 - 2483.5 @ 40) (N/A, 10), NO-INDOOR

In fact, this depends on the indoor/outdoor flags issue which can =

be

Quoted 7 lines
Quoted 5 lines
Quoted 1 line

resolved later.

But I wasn't speaking about power, I was speaking about channel bandwidth. You cannot fit a 40 MHz channel into the freq range 2483.5 - 2454.

=20
The whole band is still 2412-2483.5MHz in both cases (indoor/outdoor)=

,

Quoted 1 line

this is just that different TX power rules apply for frequencies belo=

w

Quoted 3 lines

2454 MHz and above when used outdoor.
=20
To me, it's valid to have a 40MHz channel centered at 2462 MHz coveri=

ng

Quoted 1 line

the range [2442, 2482] MHz. When used outdoor, it will be limited to =

10

Quoted 1 line

dBm on the whole range.

This is an interesting case... so right now we apply a reg rule to a channel upon register or when a regulatory domain changes. We do this in handle_channel(). This calls freq_reg_info() and one parameter we can pass there is the max_bandwidth we know we want or 0 if we have no requirement. We use 0 on max_bandwidth right now as we haven't added code for checking max bandwidth yet in mac80211, I think we can add desired tx power here as well and it'll then be able to pick up the correct rule. However this does require adding code to reg.c. and maybe mac80211. We'll have to keep this in mind and add it, but the reg rule for 2454 - 2483.5 should still not have 40 MHz for max bandwidth as only 29.5 MHz fits in it.

Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles= s" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html