doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 1 Action Frame Protection Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. Date: Authors:

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 2 Protection of Action Frames w D6.0 currently restricts protection of Action Frames to all Action Categories with the exception of a Public Action Frame

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 3 Management Frame Formats Non-Management Frame Protection Capable Frame Management Frame Protection Capable Unicast Frame Management Frame Protection Capable Broadcast/Multicast Frame

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 4 Action Frame Type defined in Action IE If Management Frame Protection is successfully negotiated, encrypted unicast Action Frames can not be distinguished!

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 5 Action Frame Category Values CategoryTG Spectrum management QoS DLS Block Ack Public802.11k Radio Measurement802.11k Fast BSS Transition802.11r

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide D6.0 Allows for protection of Robust Action Frames: e.g. all categories except for Public Action Frames However: –Some of these frames are not meant to be encrypted (11y)? –Distinction of Action Frames by category can not occur until after decryption Pseudo-code in a and a.

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 7 Some issues in a pseudo-code

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide a “decryption” looks OK

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide a Broadcast treatment needs work Public Action Frames need to be excluded Public Action Frames need to be processed.

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 10 Issues with Unicast “Action” in a

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 11 Issues with Unicast “Action”

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 12 Proposal A: include unicast-only Public Action Frames Updates to P802.11w D6.0: 3.125a Robust Action Frame: A unicast Action frame or a broadcast/multicast Action frame that is not a Public Action frame last sentence would read as “The Robust Management frames are Robust Action, excluding Public Action frames, Disassociation and Deauthentication frames.” Transmit and Receive pseudo-code must be updated: –see slides 13 and 14 for receive updates – a pg. 47 line 5: else // MMPDU has a multicast broadcast RA if (IGTK exists && MMPDU is not a Public Action frame) then //if we find a suitable IGTK Transmit the MMPDU with protection // See a else if (MMPDU is Disassociate || Deauthenticate || Public Action frame) then Transmit the MMPDU without protection else Discard the MMPDU and generate an MLME.confirm primitive to notify the SME…. – a pg. 47 line 47 else // MMPDU has a multicast broadcast RA if (IGTK exists && MMPDU is not a Public Action frame) then //if we find a suitable IGTK Transmit the MMPDU with protection // See a else if (MMPDU is Disassociate || Deauthenticate || Public Action frame) then Transmit the MMPDU without protection else Discard the MMPDU and generate an MLME.confirm primitive to notify the SME….

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 13 Proposal A: Receive Pseudo-code update for Action Frames

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 14 Proposal A: Receive pseudo-code update for Broadcast

doc.: IEEE /xxxxr0 Submission Nancy Cam-Winget (Cisco) February 2006 Slide 15 Proposal B: protect both unicast and broadcast Public Action frames Updates to P802.11w D6.0: –Remove definition: 3.125a Robust Action Frame – last sentence would read as “The Robust Management frames are Robust Action, excluding Public Action frames, Disassociation and Deauthentication frames.” Updates needed independent of Proposal B: –Receive pseudo-code for unicast needs to be fixed per Slide 13 (independent of this proposal). – a pg. 47 line 9, add: else if (MMPDU is Disassociate || Deauthenticate) then Transmit the MMPDU without protection else Discard the MMPDU and generate an MLME.confirm primitive to notify the SME…. – a pg. 47 line 51, add: else if (MMPDU is Disassociate || Deauthenticate) then Transmit the MMPDU without protection else Discard the MMPDU and generate an MLME.confirm primitive to notify the SME….