From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: netdev@vger.kernel.org, Jiri Benc <jbenc@suse.cz>,
"John W. Linville" <linville@tuxdriver.com>,
Jean Tourrilhes <jt@hpl.hp.com>
Subject: Re: [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211
Date: Tue, 24 Oct 2006 10:25:44 +0200 [thread overview]
Message-ID: <1161678344.2840.2.camel@ux156> (raw)
In-Reply-To: <43e72e890610231541k2e8e6dcbq98f58a77aa8a52d7@mail.gmail.com>
Alright, here's more now that I can think clearly again :)
> ISO 3166-1, as part of the ISO 3166 standard, provides codes for the names
> of countries and dependent areas. It was first published in 1974 by
> the International Organization for Standardization (ISO) and defines three
> different codes for each area:
>
> * ISO 3166-1 alpha-2, a two-letter system with many applications,
> most notably the Internet top-level domains (ccTLD) for countries.
> * ISO 3166-1 alpha-3, a three-letter system.
> * ISO 3166-1 numeric, a three-digit numerical system, which is
> identical to that defined by the United Nations Statistical Division.
>
> Although this would usually be only used in userspace IEEE-802.11d
> has made use of ISO-3166-1 alpha 3. This mapping was added
> to enhance stack support for IEEE-802.11d and 802.11 Regulatory
> Domain control. ieee80211_regdomains makes use of this module
> by creating a map of iso3166 alpha3 country code to stack
> regulatory domain.
But if 802.11d only requires alpha 3, why put all the other stuff into
the kernel as well?
johannes
next prev parent reply other threads:[~2006-10-24 8:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 22:41 [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211 Luis R. Rodriguez
2006-10-23 23:32 ` Johannes Berg
2006-10-24 5:33 ` Luis R. Rodriguez
2006-10-24 12:03 ` John W. Linville
2006-10-24 17:41 ` Luis R. Rodriguez
2006-10-25 8:24 ` Jiri Benc
2006-10-25 16:18 ` Luis R. Rodriguez
2006-10-24 8:25 ` Johannes Berg [this message]
2006-10-24 17:31 ` Luis R. Rodriguez
2006-10-24 14:02 ` David Kimdon
2006-10-24 17:47 ` Luis R. Rodriguez
2006-10-24 20:03 ` Simon Barber
2006-10-24 22:03 ` Luis R. Rodriguez
2006-10-24 22:52 ` Michael Wu
2006-10-25 17:43 ` Luis R. Rodriguez
2006-10-25 22:00 ` Johannes Berg
2006-10-26 14:35 ` Dan Williams
2006-10-26 14:43 ` Johannes Berg
2006-10-26 15:04 ` Luis R. Rodriguez
2006-10-26 15:33 ` Dan Williams
2006-10-26 21:41 ` Simon Barber
2006-10-26 21:47 ` Johannes Berg
2006-10-26 21:48 ` Johannes Berg
2006-10-24 22:56 ` Simon Barber
2006-10-25 5:03 ` Dan Williams
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=1161678344.2840.2.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=jbenc@suse.cz \
--cc=jt@hpl.hp.com \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=netdev@vger.kernel.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).