public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: mj888@mail.co.uk
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for Great Britian (GB) on 5GHz
Date: Wed, 28 Apr 2021 08:05:26 -0500	[thread overview]
Message-ID: <YIldlmkRu633DDY8@ubuntu-x1> (raw)
In-Reply-To: <20210428115428.AEB37A0151@smtp03.mail.de>

On Wed, Apr 28, 2021 at 01:54:28PM +0200, mj888@mail.co.uk wrote:
> Hi Seth,   Please change wireless-regdb for Great Britain (GB) on 5Ghz (band C - 5.8Ghz)   As per Ofcom statement from 24 July 2020 - Improving spectrum access for Wi-Fi Spectrum use in the 5 GHz and 6 GHz bands https://www.ofcom.org.uk/consultations-and-statements/category-2/improving-spectrum-access-for-wi-fi    DFS IS NOT LONGER REQUIRED ON 5.8GHZ (BAND C - 5725-5850 MHZ) FOR INDOOR USE / DEVICES UP TO 200MW   
>  I believe required changes are as follows:  - (5725 - 5875 @ 80), (100 mW), DFS  + (5725 - 5850 @ 80), (200 mW)        Thank you     

The proposed changes to IR 2030 are contained in Annex 3 of the document
you linked to. I pulled up IR 2030 from the Ofcom website:

https://www.ofcom.org.uk/__data/assets/pdf_file/0028/84970/ir-2030.pdf

As of yet this document does not contain the proposed changes. I'm not
familiar with the process for chaning regulations in the UK, but based
on section 1.6 it sounds like the document expresses that Ofcom made a
decision to amend the regulations, but that the document itself does not
have the effect of actually putting those changes into effect. If you
are more familiar with the process and I have misunderstood something,
please clarify.

You are correct though that this range should be 5725-5850 MHz. Seems it
should also be NO-OUTDOOR.

Thanks,
Seth

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


       reply	other threads:[~2021-04-28 13:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210428115428.AEB37A0151@smtp03.mail.de>
2021-04-28 13:05 ` Seth Forshee [this message]
2021-05-07 11:44 [wireless-regdb] wireless-regdb: Update regulatory rules for Great Britian (GB) on 5GHz mj888

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=YIldlmkRu633DDY8@ubuntu-x1 \
    --to=seth.forshee@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mj888@mail.co.uk \
    --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