A-MSDU Protection March 2007 Date: 2007-03-15 September 2006 doc.: IEEE 802.11-06/1458r0 March 2007 A-MSDU Protection Date: 2007-03-15 Notice: This document has been prepared to assist IEEE 802.11. 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 802.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, 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 <stuartk@ok-brit.com> 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 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Wingett, N., et al. Joonsuk Kim, Broadcom Corp.

March 2007 Objective This submission defines a means to allow the protection of A-MSDUs and coexistence with STAs that do not support A-MSDU protection This submission addresses CIDs 287, 302, 643, 1117, 1822, 2144, 2835, 3000, 3286 Wingett, N., et al.

Capability and Policy Signaling March 2007 Capability and Policy Signaling 7.3.2.25.3 RSN capabilities Change Figure 91 as shown below B0 B1 B2-3 B4-5 B6 B7 B8 B9 B10 B11 B12-15 Pre-Auth No Pairwise PTKSA Replay Counter GTKSA Replay Counter AES-128-CMAC Robust Management Frame protection Reserved Peerkey Enabled A-MSDU protection HT security B10: A-MSDU Protection 0 STA does not have the capability to do A-MSDU protection 1 STA does have the capability to do A-MSDU protection B11: HT Security 0: allows unprotected A-MSDU 1: discards unprotected A-MSDU Wingett, N., et al.

Construction of AAD 8.3.3.3.2 Construct AAD as follows: March 2007 Construction of AAD 8.3.3.3.2 Construct AAD as follows: g) QC – QoS Control field, if present, a 2-octet field that includes the MSDU priority. The QC TID and, when dot11AMSDUProtected is TRUE, bit 7 (A-MSDU presence) are is used in the construction of the AAD, and the . The remaining QC fields are set to 0 for the AAD calculation (bits 4 to 6 and bits 8 to 15 are set to 0). Wingett, N., et al.

A-MSDU Protection procedures March 2007 A-MSDU Protection procedures 11.18 A-MSDU Protection procedures A-MSDU protection is valid only if RSNA is selected to protect data messages and dot11AMSDUProtected is set to TRUE. A STA may discard unprotected A-MSDUs if dot11HTSecurity is set to TRUE. A STA may choose not to associate with a STA that does not advertise A-MSDU protection or HT Security in the RSN capabilities. Wingett, N., et al.

STA Behavior March 2007 STA State STA Action A-MSDU Protection = 0, HT Security = 0 May transmit unprotected A-MSDU Shall receive unprotected A-MSDU Shall discard protected A-MSDU HT Security = 1 Shall not transmit protected or unprotected A-MSDU Shall discard unprotected A-MSDU A-MSDU Protection = 1, Shall not transmit unprotected A-MSDU If peer STA is A-MSDU Protection capable then - May transmit protected A-MSDU - Shall receive protected A-MSDU - Shall discard unprotected A-MSDU If peer STA is not A-MSDU Protection capable then - Shall receive unprotected A-MSDU - Shall discard protected A-MSDU Wingett, N., et al.

March 2007 Straw Poll Do you approve of the signaling and station behavior defined in this document and in document 802.11-07/0397 as a resolution to CID’s 287, 302, 643, 1117, 1822, 2144, 2835, 3000, 3286? Yes: No: Abstain: Wingett, N., et al.

March 2007 Straw Poll Do you believe the 11N task group is ready to adopt document 802.11-07/0397 as a resolution to CID’s 287, 302, 643, 1117, 1822, 2144, 2835, 3000, 3286? Yes: No: Abstain: Wingett, N., et al.

March 2007 Motion The task group should adopt document 802.11-07/0397 as a resolution to CID’s 287, 302, 643, 1117, 1822, 2144, 2835, 3000, 3286? Yes: No: Abstain: Wingett, N., et al.