IEEE Approves Revision of Wireless LAN Standard
An anonymous reader writes "IEEE announced the publication of IEEE 802.11-2012, which defines the technology for the world's premier wireless LAN products. The new IEEE 802.11-2012 revision has been expanded significantly by supporting devices and networks that are faster and more secure, while offering improved Quality of Service and improved cellular network hand-off. The standard's relevance continues to expand with the emergence of new applications, such as the smart grid, which augments the facility for electricity generation, distribution, delivery and consumption with a two-way, end-to-end network for communications and control."
And license fees?
Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
The published IEEE standard is only for paid subscription.
OK, so how, precisely, are we to adhere to IEEE standards when viewing the standard is FUCKING PAYWALLED?
Seriously, folks, this culture of pay-to-play needs to be shut down. When you can't even read a fucking standard which will affect the entire industry without some asshole demanding payment, the system is broken.
WTF ever happened to public domain?
An enigma, wrapped in a riddle, shrouded in bacon and cheese
It's not worth it. It's a high level overview, and it's only 38 pages. I care deeply about the changes in it, and this doesn't mention ANY of the new important things that was meant to happen (eg, better adhoc). So, it's a bit of a let down, actually.
--Rob
Schlock Mercenary.
I doubt there is a single person who knows about every aspect of IEEE 802.11.
There is. His name is Matthew S. Gast. Read this book and you'll have a solid foundation, too.
kmem russian roulette: Aquillar> dd if=/dev/urandom of=/dev/kmem bs=1 count=1 seek=$RANDOM
It's not that it is hard, or particularly expensive, it is that it is a barrier to casual perusal. Said casual perusal is important, because a bored network admin who just happens to read the standard (which is way beyond his job requirements to do) might actually avoid mis-applying the technology in some obscure way that, while it works just fine for now, eventually causes grief down the road. Moreover, even though these standards are vetted pretty well, it is often the case that they still have a hole in them here or there that only a practicing in-the-trenches professional would spot.
Me I just wanted to see if they formalized any DH-exchange-based alternative to the weak 4-way handshake, or maybe formalized a way to close the hole-196 attack vector by specifying a per-host GTK mode for networks where multicast just doesn't make sense anyway (which is the case for most enterprise BYOD WLANs, which are precisely the ones most affected by hole-196.)
It's worth maybe an hour of my spare time. It isn't worth $5 of my money on top of that at this point. While I do think people who arrange and work hard on standards should get paid for their efforts, this is not the right bridge at which to collect that toll... all it does is annoy and discourage technical journalists and volunteer open source developers.
Someone had to do it.