Talk:IEEE 802.11w-2009

This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles

Low

This article has been rated as Low-importance on the project's importance scale.

This article is supported by Networking task force (assessed as Low-importance).

This article is supported by WikiProject Computer Security (assessed as Low-importance).

Things you can help WikiProject Computer Security with:

Article alerts will be generated shortly by AAlertBot. Please allow some days for processing. More information...

Answer question about Same-origin_policy
Review importance and quality of existing articles
Identify categories related to Computer Security
Tag related articles
Identify articles for creation (see also: Article requests)
Identify articles for improvement
Create the Project Navigation Box including lists of adopted articles, requested articles, reviewed articles, etc.
Find editors who have shown interest in this subject and ask them to take a look here.

Talk[edit]

complicated crap to fix an known problem. 802.11 is so retarded. —The preceding unsigned comment was added by 212.202.23.33 (talk • contribs) 22:47, 25 December 2006 (UTC)

. The reference link is invalid - can a link to a direct source be provided? —Preceding unsigned comment added by 72.66.64.248 (talk) 17:28, 25 August 2010 (UTC)[reply]

Copy and Pasted Section?[edit]

The section Usuage seems to be copied from some sort of scientific paper:

We finally see some encryption for management frames, which has been desired for a longer time. With the requirement for WFA certification of PMF for 11n, 11ac and Passpoint, we should be able to set this feature to optional, the required/mandatory flag can only be used if the client support is assured. It may be a rare case, but some hackers use the disassociate attacks to move clients to their own AP, which can now be prevented. An attacker can still send channel switch announcements to steer clients to his AP and of course as soon as an attacker is connected to the network with PMF, he or she is able to perform attacks with protected frames as well. So the remaining disturbance of client connections/transmissions without a network connection are RF jamming and CTS control frames with long reservation times.

--2.160.28.64 (talk) 09:55, 19 August 2017 (UTC)[reply]

Not suitable for wikipedia article?[edit]

Windows 8. This has caused a number of compatibility issues particularly with wireless access points that are not compatible with the standard. Rolling back the wireless adapter driver to one from Windows 7 usually fixes the issue.

This seems temporal and too specific for a wikipedia article. Maybe marking it as historical? A separate History section? --Xerces8 (talk) 13:00, 19 June 2020 (UTC)[reply]