Luis R. Rodriguez wrote:
On Thu, Jul 10, 2008 at 08:52:46AM -0700, Sam Leffler wrote:
Luis R. Rodriguez wrote:
The industry currently has different techniques for parsing and using
Country IEs. What I currently propose is to take the common denominator
between what the AP provides, what CRDA has and what the driver can
provide privately through its callback. So the wireless core can keep
as the common denominator between the AP's Country IE and what CRDA
has for the alpha2 provided by the Country IE. Drivers themselves can
further enhance regulatory enforcement by relying on private driver
data if they wish so.
Can you elaborate on the first sentence? Are you just saying that some
software blindly trusts the contents of the country IE and doesn't
constrain it's use (as you describe)? Or are you saying drivers
interpret the contents of the country IE in ways different than spec'd?
I'm saying drivers and software stacks used tend to vary on how they
use the country IE. I believe most vendor drivers *never* simply
use what the AP provides due to considerations about "rogue" APs.
I can see why too though -- but it just means the spec didn't
account for these considerations. Hence my suggestion.
Can you elaborate on the differences you see in the drivers and software
stacks? I haven't encountered significant differences.
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
