linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petko Bordjukov <bordjukov@gmail.com>
To: Maximilian Engelhardt <engelhardt@perisens.de>
Cc: seth.forshee@canonical.com, linux-wireless@vger.kernel.org,
	maxi@daemonizer.de, wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for	Germany (DE) on 5GHz
Date: Tue, 19 Apr 2016 22:27:40 +0300	[thread overview]
Message-ID: <87k2jt5rgz.wl-bordjukov@gmail.com> (raw)
In-Reply-To: <1958820.LBuzOElZFT@perisens15>

[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]

Hello,

Just to add my input to this thread. I've previously contributed the SRD ranges
for Bulgaria, hopefully this info will provide pointers for research in other EU
countries. Since then I've doublechecked the standards situation for Wi-Fi with
the local communications regulation commission and one of the staffers there has
given me an expert opinion (I would attach it, but it's a nasty HTML email in
Bulgarian, if there's interest, I'd be glad to share and translate it).

The gist on the SRDs is that in Bulgaria they fall under the following
standards (which correspond to ETSI standards):

BDS EN 300 440-2[0]
BDS EN 300 674-2-2[1]

Note that the first one is a harmonized standard (so in theory it should be
universally adopted accross the EU) and the second one is a candidate harmonized
standard (so you should check if it's already been adopted locally).

As far as I could tell, BDS EN 300 674-2-2 defines the maximum e.i.r.p. for the
SRD range but someone more knowledgable should take a look, too.

One thing that they did not mention is that there's a BDS EN 300 440-1[2] that
does indeed also specify the max e.i.r.p. but I've reached this through my own
research and did not get this info from anybody affilliated with the CRC.

Also, note that the EN 300 440-1[3] still does NOT seem to be a harmonized standard
(again, probably one should check if it has been adopted locally).

[0] http://www.bds-bg.org/en/standard/?natstandard_document_id=47135
[1] http://www.bds-bg.org/bg/standard/?natstandard_document_id=32906
[2] http://www.bds-bg.org/bg/standard/?natstandard_document_id=30570
[3] http://www.etsi.org/deliver/etsi_en/300400_300499/30044001/01.06.01_60/en_30044001v010601p.pdf

On Tue, 19 Apr 2016 21:03:16 +0300,
Maximilian Engelhardt wrote:
>
> Hi,
>
> In Europe ETSI standardized the used for short range devices (SRD) [1] in ETSI
> EN 300 440-1 [2].

[-- Attachment #2: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-04-19 19:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 18:03 wireless-regdb: Update regulatory rules for Germany (DE) on 5GHz Maximilian Engelhardt
2016-04-19 19:27 ` Petko Bordjukov [this message]
2016-04-19 20:11   ` [wireless-regdb] " Bjørn Mork
2016-04-19 20:38     ` Petko Bordjukov
2016-04-21 13:19 ` Seth Forshee
2016-04-21 18:08   ` Maximilian Engelhardt
2016-04-21 18:51     ` Seth Forshee
2016-04-21 20:13       ` [wireless-regdb] " Anne Marcel Roorda
2016-04-21 20:40         ` Seth Forshee
2016-05-02 13:42     ` 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=87k2jt5rgz.wl-bordjukov@gmail.com \
    --to=bordjukov@gmail.com \
    --cc=engelhardt@perisens.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maxi@daemonizer.de \
    --cc=seth.forshee@canonical.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).