111103770300aelb172clause102commentresolutions.docx

1、111103770300aelb172clause102commentresolutionsIEEE P802.11Wireless LANsLB 172 Clause 10.ae1.2 comment resolutionsDate: 2011-03-16Author(s):NameAffiliationAddressPhoneemailMichael MontemurroResearch in Motion4701 Tahoe Blvd, Mississauga, ON. Canada. L4W 0B4+1 905-629-4746mmontemurroOverviewThis docum

2、ent updates TGae 2.0 Clause 10.2 to resolved comments received from LB 172.REV HISTORY:R0 initial revisionOn receipt of this primitive, the SME evaluates the result code.Modify the changes to this sub-clause as follows:8.4.2.ae1 Management Frame QoS Policy element(11n)The Management Frame QoS Policy

3、 element defines access categories of management frames and is used to advertise and exchange management frame QoS policy between STAs. The use of the Mangament Frame QoS Policy element is given in clause 10.ae1. See Figure 8-4ae1 (Management Frame QoS Policy element format).Element IDLengthMFQ Poli

4、cy InformationAccess Category Assignment CountList of Access Category Assignment fields (optional)Octets: 11110-254Figure 8-4ae1Management Frame QoS Policy element formatThe Element ID field is equal to the Management Frame QoS Policy value in Table 8-50.The value of the length field is between 1 an

5、d 255. The MFQ Policy Information field indicates properties of the MFQ policy. See Figure 8-4ae1aB0B1 B7MFQ Policy TypeReserved Figure 8-4ae1a MFQ Policy Information Field formatThe MFQ Policy Identifier field identifies the policy advertised by the AP. The MFQ Policy Type field identifies whether

6、the MFQ Policy is partial or complete.The Access Category Assignment Count field indicates the number of Access Category Assignment field(s) included in this information element. The List of Access Category Assignment fields contains zero or more Access Category Assignment fields.(11n)The Access Cat

7、egory Assignment field specifies a group of management frames and their associated access categories. See Figure 8-4ae2 (Access Category Assignment Field format).AC Assignment HeaderCategory Value (optional)Action Value Bitmap (optional)Octets: 21VariableFigure 8-4ae2Access Category Assignment Field

8、 formatThe format of the AC Assignment Header subfield of the Access Category Assignment field is defined in Figure 8-4ae3 (AC Assignment Header subfield).B0 B1B2 B7B8B9B10 B11B12 B15Access Category Assignment Field TypeAccess Category Assignment Field Length IGACIManagement Frame Subtype Figure 8-4

9、ae3 AC Assignment Header subfieldThe Access Category Assignment Field Type subfield is 2 bits in length and defines the structure of the Access Category Assignment field. It is set to 0. Values 1, 2, and 3 are reserved.The Access Category Assignment Field Length subfield is 6 bits in length and defi

10、nes the length in octets of the Access Category Assignment field excluding the AC Assignment Header subfield.Modify these sub-clauses as follows:10.ae1.2 Management frame QoS policy advertisement and configuration proceduresManagement frame QoS policies are exchanged and implemented between two MFQ

11、STAs. The ACI classification by transmitting STA for every MFQ frame is governed by the MFQ policy obtained from the receiving STA. The MFQ policy is either advertised by the receiving STA or obtained through the exchange of an MFQ Policy frame or MFQ Policy Change frame.MFQ Policy is communicated t

12、hrough the MFQ Policy element as described in 8.4.2.ae1. A STA shall not transmit an MFQ Policy element that sets I=0 and G=0 in any of the included QACM subfields. A QMF STA shall use the default QMF policy if it has not received a QoS Policy frame from a peer QMF STA. A MFQ STA shall always apply

13、the MFQ policy received in a MFQ Policy frame.The MFQ Policy that the MLME uses following an MLME-START.request or MLME-JOIN.request shall be the default MFQ policy, until overridden by an explicit MLME-MFQPOLICYSET.request. (See 6.3.ae1.6). When dot11QMFActivated is changed, the STA shall invoke an

14、 MLME-START.request or MLME-JOIN.request.The ACI classification for any management frame can be reconfigured, for example, vendor-specific and vendor-specific protected management frames may be reconfigured to suit the vendor application requirements. There are two types of transmitted MFQ policy: t

15、he complete MFQ policy or the partial MFQ policy. Complete MFQ policy includes a transmission access category for each management frame that is not transmitted using the default MFQ policy access category defined in Table 10-ae1. Partial MFQ policy includes a transmission access category for State 1

16、 and State 2 management frames that are not transmitted using the default MFQ access categories defined in Table 10-ae1. STAs may indicate either a partial MFQ or a complete MFQ policy in Beacon frames to advertise the MFQ policy. STAs shall not indicate partial MFQ policy in a management frame that

17、 contains the MFQ Policy element and is not a Beacon frame.The MFQ Policy Type sub-field indicates whether the MFQ Policy is complete or partial. When the MFQ Polcy Type sub-field in the MFQ Policy Information field is set to 0, the MFQ Policy Element defines a complete MFQ policy. When the MFQ Poli

18、cy Type sub-field in the MFQ Policy Information field is set to 1, the non-AP STA shall interpret the MFQ Policy Element as the partial MFQ policy.10.ae1.2.1 Management frame QoS policy communication in a BSS, IBSS or MBSSThe MFQ Policy frame is sent by an MFQ STA to configure a MFQ policy at the pe

19、er MFQ STA in a BSS, IBSS, or MBSS.The MFQ Policy Change frame is sent by an MFQ STA to request a change to its MFQ Policy for the peer MFQ STA in a BSS, IBSS, or MBSS. A non-AP QMF STA operating in a BSS shall not transmit an MFQ Policy frame to an AP. A STA may send an MFQ Policy Change frame to r

20、equest a change in MFQ Policy at a peer STA. A non-AP STA that receives a MFQ Policy Change frame may either accept or reject the request.The AP shall respond to an MFQ Policy Change frame with an MFQ Policy frame. If the Reconfiguration field is set to 0 in the extended capabilities element in the

21、beacon frame, the AP that receives a MFQ Policy Change frame shall shall respond with an MFQ Policy frame, with the current MFQ Policy element and StatusCode set to 37 (“The request has been declined”). If the Reconfiguration field is set to 1 in the extended capabilities element in the beacon frame

22、, the AP that receives a MFQ Policy Change frame shall evaluate the MFQ Policy included in the frame, and shall respond to the request with the resulting MFQ Policy element and StatusCode set to 0 (“success) if it accepts the policy change, or 37 (“The request has been declined”) if it rejects the p

23、olicy change. If an accept status is received in the MFQ Policy frame within dot11MFQPolicyChangeTimeout, then both MFQ STAs shall transmit management frames to each other in accordance with the changes to the MFQ policy that were indicated in the MFQ Policy frame. If a reject status is received, th

24、en the configuration change request is rejected and both STAs continue to transmit frames according to the previously configured MFQ policy. The requesting STA shall not retry the same configuration change request within dot11MFQPolicyChangeTimeout from the time the requesting STA receives the rejec

25、tion frame.If the requesting STA does not receive a MFQ Policy frame in response to a MFQ Policy Change frame in dot11MFQPolicyChangeTimeout, then the requesting STA shall continue to transmit frames according to the previously configured MFQ policy.If an MFQ STA has received an Extended Capabilitie

26、s element with MFQReconfiguration subfield equal to 0 or has not received an Extended Capabilities element from a destination MFQ STA, the MFQ STA shall not transmit an MFQ Policy Config Request frame to the destination MFQ STA. An MFQ AP may send an MFQ Policy Config Request frame to an associated

27、MFQ STA. The associated MFQ STA may send an MFQ Policy Config Request to the MFQ AP in its BSS only if the most recently received Extended Capabilities element from the AP has its MFQReconfiguration subfield set to 1. The AP may accept or reject this request. If the AP rejects the request, the assoc

28、iated MFQ STA shall not request the same policy reconfiguration from the AP within the lifetime of its association. An MFQ AP, an MFQ STA in an MBSS, or an MFQ STA in an IBSS may set dot11MFQReconfigurationActivated to true or false. A non-AP MFQ STA in an infrastructure BSS shall set dot11MFQReconf

29、igurationActivated to true and shall set the MFQReconfiguation subfield to 1 in transmitted (re)association requests. An MFQ non-AP STA with dot11ReconfiguationActivated true shall accept any received MFQ Policy Configuration Response from its associated AP.The MFQReconfiguration bit shall be set to

30、 1 in the Extended Capabilities element when dot11MFQReconfigurationActivated is true. The MFQReconfiguration bit shall be set to 0 in the Extended Capabilities element when dot11MFQReconfigurationActivated is false.The SME of a peer MFQ STA uses the MLME-MFQPOLICY primitives (See 6.3.ae1.2 to 6.3.a

31、e1.5) to send a MFQ Policy frame to a peer STA. The SME of a peer STA uses the MLME-QMFPOLICY.request primitive to send an MFQ Policy frame to a peer STA. The SME of a peer MFQ STA shall set the Dialog Token to 0 and set the Status Code to 0 (“Successful”) when the MFQ Policy frame is sent unsolicit

32、ed to the peer STA.The SME of a peer MFQ STA uses the MLME-MFQPOLICYCHANGE primitives (See 6.3.ae1.2 to 6.3.ae1.5) to exchange the MFQ Policy Change and MFQ Policy frames. The SME of a peer STA uses the MLME-QMFPOLICYCHANGE.request primitive to send an MFQ Policy Change frame to a peer STA. The value of the dialog token in the MLME-MFQPOLICYCHANGE.request shall be set to a value in the range of 1 to 255. The SME of