linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <sforshee@kernel.org>
To: Timo Witte <timo.witte@gmail.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: wireless-regdb: Update regulatory rules for Germany (DE) on 6GHz
Date: Wed, 21 Jul 2021 09:29:06 -0500	[thread overview]
Message-ID: <YPgvMph+3vRbrol3@ubuntu-x1> (raw)
In-Reply-To: <CANB4YXRtyvgu946rL=gxaRqhXja1qfBQ+DSYfiMvYcax7o45EQ@mail.gmail.com>

On Mon, Jul 19, 2021 at 02:20:34AM +0200, Timo Witte wrote:
> The bundesnetzagentur has assigned WiFi 6E frequencies for germany you
> this is the
> publication of that change:
> https://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/MobilfunkDectWlanCBFunk/vfg552021WLAN6GHz.pdf?__blob=publicationFile&v=3
> 
> Following frequencies have been assigned for general use:
> 5945 - 6425 Mhz
> maximum (200 mW)
> No outdoor usage is allowed for 200mW
> 
> For "very low power devices" outdoor usage
> is allowed, but only with (25 mW)
> same frequency range 5945 - 6425
> 
> There is no DFS requirement.

This all matches with my reading of a translated version of the
document. Do you plan to send a patch to add this range? If not, I can
send one.

Thanks,
Seth

  reply	other threads:[~2021-07-21 14:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANB4YXTf0DhJfL6kPa26ZCzj8FRwwdw_enGROzL-zXuWGyrwOQ@mail.gmail.com>
2021-07-19  0:20 ` wireless-regdb: Update regulatory rules for Germany (DE) on 6GHz Timo Witte
2021-07-21 14:29   ` Seth Forshee [this message]
2021-07-21 14:55     ` Timo Witte
2021-07-21 14:57     ` Timo Witte
2021-07-21 15:27       ` Seth Forshee
2021-07-21 15:51         ` Timo Witte
2021-08-01  1:42           ` Timo Witte
     [not found]           ` <CANB4YXQMDAxwk+b+wXsTg8OzFMa4gZHxNOZ6UoWT6McM9hEVcg@mail.gmail.com>
2021-08-03  2:40             ` 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=YPgvMph+3vRbrol3@ubuntu-x1 \
    --to=sforshee@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=timo.witte@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).