From: Seth Forshee <seth.forshee@canonical.com>
To: Emil Petersky <emil.petersky@streamunlimited.com>
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: Re: [PATCH] wireless-regdb: Create entry for united European region
Date: Tue, 29 Oct 2019 08:08:53 -0500 [thread overview]
Message-ID: <20191029130853.GN30813@ubuntu-xps13> (raw)
In-Reply-To: <76f464e9-8806-ecbf-2dc8-67bb4190ecc7@streamunlimited.com>
On Tue, Sep 17, 2019 at 11:55:07AM +0200, Emil Petersky wrote:
> Create entry for united European region, as usage of frequency bands
> is harmonized over EU and almost all CEPT countries as well.
>
> All EU countries and almost all CEPT countries accepted decisions
> 2005/513/EC (5GHz RLAN, EN 301 893)
> and 2006/771/EC (amended by 2008/432/EC, Short-Range Devices, EN 300 440)
> EU decision 2005/513/EC:
> https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02005D0513-20070213
> EU decision 2006/771/EC:
> https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02008D0432-20080611
> Harmonized CEPT countries:
> https://www.ecodocdb.dk/download/25c41779-cd6e/Rec7003e.pdf
> Such decision make sense to create united European region (EU) in regdb
>
> United region for EU in regdb will enable much easier handling of proper
> wlan parameters on embedded devices sold across the Europe.
I'm a little curious about this one. I do agree that it would simplify
things, but is an EU contry code something standard that wireless APs
generally will advertise, or that clients will understand?
And we do still have all the individual countries to maintain. Maybe it
would make sense to define an EU region as rules that countries could
inherit, and then have rules for any deviations from the common EU
rules. Thoughts?
Thanks,
Seth
next prev parent reply other threads:[~2019-10-29 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 14:19 [PATCH] wireless-regdb: Fix ranges of EU countries as they are harmonized since 2014 Emil Petersky
2019-09-07 23:56 ` Seth Forshee
2019-09-17 7:58 ` Emil Petersky
2019-09-17 8:59 ` [PATCH] wireless-regdb: Harmonize ranges of CEPT countries (stand of July 2019) Emil Petersky
2019-09-17 9:55 ` [PATCH] wireless-regdb: Create entry for united European region Emil Petersky
2019-10-29 13:08 ` Seth Forshee [this message]
2019-10-29 14:57 ` Emil Petersky
2019-10-29 15:08 ` Emil Petersky
2019-11-17 14:40 ` [wireless-regdb] " b.K.il.h.u+tigbuh
2019-10-29 13:02 ` [PATCH] wireless-regdb: Harmonize ranges of CEPT countries (stand of July 2019) Seth Forshee
2019-10-29 13:01 ` [PATCH] wireless-regdb: Fix ranges of EU countries as they are harmonized since 2014 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=20191029130853.GN30813@ubuntu-xps13 \
--to=seth.forshee@canonical.com \
--cc=emil.petersky@streamunlimited.com \
--cc=linux-wireless@vger.kernel.org \
--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).