[PATCH] wireless-regdb: add regulatory rules for Iraq (IQ)

[PATCH] wireless-regdb: add regulatory rules for Iraq (IQ)

[Mohammed Abdalla]

[-- Attachment #1.1: Type: text/plain, Size: 7050 bytes --]

## 1. Why this patch exists
Iraq is currently absent from `wireless-regdb/db.txt`. As aconsequence, every OpenWrt and Linux device set to `country=IQ`falls back to the world domain (`00`), which marks most of the5 GHz spectrum as `no IR` and limits 2.4 GHz EIRP to 20 dBm. Apublic OpenWrt forum thread on the Archer AX23 in Iraq concludedwith the maintainers' standard answer:
> *"IQ is the correct code for the place; once an engineer shares> the local radio laws with regdb maintainers it will be added."*
This patch is that contribution.
## 2. The primary source
The Iraqi Communications and Media Commission (CMC), the nationalregulator, has issued a numerical regulation specifically governingunlicensed Wi-Fi, SRD, and UWB devices:
- **Title:** Regulation on short-range radio communication devices  (SRD) and devices using ultra-broadband (UWB) technology- **Issuer:** Republic of Iraq, CMC, Telecommunications Regulatory  Department, International Relations Section- **Decree:** Council of Commissioners decision No. 122/q-2025- **In force from:** 2025-09-22- **Edition:** First edition, 2025; 26 pages- **Direct PDF:**  <https://cmc.iq/wp-content/uploads/2025/09/Regulation-on-short-range-radio-communication-devices-SRD-and-devices-using-ultra-broadband-UWB-technology.pdf>
Article 4-1-13 of that regulation, titled "Wireless Access Systems(WAS)", contains a full numerical table for every Wi-Fi band. Thispatch reproduces that table directly. Nothing in the proposed`country IQ:` block is inferred or extrapolated.
## 3. The Article 4-1-13 table, verbatim
| Band | Use | Max EIRP | Required mitigations | Cited standard ||---|---|---|---|---|| 2400 – 2483.5 MHz | Indoor and outdoor | 100 mW | LBT and DAA | EN 300 328, ERC/REC 70-03 || 5150 – 5250 MHz | Indoor | 200 mW | — | EN 301 893, ITU Res. 229 (Rev. WRC-19) || 5250 – 5350 MHz | Indoor | 200 mW | — (DFS implied via EN 301 893) | EN 301 893 || 5470 – 5725 MHz | Indoor | 1000 mW | DFS and TPC (stated explicitly) | EN 301 893 || 5725 – 5875 MHz | Indoor and outdoor | 2000 mW (10 MHz ch) / 4000 mW (20 MHz ch) | — | EN 302 502 || 5945 – 6425 MHz | Indoor | 200 mW | — | EN 303 687, ECC Report 75 || 57000 – 66000 MHz | Indoor | 10000 mW | LBT and DAA | EN 302 567 |
The proposed `country IQ:` block encodes this table line for line.
## 4. The Iraqi regulation also defines its own glossary terms
For the avoidance of doubt, the regulation's Annex A explicitlydefines `Wi-Fi` as *"802.11 Local Area Networking in 2.4 and 5 GHzISM bands"*. So when the maintainers ask whether this regulationin fact covers Wi-Fi, the answer from the regulator is yes,in writing, in the regulation itself.
The same annex defines DFS, TPC, LBT, DAA, EIRP and AFA in theexact wireless-regdb sense.
## 5. Encoding choices and where they came from
A few wireless-regdb encoding details require explanation, becausethey are interpretations of the regulation's wording rather thandirect copies of numerical limits:
1. **NO-OUTDOOR on 5150–5725 MHz.** The regulation labels these   rows simply as "Indoor". The wireless-regdb idiom for that is   the `NO-OUTDOOR` flag.
2. **No NO-OUTDOOR on 5725–5875 MHz.** The regulation explicitly   labels this row "Indoor and outdoor".
3. **DFS on 5250–5350 MHz.** The regulation's own column for this   row is empty for mitigations, but the cited standard   (EN 301 893) requires DFS in this sub-band, and the corresponding   row for 5470–5725 in the same table does state DFS+TPC. Reading   the regulation as a whole, DFS for 5250–5350 is required by the   incorporated standard.
4. **Single EIRP figure for 5725–5875 MHz.** The regulation gives   two figures (2000 mW for 10 MHz channels, 4000 mW for 20 MHz   channels). The wireless-regdb format expresses one ceiling per   band; the 4000 mW figure is used because it is the higher value   that the regulation explicitly permits.
5. **6 GHz channel width set to 80 MHz.** The regulation does not   explicitly distinguish standard-power from low-power indoor   (LPI) operation, nor does it mention AFC. The conservative   choice is to encode the 6 GHz block at 80 MHz (the widest   non-AFC option in current practice) and leave a follow-up patch   for a wider channelisation once CMC clarifies AFC requirements.
6. **AUTO-BW on the 5 GHz RLAN rows.** Standard practice for   EN 301 893–compliant entries; no AUTO-BW is set on the 6 GHz   row pending the AFC question above.
If the maintainers prefer a different encoding for any of thesesix points, please push back; the underlying regulatory text isclear and any of these can be re-encoded without changing what isactually permitted under Iraqi law.
## 6. The 5.8 GHz figure looks unusually high — it is intentional
`(5725 - 5875 @ 80), (4000 mW)` with no NO-OUTDOOR is not a typo.This is what Iraq's own regulation states for this sub-band, citingEN 302 502. It is the BFWA value, not the Non-Specific SRD value.This choice puts Iraq at the high end of the regional spectrumpolicy for the 5.8 GHz band. It is included verbatim because thepurpose of wireless-regdb is to reflect what each country'sregulator actually permits.
## 7. What is not in the patch
- **5850–5925 MHz ITS / V2X bands.** Article 4-1-8 of the same  regulation covers ITS at 5855–5925 MHz with 2 W EIRP, but this  is a non-Wi-Fi RLAN application and is outside the scope of  what wireless-regdb usually encodes for `country` blocks.
- **All non-Wi-Fi SRD bands.** The regulation also covers RFID,  inductive applications, alarms, model control, automotive radar,  level probing radar, hearing aids, active medical implants, and  the full UWB regime (Articles 4-2-1 through 4-2-6). None of these  is a wireless-regdb concern.
- **6 GHz beyond 6425 MHz.** The Iraqi regulation only addresses  5945–6425 MHz at 6 GHz; the 6425–7125 MHz upper portion is not  covered, and the patch therefore does not include it.
## 8. Submission checklist
- [ ] Verify the patch applies cleanly against the current      `wireless-regdb` master; the IQ block must be inserted in      alphabetical order, between `IN` and `IR`.- [ ] Build `regulatory.db` locally and confirm with      `regdbdump regulatory.db | grep -A8 'country IQ'` that the      output matches the proposed table exactly.- [ ] Post the cover letter and patch on the OpenWrt forum thread      (231380) for community review by Iraqi engineers before      sending upstream.- [ ] Send to `linux-wireless@vger.kernel.org` with cc to      `wireless-regdb@lists.infradead.org`.
## 9. A note on responsibility
The numerical content of this patch is taken verbatim from a publicIraqi government regulation. The encoding choices listed in §5 arethe patch author's, and they are reversible.
Author: Mohammed Abdullah Ali Al-Obaidi (mnew_iraq@yahoo.com),OpenWrt forum handle `mnewiraq`. Any objection to the encodingchoices should be raised to that author or in the upstream reviewthread, not to the CMC.


[-- Attachment #1.2: Type: text/html, Size: 11942 bytes --]

[-- Attachment #2: 0001-wireless-regdb-add-Iraq-IQ-entry-2.patch --]
[-- Type: application/octet-stream, Size: 5123 bytes --]

From: Mohammed Abdullah Ali Al-Obaidi <mnew_iraq@yahoo.com>
Subject: [PATCH] wireless-regdb: add regulatory rules for Iraq (IQ)

Add a regulatory entry for Iraq (ISO 3166-1 alpha-2: IQ).

Iraq is currently absent from the regulatory database. Devices set
to country=IQ fall back to the world domain (00), which leaves most
of the 5 GHz spectrum marked "no IR" and severely restricts even
2.4 GHz operation. The Iraqi Communications and Media Commission
(CMC) has now published an explicit, numerical national regulation
that fills this gap.

Source document
---------------

  Title : Regulation on short-range radio communication devices
          (SRD) and devices using ultra-broadband (UWB) technology
  Issuer: Republic of Iraq, Communications and Media Commission
          (CMC), Telecommunications Regulatory Department,
          International Relations Section
  Decree: Council of Commissioners decision No. 122/q-2025
  In force from: 2025-09-22
  Edition: First edition, 2025; 26 pages
  URL   : https://cmc.iq/wp-content/uploads/2025/09/Regulation-on-short-range-radio-communication-devices-SRD-and-devices-using-ultra-broadband-UWB-technology.pdf

The values below are taken directly from Article 4-1-13 ("Wireless
Access Systems / WAS") of that regulation, which is the table
governing Wi-Fi (Annex A of the regulation defines Wi-Fi as
"802.11 Local Area Networking in 2.4 and 5 GHz ISM bands"). This
is not a derived reading: every band, every EIRP value, every
indoor restriction, and every required mitigation (LBT/DAA, DFS,
TPC) is named in the regulation itself.

Bands and limits, as stated in Article 4-1-13:

  2400-2483.5 MHz  : 100  mW EIRP, indoor and outdoor, LBT/DAA
                     (EN 300 328, ERC/REC 70-03)
  5150-5250 MHz    : 200  mW EIRP, indoor
                     (EN 301 893, ITU-R Res. 229 Rev. WRC-19)
  5250-5350 MHz    : 200  mW EIRP, indoor
                     (EN 301 893)  -- DFS implied via EN 301 893
  5470-5725 MHz    : 1000 mW EIRP, indoor, DFS + TPC
                     (EN 301 893)
  5725-5875 MHz    : 2000 mW EIRP (10 MHz ch) / 4000 mW (20 MHz ch),
                     indoor and outdoor
                     (EN 302 502)
  5945-6425 MHz    : 200  mW EIRP, indoor
                     (EN 303 687, ECC Report 75)
  57-66 GHz        : 10   W  EIRP, indoor, LBT/DAA
                     (EN 302 567)

Notes on the encoding chosen below
----------------------------------

* The Iraqi regulation lists bands 2 through 4 (5150-5725 MHz) as
  "Indoor"; this is encoded as NO-OUTDOOR.
* The regulation lists 5725-5875 MHz as "Indoor and outdoor"; no
  NO-OUTDOOR flag is applied to that row.
* DFS for 5250-5350 is required by EN 301 893, which the regulation
  references; the DFS flag is included accordingly.
* DFS and TPC for 5470-5725 are stated explicitly in the regulation
  ("DFS & TPC shall be implemented as adequate sharing mechanism").
* 5725-5875 MHz uses the higher of the two stated EIRP figures
  (4000 mW for 20 MHz channels) since wireless-regdb expresses a
  per-band ceiling, not a per-channel-width ceiling.
* AUTO-BW is set on the 5 GHz RLAN bands consistent with EN 301 893.
* The 6 GHz block is encoded at the 80 MHz channel width which is
  the widest standard-power option; it can be widened in a follow-up
  patch if and when CMC clarifies AFC requirements.
* 60 GHz: the regulation specifies 57-66 GHz; this matches the
  existing wireless-regdb convention used by other ETSI countries.

Background on the unique 5.8 GHz figure
---------------------------------------

The 4000 mW EIRP for 5725-5875 MHz with both indoor and outdoor
operation is not the conservative European figure; it reflects an
explicit Iraqi national choice that follows EN 302 502 (BFWA).
This is included verbatim from the regulation.

Discussion thread on the OpenWrt forum where this work was
solicited:

  https://forum.openwrt.org/t/configuring-openwrt-on-archer-ax23-in-iraq/231380

Signed-off-by: Mohammed Abdullah Ali Al-Obaidi <mnew_iraq@yahoo.com>
---
 db.txt | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/db.txt b/db.txt
--- a/db.txt
+++ b/db.txt
@@ -insert-after-IN-block@@
+# Iraq
+# Source: Regulation on short-range radio communication devices (SRD)
+# and devices using ultra-broadband (UWB) technology, First Edition
+# 2025, issued by the Iraqi Communications and Media Commission (CMC)
+# under Council of Commissioners decision No. 122/q-2025, in force
+# from 2025-09-22. Limits below are taken from Article 4-1-13
+# (Wireless Access Systems) of that regulation.
+# https://cmc.iq/wp-content/uploads/2025/09/Regulation-on-short-range-radio-communication-devices-SRD-and-devices-using-ultra-broadband-UWB-technology.pdf
+country IQ: DFS-ETSI
+	(2400 - 2483.5 @ 40), (100 mW), wmmrule=ETSI
+	(5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
+	(5250 - 5350 @ 80), (200 mW), NO-OUTDOOR, DFS, AUTO-BW, wmmrule=ETSI
+	(5470 - 5725 @ 160), (1000 mW), NO-OUTDOOR, DFS, wmmrule=ETSI
+	(5725 - 5875 @ 80), (4000 mW)
+	(5945 - 6425 @ 80), (200 mW), NO-OUTDOOR, wmmrule=ETSI
+	(57000 - 66000 @ 2160), (40)
-- 
2.43.0

RE: [PATCH] wireless-regdb: add regulatory rules for Iraq (IQ)

[Mohammed.Al-Obaidi]

Kind reminder, any update on the subject?

Mohammed

From: Mohammed Abdalla [mailto:mnew_iraq@yahoo.com]
Sent: Tuesday, May 5, 2026 7:12 PM
To: wireless-regdb@lists.infradead.org; linux-wireless@vger.kernel.org
Cc: Mohammed Abdullah Ali Al-Obaidi <Mohammed.Al-Obaidi@badraproject.com>
Subject: [PATCH] wireless-regdb: add regulatory rules for Iraq (IQ)

## 1. Why this patch exists

Iraq is currently absent from `wireless-regdb/db.txt`. As a
consequence, every OpenWrt and Linux device set to `country=IQ`
falls back to the world domain (`00`), which marks most of the
5 GHz spectrum as `no IR` and limits 2.4 GHz EIRP to 20 dBm. A
public OpenWrt forum thread on the Archer AX23 in Iraq concluded
with the maintainers' standard answer:

> *"IQ is the correct code for the place; once an engineer shares
> the local radio laws with regdb maintainers it will be added."*

This patch is that contribution.

## 2. The primary source

The Iraqi Communications and Media Commission (CMC), the national
regulator, has issued a numerical regulation specifically governing
unlicensed Wi-Fi, SRD, and UWB devices:

- **Title:** Regulation on short-range radio communication devices
  (SRD) and devices using ultra-broadband (UWB) technology
- **Issuer:** Republic of Iraq, CMC, Telecommunications Regulatory
  Department, International Relations Section
- **Decree:** Council of Commissioners decision No. 122/q-2025
- **In force from:** 2025-09-22
- **Edition:** First edition, 2025; 26 pages
- **Direct PDF:**
  <https://cmc.iq/wp-content/uploads/2025/09/Regulation-on-short-range-radio-communication-devices-SRD-and-devices-using-ultra-broadband-UWB-technology.pdf>

Article 4-1-13 of that regulation, titled "Wireless Access Systems
(WAS)", contains a full numerical table for every Wi-Fi band. This
patch reproduces that table directly. Nothing in the proposed
`country IQ:` block is inferred or extrapolated.

## 3. The Article 4-1-13 table, verbatim

| Band | Use | Max EIRP | Required mitigations | Cited standard |
|---|---|---|---|---|
| 2400 – 2483.5 MHz | Indoor and outdoor | 100 mW | LBT and DAA | EN 300 328, ERC/REC 70-03 |
| 5150 – 5250 MHz | Indoor | 200 mW | — | EN 301 893, ITU Res. 229 (Rev. WRC-19) |
| 5250 – 5350 MHz | Indoor | 200 mW | — (DFS implied via EN 301 893) | EN 301 893 |
| 5470 – 5725 MHz | Indoor | 1000 mW | DFS and TPC (stated explicitly) | EN 301 893 |
| 5725 – 5875 MHz | Indoor and outdoor | 2000 mW (10 MHz ch) / 4000 mW (20 MHz ch) | — | EN 302 502 |
| 5945 – 6425 MHz | Indoor | 200 mW | — | EN 303 687, ECC Report 75 |
| 57000 – 66000 MHz | Indoor | 10000 mW | LBT and DAA | EN 302 567 |

The proposed `country IQ:` block encodes this table line for line.

## 4. The Iraqi regulation also defines its own glossary terms

For the avoidance of doubt, the regulation's Annex A explicitly
defines `Wi-Fi` as *"802.11 Local Area Networking in 2.4 and 5 GHz
ISM bands"*. So when the maintainers ask whether this regulation
in fact covers Wi-Fi, the answer from the regulator is yes,
in writing, in the regulation itself.

The same annex defines DFS, TPC, LBT, DAA, EIRP and AFA in the
exact wireless-regdb sense.

## 5. Encoding choices and where they came from

A few wireless-regdb encoding details require explanation, because
they are interpretations of the regulation's wording rather than
direct copies of numerical limits:

1. **NO-OUTDOOR on 5150–5725 MHz.** The regulation labels these
   rows simply as "Indoor". The wireless-regdb idiom for that is
   the `NO-OUTDOOR` flag.

2. **No NO-OUTDOOR on 5725–5875 MHz.** The regulation explicitly
   labels this row "Indoor and outdoor".

3. **DFS on 5250–5350 MHz.** The regulation's own column for this
   row is empty for mitigations, but the cited standard
   (EN 301 893) requires DFS in this sub-band, and the corresponding
   row for 5470–5725 in the same table does state DFS+TPC. Reading
   the regulation as a whole, DFS for 5250–5350 is required by the
   incorporated standard.

4. **Single EIRP figure for 5725–5875 MHz.** The regulation gives
   two figures (2000 mW for 10 MHz channels, 4000 mW for 20 MHz
   channels). The wireless-regdb format expresses one ceiling per
   band; the 4000 mW figure is used because it is the higher value
   that the regulation explicitly permits.

5. **6 GHz channel width set to 80 MHz.** The regulation does not
   explicitly distinguish standard-power from low-power indoor
   (LPI) operation, nor does it mention AFC. The conservative
   choice is to encode the 6 GHz block at 80 MHz (the widest
   non-AFC option in current practice) and leave a follow-up patch
   for a wider channelisation once CMC clarifies AFC requirements.

6. **AUTO-BW on the 5 GHz RLAN rows.** Standard practice for
   EN 301 893–compliant entries; no AUTO-BW is set on the 6 GHz
   row pending the AFC question above.

If the maintainers prefer a different encoding for any of these
six points, please push back; the underlying regulatory text is
clear and any of these can be re-encoded without changing what is
actually permitted under Iraqi law.

## 6. The 5.8 GHz figure looks unusually high — it is intentional

`(5725 - 5875 @ 80), (4000 mW)` with no NO-OUTDOOR is not a typo.
This is what Iraq's own regulation states for this sub-band, citing
EN 302 502. It is the BFWA value, not the Non-Specific SRD value.
This choice puts Iraq at the high end of the regional spectrum
policy for the 5.8 GHz band. It is included verbatim because the
purpose of wireless-regdb is to reflect what each country's
regulator actually permits.

## 7. What is not in the patch

- **5850–5925 MHz ITS / V2X bands.** Article 4-1-8 of the same
  regulation covers ITS at 5855–5925 MHz with 2 W EIRP, but this
  is a non-Wi-Fi RLAN application and is outside the scope of
  what wireless-regdb usually encodes for `country` blocks.

- **All non-Wi-Fi SRD bands.** The regulation also covers RFID,
  inductive applications, alarms, model control, automotive radar,
  level probing radar, hearing aids, active medical implants, and
  the full UWB regime (Articles 4-2-1 through 4-2-6). None of these
  is a wireless-regdb concern.

- **6 GHz beyond 6425 MHz.** The Iraqi regulation only addresses
  5945–6425 MHz at 6 GHz; the 6425–7125 MHz upper portion is not
  covered, and the patch therefore does not include it.

## 8. Submission checklist

- [ ] Verify the patch applies cleanly against the current
      `wireless-regdb` master; the IQ block must be inserted in
      alphabetical order, between `IN` and `IR`.
- [ ] Build `regulatory.db` locally and confirm with
      `regdbdump regulatory.db | grep -A8 'country IQ'` that the
      output matches the proposed table exactly.
- [ ] Post the cover letter and patch on the OpenWrt forum thread
      (231380) for community review by Iraqi engineers before
      sending upstream.
- [ ] Send to `linux-wireless@vger.kernel.org` with cc to
      `wireless-regdb@lists.infradead.org`.

## 9. A note on responsibility

The numerical content of this patch is taken verbatim from a public
Iraqi government regulation. The encoding choices listed in §5 are
the patch author's, and they are reversible.

Author: Mohammed Abdullah Ali Al-Obaidi (mnew_iraq@yahoo.com),
OpenWrt forum handle `mnewiraq`. Any objection to the encoding
choices should be raised to that author or in the upstream review
thread, not to the CMC.


CONFIDENTIALITY. This communication is intended exclusively for use by the addressee and may contain confidential and/or privileged information. If you receive this communication unintentionally please inform the sender by reply immediately and permanently delete it from your system; you should not copy this communication or disclose its contents to anyone.

Re: [PATCH] wireless-regdb: add regulatory rules for Iraq (IQ)

[Chen-Yu Tsai]

Hi,

On Sat, May 16, 2026 at 3:43 PM <Mohammed.Al-Obaidi@badraproject.com> wrote:
>
> Kind reminder, any update on the subject?

Please send the patch directly to the mailing list, not as an attachment.
Otherwise there is no way to review the patch on the mailing list.

`git send-email` should do that for you.

About the commit message:

The section "Notes on the encoding chosen below" is really not needed,
unless something is not a direct translation from text to the standard
rules for wireless-regdb, or if other materials were referenced.

So talking about "Indoor" encoded as "NO-OUTDOOR" is redundant. Mentioning
DFS is also not needed, since it is obvious from the table you provided.
AUTO-BW for 5150-5350 MHz is also quite standard.

Things that are worth mentioning:

1. TPC requirements in the regulation and what was done to make the rule
   compliant (as we don't support TPC)
2. Choice between indoor-only and indoor+outdoor rules when both exist
   but with different requirements (database and Linux support only one
   rule per band)
3. unique 5.8 GHz figure as you gave


Also:

* 5725-5875 MHz uses the higher of the two stated EIRP figures
  (4000 mW for 20 MHz channels) since wireless-regdb expresses a
  per-band ceiling, not a per-channel-width ceiling.

This is slightly wrong. wireless-regdb expresses a ceiling that makes
devices compliant with all regulations in all configurations. So if
there is a power spectral density that allows the maximum EIRP at
a wider channel, but a reduced EIRP at 20 MHz, we will use the reduced
number.

As for 10 MHz, I don't think it is supported, so we don't really consider
that case. I could be wrong though.

Johannes, could you shed some light on 10 MHz channel width support?


Thanks
ChenYu

> Mohammed
>
> From: Mohammed Abdalla [mailto:mnew_iraq@yahoo.com]
> Sent: Tuesday, May 5, 2026 7:12 PM
> To: wireless-regdb@lists.infradead.org; linux-wireless@vger.kernel.org
> Cc: Mohammed Abdullah Ali Al-Obaidi <Mohammed.Al-Obaidi@badraproject.com>
> Subject: [PATCH] wireless-regdb: add regulatory rules for Iraq (IQ)
>
> ## 1. Why this patch exists
>
> Iraq is currently absent from `wireless-regdb/db.txt`. As a
> consequence, every OpenWrt and Linux device set to `country=IQ`
> falls back to the world domain (`00`), which marks most of the
> 5 GHz spectrum as `no IR` and limits 2.4 GHz EIRP to 20 dBm. A
> public OpenWrt forum thread on the Archer AX23 in Iraq concluded
> with the maintainers' standard answer:
>
> > *"IQ is the correct code for the place; once an engineer shares
> > the local radio laws with regdb maintainers it will be added."*
>
> This patch is that contribution.
>
> ## 2. The primary source
>
> The Iraqi Communications and Media Commission (CMC), the national
> regulator, has issued a numerical regulation specifically governing
> unlicensed Wi-Fi, SRD, and UWB devices:
>
> - **Title:** Regulation on short-range radio communication devices
>   (SRD) and devices using ultra-broadband (UWB) technology
> - **Issuer:** Republic of Iraq, CMC, Telecommunications Regulatory
>   Department, International Relations Section
> - **Decree:** Council of Commissioners decision No. 122/q-2025
> - **In force from:** 2025-09-22
> - **Edition:** First edition, 2025; 26 pages
> - **Direct PDF:**
>   <https://cmc.iq/wp-content/uploads/2025/09/Regulation-on-short-range-radio-communication-devices-SRD-and-devices-using-ultra-broadband-UWB-technology.pdf>
>
> Article 4-1-13 of that regulation, titled "Wireless Access Systems
> (WAS)", contains a full numerical table for every Wi-Fi band. This
> patch reproduces that table directly. Nothing in the proposed
> `country IQ:` block is inferred or extrapolated.
>
> ## 3. The Article 4-1-13 table, verbatim
>
> | Band | Use | Max EIRP | Required mitigations | Cited standard |
> |---|---|---|---|---|
> | 2400 – 2483.5 MHz | Indoor and outdoor | 100 mW | LBT and DAA | EN 300 328, ERC/REC 70-03 |
> | 5150 – 5250 MHz | Indoor | 200 mW | — | EN 301 893, ITU Res. 229 (Rev. WRC-19) |
> | 5250 – 5350 MHz | Indoor | 200 mW | — (DFS implied via EN 301 893) | EN 301 893 |
> | 5470 – 5725 MHz | Indoor | 1000 mW | DFS and TPC (stated explicitly) | EN 301 893 |
> | 5725 – 5875 MHz | Indoor and outdoor | 2000 mW (10 MHz ch) / 4000 mW (20 MHz ch) | — | EN 302 502 |
> | 5945 – 6425 MHz | Indoor | 200 mW | — | EN 303 687, ECC Report 75 |
> | 57000 – 66000 MHz | Indoor | 10000 mW | LBT and DAA | EN 302 567 |
>
> The proposed `country IQ:` block encodes this table line for line.
>
> ## 4. The Iraqi regulation also defines its own glossary terms
>
> For the avoidance of doubt, the regulation's Annex A explicitly
> defines `Wi-Fi` as *"802.11 Local Area Networking in 2.4 and 5 GHz
> ISM bands"*. So when the maintainers ask whether this regulation
> in fact covers Wi-Fi, the answer from the regulator is yes,
> in writing, in the regulation itself.
>
> The same annex defines DFS, TPC, LBT, DAA, EIRP and AFA in the
> exact wireless-regdb sense.
>
> ## 5. Encoding choices and where they came from
>
> A few wireless-regdb encoding details require explanation, because
> they are interpretations of the regulation's wording rather than
> direct copies of numerical limits:
>
> 1. **NO-OUTDOOR on 5150–5725 MHz.** The regulation labels these
>    rows simply as "Indoor". The wireless-regdb idiom for that is
>    the `NO-OUTDOOR` flag.
>
> 2. **No NO-OUTDOOR on 5725–5875 MHz.** The regulation explicitly
>    labels this row "Indoor and outdoor".
>
> 3. **DFS on 5250–5350 MHz.** The regulation's own column for this
>    row is empty for mitigations, but the cited standard
>    (EN 301 893) requires DFS in this sub-band, and the corresponding
>    row for 5470–5725 in the same table does state DFS+TPC. Reading
>    the regulation as a whole, DFS for 5250–5350 is required by the
>    incorporated standard.
>
> 4. **Single EIRP figure for 5725–5875 MHz.** The regulation gives
>    two figures (2000 mW for 10 MHz channels, 4000 mW for 20 MHz
>    channels). The wireless-regdb format expresses one ceiling per
>    band; the 4000 mW figure is used because it is the higher value
>    that the regulation explicitly permits.
>
> 5. **6 GHz channel width set to 80 MHz.** The regulation does not
>    explicitly distinguish standard-power from low-power indoor
>    (LPI) operation, nor does it mention AFC. The conservative
>    choice is to encode the 6 GHz block at 80 MHz (the widest
>    non-AFC option in current practice) and leave a follow-up patch
>    for a wider channelisation once CMC clarifies AFC requirements.
>
> 6. **AUTO-BW on the 5 GHz RLAN rows.** Standard practice for
>    EN 301 893–compliant entries; no AUTO-BW is set on the 6 GHz
>    row pending the AFC question above.
>
> If the maintainers prefer a different encoding for any of these
> six points, please push back; the underlying regulatory text is
> clear and any of these can be re-encoded without changing what is
> actually permitted under Iraqi law.
>
> ## 6. The 5.8 GHz figure looks unusually high — it is intentional
>
> `(5725 - 5875 @ 80), (4000 mW)` with no NO-OUTDOOR is not a typo.
> This is what Iraq's own regulation states for this sub-band, citing
> EN 302 502. It is the BFWA value, not the Non-Specific SRD value.
> This choice puts Iraq at the high end of the regional spectrum
> policy for the 5.8 GHz band. It is included verbatim because the
> purpose of wireless-regdb is to reflect what each country's
> regulator actually permits.
>
> ## 7. What is not in the patch
>
> - **5850–5925 MHz ITS / V2X bands.** Article 4-1-8 of the same
>   regulation covers ITS at 5855–5925 MHz with 2 W EIRP, but this
>   is a non-Wi-Fi RLAN application and is outside the scope of
>   what wireless-regdb usually encodes for `country` blocks.
>
> - **All non-Wi-Fi SRD bands.** The regulation also covers RFID,
>   inductive applications, alarms, model control, automotive radar,
>   level probing radar, hearing aids, active medical implants, and
>   the full UWB regime (Articles 4-2-1 through 4-2-6). None of these
>   is a wireless-regdb concern.
>
> - **6 GHz beyond 6425 MHz.** The Iraqi regulation only addresses
>   5945–6425 MHz at 6 GHz; the 6425–7125 MHz upper portion is not
>   covered, and the patch therefore does not include it.
>
> ## 8. Submission checklist
>
> - [ ] Verify the patch applies cleanly against the current
>       `wireless-regdb` master; the IQ block must be inserted in
>       alphabetical order, between `IN` and `IR`.
> - [ ] Build `regulatory.db` locally and confirm with
>       `regdbdump regulatory.db | grep -A8 'country IQ'` that the
>       output matches the proposed table exactly.
> - [ ] Post the cover letter and patch on the OpenWrt forum thread
>       (231380) for community review by Iraqi engineers before
>       sending upstream.
> - [ ] Send to `linux-wireless@vger.kernel.org` with cc to
>       `wireless-regdb@lists.infradead.org`.
>
> ## 9. A note on responsibility
>
> The numerical content of this patch is taken verbatim from a public
> Iraqi government regulation. The encoding choices listed in §5 are
> the patch author's, and they are reversible.
>
> Author: Mohammed Abdullah Ali Al-Obaidi (mnew_iraq@yahoo.com),
> OpenWrt forum handle `mnewiraq`. Any objection to the encoding
> choices should be raised to that author or in the upstream review
> thread, not to the CMC.
>
>
> CONFIDENTIALITY. This communication is intended exclusively for use by the addressee and may contain confidential and/or privileged information. If you receive this communication unintentionally please inform the sender by reply immediately and permanently delete it from your system; you should not copy this communication or disclose its contents to anyone.

Re: [PATCH] wireless-regdb: add regulatory rules for Iraq (IQ)

[Johannes Berg]

Hi,

> As for 10 MHz, I don't think it is supported, so we don't really consider
> that case. I could be wrong though.
> 
> Johannes, could you shed some light on 10 MHz channel width support?

It's ... complicated?

We support a _very_ limited set of 5/10 MHz operation, but I think most
of it is fairly much unreachable from userspace. I asked about removing
it entirely a few years ago, and some people were opposed, but said
people also haven't actually helped take care of it or anything ... I
was just tempted again a little while back to remove it due to the rates
issues.

Ever since my commit 5add321c329b ("wifi: cfg80211: remove scan_width
support") I believe it has been unreachable on the *client* side, but
given that we still have some support in _nl80211_parse_chandef() and
chandef functions, I expect that it would be possible to still configure
an AP or monitor interface with 5/10 MHz, though only with drivers that
have WIPHY_FLAG_SUPPORTS_5_10_MHZ, i.e. ath5k, ath9k and hwsim. I
wouldn't mind removing it all though.


Is this a concern from a regulatory POV right now, due to say power
density by channel width? This feels somewhat familiar even with higher
channel widths - maybe it's time to add such an attribute to the regdb?

johannes

Re: [PATCH] wireless-regdb: add regulatory rules for Iraq (IQ)

[Chen-Yu Tsai]

On Tue, May 19, 2026 at 4:55 PM Johannes Berg <johannes@sipsolutions.net> wrote:
>
> Hi,
>
> > As for 10 MHz, I don't think it is supported, so we don't really consider
> > that case. I could be wrong though.
> >
> > Johannes, could you shed some light on 10 MHz channel width support?
>
> It's ... complicated?
>
> We support a _very_ limited set of 5/10 MHz operation, but I think most
> of it is fairly much unreachable from userspace. I asked about removing
> it entirely a few years ago, and some people were opposed, but said
> people also haven't actually helped take care of it or anything ... I
> was just tempted again a little while back to remove it due to the rates
> issues.
>
> Ever since my commit 5add321c329b ("wifi: cfg80211: remove scan_width
> support") I believe it has been unreachable on the *client* side, but
> given that we still have some support in _nl80211_parse_chandef() and
> chandef functions, I expect that it would be possible to still configure
> an AP or monitor interface with 5/10 MHz, though only with drivers that
> have WIPHY_FLAG_SUPPORTS_5_10_MHZ, i.e. ath5k, ath9k and hwsim. I
> wouldn't mind removing it all though.
>
>
> Is this a concern from a regulatory POV right now, due to say power
> density by channel width? This feels somewhat familiar even with higher
> channel widths - maybe it's time to add such an attribute to the regdb?

There are some regulations that say X dBm for 10 MHz or X*2 dBm for 20 MHz.
I've mostly been ignoring 10 MHz since that doesn't seem to be a thing
in modern WiFi. This is slightly different from the newer PSD rules we
are seeing with 6 GHz, since it only gives two points instead of an
actual density value.


ChenYu