linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emil Petersky <emil.petersky@streamunlimited.com>
To: Seth Forshee <seth.forshee@canonical.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 16:08:24 +0100	[thread overview]
Message-ID: <31a00c5d-bb58-d423-d625-9ba4ebd177cc@streamunlimited.com> (raw)
In-Reply-To: <20191029130853.GN30813@ubuntu-xps13>

Hi Seth,

it seems, that EU domain is advertised by APs/Routers here in Europe.
I know, that many clients use EU domain (at least internally in firmware) as well.
I would like to add it and use it along with setting for individual EU members.

I've made statistic of one WiFi scan in an apartment house in Vienna (Austria).
Results are:
35 x EU (Mostly UPC/Ralink Access points)
30 x no region info
 7 x AT
 3 x DE
 2 x NL

Thanks and best regards,

Emil





On 29/10/2019 14:08, Seth Forshee wrote:
> 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


-- 
Emil Petersky

________________________________________________________________________

StreamUnlimited Engineering GmbH
High Tech Campus Vienna, Gutheil-Schoder-Gasse 10, 1100 Vienna, Austria
Office: +43 1 667 2002 4679 Fax: +43 1 667 2002 4401
Mail to: emil.petersky@streamunlimited.com
Visit us: www.streamunlimited.com

Meet us at:
CES - Las Vegas, 7 - 10 January, Westgate Hotel
ISE - Amsterdam, 11 - 14 February


  parent reply	other threads:[~2019-10-29 15: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
2019-10-29 14:57           ` Emil Petersky
2019-10-29 15:08           ` Emil Petersky [this message]
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=31a00c5d-bb58-d423-d625-9ba4ebd177cc@streamunlimited.com \
    --to=emil.petersky@streamunlimited.com \
    --cc=linux-wireless@vger.kernel.org \
    --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).